Tag Archives: Project of the Month

“Community Choice” Project of the Month Vote – July 2016

The vote for July 2016 Community Choice SourceForge Project of the Month is now available, and will run until June 15, 2016 12:00 UTC.

Linux Diagnostic Tools

Project’s goal is to create better tools for diagnosing Linux systems. Diagnostics include first failure data capture, error log analysis, preventative testing, and system inventory gathering.
[ Download Linux Diagnostic Tools ]


FreeCAD is a general purpose feature-based, parametric 3D modeler for CAD, MCAD, CAx, CAE and PLM, aimed directly at mechanical engineering and product design but also fits a wider range of uses in engineering, such as architecture or other engineering specialties. It is 100% Open Source and extremely modular, allowing for very advanced extension and customization. FreeCAD is based on OpenCasCade, a powerful geometry kernel, features an Open Inventor-compliant 3D scene representation model provided by the Coin 3D library, and a broad Python API. The interface is built with Qt. FreeCAD runs exactly the same way on Windows, Mac OSX and Linux platforms.
[ Download FreeCAD ]


GnuCash is a personal and small-business finance manager with a check-book like register GUI to enter and track bank accounts, stocks, income and expenses. GnuCash is designed to be simple and easy to use but still based on formal accounting principles.
[ Download GnuCash ]


LibreCAD is a fully comprehensive 2D CAD application that you can download and install for free. There is a large base of satisfied LibreCAD users worldwide, and it is available in more than 30 languages and for all major operating systems, including Microsoft Windows, Mac OS X and Linux, including Debian, Ubuntu, Fedora, Mandriva, Suse, etc.
[ Download LibreCAD ]


TYPO3 is an enterprise class Web CMS written in PHP/MySQL. It’s designed to be extended with custom written backend modules and frontend libraries for special functionality. It has very powerful integration of image manipulation.
[ Download TYPO3 ]


K-Meleon is a fast and customizable web browser that can be used instead of Internet Explorer on Windows. Powered by the same Gecko engine as the Firefox and Mozilla browsers, K-Meleon provides users with a secure browsing experience.
[ Download K-Meleon ]


iDempiere = OSGi + ADempiere iDempiere Business Suite ERP/CRM/SCM done the community way. Focus is on the Community that includes Subject Matter Specialists, Implementors and End-Users. iDempiere is based on original Compiere/Adempiere plus a new architecture to use state-of-the-art technologies like OSGi, Buckminster, zk.
[ Download iDempiere ]


We all know someone who tried to switch to Linux but was unsuccessful. The system that he tried was too different from what he was used to, there were too many new things and the old things were not where he expected. The goal of this project is to let anyone get used to Linux. This system is not too different from Xubuntu, on which it is based, but ChaletOS has a style that everyone knows well, appealing simplicity and an impressive speed. All this will let them to fall in love with this system quickly. Because of its small hardware requirements it will revive some old machines and refresh others, not so old. The name ChaletOS came from the style of the mountain houses in Switzerland. The concept of these houses is similar to the concept that we had while we made this system: simplicity, beauty and recognizability. Since we want the new users to feel at home, we hope this project will meet this goal.
[ Download ChaletOS ]


Simutrans is a cross-platform simulation game where players try to successfully manage transportation systems between places by land, air, and water for passengers, mail, and goods. Planes, ships, trains, trams, trucks, buses, or monorails are at your disposal, but factories operate based on contracts and passengers can only travel to their set destinations.
[ Download simutrans ]

May 2016, “Staff Pick” Project of the Month – Arch Bang

For our May “Staff Pick” Project of the Month, we selected ArchBang, a simple GNU/Linux distribution that provides a lightweight Arch Linux system combined with the OpenBox window manager. Mr. Green, the current developer of ArchBang, shared some thoughts about the project’s history, purpose, and direction.

SourceForge (SF): What made you start this?
ArchBang (AB): I took over development of iso for Will at the time to allow him to focus on his studies.

SF: Has the original vision been achieved?
AB: Mostly; we try to keep iso to a minimum with all the tools you need to install and set up archlinux.

SF: Who can benefit the most from your project?
AB: Newcomers to Arch, Linux or even more experienced users who want a comfortable portable system.

SF: What core need does ArchBang fulfill?
AB: [The need for an Arch Linux system] that’s light, easy-to-use, fast, and up-to-date (as possible).

SF: What’s the best way to get the most out of using ArchBang?
AB: Try it live or load and run from ram, get the feel of Archlinux without having to install, break or risk your own system.

SF: What has your project team done to help build and nurture your community?
AB: We tend to keep things friendly and light-hearted. [We] pride ourselves on helping out when we can or at least point a user in the right direction.

SF: Have you all found that more frequent releases helps build up your community of users?
AB: Not really noticed that so much; we aim to release every three months (seasonal) subject to any major changes in Archlinux.

SF: How has SourceForge and its tools helped your project reach success?
AB: [It has] allowed users to find and download isos easily.

SF: What is the next big thing for ArchBang?
AB: Working towards a system free iso…

SF: How long do you think that will take?
AB: Hopefully within a few months we can have a fully working release.

SF: Do you have the resources you need to make that happen?
AB: Always looking to upgrade hardware; builds currently limited to the power of my laptop.

SF: If you had it to do over again, what would you do differently for ArchBAng?
AB: For me keeping things light and gui free would be ideal.

SF: Is there anything else we should know?
AB: Special thanks goes to Oliver and Pablokal 😉

[ Download ArchBang ]

May 2016, “Community Choice” Project of the Month – Libjpeg-turbo

For our May “Community Choice” Project of the Month, the community elected Libjpeg-turbo, a SIMD-accelerated libjpeg-compatible JPEG codec library. D.R. Commander, the developer and maintainer of Libjpeg-turbo, shared some thoughts about the project’s history, purpose, and direction.

SourceForge (SF): Tell me about the Libjpeg-turbo project please.
D.R. Commander (DRC): Libjpeg-turbo is a high-speed JPEG compression/decompression library that implements the libjpeg API used by a wide variety of applications (both open source and proprietary.) libjpeg-turbo accelerates the most common compression and decompression paths for JPEG images by as much as 6x relative to libjpeg, through the use of SIMD instructions on x86, ARM, PowerPC, and MIPS CPUs. libjpeg-turbo is now included in most open source operating systems (soon including Android) and is used by popular web browsers (notably Firefox and Chrome), so most people reading this are probably using libjpeg-turbo on a daily basis, whether they realize it or not.

SF: What made you start this?
DRC: My other pet projects (VirtualGL and TurboVNC) are high-performance open source remote display tools for 3D applications, so they have always needed some sort of high-speed image codec in order to stream the output of 3D applications in real time over various types of networks. “Back in the day”, I was using vendor-specific high-speed JPEG codecs, such as the Intel Performance Primitives and Sun mediaLib, but these weren’t always open source. Miyasaka Masaru developed MMX and SSE2 extensions for libjpeg in 2006. The TigerVNC developers adopted his code and did some further work on it, then they hired me in early 2009 to add 64-bit SSE2 support and to add colorspace extensions for compressing from/decompressing to 32-bit buffers. Eventually this codec matured enough that I was able to “eat my own dog food” and adopt it in VirtualGL and TurboVNC. At some point, developers in the streaming video community caught wind of our work and encouraged me to spin off the “libjpeg/SIMD” codec into a standalone project, so that other applications could easily take advantage of it. Thus, in early 2010, libjpeg-turbo was born. Some of the earliest adopters of it, outside of the remote display community, were applications that monitor security cameras.

SF: Has the original vision been achieved?
DRC: I believe it has. In fact, in most cases libjpeg-turbo now out-performs those proprietary/vendor-specific JPEG libraries that I used to use “back in the day.” Furthermore, I believe that libjpeg-turbo has helped to further Tom Lane’s original vision for libjpeg. In the release notes for libjpeg v6b, the last version that he worked on, he mentions performance enhancements as being “of great interest” for future development. Tom’s vision was to encourage wide adoption of the JPEG standard by providing a ubiquitous and legally-unencumbered JPEG codec library. libjpeg-turbo further encourages wide adoption of the JPEG standard by making JPEG fast enough to use with real-time compression/decompression tasks, which previously weren’t possible with libjpeg. Because libjpeg-turbo implements the industry-standard libjpeg API, applications that were already written to use this API can, without modification, take advantage of the additional speed in libjpeg-turbo. New applications also have the option of using the TurboJPEG API, which allows them to more straightforwardly compress/decompress images without dealing with the complexities of the libjpeg API. The TurboJPEG API also exposes functionality that would be very difficult to achieve with the libjpeg API, such as compressing from/decompressing to YUV planar image formats and doing multiple lossless transforms on the same JPEG image. We are making JPEG a lot faster and easier to use, and this enables use cases that previously wouldn’t have been possible with open source tools.

SF: Who can benefit the most from your project?
DRC: Applications that need to compress/decompress JPEG images in real time (for instance, video applications or remote display applications) benefit the most from libjpeg-turbo. Those applications were previously forced to trade off better performance for better compression, but libjpeg-turbo allows them to have both.

SF: What core need does Libjpeg-turbo fulfill?
DRC: The need for an industry-standard, ubiquitous, easy-to-use, high-speed JPEG library. Both libjpeg-turbo and libjpeg v7 and later evolved from Tom Lane’s work (he was the sole developer of libjpeg v6b and prior); but whereas libjpeg in the post-Tom Lane era has moved in the direction of introducing clever but incompatible and non-standard extensions to the JPEG format, libjpeg-turbo has instead moved in the direction of greatly speeding up the functionality that was already there, and making it easier to use. Apparently a lot of people preferred our approach.

SF: What’s the best way to get the most out of using Libjpeg-turbo?
DRC: Applications that were written to use the libjpeg API should “just work” with libjpeg-turbo, but if they have to compress from/decompress to 32-bit buffers, then they can take advantage of the libjpeg-turbo colorspace extensions in order to increase performance even more. A lot of new applications are using the TurboJPEG API instead, because it’s so much easier to use (although it doesn’t support some of the more advanced features of the libjpeg API, such as buffered I/O.) It also goes without saying that libjpeg-turbo will be of the most benefit on CPUs whose SIMD instructions we support (x86, ARM, PowerPC, MIPS.) Also, it will be necessary to compress/decompress baseline JPEG images in order to achieve peak performance (SIMD acceleration for progressive JPEGs is still a work in progress.)

SF: What has your project team done to help build and nurture your community?
DRC: libjpeg-turbo is a one-person shop. Over the years, I have received some big code contributions, particularly for things like SIMD support on ARM and MIPS processors, but I’ve always been the sole maintainer and, with the exception of outside patch submissions, the sole developer. The libjpeg-turbo community initially formed on its own, because there was a pent-up demand for a library that furthered Tom Lane’s work without breaking backward compatibility with libjpeg v6b. Also, a lot of developers liked the fact that our project maintains a fully open code repository and issue trackers, things that have traditionally not existed with libjpeg. Since its early days, I have built the libjpeg-turbo community simply by being as responsive as I could to the needs of libjpeg-turbo users, and evolving the project in the direction that most of them seemed to want it to go.

SF: Have you all found that more frequent releases helps build up your community of users?
DRC: There’s always a balance to be struck between releasing too often and not releasing often enough. Our community of “users” largely consists of application developers, and they (as I) are more concerned with quality over quantity. Thus, libjpeg-turbo has traditionally fallen somewhere between ESR’s classic metaphors of the cathedral and the bazaar. Major releases are dictated by new features, and new features are dictated by community demand. I always strive to implement and release bug fixes as quickly as possible, but I take great care to ensure that all new features are fully vetted– that they truly solve a well-defined problem in as elegant a way as possible, without creating any backward incompatibilities or regressions. Above all, I want libjpeg-turbo (and all of my other projects) to have the maximum possible utility, stability, and performance. I treat performance as a measure of quality, so any drop in performance is considered to be a bug. Our releases are dictated by whether there are sufficient changes relative to the prior release to justify a new release, and I would much rather delay a release than put out something that is half-baked or irrelevant. I use a traditional release model, whereby I put out a beta release, a final release (usually 3 months following the beta), then usually one or two subsequent bug-fix releases (minor revisions) for each major revision. So to answer your question, it isn’t the frequency of releases that builds the community of users– it’s being responsive to what the users really want. They mostly want libjpeg-turbo to change only if the change is compelling, and they want assurance that these changes will be implemented elegantly, with an eye toward ease of readability and maintenance, and without compromising stability or performance.

SF: What was the first big thing that happened for your project?
DRC: Probably the inclusion of libjpeg-turbo in Fedora. I never set out to build an industry-standard JPEG library. Originally I just wanted to build a fast, open source JPEG library that I could use in my own remote display projects. Red Hat was the first one to include libjpeg-turbo in their O/S distribution, and it kind of snowballed from there.

SF: What helped make that happen?
DRC: In addition to its increased performance, many O/S distributors (including Red Hat) and application developers also gravitated toward libjpeg-turbo because it maintained backward ABI compatibility with libjpeg v6b. Thus, if an O/S was already using libjpeg v6b, they could switch all of their bundled applications to libjpeg-turbo without rebuilding them. libjpeg v7 and later broke backward ABI compatibility, and thus applications had to be recompiled if they wanted to switch from libjpeg v6b to one of the newer IJG releases. Backward ABI compatibility has always been a problem in libjpeg, because all of the structures in the API are exposed. However, libjpeg v6b was out there for such a long time before libjpeg v7 was released (more than 11 years) that the libjpeg v6b ABI became something of a de facto standard, and when libjpeg v7 broke backward ABI compatibility, that caused problems for a lot of developers and integrators. Many of them decided that the features introduced in libjpeg v7 and later weren’t compelling enough to justify breaking backward compatibility, so that drove them toward libjpeg-turbo, irrespective of the performance improvements.

SF: How has SourceForge and its tools helped your project reach that success?
DRC: I particularly like the file release system on SourceForge, because it helps me track the number of downloads for a particular release (which helps to gauge its rate of adoption.) Also, because SourceForge supports SSH, I can easily push new releases and pre-releases to SF as part of my automated build process. Back when the Allura transition took place, I suggested (and the SF developers implemented) several enhancements to the code viewer that helped me maintain my preferred code review workflow.

SF: What is the next big thing for Libjpeg-turbo?
DRC: I’m currently working on extending the library to support AVX2 instructions, which we’re hoping will increase performance by 20-30% on newer x86 platforms that support that instruction set. This feature is being enabled by code contributions and funding from Intel. Another project on the horizon is SIMD acceleration for progressive JPEG compression, which should speed up the compression of progressive JPEGs by about 2x.

SF: How long do you think that will take?
DRC: I expect that both features will land this Fall.

SF: Do you have the resources you need to make that happen?
DRC: The two aforementioned features are funded, but in general, I rely on donations and funded development opportunities to keep this project moving forward. I am an independent developer, so I don’t draw a salary for my work on open source projects. I do things that way because it allows me to keep these projects vendor-agnostic and free of any one organization’s agenda, but the downside is that I have to frequently ask for money in order to keep the lights on. Even if someone else develops a new feature and submits it as a patch, the best-written patches will still require many hours of work to clean up and integrate. It’s hard sometimes to make people understand that maintaining a high-quality open source project costs money, even though the software itself is free. In general, only about half of the work I do on libjpeg-turbo is paid for (either directly, through funded development and donations, or indirectly, through funding from my other open source projects that use libjpeg-turbo.) The other half is pro bono, and it’s a constant struggle to balance the need to move the project forward with the need to put food on the table.

SF: If you had to do it over again, what would you do differently for Libjpeg-turbo?
DRC: I would have probably chosen a different name. There has been a great deal of confusion over the fact that our project is called “libjpeg-turbo” but we provide an API called “TurboJPEG”. However, there’s too much traction at this point to consider a name change.

[ Download Libjpeg-turbo ]

“Community Choice” Project of the Month Vote – June 2016

The vote for June 2016 Community Choice SourceForge Project of the Month is now available, and will run until May 15, 2016 12:00 UTC.

winPenPack: Portable Software Collection

winPenPack is a project that aims at collecting the most frequently used and most popular open source applications made portable, so that they can be executed without installation from any USB Flash Drive or Hard Disk. The winPenPack suites offer a wide range of portable applications like office tools, internet tools, multimedia tools, development tools, security applications and other frequently used utilities. Everything you need, completely free, open source and portable!
[ Download winPenPack: Portable Software Collection ]


MediaPortal turns your PC into a very advanced MediaCenter / HTPC. It allows you to listen to your favorite music & radio, watch and store your videos and DVDs, view, schedule and record live TV as a digital video recorder and much much more
[ Download MediaPortal ]

SQuirreL SQL Client

SQuirreL SQL Client is a graphical SQL client written in Java that will allow you to view the structure of a JDBC compliant database, browse the data in tables, issue SQL commands etc.
[ Download SQuirreL SQL Client ]


Kodi Movistar+ TV es un ADDON para XBMC/ Kodi que permite disponer de un decodificador virtual de Movistar+ TV para distintos sistemas operativos. Las principales funcionalidades son: – Actualización automática de canales. – Guía de programación (EPG). – Grabaciones en la Nube y en local. – Visualización de grabaciones en la nube. – Sincronización de grabaciones a local para evitar su caducidad. – Gestión avanzada de series. – Timeshift. – Distribución de la señal por DLNA. – Últimos 7 días Sistemas operativos soportados: – Windows. – Mac OSX. – Android. – Linux 64 y 32 bits. – Raspberrys (B, B+ y 2), Bannana PI …
[ Download movistartv ]

Bodhi Linux

Bodhi is a minimalistic, enlightened, Linux desktop.
[ Download Bodhi Linux ]


A full-fledged autoclicker with two modes of autoclicking, at your dynamic cursor location or at a prespecified location. The maximum amounts of clicked can also be set (or left as infinite). Hotkeys work in the background for convenience. If you want to automate group of mouse actions, Please try this Whats new in v1.0.0.2: 1. You can now change your hotkeys! 2. Changed the about page 3. Added a few minor options v1.0.0.1 : 1. Your settings are now saved from your last session so you only need to enter them once. (Includes last fixed location) 2. Added double clicking and triple clicking 3. Added Right clicking and middle clicking
[ Download AutoClicker ]

The OpenGL Extension Wrangler Library

The OpenGL Extension Wrangler Library is a simple tool that helps C/C++ developers initialize extensions and write portable applications. GLEW currently supports a variety of operating systems, including Windows, Linux, Darwin, Irix, and Solaris.
[ Download The OpenGL Extension Wrangler Library ]


NamelessRom is opportunity; an opportunity to have a voice to the development team of the after-market firmware that you run on your device. The main goal of NamelessRom is to provide quality development for android devices, phones, and tablets alike. NamelessRom developers are available nearly 24/7 and respond to bug reports and feature requests almost instantly. This availability will allow you, the end-user, to have direct input into exactly what features and functions are included on the firmware that YOU run. NamelessRom == endless possibilities. Unless you have an iPhone, then you’re out of luck. Get more information and find support on our forums at
[ Download NamelessROM ]


Hydrogen is an advanced drum machine for GNU/Linux, Windows and Mac OS X. It’s main goal is to bring professional yet simple and intuitive pattern-based drum programming.
[ Download Hydrogen ]

April 2016, “Staff Pick” Project of the Month – SharpDevelop

For our April “Staff Pick” Project of the Month, we selected SharpDevelop, a free IDE for C#, VB.NET, & Boo projects on Microsoft’s .NET platform.

SharpDevelop was designed as a free, lightweight alternative to Microsoft Visual Studio and as such, works natively with Visual Studio projects and code files. SharpDevelop allows you to write applications in a number of different languages including C#, VB.NET, F#, Boo, IronPython, and IronRuby.

It comes with integrated unit and performance testing tools; Git, NuGet, and many others. Its features include project management, application compiling, code editing and debugging.

This isn’t the first time that SharpDevelop earned the coveted Project of the Month title. In July 2015, it was also voted “Community Choice” Project of the Month alongside Octave-Forge. It’s estimated to have been downloaded over 8 million times worldwide since its inception.

Download both the source code and executable files, or find the latest information and changes on #develop through the forum.

[ Download SharpDevelop ]