Unpublish projects without releases

Hi

Could you review this one: http://drupal.org/project/hr

I've added the note: http://drupal.org/node/524168#comment-1935362

Some of these have commits which makes the previous work entirely disappear for most audiences and duplication more likely as someone tries to create a node for something they think doesn't exist.

Can't they just be re-asssigned to be owned by the Abandoned Modules user (http://drupal.org/user/291168) and/or rename the Abandoned Modules user to Abandoned Projects. That at least makes it easy for the people in the webmaser queue to identify a project that doesn't have to go through normal project transfer procedures...

I care less about releases than code. If there's code in cvs I think we should _not_ unpublish them unless the author has a really good reason for us to unpublish the project.

I think it is totally useless to let people look at e.g. the translations page and notice that the advertised project does not have any or very little code or translations.

This makes a overall bad impression, IMO. This was especially prevlent with the translations.

Agreed on the bad impression. How about deleting the abandoned nodes with no commits rather than unpublishing? I'm just trying to prevent someone from coming along later and trying to create a rw translation and being blocked b/c of the unpublished one.

then he'll hopefully create a webmaster issue and it can be republished as the hr translation was.

Three projects listed on this page with commits and are still published are:
http://drupal.org/project/hr
http://drupal.org/project/sco
http://drupal.org/project/hr

Marking as fixed.