From Fedora Project Wiki

(add a second bit for people who aren't packagers)
m (→‎Template 1: 1 == 2)
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== The procedure for getting a package in EPEL ==
== The procedure for getting a package in EPEL ==


If you are already a Fedora contributor, for your own package use the standard procedures for requesting a new release branch.
If you are already a Fedora contributor, for your own package use the standard procedures https://fedoraproject.org/wiki/Package_maintenance_guide for requesting a new branch using <code>fedpkg request-branch</code>.


Otherwise, if you'd like to see a Fedora package in EPEL that is not yet available, check Fedora's [https://src.fedoraproject.org/ dist-git]  or [https://bugzilla.redhat.com/bugzilla/describecomponents.cgi?product=Fedora Bugzilla]  and look up who owns the package in Fedora.  
Otherwise, if you'd like to see a Fedora package in EPEL that is not yet available, check Fedora's [ https://src.fedoraproject.org/ ]  or [https://bugzilla.redhat.com/bugzilla/describecomponents.cgi?product=Fedora Bugzilla]  and look up who owns the package in Fedora. At this point, the requestor should do the following:


If the Fedora maintainer of the package has indicated a desire not to participate in EPEL then the proposed EPEL maintainer can request the branch directly via the standard procedures. The proposed EPEL maintainer should CC the Fedora maintainer on the branch request, so the Fedora maintainer knows that the package is maintained in EPEL as well. Additionally, please note that that the Fedora maintainer is not interested in EPEL in your request.  
# Look to see if there are any existing tickets for this package to be branched into EPEL. This can help find if there are problems on why it can't be done. (this may be due to package requirements in upstream RHEL are too old, or some other dependency problem).
# Send an email to the maintainer to see if they could make a branch of the package for EPEL. They can use the email in template 1 or something similar.


If it is unclear if the Fedora maintainer of the package intends to participate in EPEL then the proposed EPEL maintainer should file a bug against the package
If the Fedora maintainer of the package has indicated a desire not to participate in EPEL, then the requestor can do one of the following:
and ask about their plans for EPEL in general and the package at hand. If there is no answer within seven days the proposed EPEL maintainer
is free to request the EPEL branch and become the EPEL Maintainer (CC the Fedora maintainer here as well).
 
If the requestor is not a Fedora packager, they should open an email using template 2 to the epel-devel@lists.fedoraproject.org list.
 
If the Fedora maintainer later decides to participate in EPEL, then the Fedora maintainer will become co-maintainer for EPEL.  (Of course co-maintainership can be extended to Fedora).


# If the requestor is a Fedora approved packager and believes they can maintain the package in EPEL, they can open a ticket in https://bugzilla.redhat.com under the package for the current maintainer to make the branch with the requestor as the maintainer of that branch.
# If the requestor is not a packager, then they should look to see if someone is available on the EPEL development list to take over the package. These packagers can then request branches through bugzilla and take over the package.


If the maintainer does not act on the bug within 2 weeks, the proposed EPEL maintainer should bring it up with the EPSCO committee to see if they can see why it is not happening or if some other process needs to be followed. [There are some packages which are always exceptions and can need extra rules to follow.]


== Templates ==
== Templates ==


You can use the following templates to contact fedora contributors who have not stated that they are not interested in EPEL.
Template 1 is to find out if a package maintainer is interested in making a branch for EPEL. Template 2 is a general template to see if someone on the epel-devel list is interested in maintaining the branch.


=== Template 1 ===
=== Template 1 ===
Line 48: Line 46:
</pre>
</pre>


=== Template 1 ===
=== Template 2 ===
<pre>
<pre>
Hi EPEL developers.
Hi EPEL developers.

Revision as of 07:21, 28 December 2019

The procedure for getting a package in EPEL

If you are already a Fedora contributor, for your own package use the standard procedures https://fedoraproject.org/wiki/Package_maintenance_guide for requesting a new branch using fedpkg request-branch.

Otherwise, if you'd like to see a Fedora package in EPEL that is not yet available, check Fedora's [ https://src.fedoraproject.org/ ] or Bugzilla and look up who owns the package in Fedora. At this point, the requestor should do the following:

  1. Look to see if there are any existing tickets for this package to be branched into EPEL. This can help find if there are problems on why it can't be done. (this may be due to package requirements in upstream RHEL are too old, or some other dependency problem).
  2. Send an email to the maintainer to see if they could make a branch of the package for EPEL. They can use the email in template 1 or something similar.

If the Fedora maintainer of the package has indicated a desire not to participate in EPEL, then the requestor can do one of the following:

  1. If the requestor is a Fedora approved packager and believes they can maintain the package in EPEL, they can open a ticket in https://bugzilla.redhat.com under the package for the current maintainer to make the branch with the requestor as the maintainer of that branch.
  2. If the requestor is not a packager, then they should look to see if someone is available on the EPEL development list to take over the package. These packagers can then request branches through bugzilla and take over the package.

If the maintainer does not act on the bug within 2 weeks, the proposed EPEL maintainer should bring it up with the EPSCO committee to see if they can see why it is not happening or if some other process needs to be followed. [There are some packages which are always exceptions and can need extra rules to follow.]

Templates

Template 1 is to find out if a package maintainer is interested in making a branch for EPEL. Template 2 is a general template to see if someone on the epel-devel list is interested in maintaining the branch.

Template 1

Hello {{ FILL IN MAINTAINER NAME }}

I am using {{ FILL IN OS }} and am using various packages in the EPEL 
repository. I am interested in seeing {{ FILL IN PACKAGE }} add to EPEL.

Would it be possible for you to maintain the package in EPEL? If not 
do you know of a maintainer who could help you with it? While EPEL 
is more conservative in package maintenance, it does allow for updates
to later versions when needed.

If you are not interested in EPEL or don't feel like you have the time
to put your packages into EPEL, the EPEL project would like to request
that a co-maintainer who is a part of EPEL be added to your packages.

The EPEL team appreciate your help with EPEL.

[1] http://fedoraproject.org/wiki/EPEL

[2] http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies

[3]  http://fedoraproject.org/wiki/EPEL/FAQ


Template 2

Hi EPEL developers.

I am using {{ FILL IN OS }} and am using various packages in the EPEL 
repository. I am interested in seeing {{ FILL IN PACKAGE }} added to EPEL. 

I have approached the current Fedora maintainer and they are not
interested in maintaining the package in EPEL. Are there any EPEL 
maintainers who are interested in doing so?

Thank you