Initial Website working group proposal #10
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,62 @@ | ||||||
| # Website Working Group | ||||||
|
|
||||||
| ## Scope of responsibilities | ||||||
|
|
||||||
| This is a replacement of the current maintainer team @django/djangoproject-com-maintainters. The team will own maintenance of the website codebase, and liaise with the @django/ops-team for production infrastructure considerations. | ||||||
|
|
||||||
| The duties of the working group are: | ||||||
| - Introduce new features on the website | ||||||
| - Maintain and monitor the website | ||||||
| - Ensure that information on the website is accurate | ||||||
ronnzw marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
| - Help to make the website accessible to all | ||||||
|
|
||||||
ronnzw marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
|
||||||
| ### Delegated responsibilities: | ||||||
|
There was a problem hiding this comment. I would like to see two additions:
|
||||||
| - Members triage the project’s issues and pull requests. | ||||||
| - Member maintain and monitor the website including updating versions | ||||||
| - Mentor new contributors to the website | ||||||
| - Run or support djangoproject.com sessions in DjangoCon sprints. | ||||||
| - Chair, Co-Chair and Board Liaison can sign off on new features | ||||||
|
There was a problem hiding this comment.
Suggested change
ronnzw marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
|
||||||
| ## Initial membership | ||||||
|
|
||||||
| - Chair: TBA | ||||||
| - Co-Chair: TBA | ||||||
| - Board Liaison (must be an active Board member; may be the same as Chair/Co-Chair): TBA | ||||||
|
Comment on lines
+23
to
+25
There was a problem hiding this comment. This needs filling in ahead of a board review. There was a problem hiding this comment. I'm happy to be Co-chair if it's ok for everyone |
||||||
| - Other members: | ||||||
| - Sarah Abderemane | ||||||
| - Eric Sherman | ||||||
| - Mark Walker | ||||||
| - Jason Judkins | ||||||
| - Paolo Melchiorre | ||||||
| - Sanyam Khurana | ||||||
| - Tobias McNulty | ||||||
| - Ron Maravanyika | ||||||
ronnzw marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
| ## Future membership | ||||||
|
|
||||||
| ### Who is eligible to join? Any volunteer, or are there specific requirements? | ||||||
|
|
||||||
| Members must have interest in Django and should be able to work with Django. Members must be well versed with the process of contributing to **djangoproject.com** or at least willing to be guide. We welcome all experience levels, we also welcome first time contributors. | ||||||
|
|
||||||
| ### How do people who want to join sign up / volunteer / express interest? | ||||||
| Individuals can express interest by emailing to the working group mailing list at `website-wg@djangoproject.com` | ||||||
|
There was a problem hiding this comment. Could we set up a Google Form instead? From my experience with DSF mailing lists, it’s 99% spam that we receive on those emails. It’d be nice for you to define here what kind of information people should provide when applying, rather than just expect applicants will figure it out. There was a problem hiding this comment. @django/djangoproject-com-maintainters what questions must we ask if we are to build the form? There was a problem hiding this comment. To be a part of this group, I think there should be a criterion to be a contributor to any project within the Django organization OR a member of DSF. I think then it makes sense to be part of the working group. Thoughts? |
||||||
|
|
||||||
| ### How will decisions on adding/removing members be handled? | ||||||
| Direct membership: new members may self-nominate; the WG will vote (50%+1) to approve/deny new members. The WG will vote for New Chair/Co-Chairs and decision to appoint will be based on gaining majority votes. | ||||||
|
|
||||||
| Members join the group for one year term. At the end of this term, they need to opt into staying involved to keep being | ||||||
| a member of the group. | ||||||
|
|
||||||
|
|
||||||
| ## Budget | ||||||
| No allocated budget | ||||||
|
|
||||||
| ## Comms | ||||||
| - Private channel in the DSF slack | ||||||
| - A mailing list that we'll create, `website-wg@djangoproject.com` | ||||||
|
There was a problem hiding this comment. Could you explain why you’re proposing a mailing list? They tend to run slow in my experience and are prone to spam. Django has a Discord server where we could have a private channel. The DSF has a Slack workspace. Could we use either of those? There was a problem hiding this comment. Well this is open to discussion, maintainers can decided where they want comms to be. I just remembered that l got involved on the site through the DSF individual members mailing list so i just assumed. There was a problem hiding this comment. IMO, it would be better to use Django discord or DSF slack, discussion would be easier than email. There was a problem hiding this comment. I see we now have both the Slack channel and a mailing list. @ronnzw I think you need to define how each of those would be used, or if it’s open to discussion then explicitly write it here. Keep in mind the more clear-cut the group charter is, the easier it is for people to consider joining and for the board to review. So if discussions need to happen, now is the best time to raise this question with interested members. @jcjudkins yes, the DSF has a Slack Workspace for internal matters. Largely this has been used for paid employees, the board of directors, and a few working groups now. There was a problem hiding this comment. IMHO slack works fine for the working group. Mailing list can be for discussion among larger audience. |
||||||
|
|
||||||
| ## Reporting | ||||||
| We'll email a written report to the board every quarter. | ||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From this description it’s unclear to me if this working group also works on the website’s contents, or just specific things that count as "features"?
For example if someone from our Security team wants to publish a post on the website’s blog – do they reach out to this working group, or elsewhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had asked for help on this particular item and you are the one who provided the wording that is on there. I'm happy if you can add on that you feel would make sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ronnzw cool! Let‘s see what others think then.