Reform the git repositories corresponding to the four package repositories [core], [desktop], [lib32], and [gtk]
core, nine branches,
desktop, seven branches,
lib32, four branches,
gtk, two branches,
I'd like to resume the talks of reforming the four git repositories. If anyone in @chakra has access to the old discussion on Loomio, or e-mails from there, where @Ram-Z (if I recall correctly) and others presented a number of options and possible solutions, please share them here.
I remember a suggestion along the lines of "one package per git repository", where the branches corresponded to specific package repositories, e.g.:
testingbranch might be the default branch, merged into
masterupon the package being verified as working and uploaded directly to one of the
masterpackage repositories, or moved from
unstablebranch would most likely be used for VCS packages, and probably not merged with the other two branches.
I cloned the four git repositories, and estimate the number of packages to be approximately 3200:
$ ls -la total 104 drwxrwxr-x 6 totte totte 4096 feb 5 13:10 . drwxrwxr-x 3 totte totte 4096 feb 5 13:10 .. drwxrwxr-x 1532 totte totte 40960 feb 5 13:12 core drwxrwxr-x 1398 totte totte 36864 feb 5 13:21 desktop drwxrwxr-x 71 totte totte 4096 feb 5 13:21 gtk drwxrwxr-x 190 totte totte 12288 feb 5 13:21 lib32 $ find ./ -maxdepth 2 -type d | wc -l 3188
Consider one package per (GitLab) project in the group Chakra/Packages. @chakra/packages members would have access to all of them, but we could also set specific maintainers for each project if we wanted. If a new contributor wanted to maintain a single package, we could create a project in Chakra/Packages and make him/her maintainer of that project, without membership in @chakra/packages. This would provide the previously used access control.
For users looking to report an issue with a package, they would browse to https://code.chakralinux.org/groups/chakra/packages/-/issues, click the
I think a reform could help lower the barrier for new contributors to join. Even if we had to archive the current repositories with their history and start over from scratch, it is worth considering. It could be a daunting task, but I volunteer to do the grunt work of archival and creating the new structure. I would need help adapting the build system though.