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
info@openhub.net
You know how amazon has the 'people who have purchased X, have also purchased Y and Z'.
You could do a similar thing with stacks, and start to interlink projects that are 'clustered'.
Yes, I think this is a fine idea. We're waiting until we collect enough stack data to make relevant recommendations, but something like this is definitely coming.
I was also thinking that the stack data might be helpful in determining not just apps that go together like Ruby and Rails, but also apps that are alternatives to eachother, like Vim and Emacs.
If you've got any thoughts or input on this topic, I'd love to hear it -- we're still in the planning steps, so this is a good time to discuss it.
Robin
figuring out the related items is fairly easy - yo don't have to have a semantic understanding of the projects, just an understanding of the connections. The opposite is more difficult. You could certainly identify projects that are 'far away' - or weakly connected. But I wouldn't be surprised to find that technical alternatives are strongly connected. Hibernate and iBatis are such an example - I have an interest in them both.
As I said in another post, the primary appeal to me of the stacks concept is to build my dashboard of 'projects of interest' and then to monitor them from one place - but we need more data for that.