Once you have proposed a group and it has been launched, here are ways to get your group up and running:

• Every group must have one or more Chairs. Read how to choose your Chair(s).
• Review the Community and Business Group process and contributor agreements. These govern how people participate, and the copyright and patent licensing commitments that people (or organizations) make upon joining a group.
• Review your group’s home page and the infrastructure available to your group to get work done.
• Your group has a blog (currently WordPress) that you may use to post news. Each group’s posts are also disseminated on the Community and Business Group home page.
• We recommend that you create a charter that explains clearly what the group will do and why people should join it. Please consult our charter template. The group may publish the charter in its wiki or as a WordPress page, then link to it from the group’s home page. Please contact team-community-process@w3.org to have a link added to the group’s home page.
• Invite people to join the group; read more about how to join a group.
• The Group Chair(s) are authorized to publish reports by the group; see how to publish a report.

Once you are up and running, see good practice for running a group.

Questions? Write to team-community-process@w3.org.

Yes, see this HTML slide set from September 2011. If you have suggestions for the presentation or would like to improve it, please contact Ian Jacobs on site-comments@w3.org.

W3C has a number of types of groups (see the comparison of group types). These questions can help you choose the right type:

• Do you want a W3C standard? If so, choose a Working Group.
• If you don’t want a standard but do want W3C staff resources dedicated to your group? If so, choose an Interest Group.
• Do you want to be able to work in non-public space, have some support from W3C staff, and high-bandwidth connectivity with other groups? If so, choose a Business Group.
• Otherwise, choose a Community Group.

First, some important similarities:

• Anyone may participate in either.
• The group can address topics of their choosing.
• There is no end date.
• Participants agree to the same IPR policies (except that a Business Group may choose to distribute a report under the W3C Document License)

Some important differences:

• There is no cost to participate in a Community Group. Non-Member organizations and unaffiliated individuals pay a fee to participate in a Business Group.
• As a result, Business Groups benefit from additional W3C staff involvement. By default, a Community Group has no staff involvement (other than oversight of the program as a whole).
• Community Group proceedings are public. Business Groups may choose public or non-public.
• Business Groups have access to teleconference facilities.

For more details and a comparison with other W3C group types, see the full process comparison.

Community and Business Groups replaced Incubator Groups (XGs).

W3C will continue to charter Working, Interest, and Coordination Groups. When deciding whether to create an Interest Group or a Community/Business Group, note that:

• all Interest Group Charters require Member review (even those that are merely mailing lists); Community and Business Groups do not.
• Interest Groups can have Team Contacts; Community and Business Groups do not have that level of staff connectivity.
• Community and Business Groups have a stronger IPR policy than Interest Groups.

No. Anyone may participate. For Business Groups, please see the fees for participation by organizations and individuals that are not already W3C Members.

If participation in a Community or Business Group generates interest in getting more involved in W3C as a Member, please see information about W3C Membership.

Yes. However, the Community Group Reports must be available in English. Groups are encouraged to provide periodic updates in English for the benefit of the global community.

W3C encourages you to spread the word about the work that you are doing in Community and Business groups, and to encourage participation. It is appropriate to refer to this as “work happening at W3C.” Please do not say or imply that W3C “endorses” the work (as there is no process for gauging endorsement of Community Group work by other W3C groups or the Membership as a whole).

Community Groups and Business Groups themselves do not create Web standards (though their outputs may advance to the standards track in a Working Group). Therefore, please do not refer to Community or Business Group work as “standards work” or “draft standards,” and point out explicitly that these are not W3C Standards/Recommendations. See the related question: Are Community and Business Group reports W3C standards?.

No. However, the W3C Community Contributor License Agreement (CLA) and W3C Community Final Specification Agreement are designed to facilitate transition to the W3C Recommendation Track for standards development. See the related question: How can I talk about W3C endorsement of this work?.

No. It complements the Recommendation Track and is designed to facilitate transition to the Recommendation Track. W3C is an ISO/JTC1 PAS Submitter and only submits W3C Recommendations (not Community Group Reports or other report types) to ISO.

When a Community Group or Business Group wishes for a Working Group to adopt one of its Specifications, W3C facilitates the transition to the W3C Standards Track in a number of ways:

• Continuity of IPR commitments. The Community Group Agreement is designed to ensure smooth transition of IPR commitments from Community Groups to Working Groups.
• Continuity of participation. When a Working Group takes up a Community Group Report, non-Member employees may continue their participation in the Working Group for a limited duration while their employer makes the transition to Membership. The individual’s employer must have fulfilled the organizational patent requirements of the Community Group Agreement.
• Adoption by an Existing Working Group. If W3C has chartered a Working Group with a scope that encompasses the deliverable of a Community Group, the Working Group may adopt it without needing to recharter.

See How to transition work from a Community Group to a Working Group for more information.

The W3C Recommendation track can be characterized (roughly) as a series of requirements for review and implementability. If a Community or Business Group fulfills those criteria, a subsequent Working Group can advance it quickly from draft to standard. The theoretical “fast track” would be for a Working Group to publish a Last Call Draft (as the first Working Draft), process issues, then request to advance to Proposed Recommendation directly (if implementation criteria have already been satisfied).

There are other ways for Community and Business Groups to accelerate standardization. Because there are fewer barriers to participation it should be easier to convene the right stakeholders at the table right from the start (and to grow or change as needed). This makes it easy, for example, to identify the “right” requirements up front, which helps ensure that a future standard is more quickly and widely adopted.

Please write to team-community-process@w3.org. In addition:

• If you have suggestions for the CG/BG Web site, you can write to site-comments@w3.org (public archive).
• For larger suggestions about the program as a whole or new infrastructure features, you may also wish to join the Community Council.

1. Get a W3C account (if you don’t have one).
2. Be aware of the copyright and patent policies that govern contributions to any Specifications.
3. For Community Groups, there is no fee for anyone. Be aware, however, there are fees for participation in a Business Group by non- W3C Members.
4. Push the “Join” button for any current group. If you are not logged in, you will be prompted to log in. If you already have an account but we don’t know your affiliation (e.g., your employer) we will prompt you to update your account.

What you see after pushing the Join button depends on the affiliation you have declared in your user account. This is because joining a group involves agreeing to the W3C Community Contributor License Agreement (CLA). Below we describe the join process for different affiliations.

If you work for a W3C Member

If you work for a W3C Member:

• If you are a Member Advisory Committee Representative, you may join a current group immediately on behalf of your organization. After joining, you may nominate others from your organization to participate in the group.
• If you are otherwise an employee of a W3C Member, you may push a button that sends a request to your Advisory Committee Representative to join a current group on behalf of your organization. You do not join the group directly yourself. You will be informed if your Advisory Committee Representative accepts (or declines) to join the group.

If you work for a non-Member organization

• If you are affiliated with a non-Member organization, you may join a current group immediately on behalf of the organization, which we recommend in most cases.
• Or, you may request to participate without representing your affiliated organization, but those requests are subject to approval at the discretion of the W3C Staff. We attempt to address requests within one business day. W3C publishes guidelines for evaluating individual requests to participate in a group.

Other Affiliations

• If you are affiliated with the W3C Staff, you may join immediately as an individual.
• If you have no affiliation with any organization, you may join immediately as an individual.

1. Get a W3C account (if you don’t have one).
2. Push the Create a Community Group button. If you are not logged in, you will be prompted to log in.
3. Enter a name, description, and short name for the group. Please read the instructions on that page, especially about syntax restrictions for short names. For information on the group description, see When I propose a Community or Business Group, what should I say in the description?

If you are new to the W3C Community, your proposal is evaluated by the W3C staff before being made public. This review happens within three business days, but may take longer depending on staff availability. The staff may contact you with suggestions to enhance the description, or to consider engaging with an existing group rather than creating a new one. The W3C staff is responsible for advancing the new group to “Proposed” or rejecting spammy proposals.

Proposals from existing W3C Community members are announced as “Proposed” without staff review. However, the W3C staff may contact the person who proposed the group to discuss the description.

All proposed groups are listed on the proposed groups page. The three most recent proposed groups are displayed on the Community Group home page. The person who proposed the group receives an email notification that the proposal is now available, as well as some information about next steps.

Once five people push the button to show their support for the group, W3C will create the infrastructure and announce the launch of the group. All launched (and not yet closed) groups appear on the current groups page. The three most recent launched groups are displayed on the Community Group home page. All people who supported the group receive an email announcing the launch; those emails are archived at public-council@w3.org. Finally, a call for participation in the new group is created as the first blog post on the group’s home page.

Note: After support from the fifth person, please expect one business day before the W3C launches the group.

To encourage participation, a Community or Business Group description should be short, but include enough information to enable people to understand the purpose of the group and what they will do. We recommend including the following information in the group description:

• The group’s mission. For example, the first sentence might begin: “The mission of this group is to ….”
• The group’s primary activity. In particular, it is important to indicate whether the group will publish reports. If, on the other hand, the group will primarily be a discussion group, or will produce deliverables that are not reports (e.g., code, tests, use cases, etc.), please state that clearly.
• Who should participate, that is desired skills and expertise.
• Whether the group will publish one or more Specifications. If the group plans to publish Specifications, please include the sentence “This group may publish Specifications.” If the group does not plan to publish Specifications, this will make it easier for people to join the group (as there will be no patent licensing commitments). In this case, please include the following sentence in the description: “This group will not publish Specifications.”

The description may include limited HTML markup (including headers, paragraphs, lists, and links).

To avoid long descriptions, some groups provide details about their scope of work, deliverables, and operations in a separate document that is called a charter. We recommend using the Community Group charter template; see how to get started in a new group for more information.

To change a group’s description at any time (even after the launch of the group), send a request to team-community-process@w3.org.

1. Get a W3C account (if you don’t have one).
2. Push the “Support group” button for the group you wish to support. If you are not logged in, you will be prompted to log in.

Whenever you are logged in, you can see which groups you have already supported in the list of proposed groups.

Only the Advisory Committee Representative of a Member organization may join a group (or approve requests to join), and does so on behalf of the organization. Our infrastructure makes it easy for other Member employees to send requests to their Advisory Committee Representative to ask them to join a group.

See also the Guidelines for Evaluating Individual Requests to Participate in a Group.

 

 
No.

Yes. The primary question from W3C’s perspective is: who controls the patent and copyrights to contributed materials? If the project controls the rights, W3C will ask that a representative who has the authority to sign the CLA on behalf of the project join the group.

While Business Groups do not have full-time staff contacts, W3C management does assign a staff liaison to help facilitate the work of the group. The liaison shares expertise about W3C and helps connect the group chair(s) with chairs from other groups. The liaison is not generally a full-time group participant. For more information about the role of the team liaison, and to identify the liaison for a particular group, please contact <team-community-process@w3.org>.

Yes. You do not need to join the group if you only intend to follow the group’s work or engage in discussions without making material contributions; you may use the public mailing lists for those purposes. However, if you plan to contribute materially to the development of a report, W3C requires that you participate under the CLA.

W3C does not currently have a formal policy for pseudonymous participation, but is interested in understanding how best to serve the community in this situation. When a person’s legal identity is unknown to the community, W3C must nonetheless ensure sufficient IPR confidence within the community for related contributions and take into account existing participation policies. The Chairs of a group and the individual who wishes to participate pseudonymously should contact team-community-process@w3.org with any questions.

Yes. See the participation policies of the CG Process and the W3C Code of Conduct.

Yes. See the participation policies of the CG Process and the W3C Code of Conduct.

No. However the Community Development Lead is empowered to do so; see the participation policies.

Yes, both face-to-face and teleconferences.

For teleconferences, Business Groups have access to W3C teleconference services. Community Groups may use external teleconference services.

To close a group, send a request to team-community-process@w3.org.

When a group is closed, the following happens automatically:

• The list of participants is emptied and people can no longer join the group.
• The group’s home page indicates that it has been closed and the date of closure.
• The group appears in the list of past groups.

By default, we do nothing to the group’s home page (blog), mailing lists, and wiki. However, we recommend:

• Updating the group’s home page description to let people know where to turn (e.g., that work has moved to a W3C Working Group, etc.). The group can augment this communication with a blog post as well.
• Closing mailing lists that will no longer be used. Please write to sysreq@w3.org to request that a mailing list be closed, which means that content is archived but people can send no new mail to the list.

From time to time W3C closes inactive groups, in part to make it easier for the community to find active groups. Per the Community Group process, a group is deemed inactive if there are fewer than 3 participants, if there are no chairs, or if there does not appear to be any activity in the group (e.g., email or activity in known GitHub repositories) within the past six months.

Ten (10) days before closing a group for inactivity, W3C alerts the group participants. Group participants may petition to keep the group open, but must provide rationale for doing so.

See the Community and Business Group Process, which in turn links to the IPR Agreements.

We expect the W3C Advisory Board to discuss what, if any, formalization is required (e.g., integration into the W3C Process Document, additional legal discussion, etc.).

See the Patent and Copyright Policy Summary.

By joining a Community Group, you agree to the Contributor License Agreement (CLA), either on behalf of your employer or yourself. There is no need to otherwise sign the CLA.

The W3C Community Contributor License Agreement (CLA) includes a copyright grant (section 2) as does the Final Specification Agreement. In either case, the grant is directly from the person who signs the Agreement to “any person or entity who exercises copyright or patent rights granted under this CLA…”

Each group may establish its own mechanisms for recording contributions provided that the history of Contributions must must be archived permanently on the W3C Web site (see the process for details).

For instance, if the group is developing a Report in a wiki or repository, the group can establish that each contribution is included in the Report directly by the Contributor.

One mechanism available to all Community and Business Groups is a publicly readable “contrib” mailing list where participants can clearly record their Contributions. Read more about group mailing lists.

In some groups, there may be an Editor whose job it is to record Contributions from other participants. When participants entrust the Editor with the job of recording contributed material, the group must be diligent about recording the true source and date of the Contribution when the Editor is merely transcribing the Contribution. This is particularly important when a Contribution is initially spoken (e.g., during a teleconference) and transcribed by the Editor or some other party. The date of an oral Contribution is the date on which it was spoken.

Here is a rough summary of primary similarities and differences between the W3C Patent Policy and the Community Group IPR policies.

Patents

Similarities:

• Participants make Royalty-Free Licensing Requirements as defined in the W3C Patent Policy. However, the scope of defensive suspension is broader in the W3C Patent Policy.
• Participants have no disclosure obligations over the deliverables of the group.

However, the policies take different approaches in order to meet different needs (e.g., favoring lower risk or quicker startup):

• The W3C Patent Policy is “opt-out”: Participants make commitments based on charter scope, then have exclusion opportunities for each Recommendation.
• The Community/Business Group policy is “opt-in”: Participants first make commitments over their own contributions (with a limited opt-out period in case of mistakes). Then, when a report is stable, participants make a voluntary “final text commitment” over the group report as well as an RF commitment for material that advances to the Recommendation Track. (There are additional details regarding exclusion in such cases.)

Copyright

Differences:

• The Community Group copyright is permissive for the creation of derivative works. The W3C Document License is not.

Related resources:

• W3C Patent Policy FAQ
• Business Benefits of the W3C Patent Policy

To meet a different set of expectations. For instance, W3C did not adopt the W3C Patent Policy as-is for Community Groups because it is closely aligned with the W3C Recommendation Track and group chartering process, neither of which is used in Community Groups.

Because organizations ask to evaluate charter scopes (via Advisory Committee Review and whatever internal legal reviews they conduct) this requires extra start-up time. A goal in designing Community Groups was to reduce that start-up time, and so we concluded that a different IPR policy was necessary.

The resulting IPR policy has two parts: a Contributor Agreement (CLA) and a “Final Specification Agreement.” The purpose of the CLA is to allow people to join a group, determine themselves what they want to contribute to the group, and thus determine the extent of their licensing commitment. Because there is no charter scope that must be reviewed by legal, groups can start immediately and people can join them without extensive review. People can choose to contribute or not, and the CLA limits their obligations to their own Contributions to a Specification.

This approach provides a base level of protection to implementers. To secure more protection, there is a second phase where people make a voluntary Final Specification Commitment over the full text of a Report.

W3C has designed the CLA and Final Specification Agreement to integrate smoothly with the W3C Patent Policy. For instance, the new Agreements reuse the definitions of Essential Claims and Royalty-Free License of the Patent Policy. In short: we reused what we could from the existing policy, and adapted the rest to match a new set of expectations.

Both types of groups operate under the same legal agreements (the process, CLA, and Final Specification Agreement), except as follows:

• Business Groups may publish Reports under the W3C Document License.
• Non-Member and individual Business Group participants also sign a contract regarding payment, called the Business Group Agreement.

No. The two-Agreement system was designed to make it easier and faster to start groups: in general, it is possible to start a group with little understanding of the direction of a report. However, in exchange, Participants may choose not to sign the Final Agreement, if, for example, they are not satisfied with the emerging report.

Of course, walking away from a report can raise questions about whether the Participant holds Essential Claims on text not covered by the CLA. To reduce community doubt, these Participants may choose (but are not required) to disclose relevant information about any Essential Claims.

Please also note the Non-Circumvention provision of the CLA.

Each group has a public communications channel that anyone may read and write to, without having those people sign the Contributor Agreement (CLA). While this arrangement makes it easier for people to be part of a conversation, accepting text contributions from non-participants (via any channel, electronic or otherwise) raises significant IPR concerns for both participants and implementers. Each group, therefore, also has a contribution list that is only writable by group participants.

The Contributor Agreement is intended to be lightweight to encourage organizational IPR commitments, which benefit all. Some points that can be communicated to organizations that are reluctant to participate:

• The obligations under the CLA only apply to Community Group Reports. If the group does not publish a report, there are no patent licensing obligations. And the CLA includes no disclosure obligations.
• A participant only has licensing obligations for contributions. No contributions; no obligations.
• Even after a contribution, there is a 45-day opt-out period starting on the date that the contribution first appears in a Report. Thus, something contributed in error may be withdrawn within that window.
• Even after a contribution, if the material is not included in a Report within 6 months, the licensing obligations under the CLA dissolve.
• Even after a contribution, if the contribution is modified during the evolution of the Report, the licensing obligations under the CLA dissolve.
• The final specification commitment is voluntary.

No.

As described in the FAQ question How do we publish a report?, when a Final Report is published, the group is informed of an opportunity to make a commitment under the Final Specification Agreement. The announcement includes a link to a page that lists commitments for that report as well as group participants that have not yet made a commitment. On that commitments page there is a button for participants to make a commitment.

Yes.

The CLA defines a limited opt-out that requires “at minimum, in writing using the same communication mechanisms that were used to submit the corresponding Contribution and must include the exact material being withdrawn.” W3C provides a public mailing list that is the recommended mechanism for recording contributions and opt-outs.

No. However, you may, at your option, grant a non-assert in addition to the license provisions of the agreements (see “Optional, Additional Patent Grant.”). Some examples of non-assert agreements include OWF agreements, the Oasis non-Assert Covenant, or the Microsoft Open Specification Promise.

W3C does not restrict authors’ reuse of their contributions to Community and Business Groups.

Yes, outside the Specification.

Yes, under the copyright terms of the CLA. Note, however, that patent commitments extend only to implementations of the Community Group Report or any W3C Recommendation including that work; please see the Community Group policies for more detail.

No.

W3C Community Logo by W3C is licensed under a Creative Commons Attribution 3.0 Unported License. Based on a work at www.w3.org.

The logo is available as PNG and SVG.

Previous versions are available:

Process

• Process Beta (pre 8 August 2011)

Contributor License Agreement

• CLA Beta (pre 8 August 2011)

Final Specification Agreement

• FSA Beta (pre 8 August 2011)

First, ensure that the report can be accessed via a URL. If not a final report, it may be assigned a URL using the “page” feature of the group’s WordPress instance, or github. If the report is a final report, it must be published on the W3C Web site. This can be achieved through mechanisms available on GitHub. If you have questions, please write team-community-process@w3.org.

The editor ensures that the report follows a small set of requirements. The requirements page provides information about styles, copyright, etc.

The group must have a Chair in order to register and announce the publication; see how to choose a Chair. The Chair registers and announces the report. When the Chair is logged in, on the group’s home page in the section on Reports (near the top) Chairs will find a link to a page to publish reports. The page for publishing allows Chairs to announce new drafts or to advance existing drafts to “final” status. The following happens when the Chair “publishes” a report:

• The report is added to the list of reports for the group and appears on both the group’s home page and on the global Reports page.
• The system announces the publication on the group’s blog. This announcement also appears on the Community and Business Group home page and is sent as an email to the group’s public list.
• In the case of a Final Report, the announcement invites people to make commitments under the Final Specification Agreement (FSA). For each final report there is a page that lists commitments as well as group participants that have not yet made a commitment. On that commitments page there is a button for people to make a commitment under the FSA.

For information on style sheets, see the report requirements.

These are the recommended steps for first integrating a report developed outside of a CG into a group:

• Send a copy of the document to the group’s “contrib” list. This allows people to refer to an unchanging text.
• Have all the contributors to the text send follow-up emails to the group’s contrib list stating that they agree to the terms of the CLA for the entire text of the report. These commitments should be made on behalf of organizations rather than just individuals. If an organization has made a significant contribution to a report but does not agree to the terms of the CLA, this is likely to hinder the progress of the report by raising red flags for implementers. When W3C Members have contributed to a report, their Advisory Committee Representatives should send the commitment emails to the contrib list.
• Ensure that the document in the github repository satisfies the Community Group Report Requirements.
• Publish the document on the Community Group site. Group Chairs are authorized to publish, and log in to do so. Use the github URI to identify the document being published; this allows CG site users to find the latest version as the document evolves.

Yes, one can use XML namespaces and RDF namespaces in Community Group Reports. Use http://www.w3.org/ns/shortname (where the shortname is the one used for your group, or based on it). For more information about W3C’s policy regarding these types of namespaces see URIs for W3C Namespaces.

Note: The term “namespace” here does not refer to the URL of the Community Group Report itself; see how to publish a report for information about report URLs.

W3C does not register media types in the W3C tree of the IANA registry for CG/BG reports. W3C does have a process for registering media types for Working Group Recommendations. If you have any questions about media type registration, please write to team-community-process@w3.org.

Groups use different tools to publish reports. If WordPress or the group’s wiki are used, they offer revision history mechanisms to track changes.

W3C also has an online HTML diff tool.

Please see our documentation of tools and infrastructure.

Participants choose their own chairs. Please see the recommended approach for choosing chairs.

Once chairs have been chosen anyone in the group (or the W3C staff) can log in and record that information for the group; for details see the tool to identify group chairs.

For some actions, yes. W3C infrastructure is used to record who joins or leaves a group. A Community Group may use its own infrastructure to host communications, as long as those communications are public and archived permanently. The recommended way to accomplish this is to use a W3C archived mailing list in conjunction with the offsite system.

Draft reports may be published anywhere, although final reports are published on W3C’s site.

Please send comments to site-comments@w3.org. See our issue tracker.

W3C uses HTTP-based authentication for most pages on its site. This means that when you attempt to access a resource that requires a user name and password, you are prompted. Thereafter you are logged in. But there is no log out procedure for HTTP-based authentication.

We also use some tools (blogs, wikis) that have their own login processes that are based on cookies. These tools have log in and log out procedures. The username and passwords are the same as for other pages.

In W3C Working Groups, people not affiliated with a W3C Member need to be approved as “Invited Experts” in order to participate. For most Working Groups, the staff evaluates each such request, and Chair approval is required as well.

Prior to Community Groups, W3C did not maintain affiliation information for Invited Experts; those accounts are simply noted as being non-Member accounts. However, for Community Groups, in the interest of transparency about the source of contributions to a Report, we are requiring people with Invited Expert accounts to update their affiliation information. There may be a delay of at most 1 day before your request is processed by W3C staff.

Once you have recorded your affiliation information (or that you have no employment affiliation with any organization), you may join Community and Business Groups.

If you are participating in a group and are affiliated with an organization that becomes a W3C Member:

• W3C updates your account to record your affiliation with a W3C Member.
• This automatically ends your participation in the Community Group. We do this because changes in employment change representation under the Contributor Agreement (CLA).
• Your (now Member) organization is encouraged to rejoin the group. For W3C Members, the Advisory Committee Representative is the only person authorized to join a Community Group. After joining, the Advisory Committee Representative nominates you as a participant.

Note: Some of these actions happen automatically, others manually. W3C expects to streamline the process of organization transitions and their impact on participants.

Your user account includes the list of all W3C groups in which you are participating.

Please log in to our Community Group site with your W3C username, not your email address.

People have a “W3C account” which is then used to create a “WordPress account”. We have limited (LDAP) synchronization between the accounts (but plan to improve our LDAP sync). As a result, there are a small number of issues that can occur if the accounts are not in sync:

• You cannot log in to WordPress and an error message indicates that there is already an account with your email address. Solution: W3C has to update your email address in your WordPress account.

When you join a group, you are automatically subscribed to the group’s list(s). The way our lists are currently configured for these groups, you cannot unsubscribe from the list. However, if you leave the group, you are automatically unsubscribed. To leave a group, visit the group’s home page; there is a “leave” button on the right side.

Update your photo; you will be prompted to log in if you have not done so already.