diff --git a/src/content/faq/faq.yaml b/src/content/faq/faq.yaml index 8c551eb..b9153c3 100644 --- a/src/content/faq/faq.yaml +++ b/src/content/faq/faq.yaml @@ -1,8 +1,11 @@ - question: "How do I join a CoreCollective working group?" answer: > Working groups are coordinated via Google Groups mailing lists. - The Google Group can be joined by visiting the group's page, or by - emailing [group-name]+subscribe@corecollective.dev. + The Google Working Group can be joined by visiting the Working Groups page, clicking on the group + title, then click join. It can also be joined by emailing + [group-name]+subscribe@corecollective.dev where the group-name is found on + the Working Group --> About page. At a future date each Working Group will have a team page which includes the group calendar and a place to store files. Until then, all WG information will be shared via the Google Group. @@ -18,7 +21,9 @@ - question: "Can I join via email instead of the Google Groups page?" answer: > - Yes, send an empty email to [group-name]+subscribe@corecollective.dev. + Yes, send an empty email to [group-name]+subscribe@corecollective.dev where + the group-name is found on the Working Group --> About page of the + associated Google Working Group. category: "Mailing List FAQs" - question: "Are working group archives public?" @@ -30,15 +35,14 @@ category: "Mailing List FAQs" - question: "How do I propose a new CoreCollective Working Group?" - answer: > -

CoreCollective is always open to the proposal of new Working Groups. A new WG must be approved by the TAC Chair / TAC.

-

Considerations regarding requesting the launch of new WGs:

+ answer: | + CoreCollective is always open to the proposal of new Working Groups. A new WG must be approved by the TAC Chair / TAC.

Considerations regarding requesting the launch of new WGs: -

The above can be sent to enquiries@corecollective.dev for consideration. A member of the leadership team will respond with additional questions and proposed next steps.

+ The above can be sent to enquiries@corecollective.dev. category: "Working Group FAQs" - question: "How does CoreCollective work?" @@ -46,13 +50,13 @@

The two primary purposes of CoreCollective is to host Working Groups and to run engineering Initiatives.

-

Working Groups are technical discussion forums on topics relevant to the Arm ecosystem. - Each working group is chaired by a CoreCollective member, with the support of a community manager - supplied by the project. +

Working Groups are technical discussion forums on topics relevant to the + Arm ecosystem. Each working group is chaired by a CoreCollective member, + with the support of a community manager supplied by the project. Members of CoreCollective may join any active working group.

-

Initiatives are engineering projects within a Working Group which are funded by CoreCollective - members via sponsorship. +

Initiatives are engineering projects within a Working Group which are + funded by CoreCollective members via sponsorship. It provides a way for multiple CoreCollective members to drive work on a shared need. The scope, priorities and approach of an initiative is set by the members who sponsor it. Management of the initiative is provided by CoreCollective on behalf of the sponsoring members.