Forum Posts

As a temporary solution, I wrote the script https://www.jfire.org/ohloh-ssl.php/projects/10703/widgets/projectpartnerbadge which fetches the content in the background, replaces the URLs (to force the ... [More] image being loaded indirectly, too) and forwards it to the client. Unfortunately, though, ohloh.net answers differently to my script (sending some XML) than it does to the normal browser. How can I force ohloh to answer the same way? I already tried setting the User-Agent, but somehow it doesn't work. Either my User-Agent setting is ignored, or ohloh.net uses a different criteria to decide about its answer. Before I continue trying around in the dark - could you please give me some hint? [Less]

Hi Robin, just a few days and the warning popped up again :-( I searched for occurences of "GNU General Public License" and I found it in the fckeditor for which we implemented an Eclipse integration ... [More] in project org.nightlabs.eclipse.ui.fckeditor. Being a JavaScript library, the source files are directly in our project - i.e. not a JAR - and ohloh scans them. 1) fckeditor has triple-licensing and I assume that ohloh misunderstands that as a GPL license which causes a warning. The license headers look like this: * Licensed under the terms of any of the following licenses at your * choice: * * - GNU General Public License Version 2 or later (the "GPL") * http://www.gnu.org/licenses/gpl.html * * - GNU Lesser General Public License Version 2.1 or later (the "LGPL") * http://www.gnu.org/licenses/lgpl.html * * - Mozilla Public License Version 1.1 or later (the "MPL") * http://www.mozilla.org/MPL/MPL-1.1.html 2) I read a while ago that someone suggested .ohloh-ignore files (or whatever they should be named) in order to tell ohloh to skip directories/files (like JavaScript libraries). Does this feature already exist? Best regards, Marco :-) [Less]

Hi Robin, yes, it looks very good: Only blue and green icons - no warnings anymore :-D Thanks a lot! Marco :-)

Hello *, on the "Enlistments" page, you wrote "We usually correct failures within the next business day.", but yesterday passed without the failure-message to disappear or change. Therefore, I ... [More] thought you might need some help - is there anything I can do? Maybe a SVN-dump of our repository helps? I've put a gz-compressed dump of today here: http://www.nightlabs.de/~marco/jfire/jfire.svndump.gz This HTTP-server has a faster internet connection than our SVN-server, hence it might make sense to initially set up your mirror with this dump. Best regards, Marco :-) [Less]

Hi Andy, thanks for your reply and for restarting. It finished successfully. I've already added your metrics to JFire's entry page. Best regards, Marco :-)

Hi Robin, thanks a lot for the quick response and for setting up https! The URL https://www.ohloh.net/projects/10703/widgets/projectpartnerbadge is reachable now, but unfortunately, the img tag uses ... [More] the http address instead of https - thus there's still a warning/error in many browsers. Btw. the workaround works! Thanks for fixing this. But even though this works, I'd still prefer to directly include your script. Best regards, Marco :-) [Less]

Hi *, I remember that I already read some time ago that you wanted to extend the "Code analysis" page to show which files are under which license. For our project, Ohloh claims that there were 2 ... [More] files under GPL. However, none of our code is under GPL. Since we published all our code under LesserGPL, I assume that someone simply forgot the "Lesser" in 2 files, but I have no clue what files these are. Do you still plan to add this feature of showing which files have which license? If so, when? Till then, what chance do I have to get rid of this (wrong) GPL listing? I mean: Could you give me a grep command or otherwise explain how Ohloh gets the idea that it's GPL? I ask, because the warning "You should review ... carefully, especially if you are using this code for commercial purposes" is not really helpful for an ERP system which is - of course - used for commercial purposes ;-) Thanks a lot in advance! Best regards, Marco :-) [Less]

Hi Robin, thanks for your quick reply. We'll probably put the JavaScript code into a zip as a workaround. Our build process can unpack it. That should prevent ohloh to parse it. I'll discuss this ... [More] with the person responsible for this sub-project - I hope zipping is a solution (at least temporarily). Concerning the "choose one" licenses: Do you have multiple parsers (i.e. one searching for each license - not knowing the others) or is it just one parser that searches for multiple things in one pass? In the latter case, it would know that its the same file having multiple licenses and that it therefore must be a choice. But well, I understand that you are very busy... is that part open-source? I guess the people who are directly affected (e.g. fckeditor) might feel some motivation to fix it themselves. Best regards, Marco :-) [Less]

Hi Robin, if you want to test yourself, use IE 6 and go to this page: https://www.jfire.org/modules/content/id_14.html I've temporarily added all the widgets to this (not active) page using the ... [More] widgets' https links. IE6 will tell you that it contains unsecure objects and asks whether you want to load them. If you say "No", you'll see what's still http. Btw., IE7 seems to be much worse; it seems to make it quite hard to see anything at all (I've not tried it myself, though, because I don't have IE7 - I only have been told). Best regards, Marco :-) [Less]

Hello *, we're running our project website http://jfire.org entirely over https and want to integrate the http://www.ohloh.net/projects/10703/widgets/projectpartnerbadge "partner badge". When I ... [More] integrate this badge as indicated on http://www.ohloh.net/projects/10703/widgets many browsers show warning/error messages due to the inclusion of insecure (plain-text) content into a secure (ssl) website. Unfortunately, it seems ohloh.net is not available on https at all. Could you please provide the ohloh service on https, too? It is not only useful for our situation, but would provide more security during login (I really don't like passwords travelling the internet in plain-text form). Best regards, Marco :-) [Less]