GitLab | Workflow for contrib projects (#99)

[Kinsey Moore (@opticron)]

Kinsey Moore started a new discussion: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124519


I think this needs to be separated into several parts, some of which are already mentioned above. I'll refer to the points above in the first section as A1.x and the points in the second section as A2.x.

1. Justify the existence and maintenance of these repositories: RSB is easy to run in CI and thus beat on the upstream repositories. We do not want to cause the upstream repositories undue strain, especially via what is basically automation (RSB).
2. In a general sense, define the things that exist in the contrib namespace: This is largely covered by points A1.1 and A1.2 above. They should also be things that are used by RSB.
3. How the repos in the contrib namespace are used: This is largely covered by A1.3 being a general description and A2.* being some of the specifics.
4. How to add new repos to the contrib namespace: This is not addressed beyond migration of existing repositories on Github.
5. How to remove repos from the contrib namespace: This is not addressed.

In point A2.1, "no code available for a suggested change" is unclear. Is it that there isn't a contrib repo for that project yet? Does it mean a lack of a patch to effect the desired change in behavior?

@joel How does this compare to your existing workflow for pushing patches to our upstream dependencies?

-- 
View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124519
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250613/833a6b36/attachment.htm>