GitLab | Workflow for contrib projects (#99)

[Gedare Bloom (@gedare)]

Gedare Bloom commented: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124529


It would be good to provide clarity on when the mirrors should have Issues/MRs against them directly, as opposed to opening reports/code reviews upstream. I suppose in most cases it is by the developer's discretion, in which case, I don't know what the statement "for it to be official" means precisely. I don't think we want to be too prescriptive.

An example: suppose I want to send a small change to newlib. I test it locally, I send it to the newlib mailing list, it gets merged, then it shows up in the mirror. Is that an "official" change from the RTEMS commmunity, and to what extent does that matter?

-- 
View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124529
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/3a87c63c/attachment.htm>