Skip to content

Commit

Permalink
add CGCharter.html
Browse files Browse the repository at this point in the history
  • Loading branch information
@gobengo
gobengo committed Sep 26, 2024
2 parents 3e223a5 + 19684d6 commit 9474a69
Showing 1 changed file with 306 additions and 0 deletions.
306 changes: 306 additions & 0 deletions CGCharter.html
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,306 @@
<!DOCTYPE html>
<html lang="en">
<head>
<title>
{TBD: name} Community Group Charter
</title>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="//www.w3.org/StyleSheets/TR/base">
<style>
body {
max-width: 60em;
margin: auto;;
}
*:target {
background-color: yellow;
}
li {
margin-bottom: 9pt;
}
.note {
background-color: yellow;
padding: 10px;
}
.remove {
background-color: yellow;
}
</style>
</head>
<body>
<h1>
[DRAFT] Social Web Incubator Community Group Charter
</h1>
<p>
This Charter is work in progress. To submit feedback,
please use https://github.com/swicg/potential-charters/issues Issues
where Charter is being developed.
</p>
<ul>
<li>This Charter: <span class="remove">{TBD: URI}</span>
</li>
<li>Previous Charter: <span class="remove">{TBD: URI}</span>
</li>
<li>Start Date: <span class="remove">{TBD: date the charter takes effect,
estimate if not known. Update this if the charter is revised and include
a link to the previous version of the charter.}</span>
</li>
<li>Last Modifed: 2024-09-26
</li>
</ul>
<p>
The Social Web Incubator Community Group (also known as SocialCG, or SWICG) is the successor of the Social Web Working Group, which ran from 2014 to 2017.
</p>
<h2 id="goals">
Goals
</h2>
<ul>
<li>
Provide space to collaborate and coordinate for implementors who are building on any of the specifications published by the Social Web WG (2014-2017), and related technologies.
</li>
<li>
Incubate new proposals which build on or complement the Social Web WG recommendations.
</li>
</ul>

<h2 id="scope-of-work">
Scope of Work
</h2>
<p class="remove">
{TBD: Describe topics that are in scope. For specifications that the CLA
patent section applies to, it is helpful to describe the scope in a way
that it is clear what types of technologies will be defined in
specifications, as opposed to adoption by reference or underlying
technology not defined in the proposed spec. Key use cases are often
helpful in describing scope. If no specifications will be defined in the
group that the CLA patent section applies to, the charter should clearly
state that. A clear scope is particularly important where patent
licensing obligations may apply.}
</p>
<h3 id="out-of-scope">
Out of Scope
</h3>
<p class="remove">
{TBD: Identify topics known in advance to be out of scope}
</p>

<h2 id="deliverables">
Deliverables
</h2>
<h3 id="specifications">
Specifications
</h3>
<p class="remove">
{TBD: Provide a brief description of each specification the group plans
to produce. Where an estimate is possible, it can be useful to provide an
estimated schedule for key deliverables. As described below, the group
may later modify the charter deliverables. if no specifications, include:
"No Specifications will be produced under the current charter."}
</p>
<h3 id="non-normative-reports">
Non-Normative Reports
</h3>
<p>
The group may produce other Community Group Reports within the scope of
this charter but that are not Specifications, for instance use cases,
requirements, or white papers.
</p>
<h3 id="test-suites">
Test Suites and Other Software
</h3>
<p class="remove">
{TBD: If there are no plans to create a test suite or other software,
please state that and remove the following paragraph. If Github is not
being used, then indicate where the license information is. If GitHub is
being used link to your LICENSE.md file in the next paragraph.}
</p>
<p>
The group MAY produce test suites to support the Specifications. Please
see the GitHub LICENSE file for test suite contribution licensing
information.
</p>
<h2 id="liaisons">
Dependencies or Liaisons
</h2>
<p class="remove">
{TBD: List any significant dependencies on other groups (inside or
outside W3C) or materials. }
</p>
<h2 id="process">
Community and Business Group Process
</h2>
<p>
The group operates under the <a href=
"https://www.w3.org/community/about/process/">Community and Business
Group Process</a>. Terms in this Charter that conflict with those of the
Community and Business Group Process are void.
</p>
<p>
As with other Community Groups, W3C seeks organizational licensing
commitments under the <a href=
'https://www.w3.org/community/about/process/cla/'>W3C Community
Contributor License Agreement (CLA)</a>. When people request to
participate without representing their organization's legal interests,
W3C will in general approve those requests for this group with the
following understanding: W3C will seek and expect an organizational
commitment under the CLA starting with the individual's first request to
make a contribution to a group <a href="#deliverables">Deliverable</a>.
The section on <a href="#contrib">Contribution Mechanics</a> describes
how W3C expects to monitor these contribution requests.
</p>

<p>
The <a href="https://www.w3.org/Consortium/cepc/">W3C Code of
Ethics and Professional Conduct</a> applies to participation in
this group.
</p>

<h2 id="worklimit">
Work Limited to Charter Scope
</h2>
<p>
The group will not publish Specifications on topics other than those
listed under <a href="#specifications">Specifications</a> above. See
below for <a href="#charter-change">how to modify the charter</a>.
</p>
<h2 id="contrib">
Contribution Mechanics
</h2>
<p>
Substantive Contributions to Specifications can only be made by Community
Group Participants who have agreed to the <a href=
"https://www.w3.org/community/about/process/cla/">W3C Community
Contributor License Agreement (CLA)</a>.
</p>
<p>
Specifications created in the Community Group must use the <a href=
"http://www.w3.org/Consortium/Legal/2015/copyright-software-and-document">
W3C Software and Document License</a>. All other documents produced by
the group should use that License where possible.
</p>
<p class="remove">
{TBD: if CG doesn't use GitHub replace the remaining paragraphs in this
section with: "All Contributions are made on the groups public mail list
or public contrib list"}
</p>
<p>
Community Group participants agree to make all contributions in the
GitHub repo the group is using for the particular document. This may be
in the form of a pull request (preferred), by raising an issue, or by
adding a comment to an existing issue.
</p>
<p id="githublicense">
All Github repositories attached to the Community Group must contain a
copy of the <a href=
"https://github.com/w3c/licenses/blob/master/CG-CONTRIBUTING.md">CONTRIBUTING</a>
and <a href=
"https://github.com/w3c/licenses/blob/master/CG-LICENSE.md">LICENSE</a>
files.
</p>
<h2 id="transparency">
Transparency
</h2>
<p>
The group will conduct all of its technical work in public, e.g.
on the <a href="https://lists.w3.org/Archives/Public/public-swicg/">[email protected] mailing list</a>,
<a href="https://www.w3.org/wiki/SocialCG">w3.org SocialCG wiki</a>,
and git repositories cloned in the <a href="https://github.com/swicg">github.com/swicg/ Organization</a>
.
</p>
<p>
Meetings may be restricted to Community Group participants, but a public
summary or minutes must be posted to the <a href="https://lists.w3.org/Archives/Public/public-swicg/">[email protected] mailing list</a>.
</p>
<h2 id="decision">
Decision Process
</h2>
<p class="remove">
If the decision policy is documented somewhere, update this section accordingly to link to it.
</p>
<p>
This group will seek to make decisions where there is consensus. Groups
are free to decide how to make decisions (e.g. Participants who have
earned Committer status for a history of useful contributions assess
consensus, or the Chair assesses consensus, or where consensus isn't
clear there is a Call for Consensus [CfC] to allow multi-day online
feedback for a proposed course of action). It is expected that
participants can earn Committer status through a history of valuable
contributions as is common in open source projects. After discussion and
due consideration of different opinions, a decision should be publicly
recorded (where GitHub is used as the resolution of an Issue).
</p>
<p>
If substantial disagreement remains (e.g. the group is divided) and the
group needs to decide an Issue in order to continue to make progress, the
Committers will choose an alternative that had substantial support (with
a vote of Committers if necessary). Individuals who disagree with the
choice are strongly encouraged to take ownership of their objection by
taking ownership of an alternative fork. This is explicitly allowed (and
preferred to blocking progress) with a goal of letting implementation
experience inform which spec is ultimately chosen by the group to move
ahead with.
</p>
<p>
Any decisions reached at any meeting are tentative and should be recorded
in a GitHub Issue for groups that use GitHub and otherwise on the group's
public mail list. Any group participant may object to a decision reached
at an online or in-person meeting within 7 days of publication of the
decision provided that they include clear technical reasons for their
objection. The Chairs will facilitate discussion to try to resolve the
objection according to this decision process.
</p>
<p>
It is the Chairs' responsibility to ensure that the decision process is
fair, respects the consensus of the CG, and does not unreasonably favour
or discriminate against any group participant or their employer.
</p>
<h2 id="chairs">
Chair Selection
</h2>
<p>
Participants in this group choose their Chair(s) and can replace their
Chair(s) at any time using whatever means they prefer. However, if 5
participants, no two from the same organisation, call for an election,
the group must use the following process to replace any current Chair(s)
with a new Chair, consulting the Community Development Lead on election
operations (e.g., voting infrastructure and using <a href=
"https://tools.ietf.org/html/rfc2777">RFC 2777</a>).
</p>
<ol>
<li>Participants announce their candidacies. Participants have 14 days to
announce their candidacies, but this period ends as soon as all
participants have announced their intentions. If there is only one
candidate, that person becomes the Chair. If there are two or more
candidates, there is a vote. Otherwise, nothing changes.
</li>
<li>Participants vote. Participants have 21 days to vote for a single
candidate, but this period ends as soon as all participants have voted.
The individual who receives the most votes, no two from the same
organisation, is elected chair. In case of a tie, RFC2777 is used to
break the tie. An elected Chair may appoint co-Chairs.
</li>
</ol>
<p>
Participants dissatisfied with the outcome of an election may ask the
Community Development Lead to intervene. The Community Development Lead,
after evaluating the election, may take any action including no action.
</p>
<h2 id="charter-change">
Amendments to this Charter
</h2>
<p>
The group can decide to work on a proposed amended charter, editing the
text using the <a href="#decision">Decision Process</a> described above.
The decision on whether to adopt the amended charter is made by
conducting a 30-day vote on the proposed new charter. The new charter, if
approved, takes effect on either the proposed date in the charter itself,
or 7 days after the result of the election is announced, whichever is
later. A new charter must receive 2/3 of the votes cast in the approval
vote to pass. The group may make simple corrections to the charter such
as deliverable dates by the simpler group decision process rather than
this charter amendment process. The group will use the amendment process
for any substantive changes to the goals, scope, deliverables, decision
process or rules for amending the charter.
</p>
</body>
</html>

0 comments on commit 9474a69

Please sign in to comment.