Move the Priortized Bugs docs out of the wiki, and update for the new process.

modules/ROOT/nav.adoc

@@ -7,6 +7,7 @@
 ** xref:elections.adoc#_upcoming_elections[Upcoming elections]
 ** xref:elections.adoc#_elections_process[Elections process]
 ** xref:elections.adoc#_historical_elections[Historical elections]
+* xref:prioritized_bugs.adoc[Prioritized Bugs]
 * xref:pgm_guide/index.adoc[PgM Guide]
 ** xref:pgm_guide/changes.adoc[Changes]
 ** xref:pgm_guide/release_process.adoc[Release process]

modules/ROOT/pages/pgm_guide/prioritized_bugs.adoc

@@ -1,11 +1,8 @@
 = Prioritized Bugs
 
-The https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_and_issues_-_the_process[Prioritized Bugs] process is designed to get attention for issues that are not blockers but are still high-impact or high-visibility.
+The link:../../prioritized_bugs[Prioritized Bugs] process is designed to get attention for issues that are not blockers but are still high-impact or high-visibility.
 The criteria are intentionally subjective and we will drop bugs from the list if we can't convince developers to make progress.
 
-CAUTION: Some development teams used the *Triaged* keyword, which can mess with your Bugzilla queries.
-It may be worth changing the process to use a dedicated keyword.
-
 We run the meeting every two weeks.
 It is open to anyone, but in practice it's usually the FPgM and FPL who attend.
 Send the nominated and open accepted bugs a day in advance to the triage (and optionally test and devel) mailing list.
@@ -18,8 +15,4 @@ TIP: Editing the wiki by hand (despite the fact that it claims to be automated)
 Perhaps you can fork the Blocker Bugs code and use that to generate the list.
 Or perhaps you can write script that generates a static page.
 
-NOTE: The https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_and_issues_-_the_process[wiki page] refers to *PM Score* and *PgM Internal* fields.
-These are a lie.
-Don't bother with them.
-
 TIP: If you keep the https://pagure.io/fedora-pgm/pgm_communication/blob/master/f/prioritized_bugs.txt[IRC script] in the `pgm_communication` repo up-to-date, it will make it easier to prepare an agenda and keep status from meeting-to-meeting.

modules/ROOT/pages/prioritized_bugs.adoc

@@ -0,0 +1,50 @@
+= Prioritized Bugs
+
+The purpose of this process is to help with processing backlog of bugs and issues found during the development, verification, and use of Fedora distribution.
+The main goal is to raise visibility of bugs and issues to help contributors focus on the most important issues.
+The general criterion for such bugs is "failure to resolve this bug will result in unpleasantness for a subjectively large subset of users".
+
+== Process description
+
+All the bugs and issues in the Fedora distribution are tracked in https://bugzilla.redhat.com/[Bugzilla].
+As such, every item on the "Prioritized bugs and issues" list has assigned a bug ID and can be tracked using standard Bugzilla tools.
+
+The process consists of three main parts:
+
+* Nomination
+* Evaluation
+* Ageing
+
+NOTE: Prior to November 2019, bugs were tracked using the _Keywords_ and _Whiteboard_ fields in Bugzilla.
+This occasionally lead to collisions with how development teams used those fields, so we switched to using a specific flag.
+
+=== Nomination
+
+Issues eligible for this status are those which do not necessarily fail a release criterion but which have critical impact on a Fedora Edition or on a council-approved Fedora Objective.
+Issues may also be nominated from the Common Bugs list when they are deemed by QA to have critical impact.
+
+Anyone from the Fedora community can nominate a bug to be evaluated for inclusion to the "Prioritized bugs and issues" list.
+The nomination is done by setting the `fedora_prioritized_bug` flag to `?`.
+
+The list of currently nominated bugs waiting for evaluation can be seen using the link:++https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&f1=flagtypes.name&f2=OP&list_id=10626345&o1=substring&product=Fedora&query_format=advanced&v1=fedora_prioritized_bug%3F++[Bugzilla search tool].
+
+=== Evaluation
+
+Evaluation of nominated bugs is done by the Evaluation team.
+This team is comprised of the https://docs.fedoraproject.org/en-US/council/fpl/[Fedora Project Leader], https://docs.fedoraproject.org/en-US/council/fpgm/[Fedora Program Manager], and people representing Fedora Working Groups and Special Interest Groups, as well as interested community members.
+The team does not have fixed group of members.
+Instead members of the Evaluation team are formed at the beginning of the meeting during Roll Call.
+
+The team of evaluators meets on regular bi-weekly meetings on Wednesdays at 11:00 AM US/Eastern in the #fedora-meeting Freenode channel.
+See https://apps.fedoraproject.org/calendar/base/[Base Fedocal] for the authoritative meeting schedule.
+The purpose of the regular meeting is to review bugs nominated to the "Prioritized bugs and issues" list and follow up on previously-approved bugs.
+
+All the bugs reviewed during the Evaluation meeting are marked by setting the `fedora_prioritized_bug` flag to `+`.
+After the evaluation meeting, the chair exports the list of all Prioritized bugs to the "Prioritized bugs and issues" list and sends a report to the https://lists.fedoraproject.org/archives/list/triage%40lists.fedoraproject.org/[Triage mailing list].
+
+The list of currently approved bugs, can be seen using the link:++https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&f1=flagtypes.name&f2=OP&list_id=10626381&o1=substring&product=Fedora&query_format=advanced&v1=fedora_prioritized_bug%2B++[Bugzilla search tool].
+
+=== Ageing
+
+Bugs that are accepted as Priortized Bugs are re-evaluated on a regular basis.
+If the evaluation team determines after working with the maintainers that a resolution is not possible, the team may decide to remove Prioritized Bug status.