Posted by misc on March 9, 2012 at 3:21pm
Again we have an issue with a group of people doing a project application: http://drupal.org/node/1211132
It seems that we user that posted the application have done none of the commits to the project, but three other users have.
I can not see how this could be a valid application at all. How could we know which of the users that do understand the basics?
Comments
A contribution is a contribution
Remember ... our job is not to play cop, it's to help ensure code quality.
Also, if there's a policy question, let's try and keep it out of the specific issue threads.
I think it is appropriate to explain that only one user is granted the full access permission through this process, ask them to identify one account for the application, and validate that the account in question is making at least some of the commits ... but I do not agree with asking them to close and re-opening an application under a different name .
We should not be asking applicants to jump through more hoops than they have to already, and if a company wants to contribute group developed code, then we need to adjust to accomodate that scenario; not try and step in and change their development workflow.
How could we ensure code
How could we ensure code quality if we do not know who we think are doing the coding? If we are allowing groups to do applications, like in this case, we need to change how we treat 'solo' applicants that are applying for project access, and let more things through, and not be so picky about coding standards and understanding of how Drupal works - because we could not ensure in a group application.
/* Mikke Schirén, https://digitalist/ */
I disagree
You ensure it by holding the overall application to the same standards as you would a solo review ... it's obvious that the group is all reading the application thread - in my view, it's more efficient to be educating multiple developers through a single application than forcing them all to submit individual applications. (We would not grant all of them the 'full project' permission unless they were to submit their own individual projects for review; but through their participation in this application, the expectation is that their own applications would not repeat the same mistakes.)
The situation is no different than what we have on any other contrib project ... Anyone with permission can create a project, and then grant commit rights to anyone they want, irregardless of whether that committer has been through the review process or not. I don't see anything wrong with the collaborative approach in developing a project ... in fact, it is one of the underlying principles of the Drupal community. We would not say they could not contribute a project which was developed collaboratively, so it becomes hypocritical to tell them that they can not use a collaboratively developed project in the application process.
I do not agree with you on
I do not agree with you on this, but we not have to, so that is no problem :-).
/* Mikke Schirén, https://digitalist/ */