Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.synopsys.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]
Heh, thanks Sean. If only more developers had the grace and wisdom to offer free beer while requesting help.... :-) I hear you on the license detections. I'm hoping we'll have more hands on the Ohloh
@Piet, Yes, we've done some experiments locally with CVSup, and have been intending to use it for a long time. It just seems like something else is always demanding our attention. @anholt, That's
Update re: GNOME. We've finished an update.
We are using .inl as file extension for inline c++ files. Maybe add .inl as C++ file extension?
Hi jrshaw, the problem is that the project is enlisted in this subversion enlistment: https://panopticode.svn.sourceforge.net/svnroot/panopticode/trunk/ -- which doesn't exist anymore. From doing an
Among the choices for failing enlistment, there should be the option to specify that a project at least provides source tarballs. Even better would be to allow specifying the directories which contain those tarballs.
Dear Robin, Thanks very much for your answer. For point 2 and 3, a checkbox would be a good idea and will fit our wishes. For the point 1, we have a backup of the SVN before 2007-09-21. Maybe we will
It's probably fine to add a second branch if you like. You're right, you'll double-count the lines of code, but I think getting all of the commit history is more important. However, you might not be
bzr support. I can help add this if needs be :)
It would be cool if your computation of the theoretical cost of a project could reward for refactoring and penalize for rampant cut-n-paste reuse, rather than basing it purely on LOC. In a mature