|
| 1 | +# Social Media Working Group |
| 2 | + |
| 3 | +## Scope of responsibilities |
| 4 | + |
| 5 | +This working group will manage Django's official social media profiles on behalf of the Django Software Foundation. |
| 6 | + |
| 7 | +The goals of the group are: |
| 8 | +- Promote the use of Django among the World Wide Web development community. |
| 9 | +- Protect the framework's long-term viability through campaigns and sponsor relations. |
| 10 | +- Ensure the DSF’s Code of Conduct is maintained on its media channels. |
| 11 | +- Assist the board in posting official news and updates from the DSF. |
| 12 | + |
| 13 | +The group opts to manage platforms that best achieve these goals. |
| 14 | +This may be a subset of those for which Django has accounts. |
| 15 | + |
| 16 | +Delegated responsibilities: |
| 17 | +- The Chair, Co-Chair and Board Liaison can grant access to Django's official social media profiles to other group |
| 18 | + members as needed. |
| 19 | +- Members can post content to Django's official social media profiles, in alignment with the working group's agreed |
| 20 | + goals, without a board review. |
| 21 | +- Members can perform actions such as “like”, “repost” or “comment” as Django, when it aligns with the working group's |
| 22 | + agreed goals, without a board review. |
| 23 | +- Members can perform maintenance and monitor the automations which post DSF news and updates to social media channels. |
| 24 | +- Members can enforce the Code of Conduct. This may include moderating comments that do not meet our CoC or blocking |
| 25 | + users that grossly or repeatedly violate the CoC. |
| 26 | + |
| 27 | +Actions to take back to the DSF Board for votes: |
| 28 | +- Amendments to the working group's goals. |
| 29 | +- Approval on content that is outside the agreed group's goals. |
| 30 | +- Proposals of social media campaigns for our sponsors. |
| 31 | +- Proposal to have a new social media profile on a platform. |
| 32 | +- Proposal to retire a social media profile from a platform. |
| 33 | + |
| 34 | +## Initial membership |
| 35 | + |
| 36 | +- Chair: Benjamin Balder Bach |
| 37 | +- Co-Chair: Bhuvnesh Sharma |
| 38 | +- Board Liaison (must be an active Board member; may be the same as Chair/Co-Chair): Thibaud Colas |
| 39 | +- Other members: |
| 40 | + - Cory Zue |
| 41 | + - Jason Judkins |
| 42 | + - Sarah Boyce |
| 43 | + |
| 44 | +## Future membership |
| 45 | + |
| 46 | +### Who is eligible to join? Any volunteer, or are there specific requirements? |
| 47 | + |
| 48 | +Members must have demonstrable experience with social media platforms, and be registered as a Django Software Foundation |
| 49 | +Individual Member. |
| 50 | + |
| 51 | +### How do people who want to join sign up / volunteer / express interest? |
| 52 | + |
| 53 | +A form will be made available in a public space (once created this will be linked to here also). |
| 54 | + |
| 55 | +This form will include questions confirming: |
| 56 | +- their DSF membership |
| 57 | +- why they want to join |
| 58 | +- what experience and skills they bring to the role |
| 59 | +- links to their social media profiles |
| 60 | + |
| 61 | +### How will decisions on adding/removing members be handled? |
| 62 | + |
| 63 | +The working group will discuss and vote (50%+1) to approve new members. |
| 64 | + |
| 65 | +Members join the group for a 6-month term. At the end of this term, they need to opt into staying involved to keep being |
| 66 | +a member of the group. |
| 67 | + |
| 68 | +If any member wishes to leave the group before the end of their term, they can do so without a vote. |
| 69 | + |
| 70 | +Members can propose a vote on removing a member from the working group. This needs 50%+1 agreement. |
| 71 | + |
| 72 | +## Budget |
| 73 | + |
| 74 | +The working group will have no allocated budget. |
| 75 | + |
| 76 | +## Comms within the group |
| 77 | + |
| 78 | +- Fortnightly synchronous meeting |
| 79 | +- Collaborative documents when creating a content plan and/our campaign |
| 80 | +- Private channel in the DSF slack |
| 81 | + |
| 82 | +## Reporting |
| 83 | + |
| 84 | +We'll email a written report to the board every quarter. |
0 commit comments