Contrib.social

Starshot governance

Open on Drupal.org →
Created on 10 May 2024, 7 months ago

Problem/Motivation

Starshot governance is TBD, but it could use some kind of structure sooner than later so that there are named people to talk to and a process for coming to decisions etc.

Because writing and changing Drupal governance docs can take an extremely long time, and there is supposed to be a working project coming out of starshot in a short period of time, I've been hesitant to open this issue at all, however there might be a way both to add some formal governance without having to come up with a fully formed policy for it at the same time.

My suggestion is to do what we did not long ago to revitalise the coding standards group.

1. Set up a 'starshot working group' which would be under the Technical Working Group (see #3252921: Add members to and remove members from the Technical Working Group → and #3378689: Add more coding standards maintainers, part II → for how we revived the coding standards committee).

2. Similar to the coding standards committee, add an initial set of members nominated by the TWG. For the coding standards committee, this was a subset of core committers to start with, but then quickly expanded.

3. The starshot committee is then able to appoint new members to itself.

4. Starshot would then have its own documentation and policies as part of the starshot project.

In the meantime, there can be more issues in the governance queue (i.e. this one), to create a new charted working group separate from the TWG if that's desired, but that could be done in parallel. It's likely some aspects/requirements will only become clear once things are up and running so it may be hard to define a formal structure up front.

Steps to reproduce

Proposed resolution

Create a working group under the Technical Working Group, add some initial members, and go from there.

Remaining tasks

Open a follow-up to create a full chartered working group that's not under the TWG, if that's desired.

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Component

Policies

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.
  • Starshot blocker

    A potential blocker for Drupal Starshot. More information: http://www.drupal.org/project/starshot

Sign in to follow issues

Comments & Activities

  • Issue created by @catch
  • Comment 7 months ago →
    🇭🇺Hungary Gábor Hojtsy Hungary

    I don't think creating the Starshot governance under the Technical Working Group is the way to go. While it has been historically hard to change governance indeed, and that was the best way to do for coding standards, Starshot is not supposed to be lead from a technical standpoint but rather a user needs / product standpoint, so I think it needs to be set up differently, not just for the sake of paperwork but also perception. Dries pledged his focus on this project, so I don't think it will be a problem to set up whatever governance structure needed so long as the right kind of people are there.

  • Comment 7 months ago →
    🇬🇧United Kingdom catch

    The starshot group can include as much product people as necessary under the auspices of the technical working group though? I only suggested this to save time, if it doesn't save time, it's not worth considering - but also I will note there is no other issue yet, so when is that expected?

    Starshot is not supposed to be lead from a technical standpoint but rather a user needs / product standpoint

    It needs to be a combination of these - you can't meet the user / product needs without good technical foundations.

  • Comment 7 months ago →
    🇺🇸United States helenasue

    I don't want to contribute from a technical standpoint, but if there's any need for insight from a sales and/or user perspective, I'd be interested in tagging along if I can be helpful.

  • Comment 7 months ago →
    🇦🇺Australia sime Melbourne

    I would like to nominate for a governance group. I'm interested in the balance of the open source benefits vs starshot success.

  • Comment 6 months ago →
    🇺🇸United States Kristen Pol Santa Cruz, CA, USA

    I agree a governance group is crucial for this project. My understanding is the TWG may be going away:

    #3361198: Discuss the future of the Technical Working Group (TWG) →

    Though I don't think that matters since I agree the Starshot Working Group (or whatever it's called) could stand on its own IMO.

    There are subcommittees and working groups for the DA Board. But, maybe all the working group members are board members, I didn't cross reference:

    https://www.drupal.org/association/board/committees →

  • Comment 3 months ago →
    🇸🇰Slovakia poker10

    Is there any progress with the Drupal CMS governance (since the leadership team has been announced)? Or what are the next steps/plans? Thanks!

  • Comment 19 days ago →
    🇳🇿New Zealand quietone

    so I think it needs to be set up differently,

    @gábor hojtsy, what do you suggest?

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024