You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: active/website.md
+8-6
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,16 @@
1
1
# Website Working Group
2
2
3
-
## Scope of responsibilities
3
+
## Responsibilities
4
4
5
5
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.
6
6
7
7
The duties of the working group are:
8
8
- Introduce new features on the website
9
9
- Maintain and monitor the website
10
10
- Help to make the website accessible to all
11
-
12
-
13
-
### Delegated responsibilities:
14
11
- Members propose, triage, analize, discuss and implement new features
15
12
- Members triage the project’s issues and pull requests.
16
-
-Member maintain and monitor the website including updating versions.
13
+
-Members maintain and monitor the website including updating versions.
17
14
- Mentor new contributors to the website.
18
15
- Run or support djangoproject.com sessions in DjangoCon sprints.
19
16
- Chair, Co-Chair and Board Liaison can sign off on new features.
@@ -40,6 +37,11 @@ The duties of the working group are:
40
37
41
38
Members must have interest in Django and should be able to work with Django. Members must go through [contributing](https://github.com/django/djangoproject.com/blob/main/README.rst) to **djangoproject.com** or at least willing to be guide. We welcome all experience levels, we also welcome first time contributors.
42
39
40
+
### Access granting and deployment
41
+
Initial onboarding phase where only Chair and Co-Chair have permissions to merge. After onboarding of 6 months, other group members who have proven their expertise will be granted merge permissions at the discretion of the chair and co-chair. Ops team will retain access, and in case there are site infrastructure issues, would be able to restrict permissions. Process can be reviewed in the future with the ops team if needed.
42
+
43
+
The deployment of the website will be done via a ping via @django/ops-team on the pull request to deploy the branch.
44
+
43
45
### How do people who want to join sign up / volunteer / express interest?
44
46
Individuals can express interest by opening a PR to this working group repository, using a template, adding their names in the list of members.
45
47
@@ -55,7 +57,7 @@ Sums may be provided for specific activities (e.g. external consultancy, graphic
0 commit comments