council/docs
council/docs
12
1
Fork 5
Code Issues 6 Pull requests 2 Projects Activity Actions

Update most Pagure links to Forge (#287)

Browse source 
Notable exceptions:
- CoC doesn't have any public Forge repos
- fedora-badges doesn't exist on Forge

Reviewed-on: #287
Reviewed-by: Petr Bokoč <pbokoc@noreply.forge.fedoraproject.org>
This commit is contained in:
Michael Winters 2026-05-21 16:46:53 +00:00 • committed by Petr Bokoč
commit 1ce607e7a2
13 changed files with 41 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

2
council/modules/ROOT/pages/archive/index.adoc
View file

@ -9,5 +9,5 @@ Sometimes, there are policy or procedure documents that have significance for re
This section is for those, so they can be found in one place rather than scattered everywhere, and so they aren't accidentally lost forever in some future infrastructure transition.
We don't want to keep _everything_, and even of text worth preserving, this isn't necessarily the place.
But if you find something that you think is relevant to Fedora's guiding policies, overall governance, or similar, please submit as a pull request to the https://pagure.io/Fedora-Council/council-docs[{team_name} Docs].
But if you find something that you think is relevant to Fedora's guiding policies, overall governance, or similar, please submit as a pull request to the {url_docs_repo}[{team_name} Docs].
Thank you!

4
council/modules/ROOT/pages/index.adoc
View file

@ -164,7 +164,7 @@ One specific responsibility is to represent the voice of individual contributors
Each representative will also work on specific goals which they bring to the {team_name} as highlighted during the election process.
Elections are held once per year, in concert with the joint Fedora election cycle.
Two seats are selected at the even-numbered release election, e.g F40, F42, etc, and each position has a two-election (approximately one year) term. This change came into effect from the F40 election, following a council vote on [https://pagure.io/Fedora-Council/tickets/issue/470 this ticket] at the 2024 council hackfest.
Two seats are selected at the even-numbered release election, e.g F40, F42, etc, and each position has a two-election (approximately one year) term. This change came into effect from the F40 election, following a council vote on https://forge.fedoraproject.org/council/tickets/issues/470[this ticket] at the 2024 council hackfest.
No person who currently holds another {team_name} seat can be elected.
If a seat becomes vacant, the {team_name} will arrange for a temporary replacement.
@ -263,7 +263,7 @@ Former membership on the {team_name}, along with membership on the previous Fedo
== Document History
This charter was approved by the Fedora Project Board on https://fedorahosted.org/council/ticket/13[Oct. 9th, 2014] and is in effect as of Nov. 26th, 2014.
Any other significant changes will be noted here; smaller changes (minor wording or formatting, etc., without impact on meaning) can be found in the https://pagure.io/Fedora-Council/council-docs/commits/main[git repository] for {team_name} documents.
Any other significant changes will be noted here; smaller changes (minor wording or formatting, etc., without impact on meaning) can be found in the {url_docs_repo}[git repository] for {team_name} documents.
. *2014-11-26*: Initial approval by the Fedora Project Board (link:{team_issue_tracker}/issue/13[ticket]).
. *2017-04-05*: Switched “Outreach” to Mindshare (link:{team_issue_tracker}/issue/102[ticket]).

2
council/modules/ROOT/pages/policy/event-location-policy.adoc
View file

@ -110,4 +110,4 @@ Examples:
* https://pagure.io/fedora-diversity/issue/98[Diversity decision making process]
* https://discussion.fedoraproject.org/t/flock-location-and-dei-policy/102686[Initial policy discussion]
* https://gitlab.com/fedora/dei/home/-/issues/34[Initial policy proposal tracker]
* https://forge.fedoraproject.org/dei/tickets/issues/34[Initial policy proposal tracker]

16
council/modules/ROOT/pages/procedures/survey/how-to.adoc
View file

@ -1,16 +1,16 @@
include::ROOT:partial$attributes.adoc[]
= How to run the Fedora Annual Contributor Survey
= How to run the Fedora Annual Contributor Survey
[[schedule]]
== Survey Schedule
* **Apr 1st**:
Open link:{team_issue_tracker}/new_issue[{team_name} ticket] to track progress and collect feedback
Open {team_issue_tracker}[{team_name} ticket] to track progress and collect feedback
* **Apr 1st**:
Open https://pagure.io/fedora-badges/new_issue[Badges ticket] to request badge design & publication
Open {url_badges_issues}[Badges ticket] to request badge design & publication
* **April 1st**:
Open https://pagure.io/design/new_issue[Design ticket] to request banner design
Open {url_design_issues}[Design ticket] to request banner design
* **May 1st**:
Open https://docs.fedoraproject.org/en-US/websites/[Websites and Apps Team ticket] to request banner published on Fedora sites
* **May 15-24th**:
@ -42,7 +42,7 @@ include::ROOT:partial$attributes.adoc[]
=== Fedora Badges
Each year we generate a https://badges.fedoraproject.org/[Fedora Badge] that survey recipients can claim when they submit their survey responses.
A ticket needs to be opened on the https://pagure.io/fedora-badges/issues[Badges repo] requesting the badge.
A ticket needs to be opened on the {url_badges_issues}[Badges repo] requesting the badge.
The panda graphic stays the same, and the year is updated accordingly.
*This ticket should be opened by April 1st* in order to give the Badges team enough time to generate the artwork, push the badge to the website, and provide a claim link to the Survey team.
@ -71,10 +71,10 @@ The promotional blog post should then be pinned on Discussion.fpo for the month
To help ensure we reach the maximum number of Fedora contributors, we promote the survey across as many Fedora spaces as possible including our websites.
This work is done with the assistance of the link:{url_wiki}/Design[Design Team] and the xref:websites::index.adoc[Websites & Apps Team].
The first step is to open a ticket on the https://pagure.io/design/issues[Design Team pagure] to get any updates on artwork.
The first step is to open a ticket on the {url_design_issues}[Design Team issue tracker] to get any updates on artwork.
*This ticket should be opened by April 1st, and closed by May 1st.*
If there are no changes from the Design Team, proceed with the previous design.
Once the artwork is finalized, a ticket is opened on the https://pagure.io/fedora-websites/issues[Websites & Apps Team] repo to get it published.
Once the artwork is finalized, a ticket is opened on the https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/work_items[Websites & Apps Team] repo to get it published.
*This ticket should be opened by May 1st* and needs continuous check-ins.
The websites that we aim to cover are:
@ -92,7 +92,7 @@ A short email should be sent with a link to the Community Blog post as well as a
* https://lists.fedoraproject.org/admin/lists/mindshare@lists.fedoraproject.org/[Mindshare]
* https://lists.fedoraproject.org/admin/lists/devel-announce.lists.fedoraproject.org/[Devel-announce]
* https://lists.fedoraproject.org/admin/lists/diversity.lists.fedoraproject.org/[DEI]
* https://lists.fedoraproject.org/admin/lists/diversity.lists.fedoraproject.org/[DEI]
[[promotion--irc-twitter]]
=== IRC & Twitter

10
council/modules/ROOT/pages/procedures/survey/questions.adoc
View file

@ -16,7 +16,7 @@ This survey is being ran by the {team_name} to better understand our Fedora Cont
Who gets to see the raw data::
{team_name} members and LimeSurvey moderator.
Who gets to see the summary data::
Public.
@ -112,7 +112,7 @@ Changelog::
** I don't follow Fedora news
** Other
* How comfortable do you feel speaking up about your ideas/opinions/theories or asking questions in Fedora spaces? (chat platforms, pagure, discussion)
* How comfortable do you feel speaking up about your ideas/opinions/theories or asking questions in Fedora spaces? (chat platforms, forge, discussion)
** Completely comfortable
** Somewhat comfortable
** Neutral
@ -150,7 +150,7 @@ Changelog::
** riscv
** i686
** I don't know
* Do you use Fedora Modules? [S]
** Yes
** I tried, but then disabled them
@ -323,7 +323,7 @@ Do you use Fedora to write code?
** GitHub
** GitLab
** Gitea
** Pagure
** Fedora Forge
** SourceForge
** Sourcehut
** I don't use forge systems
@ -392,7 +392,7 @@ Do you use Fedora to write code?
** Other
* How accessible do you find Fedora resources to be?
(such as docs, wiki pages, pagure repo, IRC/chatroom)
(such as docs, wiki pages, forge repo, IRC/chatroom)
** Rating 1 (not accessible) - 5 (easily accessible)
* How satisfied are you with community outreach within and outside of the Fedora Project?

10
council/modules/ROOT/pages/procedures/team_directory.adoc
View file

@ -26,7 +26,7 @@ However, presence in the directory may be used by other teams to evaluate fundin
[[content]]
== Content
Teams should list the following information in the format specified by the https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[template]:
Teams should list the following information in the format specified by the {url_team_template}[template]:
* Team name
* Team summary
@ -44,7 +44,7 @@ It is expected that not all teams will have answers for the above.
They should be provided when they exist.
====
Content may be stored in the https://pagure.io/Fedora-Council/council-docs[council-docs] repo if the team does not have its own docs repo.
Content may be stored in the {url_docs_repo}[council-docs] repo if the team does not have its own docs repo.
If a team has its own docs repo, the content can be kept in that repo so that it can be used to render the team's own documentation.
This allows for a single source of truth and prevents content from diverging.
@ -68,13 +68,13 @@ Checks can be done at any time, but should be done around the branch date for ea
The directory requires a file that contains the information about the team.
The suggested naming convention is `NAME_team_info.adoc`, but any valid file name is acceptable.
The file may be stored in the team's own documentation repository or in the https://pagure.io/Fedora-Council/council-docs/[council-docs repository].
See the https://pagure.io/Fedora-Council/council-docs/blob/main/f/engineering/modules/ROOT/partials/TEMPLATE_team_info.adoc[example template] for format and structure.
The file may be stored in the team's own documentation repository or in the {url_docs_repo}[council-docs repository].
See the {url_team_template}[example template] for format and structure.
[[mechanism-rendering]]
=== Rendering the directory
Teams will appear in the directory if the team info file is included in the `{engineering,mindshare}/modules/ROOT/pages/index.adoc` directory of the https://pagure.io/Fedora-Council/council-docs/[council-docs repo].
Teams will appear in the directory if the team info file is included in the `{engineering,mindshare}/modules/ROOT/pages/index.adoc` directory of the {url_docs_repo}[council-docs repo].
After `include`-ing the info file, the index page must include the `team_render.adoc` file that defines the rendering.
[[mechanism--reusing-data]]

4
council/modules/ROOT/pages/procedures/welcome.adoc
View file

@ -43,7 +43,7 @@ If there is something {team_name}-related that you do not have access to, open a
[[communication]]
== Communication
The {team_name} is working on improving some of our communication methods. We are tracking this work in [https://pagure.io/Fedora-Council/tickets/issue/536 ticekt #536] and will update our docs page with a new process once complete.
The {team_name} is working on improving some of our communication methods. We are tracking this work in link:https://forge.fedoraproject.org/council/tickets/issues/536[ticket #536] and will update our docs page with a new process once complete.
In the meantime, we try to have asynchronous conversations in the link:{team_asynch_communication}[#council tag] on Fedora Discussion.
This is a public forum, so we expect—and welcome—input from community members who are not on {team_name}.
On the rare occasions when we need to discuss confidential matters, we have a private mailing list.
@ -55,7 +55,7 @@ For very time sensitive or urgent confidential matters, we might use our private
[[meetings]]
== Meetings
The {team_name} holds bi-weekly business meetings on #meeting:fedoraproject.org on Wednesdays. The Fedora Operations Architect creates an agenda in advance of this meeting in our [https://fedoraproject.org/wiki/Council_Meetings meetings wiki page] and posts it to discussion.fedoraproject.org under the '#council' tag in Project Discussion. Minutes are posted as a reply to this post once the meeting concludes.
The {team_name} holds bi-weekly business meetings on #meeting:fedoraproject.org on Wednesdays. The Fedora Operations Architect creates an agenda in advance of this meeting in our link:https://fedoraproject.org/wiki/Council_Meetings[meetings wiki page] and posts it to discussion.fedoraproject.org under the '#council' tag in Project Discussion. Minutes are posted as a reply to this post once the meeting concludes.
These are an opportunity to check on the progress of tasks and have conversations about open issues.
Attendance is not mandatory, but we encourage you to attend and participate as often as you can.
Business meetings are open to the community at large.

8
council/modules/ROOT/partials/attributes.adoc
View file

@ -22,8 +22,8 @@
:team_synch_communication_name: Fedora Chat/Matrix
// Issue tracker
:team_issue_tracker: https://pagure.io/Fedora-Council/tickets
:team_issue_tracker_name: Pagure
:team_issue_tracker: https://forge.fedoraproject.org/council/tickets
:team_issue_tracker_name: Forge
// Meetings
:team_meetings: https://calendar.fedoraproject.org/council/
@ -36,3 +36,7 @@
// Common URLs
:url_commblog: https://communityblog.fedoraproject.org
:url_wiki: https://fedoraproject.org/wiki
:url_docs_repo: https://forge.fedoraproject.org/council/docs
:url_badges_issues: https://pagure.io/fedora-badges/issues
:url_design_issues: https://forge.fedoraproject.org/design/tickets
:url_team_template: https://forge.fedoraproject.org/council/docs/raw/branch/main/project/modules/ROOT/partials/TEMPLATE_team_info.adoc

8
project/modules/ROOT/pages/communications.adoc
View file

@ -1,3 +1,5 @@
include::ROOT:partial$attributes.adoc[]
= Communication in Fedora
As referenced on the xref:join.adoc[Get Involved] page below, Fedora is a massive global organisation with many people with different skills carrying out different roles.
@ -8,8 +10,8 @@ This current page goes into more detail around the various communication channel
=== Chat
Fedora officially uses Matrix as the primary synchronous channel to speak to each other in real-time.
Fedora's homeserver is link:https://chat.fedoraproject.org/[] and you can use your Fedora Account System (FAS) account to connect.
Fedora officially uses Matrix as the primary synchronous channel to speak to each other in real-time.
Fedora's homeserver is link:https://chat.fedoraproject.org/[] and you can use your Fedora Account System (FAS) account to connect.
If you are already on Matrix and use a different homeserver, use link:https://matrix.to/#/#fedora:fedoraproject.org[] to join Fedora Chat.
If you have an account hosted on the `chat.fedoraproject.org` (or `fedora.im`) homeserver, you can find information on how to remove your account xref:legal::privacy.adoc#_how_to_access_modify_or_update_your_information[in the Fedora Legal Documentation].
@ -44,7 +46,7 @@ https://communityblog.fedoraproject.org[Fedora Community Blog] brings you contri
Within the Community Blog you'll also find https://communityblog.fedoraproject.org/tag/fridays-fedora-facts/[Friday's Fedora Facts].
These are weekly posts with status updates, schedule info, etc..
The Fedora Pagure source control repository allows posting of https://pagure.io/Fedora-Council/council-docs/issues[issues] which can be discussed, assigned and remediated.
The Fedora {team_issue_tracker_name} source control repository allows posting of link:{team_issue_tracker}[issues] which can be discussed, assigned and remediated.
Here you can raise issues or view, comment on, and request to act on open issues.
There are a number of official and other social media accounts, on various networks.

2
project/modules/ROOT/pages/initiatives.adoc
View file

@ -28,7 +28,7 @@ The Initiative Lead works regularly with all relevant groups in Fedora to ensure
== Proposing a Community Initiative
To propose a Community Initiative to the Council, the Lead should first discuss on the https://discussion.fedoraproject.org/tag/council[#council tag on Fedora Discussion].
Next, if well-received, file a https://pagure.io/Fedora-Council/tickets/[ticket].
Next, if well-received, file a {team_issue_tracker}[ticket].
Of course, people need to be ready to do the actual work required — a Community Initiative without passionate bottom-liners will not get far.
To succeed, Community Initiatives require a leadership team with division of responsibility.

2
project/modules/ROOT/partials/TEMPLATE_team_info.adoc
View file

@ -26,7 +26,7 @@
:team_synch_communication: #council:fedoraproject.org
// Issue tracker
:team_issue_tracker: https://pagure.io/Fedora-Council/tickets
:team_issue_tracker: https://forge.fedoraproject.org/council/tickets
// Meetings
:team_meetings: https://fedoraproject.org/wiki/Council_Meetings

3
project/modules/ROOT/partials/attributes.adoc
View file

@ -3,3 +3,6 @@
// Common URLs
:url_commblog: https://communityblog.fedoraproject.org
:url_wiki: https://fedoraproject.org/wiki
:team_issue_tracker: https://forge.fedoraproject.org/council/tickets
:team_issue_tracker_name: Forge

2
project/modules/code-of-conduct/pages/committee.adoc
View file

@ -106,7 +106,7 @@ Please respond with acknowledgement that you have reviewed these commitments and
[[history]]
== History
The Committee structure was https://pagure.io/Fedora-Council/tickets/issue/442[approved by the Fedora Council] in April 2023.
The Committee structure was https://forge.fedoraproject.org/council/tickets/issues/442[approved by the Fedora Council] in April 2023.
[[previous]]
=== Previous members