Forums : Technical Issue Help
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]
enlistment policy.
Hi viyyer,
That's a very good question. Our enlistment policy hasn't been well communicated and we will take your post as a reminder to improve this. Meanwhile, here's a summary:
- We want projects to be enlisted in their development trunk.
- If a project has migrated repositories and did not backport their old history into the newer repository, posters should not include the older repository (this is a requested feature we don't support yet).
- If a project has multiple versions contained in seperate and ongoing development branches, modules or repositories, we encourage people to post the versions as seperate projects in Ohloh.
- We encourage well-componentized projects to be broken out that way into several Ohloh projects.
Hope this helps, let me know if not.
Hi Jason,
There's something I don't get in your policy. When you say
If a project has migrated repositories and did not backport their old history into the newer repository
what is that supposed to mean? How a project that has migrated its code repository could not backport code to the newer ? I'm probably missing something due to my english understanding of backport, sorry. Could you please rephrase this?
My case is simple: I administrate the Mediboard project. We have migrated from a CVS to a SVN repository for well known reasons, with the exact same code. Shouldn't I be enlisting the older CVS rep on Ohloh to reflect the real Mediboard history?
Thanks in advance for your clues.
