Re: ELN SIG First Meeting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Mar 15, 2021 at 09:10:52AM -0400, Stephen John Smoogen wrote:
> On Sun, 14 Mar 2021 at 16:42, Kevin Fenzi <kevin@xxxxxxxxx> wrote:
> 
> > On Sat, Mar 13, 2021 at 05:09:44PM -0800, Troy Dawson wrote:
> >
> > I'm not sure this is all a super big deal, but I'd really like to make
> > sure we make _very_ clear who is responsible for what. Some maintainers
> > would be happy to maintain for that long cycle (from landing in
> > eln-extra now, to epel 10 next, to epel10... thats what... 13 years?),
> > but some may not, and some might be happy for part of it but not the
> > entire thing.
> >
> >
> I thought we made a change 3-4 years ago. We stopped saying a maintainer
> has to maintain for 10 years. Packages in EPEL are from volunteers and
> volunteers come and go. Volunteers have different ideas of what they want
> to support at different times. In the same way that EPEL has no set of
> packages that is 'EPEL', it also can have no timeline for how long a
> package is going to be in the repository. If a maintainer decides they are
> done, and no one wants to take over the package.. it and everything that
> requires it can go.
> [The reason being that the half-life of a volunteer in Fedora is about 3
> years and we had a lot of dead packages where people thought they were
> being maintained, the maintainer was burnt out and not responding until we
> asked and they said 'they had stopped caring years ago.'.]

Yes, absolutely. I agree that volenteers can and should maintain what
they wish for as long as they wish to do it.

Thats not the part I'm worried about. It's when other groups or people
are maintaining a package. How involved should the Fedora maintainer be?

IMHO they should be as involved as they wish to be, which would range
from: No, I don't want to have anything to do with eln-epel to I
would prefer to maintain it myself. 

But I guess the promise here is just like eln: 
No branches, no changes, Fedora maintainer has control of their rawhide
spec to accept/reject changes to fix eln-epel things?

If ELN sig is willing to do all that more work I suppose we could try
it. Ideally it would be nice to get FMN fixed first, but oh well.

kevin

Attachment: signature.asc
Description: PGP signature

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux