GitLab | Workflow for contrib projects (#99)

[Amar Takhar (@amar)]

Amar Takhar commented on a discussion: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124538


I mentioned to Christian above that maybe something under a `__rtems__` guard or an rtems-only header?  I don't know how we define "rtems only" it's not like anyone is going to get in trouble if a patch is missed so I would say use discretion?  I think over time we'll figure it out via "this should have been an MR to our mirror" or "there was no need to open an MR for this".

I think the definition is always going to be a little fuzzy unless it's strictly an rtems header or under `__rtems__`.

Your example can be any case really even if a change is general ie, consumable by everyone but was made directly due to a requirement for RTEMS I would consider that an RTEMS change but if it's just a change to newlib for everyone then no I wouldn't.

Again, discretion is going to be the valuable part here because it's not a big deal at all if some things get missed.  We have zero tracking now and having it "mostly" tracked is great.

-- 
View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124538
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/725edc6c/attachment-0001.htm>