Drupal documentation project teams are now responsible for creating and maintaining project specs for ongoing projects and submitting proposals for any new projects in the future. The reasons that are outlined in the attached document which will be a handbook page. Creating project proposals and maintaining specs are a condition of the autonomy that project documentation teams enjoy. As documentation coordinator, I will not approve any new large or even smaller, controversial projects that do not go through the vetting process of submitting a proposal. As we have already seen, email archives of disucssions alone are not suitable for managing these projects.
So please review the handbook page and let's discuss how to refine and how to implement this effectively.
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| doc_project_proposals.html | 2.99 KB | cel4145 |
Comments
Comment #1
cel4145 commentedThis page has been added to the documentation guide in the handbook. Marking as fixed.
Comment #2
cel4145 commented