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.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]
I would like to build a maven plugin ...
I would like to build a maven plugin (or similar) that will read your POM file and use Ohloh to calculate the total project cost of all of the projects that you depend on.
To do this, I will need a way to correlate the pom groupId and artifactId to an Ohloh project ID.
I was thinking that since you are already analyzing the source code provided for each of these projects, you could fairly easily read any associated POM files for the project, and then make that information available. For instance, you could access a project by the normal URL:
http://www.ohloh.net/projects/3958
OR - by the POM URL
(or such):
http://www.ohloh.net/projects/pom/wicket/wicket
http://www.ohloh.net/projects/pom/wicket/wicket-extensions
http://www.ohloh.net/projects/pom/org.springframework/spring
Or, even better, you could provide this as part of your REST API - provide the groupId and artifactId as part of the URL, and get the project stats, including estimated cost.
Hi Anonymous Coward,
Thanks for bringing POM files to my attention. It's timely because we're thinking about how we can have stacks (mostly for dependencies) for projects.
If a project had a stack, would that answer most of your need?
Could you also answer a couple questions about POM files:
- Is it safe to assume that each project on Ohloh will have only one POM file?
- Are they used only for Java projects?
- Are there other schemas that do the same thing?
Thanks!
Greetings AC,
We haven't adopted a standard project schema (yet). As they say, the problem with standards is that there are so many to choose from!
It looks like DOAP and POM have gained/attained some momentum, while PAD seems dead-ish (I haven't seen much PAD use). Alternatively, Freshmeat's schema, while not 'standard', would be very convenient .
Your request is very reasonable and somewhat related to a feature we'd like to implement soon-ish: single project title namespace. The goal would be to move to more useful urls (think: /projects/gaim rather than project/3242).
So, if I understand your request correctly, we'd have to add POM groupId and artifactID fields to our project properties and allow the ability to refer to projects with the url you describe. Finally, we'd have to render the appropriate POM XML files -- right?
I'm theoretically inclined to do this, except for one nagging question: for what percentage of projects would POM be relevant?
