Forums : Suggestions for Ohloh 2.0
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Commit gauge should add commits from reintegrated branches
The listed commits, which only incorporates commits to trunk, feeds the commit gauge in the Ohloh object on my Google Code project website.
This negatively reinforces use of branches to do larger pieces of work.
For example, I just did a huge piece of work on a branch, something like 40 commits, but my project barely shows a pulse because only the reintegrate commit to trunk shows on the commits gauge.
I can understand how you might not want to show branches because they might be used for experimentation then deleted, but if a branch is merged by SVN reintegration, then could you find a way to apply its commits to the commit gauge? Thank you!
IIRC you can add the branch as a separate enlistment. You can also switch to a SCM that won't squash your merges. ;)
Thanks for the tip about adding an enlistment, though it means a project manager has to go to ohloh and add an enlistment for each reintegrated branch. That's a manual process that should be automatic given that it is automatically detectable that a branch got reintegrated to trunk. Not sure what your comment about switching to another SCM means, but what I did was connect ohloh to a Google Code project running under SVN and just thought that perhaps that should work automatically.
Adding a new enlistment for each branch is pain, and it will also bring incorrect source code stats because of counting duplicate code.
Agree with the need to follow SVN merge history. Just like svn log -g, which displays commits of merged branches too.
Is it too complicated to implement in Ohloh crawler?
