Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Website working group proposal #10

Open
wants to merge 16 commits into
base: main
Choose a base branch
from
62 changes: 62 additions & 0 deletions active/website.md
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:
Copy link
Sponsor Member

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?

Copy link
Author

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.

Copy link
Sponsor Member

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.

- 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:
Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like to see two additions:

  • Who has the right in the group to merge pull requests? Is it "chair / co-chair / board liaison", or "everyone" or "no one"?
  • Who has the right to publish new content on the site?

- 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
Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Chair, Co-Chair and Board Liaison can sign off on new features
- Chair, Co-Chair and Board Liaison sign off on new features

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
Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs filling in ahead of a board review.

Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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`
Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@django/djangoproject-com-maintainters what questions must we ask if we are to build the form?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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`
Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO, it would be better to use Django discord or DSF slack, discussion would be easier than email.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a DSF slack?

Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.