ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Working on this initiative
2
To provide any feedback on this effort, add a comment on the META issue: https://www.drupal.org/project/contribution_events/issues/3342443
3
To volunteer to help, add a comment on the Volunteers tab and/or comment on this issue: https://www.drupal.org/project/contribution_events/issues/3342447
4
To suggest a project, add a comment on the Projects tab and/or comment on this issue: https://www.drupal.org/project/contribution_events/issues/3342468
5
6
Process for co-maintaining projects without compatible dev branch
7
0. If you do not have permission to opt-in to security coverage, you will need to have someone who does become a co-maintainer first, check in via the #d10readiness channel
8
1. Review projects in Projects tab
9
2. Find a project where you know how to test the module/theme
10
3. Verify the project does not already have pending co-maintainer issues
11
4. Check the issue queue for Drupal 10 compatibility issues
12
5. Check the dev branch to see if it is already D10 compatible
13
6. If you want to co-maintain, comment on the Projects tab for that project in the "Who to adopt?" column (alternatively, DM Kristen Pol for edit access)
14
7. Create an issue to offer to co-maintain (example)
15
7a. Add a related issue on that comment to META noted at the top of this tab
16
8. IMPORTANT Contact the project maintainer(s) via Drupal.org or by other means [see more details in this issue]
17
9. IMPORTANT Add information in the issue summary showing that you have contacted the maintainer and who you contacted and what you sent [see more details in this issue]
18
10. You have to give the maintainer 14 days to respond
19
11. After 14 days, if there is no response, you can move the issue into the projectownership queue (note, only do this if you can opt-in to security coverage)
20
12. If co-maintainership is granted or is not granted, add a comment on the Projects tab
21
13. If granted, provide issue credit to those involved on the issue to offer to co-maintain
22
14. Go through all Drupal 10 compatibility issues and review/test as appropriate and update issue credit as appropriate
23
15. Once all D10 issues are ready, merge into the appropriate dev branch (be careful if there are multiple branches that you are using the correct one; ask in #d10readiness if you aren't sure)
24
16. Mark all merged issues as Fixed and verify issue credit is correct (make sure to give yourself credit for this work; you can also give credit manually to anyone who helped you offline in the Slack channel)
25
17. (Optional) Review the RTBC issues and review/assess/test each as appropriate to merge what you can (make sure to give issue credit as appropriate)
26
18. If you don't have access to create releases, create an issue for the maintainer to create a release (example)
27
19. If you have access to create releases, determine the release number to use (if in doubt, ping us in Drupal #d10readiness Slack, there are opinions :)
28
20. Create a tag with that version
29
21. Through the project page, click "Add new release" and choose the new tag and add descriptive text
30
22. Through the project page, click "Administer releases" and adjust as appropriate (if in doubt, ping us in the Drupal #d10readiness Slack)
31
23. Add comment on the Projects tab with the status
32
24. If you won't be continuing to maintain the project, update the project status to "Unsupported" and add a note at the top of the page that the project is no longer supported
33
25. Ping us in the #d10readiness channel so we can celebrate your win!
34
35
Resources
36
Slack thread on project suggestions
37
Slack thread for soliciting volunteers
38
How to become project owner, maintainer, or co-maintainer
39
Old abandoned project process page is missing but is archived
40
Co-maintaining projects
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100