Understood. I appreciate the help.

You did it. Though, I have no idea what the alias UI is. I'd never seen that before. What I expected to happen in this process is one of the following: The original Qublog Position would be modified ... [More] when the original enlistment was deleted (or at some point when Ohloh had the opportunity to note the enlistment/usrname was gone/invalid) so that I was no listed as "None / I don't want to say." OR I would expect the "I Am This Person" button to have allowed me to update the Qublog Position record to the correct username since the old name was invalid. A possible third option would be to just show an error message explaining the problem, but if you do that it seems like you could just go ahead and do option (2) while you're at it. [Less]

I setup a previous enlistment in Subversion and added myself as a contributor on the Qublog project. When I try to add myself as a contributor in the new project, I get a screen like this: ... [More] http://www.grabup.com/uploads/c33f3dd6f8e67bb764223f7723e88c28.png If I click submit, I get this error here: http://www.grabup.com/uploads/7423e095737707500a677b74af032c12.png [Less]

Awesome.

+1 I like it. :)

Well, Drupal modules and themes are developed as individual pieces in their own forge-style environment (via the Project and Project Issue modules). All the module projects are hosted on Drupal's site ... [More] and the infrastructure provided is, in my opinion, one of the reason Drupal has been so successful. Adding a new module for download involves creating a project node on drupal.org, creating the CVS directory in the module directory of the contributed CVS module of cvs.drupal.org, tagging the code as belonging to specially named tags, and then creating a release node which results in a bot automatically packaging your module for release for you. Basically, they try to do as much as possible for QA purposes (and are slowly adding the infrastructure to improve the QA enforcements more and more). Or at least, that's the process as I know it. I'm not actually familiar with anything in Drupal core or any of the Drupal core devs. The super-project idea would be great. [Less]

On another thread, it's been mentioned that the Drupal (contributed) project has been purposely stopped from updating it's enlistment because it got far behind and ohloh hasn't had the opprotunity to ... [More] catch up yet without halting the enlistments on other projects. I also kind of feel like the Drupal (contributed) project is counter-intuitive. It seems like it would make more sense for it to be split into the various modules, themes, etc. rather than be one super-project. This makes particular sense given that each Drupal module, theme, etc. has it's own project page, downloads, etc. So it seems that deleting this project and then letting each module author add his own modules and themes and such back in would make sense to help with both of these issues. Any thoughts? [Less]

+1 That would be great! :)

Ack! I'm getting loads of repeats on all the emails being sent to me every time someone makes a comment on one of my threads.

I don't think the posts are un-updated so much as not updated again. It looks like they're still behind now so the backlog is starting up again on these same projects. The ones I referred to are back up to 10 days again.