Bug 1189920

Summary: python-zbase32 in EPEL
Product: [Fedora] Fedora Reporter: Vladimir Stackov <amigo.elite>
Component: python-zbase32Assignee: Christopher Meng <i>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: i
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-24 11:24:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vladimir Stackov 2015-02-05 20:05:52 UTC
Greetings,

I would like to see python-zbase32 in in Extra Packages for Enterprise Linux
(EPEL) [1] and opening this bug as you didn't yet let the EPEL team
know via the Contributor Status [2] page if you are planning to build
this package in EPEL.

Are you interested in maintaining your packages in EPEL? EPEL is an add-on
repo for RHEL and compatible spinoffs such as CentOS. EPEL uses the same
CVS and the same build servers as Fedora and a lot of Fedora maintainers
are EPEL maintainers as well; the main difference is just that packages
in EPEL are updated more carefully and supported for a longer timeframe.
See [3] and [4]  for details. In short: EPEL tries to ship a package once
and update it to later versions only when there is a strong need to.

For branching your packages for EPEL follow the standard Fedora
procedure [5] -- instead of F20 or F21 targets just use EL6 and EPEL7 as
branch names.

If you are not interested in EPEL please let the EPEL contributors know
and update the information on [2] to avoid further reports like this --
that just takes a minute or two and would be a great help for the EPEL
team. Please note that EPEL maintainers that might want to see your
package in EPEL will likely start to maintain the package in EPEL sooner
or later and thus become co-maintainers [6] of your packages for EPEL.

I appreciate your help with EPEL.

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

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

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

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

[5] http://fedoraproject.org/wiki/PackageMaintainers/CVSAdminProcedure

[6] http://fedoraproject.org/wiki/Extras/Policy/EncourageComaintainership

Comment 1 Christopher Meng 2015-02-24 11:24:26 UTC

*** This bug has been marked as a duplicate of bug 1190308 ***