Forums : Posts

Find a project contributor that is not linked to any account. Give kudos to that contributor. Link that project contributor to your own account. Our system is smart enough to recognize when you're ... [More] trying to give kudos to yourself. We ignore those kudos when we calculate the rankings. [Less]

Oh yes, and regarding duplicate Subversion repositories: It is actually very common and intentional for several projects to include the same Subversion repository. In an ideal implementation, the ... [More] Ohloh website would offer the flexibility to aggregate several smaller projects into a single large report. But we don't do that yet. So, a lot of teams have created individual project pages for their sub-projects, then a master project that includes all of the code from all of the sub-projects. GNOME does this, for example. I'm not saying we couldn't improve things with a warning or something when you try to do this. And in general, our project search could stand a lot of improvement. Hmm, no end of features to write... [Less]

Hi Chris, Absolutely. In the 'Grand Vision' of what Ohloh can become, we do think about adding the ability to track bug databases, and how we might link status changes in bugs to changes in lines of ... [More] code. Automated reports about test code (who writes it, who doesn't), defect rates (who creates them, who resolves them), and code coverage would be really interesting and powerful. In the long run, I think Ohloh should be aiming for a pluggable architecture that lets us absorb all kinds of project-related data and correlate it in interesting ways. [Less]

I've merged these projects into Worldwind. The root of the problem seems to have been disagreement about whether the project name has a space in it or not.

bump

Looking forward to faster updates :)

Well, here my example from the main PostNuke repository (a Gforge server we run for project development) http://noc.postnuke.com/top/mostactive.php. Now, here comes the challenge: 1) Some of those ... [More] sub-projects are already registered at Ohloh. Most are not. 2) We could grep out the project names from the source text of the above link: For example http://noc.postnuke.com/projects/pnphpbb2/ becomes svn checkout https://noc.postnuke.com/svn/pnphpbb2/trunk; but: 3) Most projects there are using SVN, while some still insist on CVS. 4) Most projects are advised to put recent code into a /trunk - some however do not. 5) Several projects did not move to our central Gforge server, but instead still use places like Sourceforge - for example http://sourceforge.net/projects/elfisk/. Well, those can only be manually added untill you digg all those places completely on an automated base. So, that's PostNuke only - I believe many bigger projects face the same difficulties. Slightly easier for sidux: All active sub-projects can be found here http://svn.berlios.de/wsvn/fullstory, and all of them use SVN and /trunk. It's just that none of us has any intention to manually add or delete changes at Ohloh.;-) Greetings, Chris [Less]

Oups - sorry. I completely missed your swift to stacks, and made myself an idiot by writing about a problem we had half a year ago. ;-) Greetings, Chris

Hi Anton, No worries. I've rescheduled the download and it is running now.

The data is all OK. The web page is sloppy when creating the text. Our reports generate monthly statistics. This project has only one month of activity, so the first month of our report is September 2007. That month began 24 days ago. Silly bug.