Written by robert-vazan the 1 Sep 12 at 11:30.
Global category: Project Web.
New
Sourceforge encourages projects to migrate their hosted apps (e.g. WordPress or wiki) to project web space. All these apps come with administration interface that requires administrator to log in. Since project web doesn't support SSL, administration sessions go through unencrypted HTTP connections, which makes them vulnerable to trivial password/cookie sniffing attacks. This is particularly important on sourceforge where software is distributed to end users. Hijacking WordPress, for example, would allow the attacker to insert fake download links that would enable the attacker to infect thousands of other systems.
Written by hackerb9 the 31 Aug 12 at 05:21.
Global category: User Interface.
New
One of sourceforge's main features is the ability to download a program or source code. Unfortunately, this ability is hampered by the allowance of advertisements that have big "DOWNLOAD" buttons. An unsuspecting user can easily click on them thinking they are using a button which is truly part of sourceforge rather than a link to an external site.
Written by yaplej the 9 Aug 12 at 23:19.
Global category: Tracker.
New
The Tracker is a great tool for support tickets, feature requests and bugs but lacks any method to get feedback from users what Features they really want.
There are other tools such as IdeaTorrent but that requires installing the app and configuration so its not "ready to go".
Written by tosterdahl the 8 Aug 12 at 16:46.
Global category: Donations.
New
I really like the idea of open source. Yet, open source means that the results are shared, it does not necessarily mean that developers are unpaid. In fact most large open source projects have contributors paid by different organisations. While this works well for those projects, for the smaller projects often hosted on Source Forge contributors have better things to do with their time than hunting for sponsors. For some consumer-oriented projects with many users the prospect of coordinating sponsorships of perhaps a couple of bucks each is not realistic. On the contrary - people and organizations would be more likely to want to donate if they can pay for particular features. Sponsors would profit from being able to influence the direction of a project. By providing a revenue stream open source project leads could engage people that would otherwise not be available to the project.
Written by tg1w the 1 Aug 12 at 13:59.
Global category: Source Code Mgmt. (SCM).
New
Hi
I'd be happy to get more expressive information out of the "Browse commits" command. This implies seeing the revision numbers, if not also the author.
Also, I find it confusing that I cannot "Browse commits" only for a particular folder/file. I would see the "Browse commits" button as taking into consideration the actual browsed folder on the GUI, and not the whole SVN repository.
Finally, this would be related to browsing the repository: we have access to a "Read/Write access" bar which is followed by a textbox with an svn command in it. Unfortunately, this command also does not take into consideration the currently browsed folder. I would appreciate if, after browsing a folder, I would get a direct "svn checkout" link to it.
Written by yaplej the 28 Jul 12 at 05:44.
Global category: SCM - Subversion.
New
With multiple users commiting changes it might be good to have some enforcement of code style rules in svn to ensure that all the code is writen in a similar style.
Written by cosmicknight the 6 Jul 12 at 18:44.
Global category: Community.
New
There are a lot of projects available and it is not always clear exactly what each does. Researching the choices and trying out candidates is a cumbersome, time consuming task. Word of mouth is powerful way to connect those who know what a project does with those who have a problem to solve. This would benefit users who need a solution and projects by bringing them together.
Written by danielkaneider the 1 Jul 12 at 10:11.
Global category: File Release System.
New
Many projects are releasing both x64 and win32 versions of their builds. Currently the system neither does automatically choose a x64 download version for users with that operating system, nor is there a possibility to set some file as a default download considering cpu level. Only differentiations on OS level is currently possibile.
The result is, that many user with a x64 operating system download a 32bit build although there would be a x64 build available.
Written by x-n-th the 30 Jun 12 at 16:45.
Global category: User Interface.
New
Icons for supported platforms on the project pages should have pop up information tool tips , for example ; could be extended to every icon showing any information. I didn't know what the icon for the BSD OS looked like and had to search for it. This readily available information via a popup would "encourage" users like me to use these vaious other softwares.
ThanX,
BillH
Written by jeffharris the 15 Jun 12 at 20:22.
Global category: SCM - Mercurial.
New
The specific problem encountered is the lack of push/pull support for bookmarks. The bookmark extension can be enabled, but push and pull do not work with it. The newer versions of Mercurial support push and pull of bookmarks.
The phases feature would also be available with the newest version of Mercurial.
Written by dubslow the 7 Jun 12 at 15:25.
Global category: SourceForge 2.0 Beta.
New
In my Code application, when I click on the primary .cu CUDA file (or the Makefile), it says "[file] is not known to be viewable in your browser." This despite the fact that I added .cu as a "Viewable File Extension" in the admin area of the Code app. And then of course, when I force it to display, it's displayed as plain text, despite the fact that CUDA is a subset of C++ and (my file at least) is essentially just C anyways.
Written by dubslow the 7 Jun 12 at 07:44.
Global category: File Release System.
New
In the Downloads area, files such as a "README" or in my case a default .ini configuration file are examples of files that can and should be updated by developers. However, anytime someone commits a revision to such files, currently an admin (or someone with permissions) has to download that new revision and then upload it from their hard drive to the Downloads tool.
Written by ffried94 the 4 Jun 12 at 14:08.
Global category: SCM - Git.
New
I would like to make sparse checkouts on my git repository.
I got an error message all the time, so I googled a little bit.
I found out that sparse checkouts are not possible, because git 1.6 doesn't support that. And on the SourceForge Servers thats the running version of git.
I would like to be able to navigate to a *specific line* in that file.
Rationale: Whenever I get errors in my program, I know the exact line of code where the error occurred. At the moment I just display the line number and a link to the file on sourceforge, meaning the user has to scroll down through several thousand lines of code to find the exact spot where the error occurred. This is tiring and inconvenient. I would like to be able to point the user to the exact place in the code.
Such a feature could save me from a lot of offline debugging time (I don't always have my programming/debugging tools at hand).
Thanks for reading this suggestion!
[Edit:] A bold after-thought: of course, this suggestion is steering in the direction of "wikify-ing" complex programming projects - imagine being able to edit code and commit directly online, from the scm page...
Todor