Support Gitlab repositories for working groups

As discussed via email we would like to enable working groups to be provisioned Gitlab repos to support collaboration. We now have a working group (IDE Platform) who has specifically asked for this capability, so we would like to get to this sooner than later. I think a few things that need to get done here are:

• rename the current "Eclipse" top-level group to "Eclipse Projects"
• create a top-level group "Eclipse Working Groups"
• provision repos upon request. Establishing a process to do this (perhaps via Gitlab here) would be required as well Happy to answer any questions! /cc @wbeaton @droy

changed the description

The first two items are done: https://gitlab.eclipse.org/explore/groups

The third may need some formal representation in PMI: https://projects.eclipse.org @wbeaton @cguindon

At some point, we're going to need to formalize how we track representation in the various working group committees so that we can automate these sorts of things and otherwise have some source of truth. Whether or not the PMI is the right place for this is something that we should discuss.

We've hit this issue in places like Google Drive sharing, specification committee resources on Github (e.g. Jakarta EE), and other collateral (e.g., Jakarta EE). I believe that all of the examples that I've listed are currently managed manually.

It's also the case that working groups will likely want to leverage the ability to arbitrarily nest groups; we should anticipate this (see #42 (closed)).

/cc @scorbett

Track representation of the committees is completed to some degree, or tracked internally.

For now, I suggest :

1. Each WG gets one top-level group under https://gitlab.eclipse.org/eclipse-wg ;

2. The group name should be the formal WG name (ie, https://gitlab.eclipse.org/eclipse-wg/eclipse-ide; https://gitlab.eclipse.org/eclipse-wg/adoptium; https://gitlab.eclipse.org/eclipse-wg/eclipse-edge-native) or accepted short form;

3. New WG projects be requested as a Gitlab issue (either in the WG "group") or against EF GitLab, to ensure requests are tracked

4. It should be understood that WG projects do not include CI resources, but do include repo, wiki, issues and all currently available GitLab features

Thoughts?

Here's a concrete example of what we are thinking:

• Working Groups (Public with some private projects: https://gitlab.eclipse.org/eclipse-wg)
  • eclipse-ide https://gitlab.eclipse.org/eclipse-wg/eclipse-ide
    • Marketing Committee (private)
    • Steering Committee (private)
    • Ide-wg.eclipse.org (Public: website)
  • ecdtools https://gitlab.eclipse.org/eclipse-wg/ecdtools
    • Marketing Committee (private)
    • Steering Committee (private)
    • Open-vsx.org (Public)
    • Openvsx-publisher-agreement-specs (Public)
    • Ecdtools.eclipse.org (Public: website https://gitlab.eclipse.org/eclipse-wg/ecdtools/ecdtools.eclipse.org)

I got started on this and I created the following in the Eclipse Working Groups GROUP:

1. An Eclipse IDE GROUP: https://gitlab.eclipse.org/eclipse-wg/ide-wg
2. An ide-wg.eclipse.org PROJECT for hosting the WG website source code: https://gitlab.eclipse.org/eclipse-wg/ide-wg/ide-wg.eclipse.org

1. New WG projects be requested as a Gitlab issue (either in the WG "group") or against EF GitLab, to ensure requests are tracked

It's not possible to create an issue under a GROUP. Gitlab only allows issues to be created within a PROJECT.

I've started a Google Doc today to start documenting our vision for Gitlab in regards to how we want to implement Groups and Projects: https://docs.google.com/document/d/1pSdhjiHumRzUZgjE0YYZJgJg6JFKTlmE1vAOOEEbvqc/edit#

In order to avoid getting requests from all over the place (Infrazilla, Github and Gitlab), we should be specific to where we expect these issues to be created.

I recommend the following options:

1. We use our existing Gitlab project: https://gitlab.eclipse.org/eclipsefdn/gitlab
2. We create a "General Inquiries" project under https://gitlab.eclipse.org/eclipse-wg to capture requests from all WG.

Agreed, @cguindon

I've created https://gitlab.eclipse.org/eclipse-wg/general-inquiries as a place to submit WG-related requests, and I believe @scorbett will schedule a call with all WG-related participants so we can review these options, and explain the workflow. Once that call has taken place, I suggest we can mark the last task as complete, and close this issue.

Meeting has been scheduled for June 3 (we are a busy crowd) :-)

marked the checklist item provision repos upon request. Establishing a process to do this (perhaps via Gitlab here) would be required as well as completed

I believe we are done here. WGs have a space on GitLab, we've presented GitLab to the WG managers with a proposed process for using GitLab for Working Groups (ie, file an issue on GitLab and state requirements).

closed

added Working Groups ~16083 labels