Archive | General RSS for this section

Third party offers will be presented with Opt-In projects only

In an effort to address a number of concerns we have been hearing from
the media and community at large, we at SourceForge would like to note
that we have stopped presenting third party offers for unmaintained
SourceForge projects.

While we had recently tested presenting easy-to-decline third party
offers with a very small number of unmaintained SourceForge projects,
we discontinued this practice promptly based on negative community
feedback.  At this time, we present third party offers only with a few
projects where it is explicitly approved by the project developer, or
if the project is already bundling third party offers.

As a company, we at SourceForge pride ourselves on being highly
responsive to our community members and, with that in mind, do our
best to respond to all communications and address all concerns in a
timely manner. We encourage anyone that would like additional
information about our practices or specific issues they have  to reach
out to us directly by using the “Help” link in the header of the
SourceForge site, which provides contact information for our Support
team and which will ensure any questions or issues you may have are
resolved in an efficient manner. As usual feel free to contact us also at


June 2015, “Community Choice” Project of the Month – VBA-M

For our June “Community Choice” Project of the Month, the community elected VBA-M, a merge of the original Visual Boy Advance forks. The VBA-M Team shared their thoughts about the project’s history, purpose, and direction.

SourceForge (SF): Tell me about the VBA-M project please.
VBA-M Team: VBA-M started out as a project to merge all known forks of the original Visual Boy Advance into one solid project. I guess you could say “the fork to end all forks” but not at the same time.

SF: What made you start this?
VBA-M Team: We were tired of all the other forks and wanted just a basic build that had the most useful features from various forks. So we merged features from various forks into one place and added a few of our own to make it our own.

SF: Has the original vision been achieved?
VBA-M Team: For the most part we like to think so but like any project, we want to continue improving VBA-M and make it even better. For example, e-reader support, core improvements, and useful features from other forks were added; however, there are still a few things to get working satisfactorily, such as game boy linking; although, recent contributions improved our game compatibility a great deal.

SF: Who can benefit the most from your project?
VBA-M Team: A lot of people benefit from VBA-M, from Game Boy Advance enthusiasts, hardware tinkerers, and folks who own games they no longer have an original system for. For example, a lot of folks played Pokemon on a Game Boy and wished for a bigger screen.

SF: What is the need for improvements upon Visual Boy Advance?
VBA-M Team: Well right now the biggest thing is stabling our new cross-platform interface, which uses the wxWidgets toolkit to make sure each feature works properly cross-platform (Windows, Linux, OSX) on a variety of compilers and libraries. Then we will add features requested by our users, like hardware-accelerated graphics filters and we may even re-implement the linking code, particularly the IPC (single computer) code.

SF: What’s the best way to get the most out of using VBA-M?
VBA-M Team: VBA-M is a merge of the many forks of VBA and the best way is to explore all of the merged features of VBA-M (from GBA to GBA Cable and RFU wireless link gaming, GameCube (Dolphin) link gaming, Game Boy link gaming (across operating systems), e-Reader scanner support, GDB debugging support, xBRZ 1.3 support, OAM viewers, tilt sensor support in WarioWare – Twisted, Solar Sensor support, automatic save type detection, ROM database support and flashcart CHT cheat support for the GBA cheats database). In short, take a look and tell us if we are missing something that you need.

SF: What has your project team done to help build and nurture your community?
VBA-M Team: We simply add features that the community has requested and encourage contributions such as translating the UI to a requested language, reporting bugs, getting VBA-M packaged by Arch Linux, Ubuntu, and Debian, and help with the VBA-M forum.

SF: Have you found that more frequent releases help build up your community of users?
VBA-M Team: Yes, a surge of activity and interest follows whenever a new release occurs. And some of the changes should help narrow down issues considerably.

SF: What was the first big thing that happened for your project?
VBA-M Team: Several things, for instance:

  • darktjm, the original author of the wxWidgets code, decided to contribute some code that paved the way for our new interface. For this we are forever grateful.
  • Replacing the old 1.8 GBA core with a new core, which had a 15% speed increase from the old core and was never officially implemented.
  • The current WIP WxWidgets GUI, and the mature libretro implementation, which both opened the doors for true extensive cross platform compatibility by RetroArch; a rather nice way of running emulator cores, games, graphics demos, and other things.
  • Replacing the APU with the one written by Blargg improved the audio of many games while reducing emulation complexity.

SF: What helped make that happen?
VBA-M Team: A couple of months ago, during a quiet period, we started to fix the linking and tried to improve the wxWidgets interface, including bringing in features that were initially in the MFC interface over to the new interface so that all wxWidgets platforms are represented.

SF: What was the net result for that event?
VBA-M Team: Overall, we have a unified interface for major operating systems and an improved user experience

SF: What is the next big thing for VBA-M?
VBA-M Team: Once we fix a small few issues, we are hoping to do a few beta builds and do a 2.0.0 release finally.

SF: How long do you think that will take?
VBA-M Team: We hope that when this interview is published we will have gotten through a few betas and, maybe, have a release candidate.

SF: Do you have the resources you need to make that happen?
VBA-M Team: Yes, for the most part but we could do with some other platform developers, such as an OSX developer, if possible. Actually, any help would be appreciated, such as help making bug fixes, creating new features, finding and reporting bugs, translations, and supporting new users in the forum.

SF: If you had it to do over again, what would you do differently for VBA-M?
VBA-M Team: Using a cross-platform UI system like wxWidgets instead of a single-platform framework like MFC would have made VBA-M usable by a wider user base and improve the underlying GB/GBC/GBA cores.

SF: Why?
VBA-M Team: To make it more accurate and improve speed.

SF: Any reason you can’t do that now?
VBA-M Team: Presently, the issue is the time to go back and do it over again.

SF: Is there anything else we should know?
VBA-M Team: We accept all feedback, both positive and negative at the VBA-M forum.

[ Download VBA-M ]

June 2015, “Staff Pick” Project of the Month – git-osx-installer

For our June “Staff Pick” Project of the Month, the we selected git-osx-installer, a stand-alone installer for Git. git-osx-installer’s lead developer, Tim Harper, shared his thoughts about the project’s history, purpose, and direction.

SF: What made you start this?
Harper: Six years ago (or so), before Git really started to dominate the developer tool space, I wanted to get our graphic designers using Git. The biggest issue was getting Git deployed to their laptops. Installing Xcode, then building, and compiling git from source was too much work. There wasn’t an installer yet, so I saw an opportunity to contribute to a tool I loved and also solve a problem at work simultaneously; thus, the stand-alone installer was born.

SF: Has the original vision been achieved?
Harper: Yes. Since then, Apple has started to ship Git with their Xcode tools package, which is helpful. However, it’s all bundled together unfortunately, so having the stand-alone installer is a nice option for those who just want Git and don’t want to install the rest of the stuff on their laptop.

SF: Who can benefit the most from your project?
Harper: People who just want Git and don’t want the entire build-stack.

SF: What’s the best way to get the most out of using git-osx-installer?
Harper: The biggest issue I see is people don’t follow the instructions or don’t know which version to install. Because OS X versions have differed so much, I’ve had to start building versions of the installer for those who are still on old versions of Git.

SF: What has your project team done to help build and nurture your community?
Harper: We’ve provided a streamlined way for the OS X masses to install and use Git.

SF: Have you all found that more frequent releases helps build up your community of users?
Harper: People do get annoyed when the installer is significantly behind the latest release, so yes.

SF: What was the first big thing that happened for your project?
Harper: The installer just kind of took off on it’s own. I didn’t really need to market it, just let a few people know about it’s existence. Initially, I posted comments on blog articles where people described how to install git. referred to the installer as the official way to get Git installed on OS X laptops and that has been good for the effort.

SF: What is the next big thing for git-osx-installer?
Harper: I plan to continue to support the project while it fulfills a need. If somebody comes along and does a better job at it, I’ll happily hand over the reigns. I just want to see Git succeed as much as possible because it truly is a marvelous tool.

SF: Do you have the resources you need to make that happen?
Harper: Yes

SF: If you had it to do over again, what would you do differently for git-osx-installer?
Harper: There was a period where I neglected the project and there were installer issues on older OS X versions; that created “bad karma” and earned the installer some one star reviews. I was quite busy with life but could have made it a priority to solve these issues earlier and help people avoid frustration.

[ Download git-osx-installer ]

Project of the Week, June 1, 2015

Here are the featured projects for the week, which appear on the front page of

SciPy: Scientific Library for Python

SciPy is package of tools for science and engineering for Python. It includes modules for statistics, optimization, integration, linear algebra, Fourier transforms, signal and image processing, ODE solvers, and more.
[ Download SciPy: Scientific Library for Python ]

JasperReports Library

The JasperReports Library is the world’s most popular open source reporting engine. It is entirely written in Java and it is able to use data coming from any kind of data source and produce pixel-perfect documents that can be viewed, printed, or exported in a variety of document formats including HTML, PDF, Excel, OpenOffice, and Word.
[ Download JasperReports Library ]


dispcalGUI is a graphical user interface for the display calibration and profiling tools of Argyll CMS, an open source color management system. Calibrate and characterize your display devices using one of the many supported hardware sensors, with support for multi-display setups and a variety of available settings like customizable whitepoint, luminance, tone response curve, the option to create matrix and look-up-table ICC profiles, with optional gamut mapping, and some proprietary 3D LUT formats.
[ Download dispcalGUI ]


WinPython is a free open-source portable distribution of the Python programming language for Windows XP/7/8, designed for scientists, supporting both 32bit and 64bit versions of Python 2 and Python 3.
[ Download WinPython ]

Filesystem in Userspace

FUSE makes it possible to implement a filesystem in a userspace program. Features include: simple yet comprehensive API, secure mounting by non-root users, support for 2.4 and 2.6 Linux kernels, and multi-threaded operation.
[ Download Filesystem in Userspace ]


Scintilla is a free source code editing component which includes useful features such as syntax styling, error indicators, folding, code completion and call tips. The project includes SciTE (SCIntilla based Text Editor).
[ Download Scintilla ]


SuperTuxKart is a 3D kart racing game featuring Tux and friends.  It is a racing game focusing on fun and ease of play, and includes many tracks, characters, and items for you to try.
[ Download SuperTuxKart ]

Quite Universal Circuit Simulator

Qucs is a circuit simulator with a graphical user interface. The software aims to support all kinds of circuit simulation types such as, e.g. DC, AC, S-parameter, Transient, Noise, and Harmonic Balance analysis. Pure digital simulations are also supported.
[ Download Quite Universal Circuit Simulator ]

West Point Bridge Designer and Contest

A national virtual bridge engineering contest with prizes for middle and high school kids, grades 6 to 12, but anyone can enter for fun. Based on the award-winning Bridge Designer client software, now Open Source through this project. The website infrastructure supports worldwide participation in qualifying and semifinal rounds with a tiny administrative staff. The new Rails back end is a RubyMine project. Thanks to JetBrains for this mega development environment!
[ Download West Point Bridge Designer and Contest ]

GIMP-Win project wasn’t hijacked, just abandoned

There has recently been some report that the GIMP-Win project on SourceForge has been hijacked; this project was actually abandoned over 18 months ago, and SourceForge has stepped-in to keep this project current.  For more details, read on…

The GIMP-Win project was registered on SourceForge in October of 2004.  In 2013, the GIMP-Win author discontinued use of SourceForge for download delivery.

Based on our prior outreach to the GIMP-Win author, we understand that they had concerns about the presence of misleading third-party ads on SourceForge.  They were not alone in those concerns — we were also concerned — leading us to establish a program to enable users and developers to help us remove misleading and confusing ads.

In cases where a project is no longer actively being maintained, SourceForge has in some cases established a mirror of releases that are hosted elsewhere.  This was done for GIMP-Win.

When we establish a mirror, we change the status on the project to clearly delineate it as a mirror, and change administrative control of the project to clearly delineate that it is editorially curated by SourceForge.

Mirrored projects help enable end-users to stay current with the latest releases, particularly where SourceForge continues to house historical releases for community benefit.

Mirrored projects are sometimes used to deliver easy-to-decline third-party offers, and the original downloads are always available.

Since our change to mirror GIMP-Win, we have received no requests by the original author to resume use of this project.  We welcome further discussion about how SourceForge can best serve the GIMP-Win author.

[updated on 28-5-2015] Since yesterday, SourceForge Gimp-Win mirror downloads only the original software without any offers. We also invite the Gimp-Win developer to take back control of the project if that is his desire, while respectfully asking that he maintain any project updates or allow us to do so.