Forums : Posts

Hi Amir, I changed my mind and chose 10861 to be the definitive one instead - it had better information already in it. Ohloh's backend is intelligent enough to only process a repository once (even ... [More] if it's included in many projects) - so we didn't incur much overhead in having both projects on our system. However, our most precious commodity - our users and our own time - still ends up being wasted by duplicate projects. Your suggestion is very good: adding a 'report problem' link would help out a lot. We'll try to add this after we ship the v2 UI (which should be any day now). [Less]

We shut down our system this weekend for a database upgrade. The system is back online now and the reports are updating.

Hi Maurice, This was a problem on our end. I've rescheduled the job, and the report should update soon. Thanks, Robin

As much as I would like to see a good estimation of when a particular project is going to be updated next time I have to admit that a queue position is not remotely more helpful than the status page. ... [More] In this case having two or three queue positions, not to speak of an average queue position, is not going to be any remedy at all. Maybe you could start working towards more information on this subject by providing a link to the status page on the enlistment screen. Another step could be to dynamically generate the update picture depending on the project somebody came in from and highlight the day of that particular project. It is not easy to count the bars and memorize all the dates from the projects you are interested in. Just basic thoughts I've had on this, though not yet a solution. Because in the end: users will ALWAYS want this feature. :) Hagen. [Less]

The possibility to search users thru by countries.

Thanks Robin and Steffan!

Greetings lodo-admin, How embarrassing. Our licenses list was not filtering out the deleted licenses (even though your UNDO of the creation, was, in fact, doing the right thing in the database). I've ... [More] since fixed this bug. As for the question of whether the original affero license (id:135) should be edited with your changes, I will leave to your discretion: I am not up-to-date on this license and it sounds like you know more than I do ;-). Thank you for finding and posting this bug. [Less]

Robin, Thank you very much again! Everything works now. I'll be patient next time and I'm not going to bother you about similar issues :-) Cheers, Mateusz

In my profile it lists that I only have 6 commits, and all of them are from Jan. 14. The Source Mage project's repos have been scanned much more recently than that, and in particular the cauldron.git ... [More] repo was processed as recently as 20 hours ago. If you look in the cauldron.git repo, I have various commits at 32 hours ago and 23 hours ago. [Less]

P.S. You are exactly right about the branches -- tailor does the easy thing, which is pretend that branches don't exist. If you want to convert one single line of darcs history into one single line of git history, tailor is a perfect tool.