Posted by MiSc on February 5, 2012 at 10:08am
This feature module is firstly aimed to members of the squad so that the quickly can setup a new, or start fresh, site to be able to for example work on patches or other issues for the media project.
This application: http://drupal.org/node/1429034
I see the need for the bug squad to have this, but I do not see the reason why it should be a full project on drupal.org...

Comments
Don't see the downside.
There have been a few other examples of 'feature' modules coming through the project application process in the past, which have generated a fair amount of discussion with regard to how to evaluate an exported 'feature' from a project application perspective ... especially in the context of whether reviewers can get a sense of an applicants coding ability from what in some cases is a click of an 'export' button.
That said, there are numerous cases of other 'one-off' and single use case projects hosted on drupal.org; so I wouldn't let 'size of target audience' be a contributing factor to whether a project makes it into the contrib repositories ... and in this case, the feature also serves nicely for people outside of the bug squad who simply want to quickly evaluate an integrated media setup without having to struggle through their own WYSIWYG configuration, so I'd see that as another +1 for inclusion on d.o.
A third contributing factor (though not part of the project application process directly) is the initiative being shown by the applicant in starting up a 'media bug squad' in the first place ... the application process can be very off-putting to new contributors, but as a community, I think we need to do everything within our power to support and encourage individuals who are willing to go that extra mile for the benefit of the community as a whole.
Yeah, you are right.
Yeah, you are right.
/* Mikke Schirén, http://nodeone.se/ */