The future of Fedora-tagger

[Pierre-Yves Chibon]

Good Morning everyone,

Some of the folks in the Fedora infrastructure team met up just before
devconf.cz in January and went quickly through "the state of apps".
One app that appears to be currently broken is fedora-tagger [1].
Basically it is still listening for new packages being added to pkgdb, which
means it's outdated for all packages since pkgdb has been deprecated.

From the Fedora Infrastructure's perspective, we don't want to invest time to
maintain this app. We have other tasks that we want to prioritize.
However, the app itself is still running quite fine and is low maintenance.
So if some people were interested in keeping it alive we can make it happen.
But we're not the ones who are going to do it.

Fedora-tagger does have some interest, especially to new comers.
So we would like to know if commops would be interested taking over this
project.

If there is sufficient interest and will, we will transfer fedora-tagger and
help getting keeping it running.
Otherwise we will deprecate it.

The current idea would be to deprecate this service at the infra FAD. Which
means we need an answer at the latest next week (say Thursday March 29th) so
that if we deprecate it we have time to announce it more broadly.


Thanks for reading all the way through here and looking forward your feedbacks,

Pierre
- For the Fedora Infrastructure Team


[1] https://apps.fedoraproject.org/tagger/
    https://github.com/fedora-infra/fedora-tagger

[Brian Exelbierd]

On Wed, Mar 21, 2018, at 6:35 PM, Pierre-Yves Chibon wrote:
>  Good Morning everyone,
>  
>  Some of the folks in the Fedora infrastructure team met up just before
>  devconf.cz in January and went quickly through "the state of apps".
>  One app that appears to be currently broken is fedora-tagger [1].
>  Basically it is still listening for new packages being added to pkgdb, which
>  means it's outdated for all packages since pkgdb has been deprecated. 
Where, other than tagger, is this data used?

>  From the Fedora Infrastructure's perspective, we don't want
> to invest time to
>  maintain this app. We have other tasks that we want to prioritize.
>  However, the app itself is still running quite fine and is low maintenance.
>  So if some people were interested in keeping it alive we can make it happen.
>  But we're not the ones who are going to do it. 
Are you all commiting to getting the project into functional shape, or just transferring
it in the broken state?

regards,

bex

> 
> Fedora-tagger does have some interest, especially to new comers.
> So we would like to know if commops would be interested taking over this
> project.
> 
> If there is sufficient interest and will, we will transfer fedora-tagger and
> help getting keeping it running.
> Otherwise we will deprecate it.
> 
> The current idea would be to deprecate this service at the infra FAD. Which
> means we need an answer at the latest next week (say Thursday March 29th) so
> that if we deprecate it we have time to announce it more broadly.
> 
> 
> Thanks for reading all the way through here and looking forward your feedbacks,
> 
> Pierre
> - For the Fedora Infrastructure Team
> 
> 
> [1] https://apps.fedoraproject.org/tagger/
>     https://github.com/fedora-infra/fedora-tagger
> 
> _______________________________________________
> Fedora Community Operations (CommOps) mailing list -- 
> commops(a)lists.fedoraproject.org
> To unsubscribe send an email to commops-leave(a)lists.fedoraproject.org
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

[Pierre-Yves Chibon]

On Wed, Mar 21, 2018 at 06:39:17PM +0100, Brian Exelbierd wrote:
>  
>  
>  On Wed, Mar 21, 2018, at 6:35 PM, Pierre-Yves Chibon wrote:
>  > Good Morning everyone,
>  > 
>  > Some of the folks in the Fedora infrastructure team met up just before
>  > devconf.cz in January and went quickly through "the state of apps".
>  > One app that appears to be currently broken is fedora-tagger [1].
>  > Basically it is still listening for new packages being added to pkgdb, which
>  > means it's outdated for all packages since pkgdb has been deprecated.
>  
>  Where, other than tagger, is this data used? 
I believe fedora-packages uses it but it would be easy to carve out.

>  > From the Fedora Infrastructure's perspective, we don't
> want to invest time to
>  > maintain this app. We have other tasks that we want to prioritize.
>  > However, the app itself is still running quite fine and is low maintenance.
>  > So if some people were interested in keeping it alive we can make it happen.
>  > But we're not the ones who are going to do it.
>  
>  Are you all commiting to getting the project into functional shape, or just transferring
> it in the broken state? 
We're transferring it as is and offering support to get it fixed. We're not
going to fix it so if no one else is interested in fixing it, we'll deprecate
it.


Pierre

[Alberto Rodriguez Sanchez]

Hi pingou,

let us open a little discussion about this:

https://pagure.io/fedora-commops/issue/149

maybe we can give you a clear answer soon

regards

On Thu, 2018-03-22 at 08:53 +0100, Pierre-Yves Chibon wrote:
> On Wed, Mar 21, 2018 at 06:39:17PM +0100, Brian Exelbierd wrote:
> > 
> > 
> > On Wed, Mar 21, 2018, at 6:35 PM, Pierre-Yves Chibon wrote:
> > > Good Morning everyone,
> > > 
> > > Some of the folks in the Fedora infrastructure team met up just
> > > before
> > > devconf.cz in January and went quickly through "the state of
> > > apps".
> > > One app that appears to be currently broken is fedora-tagger [1].
> > > Basically it is still listening for new packages being added to
> > > pkgdb, which
> > > means it's outdated for all packages since pkgdb has been
> > > deprecated.
> > 
> > Where, other than tagger, is this data used?
> 
> I believe fedora-packages uses it but it would be easy to carve out.
> 
> > > From the Fedora Infrastructure's perspective, we don't want to
> > > invest time to
> > > maintain this app. We have other tasks that we want to
> > > prioritize.
> > > However, the app itself is still running quite fine and is low
> > > maintenance.
> > > So if some people were interested in keeping it alive we can make
> > > it happen.
> > > But we're not the ones who are going to do it.
> > 
> > Are you all commiting to getting the project into functional shape,
> > or just transferring it in the broken state?
> 
> We're transferring it as is and offering support to get it fixed.
> We're not
> going to fix it so if no one else is interested in fixing it, we'll
> deprecate
> it.
> 
> 
> Pierre
> _______________________________________________
> Fedora Community Operations (CommOps) mailing list -- commops(a)lists.f
> edoraproject.org
> To unsubscribe send an email to commops-leave(a)lists.fedoraproject.org

[Pierre-Yves Chibon]

On Wed, Mar 28, 2018 at 07:04:16AM -0600, Alberto Rodriguez Sanchez wrote:
>  Hi pingou,
>  
>  let us open a little discussion about this:
>  
>  https://pagure.io/fedora-commops/issue/149
>  
>  maybe we can give you a clear answer soon 
As per the original email, I'd need an answer by tomorrow (say 16:00 UTC) so we
can plan/announce the retirement if it's the way it goes.


Pierre