For now, I simplified the idea slightly. This list include only merge-requests by first-time contributors that have had no feedback from anyone.
If you are familiar with one of these projects, perhaps you can usefully review, test or comment on a merge request or two.
Note that most projects reserve the ‘merge’ action for project maintainers. Let’s not actually merge these changes without permission from the relevant project maintainers.
gnome-calendar - Fix crash when hopping between years while still loading calendars
The reason why we have a shared GNOME group, with the ability to review/merge changes in every GNOME project, is to encourage drive by reviews and contributions. It allows projects to continue improving without blocking on a single person.
Yes, some maintainers reserve the right to gate all the contributions—that is good and proper. Nevertheless, for changes such as documentation, typo fixes, and improvements in ancillary data, I think we should take advantage of the shared GNOME ownership. This is especially true for shared projects, like the GNOME documentation; the documentation team is small, so the whole community should really take ownership of contributions, there.
I think this has been the case for the past 20-odd years, and it’s entirely up to individual maintainers to specify stricter rules, if they so choose. We start from a place of permission, not of restriction.
In any case, you’re right: we should be more explicit about this policy. I’ll try an open a topic, and then we can modify the wiki.
I think this has been the case for the past 20-odd years, and it’s entirely up to individual maintainers to specify stricter rules, if they so choose. We start from a place of permission, not of restriction.
And that does happen. For example, I know (and respect) that pwithnall likes to keep the last word on glib MRs
If you are part of the GNOME group—i.e. you have an LDAP account on GNOME infrastructure—then you have developer access to all projects under the GNOME group on GitLab.
Great idea! I noticed one merge request was nothing more than a typo fix. As that used to be ok to commit, plus again confirmed here I’ve asked to re-enable my account. Apparently it got disabled or something. It’s no fun if people wait 2 weeks for a typo merge request.
Update: Merged two simple typo fixes from a new contributor. As my previous git experience was nothing more than applying a file as a patch the GitLab experience is a little nerve wracking. I’m still terrible with Git, but at least I mostly know when it used to be ok to apply a patch.
