Information regarding upcoming Gitlab Migration

[Ilya Bizyaev]

Hello Bhushan!



Thank you for you work on the Gitlab migration!



The lists look good! Here are some ideas that I have, in case you think they can be considered before we transition:

• The "applications" category is somewhat misleading to me: it does not include all KDE applications, and not all repositories in that category are applications either. Looking through the list of projects in there, I think they can be safely distributed across other categories. Most complicated there are IMO kate, dolphin, klook, konqueror, konsole and yakuake. Somehow terminal emulators, file managers and text editors feel like they belong to the same category, but I don't know how to call it; maybe "files"?

• Tentative, but I think a category called "science" might make sense creating. Since KDE regularly attempts to promote usage of our software in scientific institutions, that wouldn't hurt either. E.g. Mark (an app for data science) doesn't really belong in "education", and I think is also true for labplot and rkward.

• I see a category named "others". Looking at its contents, maybe it can be renamed to "community"?



Looking forward to the move!



Cheers,

Ilya.





---- Дата: Пн, 27 апр 2020 04:40:01 +0300 Bhushan Shah <bshah at kde.org> написал(а) ----



[Please keep mailto:sysadmin at kde.org list or mailto:bshah at kde.org in the CC for 
replies] 
 
Hello Community members, 
 
In view of upcoming Gitlab migration, we sysadmin team wants to share 
the recommended structuring for the repositories on Gitlab. 
 
We had multiple options, 
 
- Flat structure: In this option we would have everything under one 
 single namespace/group: https://invent.kde.org/kde/knetwalk 
- Subgroups under top-level group: In this option we would have a groups 
 under KDE namespace: https://invent.kde.org/kde/games/knetwalk 
- Groups at top level: In this option we would establish a series of 
 groups at the top level, e.g. https://invent.kde.org/games/knetwalk 
 
We have discussed this with small but representative group of 
contributors or maintainers, and based on their suggestions, we 
recommend that we go with option 3. Having sub-groups at top level will 
allow us to, 
 
- Provides good visibility on all reviews, tasks and other items within 
 the groups/modules we define 
- Provides improvements to discoverability of projects 
- Makes it possible for groups of projects to establish a group level 
 task board should it fit their needs (for tracking a release for 
 instance) 
- Makes the most semantic sense, as the ‘KDE’ top level group suggested 
 in option 2 is duplicative considering the Gitlab instance is under 
 kde.org. 
- The discoverability of projects is maximised, as there is no need to 
 open the top level ‘KDE’ group before going into the subgroup. 
 
I've worked on draft "move" of the current set of the repositories in 
their respective subgroups at the repo-metadata project's branch [1]. 
You can browse the directory structure to get idea of how final 
structure on Gitlab would look like. 
 
If we don't have any objections we would like to implement this next 
week and move projects to https://invent.kde.org. 
 
Thanks! 
Bhushan for sysadmin team 
 
[1] https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects-invent?h=bshah/invent 
 
-- 
Bhushan Shah 
http://blog.bshah.in 
IRC Nick : bshah on Freenode 
GPG key fingerprint : 0AAC 775B B643 7A8D 9AF7 A3AC FE07 8411 7FBC E11D
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20200427/4ad89cd2/attachment.htm>