RFC: EPEL branching if Fedora maintainer does not react
rob.myers at gtri.gatech.edu
Mon Jul 16 19:03:32 UTC 2007
On Sun, 2007-07-08 at 19:46 +0530, Rahul Sundaram wrote:
> Thorsten Leemhuis wrote:
> > If the Fedora maintainer within less then 1 month wants to participate
> > in EPEL, then the EPEL maintainer of the package must hand primary per
> > release maintainership back to the Fedora maintainer (and become
> > comaintainer, if interested), if he's interested. If the Fedora
> > maintainer at a later point in time wants to participate in EPEL and get
> > his package back then the EPEL maintainer should strongly consider doing
> > so, but doesn't has to.
> > How does this sound?
> Good but I would remove the gender specific language.
how does this look?
If an EPEL maintainer wants to get a Fedora package into EPEL,
first check the ContributorStatus document, located in the wiki at
If the Fedora maintainer of the package has indicated a desire not to
participate in EPEL then the EPEL maintainer can request the branch
directly via the standard procedures (e.g. via bugzilla currently). The
EPEL maintainer should CC the Fedora maintainer on the branch request,
so the Fedora maintainer knows that the package is maintained in EPEL as
If it is unclear if the Fedora maintainer of the package participates in
EPEL then the EPEL maintainer should mail the Fedora maintainer and ask
about their plans for EPEL in general and the package at hand. If there
is no answer within seven days the EPEL maintainer is free to request
the EPEL branch (CC the Fedora maintainer here as well).
If the Fedora maintainer later decides to participate in EPEL, and no
more than one month has passed, then the EPEL maintainer of the package
must hand primary per release maintainership back to the Fedora
maintainer (and become comaintainer, if interested). If the Fedora
maintainer later decides to participate in EPEL, and more than one month
has passed, the EPEL maintainer of the package should strongly consider
returning maintainership, but does not have to.
More information about the epel-devel-list