-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial proposal for social media working group.
- Loading branch information
1 parent
69b5e6a
commit 6e407b9
Showing
1 changed file
with
60 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
# Social Media Working Group | ||
|
||
## Scope of responsibilities | ||
|
||
This working group will manage Django's official social media profiles. | ||
|
||
Delegated responsibilities: | ||
- The Chair can grant access to Django's official social media profiles and each member will have access. | ||
- Members can post content to Django's official social media profiles, in alignment with the working group's agreed strategy/goals, without a board review. | ||
- Members can like/repost/comment as Django, when it aligns with the working group's agreed strategy/goals, without a board review. | ||
|
||
Actions to take back to the Board for votes: | ||
- Amendments to the working group's strategy/goals. | ||
- Approval on content that is outside the agreed group's strategy/goals. | ||
- Proposals of social media campaigns for our sponsors. | ||
|
||
## Initial membership | ||
|
||
- Chair: | ||
- Co-Chair: | ||
- Board Liaison (must be an active Board member; may be the same as Chair/Co-Char): | ||
- Other members: | ||
|
||
## Future membership | ||
|
||
**Who is eligible to join? Any volunteer, or are there specific requirements?** | ||
|
||
Members must have some experience using at least one of Django's social media platforms (such as X). | ||
|
||
**How do people who want to join sign up / volunteer / express interest?** | ||
|
||
By sending an email to: `[email protected]` | ||
|
||
This email should include: | ||
- why they want to join | ||
- what experience/skills they bring to the role | ||
|
||
All members should have access to this email. | ||
|
||
**How will decisions on adding/removing members be handled?** | ||
|
||
The working group will discuss and vote (50%+1) to approve new members. | ||
|
||
If any member wishes to leave the group, they can do so without a vote. | ||
|
||
Members can propose a vote on removing a member from the working group. This needs 50%+1 agreement. | ||
|
||
## Budget | ||
|
||
The working group will have no allocated budget. | ||
|
||
## Comms within the group | ||
|
||
- Fortnightly synchronous meeting | ||
- Collaborative documents when creating a content plan and/our campaign | ||
- Private group on the Django Forum | ||
|
||
## Reporting | ||
|
||
We'll email a written report to the board every quarter. |