Created Solid World and Newsletter Teams #321
Conversation
|
Question - would all members of these teams also be voting members of the Solid Team itself? |
|
Possible addition to responsibilities of each team : The team should make an effort to ensure that socially beneficial organizations and underrepresented voices are part of the target audience and highlighted in the content. |
|
Good points, @jeff-zucker . I've updated the copy. |
| # Solid World Team | ||
|
|
||
| ## Purpose | ||
| This charter sets out to explain the Solid World Team, an official webinar with the purpose of informing subscribers of happenings in the Solid ecosystem. | ||
|
|
||
| ## Membership | ||
| The Team shall consist of members who join on a volunteer basis. The members are appointed by the Director of Solid or are appointent by a group concensus at the general Solid Team meeting and will become a part of the Solid team if not already. At least one member of the Solid World Team must be present at general Solid Team meetings. | ||
|
|
||
| Individual members are to be determined. | ||
|
|
||
| ## Responsibilities | ||
| The Solid World Team is tasked with compiling information for, organizing, and hosting the Solid World webinar. Presenters for the webinar may be sourced from anywhere, but a publicly available submission form must be one source. The Team should keep a written record of the rationale for the inclusion or exclusion of submitted information. The Team should make an effort to ensure that socially beneficial organizations and underrepresented voices are part of the target audience and highlighted in the content. |
There was a problem hiding this comment.
Public requests: open PRs and have alternative methods move content towards a PR.
Private requests: make it clear to the submitter that the chosen method is private to Solid Team. This content should also make its way into a PR but accessible only to Solid Team.
Creators can curate the agenda. Also want to fully acknowledge and support Jeff's recommendation here: #321 (comment) . That should be part of the criteria and all announcements and communication should be clear.
Rotate moderators.
Open chat during the call. Make sure people can discover each other.
(If things are closed off, there is no point in having a live webinar because the talks might as well be pre-recorded, people can read text off their screen if they need to etc.)
It MUST be absolutely clear whether people have the consent to speak on behalf of any group.
| # Solid Newsletter Team | ||
|
|
||
| ## Purpose | ||
| This charter sets out to explain the Solid Newsletter Team, an official email blast with the purpose of informing subscribers of happenings in the Solid ecosystem. | ||
|
|
||
| ## Membership | ||
| The Team shall consist of members who join on a volunteer basis. The members are appointed by the Director of Solid or are appointent by a group concensus at the general Solid Team meeting and will become a part of the Solid team if not already. At least one member of the Solid Newsletter Team must be present at general Solid Team meetings. | ||
|
|
||
| Individual members are to be determined. | ||
|
|
||
| ## Responsibilities | ||
| The Solid Newsletter Team is tasked with compiling information for, writing, and sending a montly newsletter. Information for the newsletter may be sourced from anywhere, but a publicly available submission form must be one source. The Team should keep a written record of the rationale for the inclusion or exclusion of submitted information. The Team should make an effort to ensure that socially beneficial organizations and underrepresented voices are part of the target audience and highlighted in the content. |
There was a problem hiding this comment.
There is no particular need for a "team" above and beyond the current Creator role if there needs to be a group that owns the task.
As mentioned elsewhere, the whole thing can be done in the open with PRs (like TMiS and virtually everything else in the community), as well as automating the email distribution.
There was a problem hiding this comment.
There is no particular need for a "team" above and beyond the current Creator role if there needs to be a group that owns the task.
I'm not sure it is a good idea to lump these things together: get better content on sp.org; better workflow for sp.org (jekyll,etc.), create onboarding materials; create translations; create outreach materials like the newsletter; move to an RDF-based site; move to CSS. These things are all related and, to some extent, each needs a team. I'm not sure if one giant Creator role is the best way to handle that.
There was a problem hiding this comment.
-
I see your point. I'll just emphasise that I see this being more about tasks and less emphasis on roles or teams. As long as curation is an open collaborative effort, e.g., anyone being able to propose items to be included in the newsletter in the open, and that there are some curators making sure that it is a balanced representation of the activities in the Solid community, and gets sent out, great. Most of that workload can be distributed and automated as I see it.
-
As for the email-based newsletter itself, I would like to add that the canonical URL for the announcement should be available under a space that the Solid Team has actual authority over, as opposed to a random third-party controlled email campaign archive. There is nothing a whole lot here than notifying email subscribers about an HTML document. Couldn't a
solid/newsletterrepo be leveraged to address a number of things here? -
Transparency on subscriber data (excluding any identifiable information), e.g., where is the list stored, can the Solid Team or only a specific "team" can view or manage the list? How about other data that may have been collected about subscribers, e.g., interests, in the past - possibly through surveys?
This PR proposes the Solid World and Solid Newsletter teams along with some of their responsibilities.