GitLab | Workflow for contrib projects (#99)

[Amar Takhar (@amar)]

Amar Takhar created an issue: https://gitlab.rtems.org/administration/gitlab/-/issues/99

Assignee: Amar Takhar

We discussed during our last meeting 2025-06-05 on how to handle contributed code -- as in code we _upstream_ to projects.  Currently it's a bit of a jumble as we've never had a formal process on how we manage these.  It creates a fractured history and we've never had a formal way to discuss before things are sent upstream on behalf of the project.

The goal is, if it's a patch going upstream on behalf of the project for it to be official we'll need to have an MR that exists locally on our GitLab.

A few things to note.

1. These mirrors are **read only** any changes made will be overwritten and most actions will be blocked
2. In order for RTEMS to consume a change to any of these repositories it **must** be upstreamed
3. Before submitting a patch we will track using issues in those projects and MRs

The suggested workflow we talked about is:

1. Open an issue if there is no code available for a suggested change to have a discussion
2. If there is a change open an MR against the main branch of the contrib repository
3. Upstream the patch and link the PR/Email/whatever in the MR if possible
4. Once the change has been merged upstream link to the **local contrib repo** commit hash that contains the change(s) then **close** the MR.  If the has remains the same GitLab will automatically remove the commits from the MR.  If the MR is closed and commits still exist this means it was modified upstream which is fine but gives us a good indication.

Any comments about this can be added below for discussion the contrib repos have been added for forking already.

-- 
View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/99
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/20250611/1b209a5f/attachment.htm>