epel/docs
8
0
Fork 3
Code Pull requests 4 Projects Activity

Issue tracker migration changes

Browse source 
Signed-off-by: Diego Herrera <dherrera@redhat.com>
This commit is contained in:
Diego Herrera 2026-02-16 16:16:58 -03:00
commit 8d8b2a39d5
5 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

4
modules/ROOT/pages/epel-packagers-sig.adoc
View file

@ -90,7 +90,7 @@ have been packaging with Fedora and/or EPEL for at least a year.
The procedure is similar to that
for xref:fesco::Provenpackager_policy.adoc#_becoming_provenpackager[provenpackagers].
* File a ticket in the link:++https://pagure.io/epel/issues++[EPEL issue tracker] indicating why you wish to
* File a ticket in the link:++https://forge.fedoraproject.org/epel/steering++[EPEL issue tracker] indicating why you wish to
become a member.
* A link:++https://accounts.fedoraproject.org/group/epel-packagers-sig/++[Packagers SIG Sponsor] will send an e-mail to the SIG members, so they
are aware about the ticket.
@ -103,7 +103,7 @@ If you haven’t been approved after one week, the EPEL Steering Committee will
=== Get to work
* Look through link:++https://pagure.io/epel/issues++[the general EPEL issues] related to packaging and see where you can help.
* Look through link:++https://forge.fedoraproject.org/epel/steering++[the general EPEL issues] related to packaging and see where you can help.
* Look through link:++https://bugzilla.redhat.com/show_bug.cgi?id=EPELPackagersSIG++[the EPEL Packagers SIG bug tracker], see if there are any you want to help with.
* Look through link:++https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&f1=days_elapsed&list_id=11600601&o1=greaterthan&product=Fedora&product=Fedora%20EPEL&query_format=advanced&short_desc=epel&short_desc_type=allwordssubstr&v1=14++[old epel bugs]. Many of them are requesting packages. See if there are any you think should be added to the EPEL Packagers Sig tracker.
* Look at link:++https://packager-dashboard.fedoraproject.org/dashboard?groups=epel-packagers-sig++[the EPEL Packagers SIG dashboard] to see if there is anything there you can do.

2
modules/ROOT/pages/epel-packaging.adoc
View file

@ -33,7 +33,7 @@ This does not mean that EPEL packages should incorrectly identify
a dependency as weak (e.g. changing a Requires to a Recommends).
On a case by case basis, exceptions to this policy may be granted
by the EPEL Steering Committee.
To request an exception link:++https://pagure.io/epel/issues++[open an issue]
To request an exception link:++https://forge.fedoraproject.org/epel/steering++[open an issue]
and add the "meeting" tag.
[[eln]]

2
modules/ROOT/pages/epel-policy-incompatible-upgrades.adoc
View file

@ -27,7 +27,7 @@ xref:epel-communication.adoc[Bugzilla] against the
package.
. In the case of a critical CVE the maintainer *MAY* build the package
and submit it to bodhi for testing. 'Auto-request stable?' *MUST NOT* be checked.
. File an link:++https://pagure.io/epel/issues++[EPEL issue]. This can be done while
. File an link:++https://forge.fedoraproject.org/epel/steering++[EPEL issue]. This can be done while
discussion is ongoing; please link to the thread in the mailing list archive so the EPEL
Steering Committee can monitor the discussion and know when it is ready to be discussed.
. After a week of mailing list discussion, an EPEL Steering Committee member will add the

2
modules/ROOT/pages/epel-policy-steering-committee.adoc
View file

@ -80,7 +80,7 @@ The meeting is public and everyone is invited.
=== Committee meeting voting
The EPEL Steering Committee tracks ongoing decisions using the
link:++https://pagure.io/epel/issues++[EPEL ticketing system].
link:++https://forge.fedoraproject.org/epel/steering++[EPEL ticketing system].
Decisions are voted on at the weekly Steering Committee meeting.
These decisions usually fall into one of these categories:

6
old.docs/source/EPEL-meeting-process.rst
View file

@ -13,7 +13,7 @@ On Tuesday before the Wednesday meeting, do the following tasks:
1. First, check the trac "All Active Tickets" report:
https://pagure.io/epel/issues
https://forge.fedoraproject.org/epel/steering
2. For each ticket, make sure to check with and invite stakeholders
who may not be CC'd in the ticket. Consider deferring issue if
@ -39,7 +39,7 @@ or run:
date -d '{{#time:Y-m-d|wednesday}} 18:00 UTC'
Links to all tickets below can be found at:
https://pagure.io/epel/issues
https://forge.fedoraproject.org/epel/steering
AGENDA
@ -60,7 +60,7 @@ AGENDA
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://pagure.io/epel,
this e-mail, file a new ticket at https://forge.fedoraproject.org/epel/steering,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.