I've deleted 102 since it appeared to be less popular and its code enlistment was out of date. I've consolidated the stacks, etc.. into 4075.
Also Rhythmbox seems to be duplicated: see http://www.ohloh.net/projects/4116 and http://www.ohloh.net/projects/4453
Thanks for findings this. I've deleted 4116, which looked to be more complete, and moved its ratings and stacks over to project 4453.
Also nanoblogger is here four times: * http://www.ohloh.net/projects/5366 * http://www.ohloh.net/projects/5365 * http://www.ohloh.net/projects/5364 * http://www.ohloh.net/projects/5363
geez - I'm getting the hint that we really need to catch this at project creation time. I'll clean em up tomorrow. Thanks!
I've cleaned up the recent duplicates (Apatana and NanoBlogger).
In both cases, the duplicates were created by the same person in a very short period of time -- which makes me think that perhaps the people who created these projects were simply having some trouble editing the project info, and perhaps weren't even aware they were creating duplicates as they edited.
Is there something confusing about the project creation process that we should fix? Of course it's all totally obvious to us, but we're the nerds who wrote the mess, so how does it look to our users? Any feedback?
I didn't see any difference between Apatana projects. Maybe a very common case in Web Applications: the guy who created the project clicked "submit", but didn't receive a response (timeout, page loading cancelled,...) althought the request may be received by the server. Users often click on the submit button again thinking it was not successful. Maybe inserting and managing an hidden big random number in the form could help detecting duplicate submits ?
Robin Luckey: For that problem, it would probably be a very good idea to implement duplicate form submission detection, either on the server side, or even simply on the client side by disabling the submit button on post.
There's less you can do about independent duplicates, but detecting identical names and inserting an additional confirmation would probably help a lot already (such as with the Mercurial duplication).
@Robin: To be honest I have no idea why nanoblogger was created so many times. I sometimes have similar problems with ohloh, especially when server response is bad. Maybe some ajax code timeouts in this case and resubmits the data? I didn't investigate the details, but when ohloh is heavy loaded, my posts are sometimes submitted several times.
I've merged these Octave projects. The dup project problem is really annoying. What's the best solution? Simply restricting the project names to be unique is not necessarily enough - in this case they had different names. I wonder if we should also use the home page url to determine similarity. Any other suggestions?
I wouldn't go for name or home page duplicates except at creation time, and even then only to let the user click a "yes I'm sure" button.
Just a thought ...
OpenH323 is also multi-duplicated
Hi Bertrand - thanks for the notice. Something strange must have happened. It looked like you created the project 12 times (you didn't , did you?). Anyway - i undid all save one.
Aren't you supposed to be on vacation? *cough*
Edit: Sorry, it's 6am, I'm fiddling with design elements on my blog and listening to Queen ... kinda bored ya see. Incidentally, your formatting markup is starting to get irritating, since I'm used to using a couple of Asterixs, uh, asterisks, to delimit third person actions ... which looks completely wrong on here. How to put in a couple of splats? Backslash?
Found another duplicate project:
I've deleted the recently added duplicate.
Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.