Bhushan Shah ha scritto: > - But most importantly, this breaks with the non-unique leaf repository > names feature offered by the proposed structure. So, There could be > maui/documentation and wikitolearn/documentation. But we would have > single KDE/documentation redirect
Just to clarify: are we going towards a non-unique leaf repository name? I thought we were going to maintain the leaf uniqueness regardless. If this is the case, I'd really like to express my disappointment: we are basically forcing back the namespaces as part of the application name. Dolphin is going to be referred to application/dolphin or application_dolphin, kstars as education/kstars and so on, because we can have duplicates. This is a huge step back, also because the namespaces are mixed: we have subproject types (wikitolearn, maui, plasma-mobile) and category types (education, pim, graphics, etc). What if plasma-mobile want to distinguish their projects by categories? That's inconsistent. We don't know where we will be in 10 years in terms of tooling, maybe gitlab itself will introduce better filtering capabilities, let's keep at least the uniqueness of leaves. I suspect we need some compromise decision (not win-win, sadly) here, but I feel that having both (mixed) subcategories (non-flat) and no uniqueness of repository names is going to be the worst combination. -- Luigi