Problem/Motivation

The individuals members of a working group change independently of the charter. Therefore, the charter should direct to where the current members are listed.

Steps to reproduce

View the documentation, infrastructure and the licensing charters.

Proposed resolution

Remove the names are add where the names should be listed.

Only the Documentation Working Groups, Drupal Licensing Working Group and Drupal.org Infrastructure Working Group are changed here because the memberships is listed elsewhere.

Remaining tasks

Review
Commit

User interface changes

API changes

Data model changes

Issue fork governance-3482053

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

quietone created an issue. See original summary.

quietone opened merge request !28

quietone’s picture

quietone commented
Status: Active » Needs review
quietone’s picture

quietone commented
Status: Needs review » Reviewed & tested by the community

This was agreed to at a meeting of core committers and the DA, so setting to RTBC.

When I try to apply the suggestion made by @longwave, I get an error, "Can't apply as this line was changed in a more recent version." A message I have not seen before.

quietone’s picture

quietone commented

I meant to add, it is a simple typo so I reckon it can be fixed on commit.

hestenet made their first commit to this issue’s fork.

  • hestenet committed 7118f7ab on main authored by quietone 
    fix: #3482053 Remove member names from some charters

By: quietone
By:...
hestenet’s picture

hestenet
He/Him
Location Portland, OR 🇺🇸
commented
Status: Reviewed & tested by the community » Fixed

Merged! Thanks, all.

https://project.pages.drupalcode.org/governance/charters/drupalorg-infra...

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.