Engage projects to make use of new GL features
After internal discussions, it was decided to invite more projects to use the new features we've started to support in Gitlab. This includes arbitrary project nesting (#42 (closed)) and top-level project nesting. See https://gitlab.eclipse.org/eclipse/technology/dash for an example, and the handbook for documentation.
We wish to gain more experience in handling these types of requests and to better serve the community. To this end, we will reach out to a few project leads from different projects and invite them to test these unannounced features. I suggest that we look to Asciidoc and Eclipse OpenK for early adopters. They are medium-sized projects, with Asciidoc having expressed interest in this feature in the past.
Looking for +1 before I reach out just to make sure we're on the same page!
/cc @webdev /cc @eclipsefdn/it/releng
Activity
assigned to @malowe
added to epic &12 (closed)
Calling PLs from those projects! Are you guys interested in using some unannounced features for Gitlab? You already have access to one (arbitrary/self-managed subgroups), but we can also look at giving you guys some top-level project (TLP) nesting. I think TLP nesting is more attractive for Asciidoc folks as they have their own TLP, but the offer is open to both!
Let me know what you guys think. As I said, you guys can already create new groups and do arbitrary nesting of stuff, as that is enabled for everyone. Keep in mind that moving your projects around could cause some hiccups in things like CI, or any links to old paths, and everything that previously applied still applies. We strip any permissions granted to users in subgroups or nested projects still, and ECA will apply to all projects in your namespace (unless you apply for an excluded namespace for things like mirrors).
/cc @tewolde
/cc @rwinch
/cc @asalgadoromero
/cc @swhitesal
/cc @mojavelinuxFor the AsciiDoc TLP and AsciiDoc Language projects, we ended up with a split:
However, we are using the nesting inside asciidoc-lang, which holds asciidoc-lang and asciidoc-tck. However, asciidoc-tck isn't a separate project from asciidoc-lang, just a separate repository.
To be honest, I'm just not sure what to do at this point. What I can tell you is from the outside, it now looks like we have two initiatives going on, and that's just confusing for people. I would have preferred if there was one group named "asciidoc" with "asciidoc-tlp", "asciidoc-lang", and "asciidoc-tck" underneath it. But I kind of just ran out of energy to try to win this battle and just got used to what we have.
I think we're fine with Eclipse Austen having its own space. But, again, even I just lost the thread (and really the motivation) trying to advocate for what to do.
mentioned in issue #42 (closed)
