Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add strawman cg charter from https://github.com/w3c/cg-charter #1

Merged
merged 12 commits into from
Oct 4, 2024

Conversation

gobengo
Copy link
Contributor

@gobengo gobengo commented Sep 26, 2024

Motivation:

  • propose a SWICG charter into this repo based on the template at https://github.com/w3c/cg-charter
  • include no opinionated changes to the charter template, just those that reflect what's been happening in SWICG (e.g. links to github org, mailing list, wiki)
  • provide one starting point that others can propose patches to of more opinionated deviations from the w3c/cg-charter
  • preserve git history of the CGCharter.html so others can see the small commits I added with @dmitrizagidulin at TPAC 2024

@gobengo gobengo marked this pull request as ready for review September 26, 2024 21:51
ianbjacobs and others added 11 commits September 26, 2024 14:52
@ianbjacobs
Removed the paragraph on not sing the cg contrib list and not doing contributions on mail list (when using GitHub).  that latter sentence was being dropped by users of the template.  it's not necessary so making the template consistent with use.
@ianbjacobs @wseltzer
The test suite section for the CG Charter template points to a page that is only about WGs.  It includes the 2 ways to include test suites in a WG (either as part of the spec or not) and also directly refers to the W3C patent policy.  It's not at all relevant to CGs. 

It would be better just to point to the GitHub LICENSE.md file if in GitHub.

 I followed links in that material until I found the W3C license used and proposed putting that in the LICENSE.md file for the WebVR CG.   That's a separate change I'll suggest in the W3C LICENSE.md file for CGs.
changed it to link to the license section of the charter (since we don't know where they will put their charter in their GitHub repo)
@ianbjacobs
Got this from Google in second screen CG.
Install tidy from http://binaries.html-tidy.org
Download tidyconfig.txt:
https://raw.githubusercontent.com/w3c/presentation-api/gh-pages/build/tidyconfig.txt
Run tidy on command line:
tidy -config tidyconfig.txt -o output.html input.html
@gobengo gobengo force-pushed the add-cg-charter-template branch from d218fb3 to 9e7799a Compare September 26, 2024 21:53
Copy link
Contributor

@csarven csarven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just want to note here the Solid CG charter. Social CG can borrow/adapt whatever is suitable for the Social CG charter. (See some of its development on record in PR).

The Solid CG charter was inspired by the Credentials CG's charter. One important shared aspect between the Solid and Credentials CG charters is the chair election process, which actually differs from the CG charter template. The chair election process is intended to be as democratic and transparent as possible. It resembles W3C AB/TAG elections, ranked-choice voting. See the documented Chair Election Process, which was developed in collaboration between the then CG Chair (myself) and W3C staff (@ianbjacobs). The Solid CG was fortunate to be the first to use W3C's WBS questionnaire system for the CG's chair election. It was an experiment, and it turned out great! And, I would like to see this process and tooling more widely used across all CGs: w3c/cg-council#24 , and all election data can be found at https://github.com/w3c-cg/solid/tree/main/elections/2023/ . In a nutshell, to run an election, eligible voters need to be identified and authorized to vote. Some of that work rests on the CG (as detailed in links above) and some takes advantage of the W3C infrastructure. The alternative, e.g., using third-party systems, identifying voters etc., is far more complex and not particularly as trustable.

While the CG charter template served as a good template, the Solid CG charter in various ways resembles the WG charter template, which is developed at https://github.com/w3c/charter-drafts . The primary reasons for this was that the WG charter was more actively developed and also to minimise the gap between the CG charter and WG charter, and as a side-effect helping the community develop more familiarity on shared processes. For instance, unless otherwise stated, the Solid/Credentials CG charters lean on the W3C Process as guidance even if things don't necessarily apply.

Happy to share more lessons learnt...

@bumblefudge
Copy link
Contributor

bumblefudge commented Sep 27, 2024

One important shared aspect between the Solid and Credentials CG charters is the chair election process, which actually differs from the CG charter template.

Any objections to opening a separate branch (off this branch) that copy-pastes the Solid chair-voting mechanisms? I participated in a few CCG elections and I would be glad to mediate/direct-traffic on a separate PR just for chair-selection, if people have strong feelings. Chair selection by the whole CG, and avoiding manual processes for it, both seem like an unalloyed good to me, but maybe people have concerns there that aren't obvious to me?

@bumblefudge
Copy link
Contributor

Happy to share more lessons learnt...

Keep them coming!

@melvincarvalho
Copy link

Any objections to opening a separate branch (off this branch) that copy-pastes the Solid chair-voting mechanisms?

I think it could work well. In Solid, we had 3 chairs chosen from 5 candidates, with the largest voting block being Inrupt, Solid's biggest employer. All 3 chairs were current or former Inrupt employees, while the two more grassroots candidates didn’t make it, though all were well qualified. Just something to consider around diversity and voting blocks.

@bumblefudge
Copy link
Contributor

bumblefudge commented Sep 27, 2024

All 3 chairs were current or former Inrupt employees,

Good shout-out. In the Credentials CG [EDIT: I seem to remember there being, but i never looked up the exact text,] a "1 member max per organization" rule (with a little wiggleroom for "organization") so I would maybe prefer some variation on that proviso, since having, say 3 Automatic/Threads/Mastodon gGmbH folks taking over the CG seems like a possible, if in the short term unlikely, failure mode...

@csarven
Copy link
Contributor

csarven commented Sep 28, 2024

"1 member max per organization" (with a little wiggleroom for "organization"

AFAICT, this is not expressed in the Credentials CG charter.

However, the Solid CG charter includes the following:

Chair nominees and elected chairs per term MUST have unique affiliations.

An affiliation MAY submit one ballot that ranks candidates in their preferred order.

which is adapted from W3C Process's Advisory Board and Technical Architecture Group Elections:

each Member (or group of related Members) may submit one ballot that ranks candidates in the Member’s preferred order.

This is addressed in the eligible chair candidates and voters process.

Copy link
Contributor

@tantek tantek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only one minor editorial change (W3C has a "Code of Conduct" now) but other than that, let's land this so we can start figuring out all the TBD sections and incrementally improving it. Thanks for this initial hard work @gobengo!

CGCharter-1727386911.html Outdated Show resolved Hide resolved
Co-authored-by: Tantek Çelik <blog@tantek.com>
@gobengo
Copy link
Contributor Author

gobengo commented Oct 4, 2024

iiuc SWICG resolved in today's meeting to merge this. If anyone has final concerns, raise them! (but also once merged, more PRs modifying this are welcome/expected)

@dmitrizagidulin
Copy link
Member

Merging, thanks for your work everyone! (And great discussion on today's call). Let's continue the conversation in further PRs!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.