Posts Tagged ‘sourceforge’
During last months we’ve been working to improve Bicho, one of our data mining tools. Bicho gets information from remote bug/issue tracking systems and store them in a relational database.
The next release of Bicho 0.9 will also include incremental support, which is something we’ve missed for flossmetrics and for standalone studies with a huge amount of bugs. We also expect that more backends will be created easily with the improved backend model created by Santi Dueñas. So far we support JIRA, Bugzilla and Sourceforge. For the first two ones we parse HTML + XML, for sourceforge all we have is HTML so we are more dependent from the layout (to minimize that problem we use BeautifulSoup). We plan to include at least backends for FusionForge and Mantis (which is partially written) during this year.
Bicho is being used currently in the ALERT project (still in the first months) where all the information offered by the bug/issue reports will be related to the information available in the source code repositories (using CVSAnaly) through semantic analysis. That relationship will allow us to help developers through recommendations and other more pro-active use cases. One of my favorites is to recommend a developer to fix a bug through the analysis of the stacktraces posted in a bug. In libre software projects all the information is available in the internet, the main problem (not a trival one) is that it is available in very different resources. Using bicho against the bts/its we can get the part of the code (function name, class and file) that probably contains the error and the version of the application. That information can be related to the one got from the source code repository with cvsanaly, in this case we would need to find out who is the developer that edit that part of the code more often. This and other uses cases are being defined in the ALERT project.
If you want to stay tunned to Bicho have a look at the project page at http://projects.libresoft.es/projects/bicho/wiki or the mailing list libresoft-tools-devel _at__ lists.morfeo-project.org
[This entry is part of the work I do in LibreSoft and it is also available in my blog at libresoft.es]
Last Friday some workmates from LibreSoft and I were in the Open Forges Summit, we couldn’t be there more than a couple of hours because we returned the same day but it was really interesting hearing a discussion about the problem of the data lock-in among people from sourceforge, codeplex, fusionforge, berlios and other places.
Some of the problems that came up in the discussion are summed up by Eric S. Raymond in this recommended blog entry “Three Systemic Problems with Open-Source Hosting Sites“, IMHO these should be the target for the next years in FLOSS forges, but at the end forges are an agregation of useful tools and some of them are now toooo big for being flexible. Maybe it wouldn’t be that bad to stop and re-think the workflow to give them a social approach and get its data distributed (and even standardized)
Yesterday night I found out that Sourceforge made available a new beta forge. You can browse the projects created so far in the new beta using the URL http://sourceforge.net/p/, to have a look at a test project go to http://sourceforge.net/p/fancypants/home/.
I also created a project to see what the new features are. At a glance you will notice that the layout is entirely different and simpler, the “old” sourceforge’s pages were offering too much information. Once you create the project you can add new resources to it, git, bts, wiki and so on .. nothing new under the sun at this point, but I’m pretty sure new features are coming soon. I’ve read in the Mark Ramm’s blog some interesting info:
- “And we are committed to making this the most open forge possible. We’re committed, to open processes, open code, and perhaps most importantly open data.” Encouraging sentence
- “data should be portable (every project gets their own database, which they can take with them if they want)”. I like this, if you want to be the best forge platform you shouldn’t obly people to stay, you must convince them to come
- “open source community ought to be able to extend and enhance the tools they need”
In any case, after a couple of minutes in the new forge I have some questions:
- Shouldn’t forges be more people oriented? I do love the way github does it
- Will be possible to integrate third party services (bugzilla or mediawiki for instance) in remote?
- Will be possible to import data from third party services? (for instance import a remote svn to git or mantis bugs to the sf’s bts)
- Are they going to integrate the forge with the ohloh’s results?
- Are they improving the search engine? I didn’t manage to find a person using its real name in the “old” sourceforge’s forge
- Some of the links in the beta redirects you to the “old” forge, I guess they will replace this with the new features slowly.
Passing new software to production is always funny and stressful. Good luck to the sourceforge’s team
Some interesting links: