#154 Refresh README
Merged 2 years ago by salimma. Opened 2 years ago by carlwgeorge.
carlwgeorge/epel readme-refresh  into  main

file modified
+20 -7
@@ -9,10 +9,23 @@ 

  

  ## Issue Tracker

  

- EPEL issues are meant for tracking work needed on packages in the

- various EPEL repositories. Items to be reported are problems with

- packages over-riding core RHEL/CentOS packages, packages needed to be

- branched to EPEL, clarifications on policy that need to be dealt with

- in weekly meetings, and agendas of weekly meetings. Problems NOT to be

- reported are bugs in packages. These need to be filed in ​Red Hat

- Bugzilla.

+ EPEL issues are meant for tracking work needed on packages in the various EPEL

+ repositories. Items to be reported are problems with packages over-riding core

+ RHEL/CentOS packages, clarifications on policy that need to be dealt with in

+ weekly meetings, and agendas of weekly meetings. Problems NOT to be reported

+ are bugs in packages or requests to create new EPEL branches of packages. These

+ need to be filed in [Red Hat Bugzilla][bugzilla].  Release Engineering issues

+ (koji, bodhi, etc.) should be reported in the [releng issue tracker][releng].

+ Infrastructure related issues should be reported in the [fedora-infrastructure

+ issue tracker][infra].

+ 

+ ## Contributions

+ 

+ The project welcomes contributions to our documentation.  If your pull request

+ is describing a yet to be implemented change, or if you would like to iterate

+ on feedback before merging, please include the word `DRAFT` in the pull request

+ title to indicate to others that it is not ready to be merged yet.

+ 

+ [bugzilla]: https://bugzilla.redhat.com/

+ [releng]: https://pagure.io/releng/issues

+ [infra]: https://pagure.io/fedora-infrastructure/issues

  • mention contributions, including DRAFT instructions
  • send branch requests to bugzilla, not here
  • mention releng and fedora-infra issue trackers

Pull-Request has been merged by salimma

2 years ago
Metadata