Give the gift of Drupal. All merchandise is 50% off through 2016.
With the work going on in issues likeand elsewhere, one of the things that's going to help us move forward is defining additional people to sit in MAINTAINERS.txt. It'd be good, for a number of reasons, to define better what that actually means.
The current text reads:
"The people listed here have agreed to do more quality assurance work for
particular areas of Drupal. All of them are subject to change."
Proposed text would read something more like:
"The people listed below set architectural direction for their respective subsystems, and ensure their parts of the Drupal core issue queue are being looked after. Maintainers are both the main point of contact for new contributors who are working on issues touching a certain subsystem, as well as for core maintainers who wish to get a sanity check of proposed patches.
If you'd like to be listed here, a good place to start is performing some basic issue queue triage and clean-up in the respective subsystem, followed by reviews and patches for outstanding issues. Once you've established a contribution record for a few weeks, post an issue at http://drupal.org/node/add/project-issue/drupal to recommend yourself for MAINTAINERS.txt under the relevant subsystem."
I'm sure that needs tons of more work, but that's along the lines of what the general unwritten definition of subsystem maintainer is, I think. It'd be helpful in a recruiting effort to know what people are signing up for, and what's expected of them.
|#32||maintainers-clarify-reroll-for-D7-1263644-32.patch||1.37 KB||Tor Arne Thune|
PASSED: [[SimpleTest]]: [MySQL] 36,937 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 33,109 pass(es). View
PASSED: [[SimpleTest]]: [MySQL] 32,928 pass(es). View