Forums : Posts

Thanks!

My project is now classified as using LGPLv3. Thanks for the update, Jérôme.

ok thanks, as I said I was curios about this and you don't have to change anything for me :) (ok gimme a cudo for logical thinking :P)

Yup, everything seems to work now. Thanks! happily hops to go and release a new #www-ohloh-api version

if both Title and Describe your contributions is filled in, only title is actually shown. why?

Ok, this is awkward. Looks like my memory of this feature per person, combined with skimming over 'related projects', mixed up into something nonexistant in my mind. On the other hand, it would ... [More] perhaps be interesting for the wishlist: creating a list of other projects (libraries, tools, IDEs) used in development of a particular project. e.g. a C++ game adds gcc and SDL, a Python text editor adds python, wxwidgets and wxpython, ... [Less]

Thanks a lot. I feel a bit stupid: I should have figured this out by myself. Thanks for the info. Maybe you could add that info on the journaling pages :-) Jérôme.

Very strange -- it looks like we are experiencing some kind of crash during the count. I'll keep an eye on this one today and figure out what's going wrong.

Well, I hate to be contrary, but I think our report is correct. Check out file src/main/config/project/project.pod.xml -- it has 17,409 lines of XML, which is nearly as big as all of the Java in this ... [More] project combined. It's true that there's about 68K total lines of Java in this project, but the majority of this is comments and blank lines. Looking purely at code lines, there's only about 18K lines of Java code. If you want to play around with exploring line counts, you can download the source code for our line counter here. [Less]

Hi bln, We are happy to lift the API key limit if required, and have done so in the past. We do encourage people to use caching when possible, but if you develop a popular application we're more than ... [More] happy to help out. Part of the reason for the limit is so that people will contact us first before surprising us with millions of hits. It's true that you can't put your application's secret into the source code if you are distributing it. OAuth wasn't really intended for distributed code -- it was designed for use with web services, which allows secret data to exist where it is inaccessible to the end user. So if you're distributing your code, your secret won't stay secret, and you shouldn't use OAuth. If your users are savvy and patient, it's probably OK to go ahead and instruct users to get an API key from Ohloh and configure the application to use their own key and secret. It's also possible to simply log a user in, if they are willing to give you their username and password. We haven't formalized this in the documentation, but it is possible to post the login form and get a session cookie. Let me know if you need some specific help here; we haven't discussed this much internally, and we might have some things to sort out first. Thanks, Robin [Less]