I tried to figure out what the recommended process was for vetting an idea for a new project you are willing to be the maintainer for, and couldn't really find it. There is all kinds of help for applying for a CSV account, but if I have one, I'm not sure what I'm supposed to do to vet a new project.

Can you guess which Dev thread sparked this issue? I heard you Angela :)

What I'd propose. Start by adding

* Vet your project idea

In front of "Produce your contribution" on node 22286. This ideally would be a link to guidelines for vetting this project idea.

What I have done in the past is:

* Look for modules that could be modified and post feature requests with the phrase, "Willing to code and contribute patch" on the issue queue. Wait for a "Patches welcome" common to be submitted by the maintainer before proceeding to spend the effort on rolling a patch.
* If you don't get a response in the issue queue, use the contact form for the developer to try and get a response. Be sure to indicate both your willingness and experience in contributing to the module.
* If you can't find a module that does the same thing, post a message to the devel list asking for opionions on both concept and name of the proposed project. Give a couple of days to a week for appropriate responses.

This is my first doc contribution, so I thought I'd vet this here before just starting to edit the page.

So what do ya think? A little encouragement and I'll start typing :)

Comments

dman’s picture

dman commented

Cross-reference to A suggestion for reducing new-duplicated modules : require RFC or statement of intent posting because I think there is the same idea there. Or it's a duplicate ? ;-)

Here's my example of a proposed module awaiting input.

.dan.

arianek’s picture

arianek commented
Status: Active » Fixed

i think all of that is pretty much represented in http://drupal.org/cvs-application/requirements which has had some additions to reflect this. closing unless anyone objects.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.