Projects with empty code

Posted by klausi on February 2, 2016 at 7:37am

Received a question from an applicant per mail:

Hi, I have a question about the project reviews, how come my project is still sandbox and there is people that can create 'projects' with empty code? isn't that against rules or at least ethics?

https://www.drupal.org/project/amp

Comments

Once we give people the git

Posted by klausi on February 2, 2016 at 7:41am

Once we give people the git vetted user role we trust them to be responsible on drupal.org. If you think that a project is not used you can take it over by following the abandoned project process: https://www.drupal.org/node/251466

Otherwise it might also help to just ask the maintainer of the empty project what their plans are and if you can help out as co-maintainer.

If somebody is clearly squatting many project namespaces you can also escalate to the drupal.org webmasters to stop the person from doing so: https://www.drupal.org/project/issues/webmasters

I would also recommend they

Posted by frob on February 3, 2016 at 9:00pm

I would also recommend they look in the issue queue for the project. AMP in particular is a planned project with movement in the issue queue related to planning the project. As AMP as a standard is not in a very stable state, it makes sense to check the issue queue.

What about projects that should be sandboxes?

Posted by perignon on February 3, 2016 at 10:07pm

This is a segway into another topic I have been drafting for this group. Projects that are being posted on D.O that are not a project at the outset of posting. They are developmental code, i.e. what should be a sandbox. I am still building the post, but the Gist of it is that maybe certain attributes should not be allowed when creating a full project and/or force all projects through a sandbox period.

Brady
@fastglassllc
@derailedonline