operations/docs
operations/docs
3
1
Fork 9
Code Issues 4 Pull requests Activity Actions

Update repo layout

Browse source 
We've changed a few things based on https://discussion.fedoraproject.org/t/repo-consolidation/30198/7
This commit is contained in:
Ben Cotton 2021-06-07 17:11:18 -04:00
commit 0478ec3e94
5 changed files with 18 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

9
modules/ROOT/pages/elections.adoc
View file

@ -37,15 +37,14 @@ Selected questions:
* https://pagure.io/mindshare/issue/270[Mindshare Committee - ticket #270]
////
The top 3 selected questions for each team are published in https://pagure.io/fedora-project-schedule/blob/master/f/elections/[Pagure].
The top selected questions for each body are put in teamplates in the elections-interviews repo (`ssh://git@pagure.io/tickets/fedora-pgm/elections-interviews.git`).
=== Nominations for Elected Positions
During this period you may self-nominate to open seats.
If you wish to nominate someone else, please consult with that person ahead of time.
Wiki nomination pages carry additional details about the nominee which the nominee is expected to write.
During this period people may self-nominate to open seats.
If they wish to nominate someone else, please consult with that person ahead of time.
=== Interviews
Nominees are requested to answer the selected questions using a https://pagure.io/fedora-project-schedule/issues[private issue in Pagure].
Nominees are requested to answer the selected questions using a https://pagure.io/fedora-pgm/elections-interviews/issues[private issue in Pagure].
In this way, only the Program Manager and Fedora Action and Impact Coordinator (as election wrangler substitute) are allowed to see these answers.
=== Voting Setup & Validation & Publishing of interviews

1
modules/ROOT/pages/index.adoc
View file

@ -3,7 +3,6 @@
Keep up to date with program management information on the https://communityblog.fedoraproject.org/category/program-management/[Fedora Community Blog] or by attending the weekly FPgM office hours at https://apps.fedoraproject.org/calendar/council/#m9570[0900] or https://apps.fedoraproject.org/calendar/meeting/9915/[1600] (America/Indiana/Indianapolis) Wednesdays in #fedora-meeting-1.
TIP: To report issues with schedules, file an issue in the https://pagure.io/fedora-pgm/schedule[schedule repo].
To report an issue with elections, file an issue in the https://pagure.io/fedora-project-schedule[mis-named schedule repo].
To report an issue with this document, file an issue in the https://pagure.io/fedora-pgm/pgm_docs/[pgm_docs repo].
== Fedora Program Manager

4
modules/ROOT/pages/pgm_guide/elections.adoc
View file

@ -28,9 +28,9 @@ Perhaps you would like to extend the voting app to allow nomination and election
=== During/after the nomination period
* Update the `templates/*` files in the repo (ssh://git@pagure.io/tickets/fedora-project-schedule.git) with the new questions
* Update the `templates/*` files in the repo (ssh://git@pagure.io/tickets/fedora-pgm/elections-interviews.git) with the new questions
* Edit the link:https://fedoraproject.org/wiki/Template:Election_Banner[election banner template] in the wiki to update the dates and current status
* Candidates will post interviews in private issues on the poorly-named https://pagure.io/fedora-magazine-proposals/issues[fedora-project-schedule] repo.
* Candidates will post interviews in private issues in the https://pagure.io/fedora-pgm/elections-interviews/issues[elections-interviews] repo.
* If the Community Blog post announcing nominations is set to "sticky", un-sticky it.
=== After the interview period

12
modules/ROOT/pages/pgm_guide/release_process.adoc
View file

@ -68,7 +68,7 @@ keepalive request in order to keep building the spin or lab. I have
opened Pagure issues[1] for all Spins and Labs listed on the wiki[2].
If you are the owner of one of those spins and labs, please reply in
the appropriate ticket by30 January 2019 to indicate the spin should
the appropriate ticket by 30 January 2019 to indicate the spin should
continue to be produced. If there is a spin or lab that does not have
an open ticket, please create one[3].
@ -77,9 +77,9 @@ maintained. Future improvements to the release process that will allow
for teams to self-publish solutions will eventually remove the need
for these keepalives.
[1] https://pagure.io/fedora-project-schedule/issues
[1] https://pagure.io/fedora-pgm/pgm_team/issues?status=Open&tags=spins+keepalive&close_status=
[2] https://fedoraproject.org/wiki/Releases/30/Spins
[3] https://pagure.io/fedora-project-schedule/new_issue
[3] https://pagure.io/fedora-pgm/pgm_team/new_issue
....
A couple of days before the deadline, send an email to spins and devel-announce mailing lists saying which ones will be retired.
@ -162,7 +162,7 @@ WARNING: If you run this after Branch Day, you will need to add constraint on th
* You can use this https://bugzilla.redhat.com/buglist.cgi?classification=Fedora&f1=component&f3=component&f4=bug_status&f5=component&f6=component&keywords=FutureFeature%2C%20Tracking%2C%20&keywords_type=nowords&list_id=10832664&o1=notequals&o3=notequals&o4=notequals&o5=notequals&o6=notequals&product=Fedora&product=Fedora%20Container%20Images&query_format=advanced&short_desc=RFE&short_desc_type=notregexp&v1=Package%20Review&v3=kernel&v4=CLOSED&v5=Changes%20Tracking&v6=Container%20Review&version=rawhide[Bugzilla query] to select bugs that meet the criteria above.
Save the results as a CSV file and run the https://pagure.io/fedora-project-schedule/blob/master/f/scripts/closebugs/fedora_rebase.pl[`fedora_rebase.pl` script] against it. For example:
Save the results as a CSV file and run the https://pagure.io/fedora-pgm/pgm_scripts/blob/main/f/closebugs/fedora_rebase.pl[`fedora_rebase.pl` script] against it. For example:
`fedora_rebase.pl 31 bugs-2019-08-13.csv`
@ -368,7 +368,7 @@ This {bugzilla_eol_query}[Bugzilla query] will give you the right results (just
NOTE: The EOL warning script expects 9 columns when using the version check (default).
This requires changing the default BZ columns, so use the script above.
Someday, we should change the scripts to use field names instead of mindless CSV parsing so that this becomes a non-issue.
Run the https://pagure.io/fedora-project-schedule/blob/master/f/scripts/closebugs/fedora_eol_warning.pl[`fedora_eol_warning.pl` script] against it.
Run the https://pagure.io/fedora-pgm/pgm_scripts/blob/main/f/closebugs/fedora_eol_warning.pl[`fedora_eol_warning.pl` script] against it.
For example, to warn that Fedora 29 will be EOL on 19 November 2019:
`fedora_eol_warning.pl 29 2019-11-19 bugs-2019-10-22.csv`
@ -393,7 +393,7 @@ NOTE: The EOL warning script expects 9 columns when using the version check (def
This requires changing the default BZ columns, so use the script above.
Someday, we should change the scripts to use field names instead of mindless CSV parsing so that this becomes a non-issue.
Run the https://pagure.io/fedora-project-schedule/blob/master/f/scripts/closebugs/fedora_close_eol.pl[`fedora_close_eol.pl` script] against it.
Run the https://pagure.io/fedora-pgm/pgm_scripts/blob/main/f/closebugs/fedora_close_eol.pl[`fedora_close_eol.pl` script] against it.
For example, to close Fedora 29 bugs with an EOL date of 19 November 2019:
`fedora_close_eol.pl 29 2019-11-19 bugs-2019-10-22.csv`

11
modules/ROOT/pages/pgm_team/other_repos.adoc
View file

@ -9,10 +9,11 @@ The documentation (like this page!) published to docs.fedoraproject.org.
* https://pagure.io/fedora-pgm/pgm_communication[pgm_communication].
Source files for a variety of non-docs communications.
This includes the weekly Friday's Fedora Facts on the Community Blog and scripts for the weekly FPgM office hours and Prioritized Bugs meetings.
It is also used for a few scripts that do things like handle Bugzilla housekeeping.
* https://pagure.io/fedora-pgm/change-management[change-management].
Scripts for wrangling changes.
* https://pagure.io/fedora-pgm/pgm_scripts[pgm_scripts].
Scripts for wrangling changes, doing Bugzilla housekeeping, etc.
Primarily this means parsing the wiki pages and creating new Bugzillas.
* https://pagure.io/fedora-project-schedule/[fedora-project-schedule].
It does not contain the schedule!
* https://pagure.io/fedora-pgm/schedule[schedule]
Tooling for managing the release schedule.
* https://pagure.io/fedora-pgm/elections-interviews[elections-interviews].
The issues are used for elections interviews.
This is handled by the FPgM and FCAIC, but it exists in the fedora-pgm namespace, so don't be surprised by it.