docs/tickets
19
4
Issues 34 Pull requests Projects Activity

Repository alignment #18

New issue
Closed
opened 2026-03-03 11:05:54 +00:00 by pbokoc · 1 comment
pbokoc commented 2026-03-03 11:05:54 +00:00
Owner
Copy link

The migration to Forgejo is a good opportunity to fix various messes in our repositories. Here's a checklist of things I want to see brought in line:

  • Default branch is set to main (with the possible exception of the central repo) - see #37
  • Fix the READMEs - see #36
  • Git submodule for common files - see #17
  • Structure (partials, assets, etc.) is up to date and files such as partials are included correctly - see #38
  • Ensure that the UI bundle for local builds points to wherever the UI bundle is built now (the UI repo will have been migrated from gitlab as well)
  • The two or three repos such as the Packaging Guidelines that are using Makefiles are updated to follow common structure and tooling - see #39
  • Repository wiki and packages disabled
  • Use the same set of labels - see #40
  • Permissions

These requirements should also be documented in contributor docs so any new repos can follow the same guidelines going forward.

The migration to Forgejo is a good opportunity to fix various messes in our repositories. Here's a checklist of things I want to see brought in line: - [x] Default branch is set to `main` (with the possible exception of the central repo) - see #37 - [x] Fix the READMEs - see #36 - [ ] Git submodule for common files - see #17 - [ ] Structure (partials, assets, etc.) is up to date and files such as partials are included correctly - see #38 - [ ] Ensure that the UI bundle for local builds points to wherever the UI bundle is built now (the UI repo will have been migrated from gitlab as well) - [ ] The two or three repos such as the Packaging Guidelines that are using Makefiles are updated to follow common structure and tooling - see #39 - [x] Repository wiki and packages disabled - [x] Use the same set of labels - see #40 - [x] Permissions These requirements should also be documented in contributor docs so any new repos can follow the same guidelines going forward.
pbokoc added this to the (deleted) project 2026-05-05 15:01:35 +00:00
pbokoc removed this from the (deleted) project 2026-05-05 15:07:21 +00:00
pbokoc commented 2026-07-08 13:42:03 +00:00
Author
Owner
Copy link

Closing this now - some of the subtasks aren't finished, but they're tracked in their own issues. This one was originally opened in lieu of a project board since that functionality wasn't there back in March, but we don't have that problem now.

Closing this now - some of the subtasks aren't finished, but they're tracked in their own issues. This one was originally opened in lieu of a project board since that functionality wasn't there back in March, but we don't have that problem now.
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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
pbokoc
1 participant
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#18
No description provided.