docs/tickets
19
4
Issues 34 Pull requests Projects Activity

Location of current docs-team project boards #48

New issue
Closed
opened 2026-06-02 06:04:40 +00:00 by egret · 3 comments
egret commented 2026-06-02 06:04:40 +00:00
Member
Copy link

Is it feasible for us to have all the current project boards in one location?

At present, our project boards can be found in one of two different locations:

  1. The org level projects.
  2. Individual repos, for example the Tickets project section.

If we have all the projects in one place, it may make it easier for people to get a general overview of what everyone is working on. Could be useful for team meetings.

Is it feasible for us to have all the current project boards in one location? At present, our project boards can be found in one of two different locations: 1. The org level [projects](https://forge.fedoraproject.org/docs/-/projects). 2. Individual repos, for example the Tickets [project](https://forge.fedoraproject.org/docs/tickets/projects) section. If we have all the projects in one place, it may make it easier for people to get a general overview of what everyone is working on. Could be useful for team meetings.
egret commented 2026-06-02 13:42:40 +00:00
Author
Member
Copy link

Docs meeting discussion - project boards to be migrated to the org level.

Docs meeting discussion - project boards to be migrated to the org level.
🚀 2
pbokoc commented 2026-06-02 14:42:43 +00:00
Owner
Copy link

We have consensus that we should use org-level boards for the extra flexibility. Per-repo projects will however have to remain enabled because otherwise you can't attach issues to org boards - see https://docs.fedoraproject.org/en-US/forge-documentation/known_issue_organization_projects/

@egret volunteered to migrate the 4 boards from this repo to the org level. (Don't forget to reassign the issues that are currently in them to the new boards :).

We should also document that per-repo boards shouldn't be used. (Maybe a new page in contributor docs about organizing work items? - Needs a new issue opened in the contributor docs repo)

We have consensus that we should use org-level boards for the extra flexibility. Per-repo projects will however have to remain enabled because otherwise you can't attach issues to org boards - see https://docs.fedoraproject.org/en-US/forge-documentation/known_issue_organization_projects/ @egret volunteered to migrate the 4 boards from this repo to the org level. (Don't forget to reassign the issues that are currently in them to the new boards :). We should also document that per-repo boards shouldn't be used. (Maybe a new page in contributor docs about organizing work items? - Needs a new issue opened in the contributor docs repo)
egret commented 2026-06-03 12:40:46 +00:00
Author
Member
Copy link

Closed due migration finished. New issue for docs page work items opened.

Closed due migration finished. New issue for docs page work items opened.
egret closed this issue 2026-06-03 12:41:02 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
Contributors' Guidance
Improve written Material
 Improve the existing contributor documentation

  
Contributors' Guidance
technical support measures
 Improve contributors' guidance by technical efforts like vale or similiar linters

  
effort
high
 Will take a long time

  
effort
low
 Easy fix

  
effort
medium
 Will take some time

  
good first issue
Take this if you're new!

  
help wanted
Needs help or feedback from the wider Fedora community

  
meeting topic
Need to discuss this at a Docs team meeting

  
needs changes
Needs changes or fixes before closing

  
needs reporter feedback
Additional feedback or information from the reporter is needed to advance

  
needs review
Someone needs to look at this

  
priority
high
 Fix this NOW NOW NOW!

  
priority
low
 Low priority tasks

  
priority
medium
 Medium priority tasks

  
priority
on hold
 Work has been temporarily halted, usually because another task needs to be completed first.

  
type/content
Changes to the contents of the site - the actual docs

  
type/misc
Changes to non-content parts of the site. CSS, Actions, scripts, etc.

No labels
Contributors' Guidance
Improve written Material
Contributors' Guidance
technical support measures
effort
high
effort
low
effort
medium
good first issue
help wanted
meeting topic
needs changes
needs reporter feedback
needs review
priority
high
priority
low
priority
medium
priority
on hold
type/content
type/misc
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Docs Team Meeting Planner
Assignees
Clear assignees
No assignees
egret
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
docs/tickets#48
No description provided.