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.All project ownership issues got moved to the new issue queue https://drupal.org/project/projectownership. That queue has 3 components:
- Ownership transfer - for when people want to transfer project ownership to one another
- Abandoned / unsupported projects - for when people want to mark their projects as such
- Needs maintainers - new process, community members can create an issue when some project needs maintainers, others can apply to become one
Remaining tasks:
Write proper project description on the project pageUpdate all documentation about project ownership transfer to point to the new queue- Write documentation page for the new "Needs maintainers" component / process
Done:
Create 'project ownership' project https://drupal.org/project/projectownership
Move existing project ownership issues from webmasters queue to the new queue.
#2256249: Move 'Project ownership' issues to the new queue
Original post by jibran
@herom proposed a very nice idea on the Drupal.org 2014 roadmap brainstorming group about creating a "Need Maintainers" page. The basic idea is to create a page where module owners or users can ask for new maintainers, and interested users can apply maintainership. @jibran added a counter proposal
Let's make a "Need Maintainers" project on d.o. with an issue queue just like the webmasters issue queue.
If a module required a new maintainer, then the module owner or any other user can create an issue "Need Maintainer for x.y.z module" with a little explanation about why this project needs maintainers and list benefits, if any, of becoming a maintainer. Interested users can reply to the issue, and we can close/fix the issue once we have a new maintainer.
Comments
Comment #1
webchickThis sounds fantastic to me. I actually wonder too if we c/should just move the entire "Project ownership" process over to this queue instead? It'd be much more discoverable that way.
Comment #2
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedThat sounds like a very good idea.
Comment #3
tvn CreditAttribution: tvn commentedGreat idea and +1 to moving all 'project ownership' stuff to this queue.
Comment #4
webchickWell then!
Marking RTBC, and will leave this for a couple of days.
Comment #5
tvn CreditAttribution: tvn commentedI'd love to get sreynen's opinion on this as he is doing most of work in 'Project ownership' queue recently. Pinged him on IRC.
Comment #6
sreynen CreditAttribution: sreynen commentedThis sounds good to me. My only request is that abandoned/unsupported projects have a separate component, so it stays easy to focus on that particular subset of issues.
Also, just FYI, there's a group that seems to be largely intended to solve the same problem:
https://groups.drupal.org/co-maintainers-projects
But that's not really being used, so I don't see that as a problem.
Comment #7
Homotechsual CreditAttribution: Homotechsual commentedLove this idea!
Comment #7.0
Homotechsual CreditAttribution: Homotechsual commentedjust fixing typos and sentences.
Comment #8
tvn CreditAttribution: tvn commentedOk, I think enough time passed for anyone to say anything against this idea, so I am going to implement it.
Comment #9
tvn CreditAttribution: tvn commentedComment #10
tvn CreditAttribution: tvn commentedComment #11
dddave CreditAttribution: dddave commentedGlad I found this or I would've been pretty lost when suddenly all those issues were gone. ;)
Adding a late +1 and a reminder that we need to adjust our docs after implementation.
Comment #12
tvn CreditAttribution: tvn commentedCreated #2256249: Move 'Project ownership' issues to the new queue to move issues around.
Comment #13
tvn CreditAttribution: tvn commentedIssues got moved to the new queue https://drupal.org/project/projectownership. I removed "Project ownership" component from the Webmasters queue.
Remaining tasks here are:
1. Write proper project description on the project page
2. Update all documentation about project ownership transfer to point to the new queue
3. Write documentation page for the new "Needs maintainers" component / process
Any takers?
Comment #14
tvn CreditAttribution: tvn commentedComment #15
tvn CreditAttribution: tvn commentedComment #16
dddave CreditAttribution: dddave commentedI'll work on this over the next days.
Comment #17
dddave CreditAttribution: dddave commentedJust an update: #1 and #2 should be mostly done. I still have #3 to do though.
Comment #18
dddave CreditAttribution: dddave commentedCreated https://www.drupal.org/node/2332703 (unpublished for now). Is this getting in the right direction? Reminder for myself: If the
sitepagegoes live, add info about it on the project page.edit: dang, false friend
Comment #19
tvn CreditAttribution: tvn commentedThanks for starting the doc dddave. I edited it a bit to be more about 'what you should do if you need co-maintainer' versus 'what you should do if you don't have permissions to add someone'. I also found this page: https://www.drupal.org/node/23789 it has some tips 'How to find co-maintainer' at the bottom. I merged the ones which still make sense into your page. I think once this new page is published, we can remove those instructions and just link to the new page.
Comment #20
dddave CreditAttribution: dddave commentedLet's get this finally finished. What needs to be done here? I've dropped the ball and could need some guiding light.
Comment #21
tvn CreditAttribution: tvn commentedI think that your page just needs to be published and this is pretty much it.
Comment #22
dddave CreditAttribution: dddave commentedPublished the page and added info about it on the project page.
Comment #23
joachim CreditAttribution: joachim commentedYou also need to update the documentation pages that explain procedures such as taking over abandoned projects
Comment #24
dddave CreditAttribution: dddave commentedAdded info/links to the best practices for comaintaining page and the dealing with unsupported modules page.