Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This should not need a summary.
Somewhat required if we do #1290652: Trial adding MAINTAINER.txt folks as core 'issue queue maintainers'.
Comment | File | Size | Author |
---|---|---|---|
#22 | initiatives-alphabetical.patch | 1023 bytes | xjm |
#17 | initiative-owners-mobiletoo.patch | 1023 bytes | Bojhan |
#15 | initiative-owners-1290710-14.patch | 948 bytes | xjm |
#12 | 1290710_initiative_owners_in_maintainers.patch | 1.16 KB | gdd |
#5 | 1290710_initiative_owners_in_maintainers_txt.patch | 775 bytes | gdd |
Comments
Comment #1
gddSo other than crushing fear, I do have a valid concern with this in that it implies that the initiative owners will continue to maintain their individual projects going forward past release. It seems to me that MAINTAINERS.txt is mostly useful for identifying who is in charge after a release happens, not during the development cycle when pretty much anyone who would read it already knows. While some or all of us may continue maintaining our subsystems after release, its never been a defined part of our role, and honestly after Drupal 8 launches I may very well want to find some interested parties to keep pushing things forward while I sleep for a year or something.
Will be interested to hear how the others feel about it.
Comment #2
catchI'd see this as "maintaining the initiative", and when the initiative is done, that entry could be removed. If it results in someone maintaining a topic area semi-permanently or a new subsystem or whatever, then we can add an entry for that separately.
Comment #3
gddOK if we take it from that perspective, then I'm fine with this I think.
Comment #4
jhodgdonSee also #1263644: Define what being in MAINTAINERS.txt means, which is currently stalled since no one has commented on it in 3 weeks, sigh. Can we move that forward?
Comment #5
gddGiven that #1290652: Trial adding MAINTAINER.txt folks as core 'issue queue maintainers' has landed, it seems to be time to do this.
Comment #6
jhodgdonThat looks mostly reasonable.... I'm wondering if we should put a phrase/sentence in like the one in the components section that says "See http://drupal.org/contribute/core-maintainers for more information...", and add to that page a section expanding on what the role of an initiative maintainer is, and for that matter, what an "initiative" is?
Comment #7
webchickThis makes sense to me.
Comment #8
webchickOh, whoops. jhodgdon's points are sound.
Comment #9
jhodgdonDo we have some text already written somewhere explaining what an "Initiative" is and what the owner's role is? Front page post? Blog post? Doc page? If not, does someone want to make some up, so we can get it added to http://drupal.org/contribute/core-maintainers ?
Comment #10
webchickProbably http://drupal.org/community-initiatives/drupal-core is the best thing we have right now.
Comment #11
jhodgdonProposed content to add to http://drupal.org/contribute/core-maintainers :
-----
Initiative owners
(link to http://drupal.org/community-initiatives/drupal-core)Initiatives(endlink) are larger projects that are intended to re-architect or otherwise improve large areas of the Drupal core code-base, and which have been approved by the branch maintainers as official projects for the currently in-development release. Initiative owners have the following responsibilities:
- Coordinate work on the initiative.
- Communicate the plans, progress, and needs of the initiative to the community and the branch maintainers.
----
I actually think that might be enough... I don't think we need to get into any more detail about what the owners do here, or what initiatives are? Thoughts?
Comment #12
gddI'm fine with that text. Attached is a new patch. I moved the link to a new line at the bottom because being a plain text file the inline linking didn't seem to make much sense to me.
Comment #13
gddComment #14
jhodgdonI went ahead and added the text from #11 to http://drupal.org/contribute/core-maintainers -- If it needs editing later, we can edit it later. The joys of Drupal book pages. :)
I don't think we want the whole text from #11 in the maintainers.txt file though. I think we should do what we did for the other sections -- put a short intro and link to http://drupal.org/contribute/core-maintainers instead.
Comment #15
xjmHow about this?
Comment #16
webchickLooks good, except you need John Albin for Mobile in there too. :)
Comment #17
Bojhan CreditAttribution: Bojhan commentedadded
Comment #18
Bojhan CreditAttribution: Bojhan commentedComment #19
webchickLooks good!
Comment #21
chx CreditAttribution: chx commented#17: initiative-owners-mobiletoo.patch queued for re-testing.
Comment #22
xjmPutting the initiatives back in alphabetical order. :)
Comment #23
webchickOk. :P Trying this again.
Comment #24
catchCommitted/pushed to 8.x. Thanks!
Comment #25.0
(not verified) CreditAttribution: commentedUpdated issue summary.