[Tiki-devel] Major modifications made to https://dev.tiki.org/Where-to-commit
Marc Laporte <[email protected]>
| Newsgroups | gmane.comp.cms.tiki.devel |
|---|---|
| Message-ID | <[email protected]> |
Executive summary: We made major changes to: https://dev.tiki.org/Where-to-commit If you have any concerns, please share them now. Details: In the old days, we gave everyone commit access, and this served us well: * https://sourceforge.net/blog/podcast-tikiwiki/ * https://tiki.org/article370-Tiki-reaches-500-contributors-with-commit-access Since the move to Git (https://dev.tiki.org/Tiki-Version-control-history), we slowed down on giving commit access, because merge requests from new contributors are approved by existing devs. Now with over 3000 merge requests managed, we have some tangible experience on how things work: https://gitlab.com/groups/tikiwiki/-/merge_requests?scope=all&state=all Some key community members have been having multiple discussions about how to improve our workflow. Notably, it was discussed here: https://tiki.org/Roundtable-Meeting-2023-06#Recording One of our goals is to make developers more autonomous. And this will lead us to promote some community members in term of Git commit access (from reporter to developer). So what is the optimal/balanced approach? It was time to document an evolve consensus for expectations. This is what we have so far: https://dev.tiki.org/Where-to-commit and we still start to implement soon. I look forward to your enhancements. Best regards Marc _______________________________________________ TikiWiki-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel