Support Technician at SourceForge.net
@tremblaysimon The only place where we (SourceForge) display this is in the files interface as described above. Also, quite frequently, individual projects will choose to post file hashes on their own websites.
9 months, 2 weeks ago on Verifying Downloaded Files
We do have some features that can help automate releases. For example, we offer uploads via SFTP (which you already use), SCP, and rsync over SSH. The latter two in particular are well suited for incorporating into some sort of a release script (I personally like rsync the best for this). See our documentation here: https://sourceforge.net/p/forge/documentation/File%20Management/
Note that you can use those to upload to both the project web space as well as the file release system.
As for making a file default, we have some instruction on doing that via an API here: http://sourceforge.net/p/forge/community-docs/Using%20the%20Release%20API/
For tickets, it's not currently possible to change admin settings via an API, but we do have an API that can be used to interact with tickets, wiki pages, etc. http://sourceforge.net/p/forge/documentation/Allura%20API/
Hopefully this information helps, please let us know how else we can advise. If you can elaborate on the "etc", perhaps I can provide some insight on that as well.
Chris Tsai, SourceForge.net Support
9 months, 2 weeks ago on Continuous Delivery is for Open Source Too
@ilg That was an unrelated issue. This has also been fixed.
11 months ago on Allura Platform Instability
As this blog post implies, we (SourceForge) do not have, and are not distributing the distribution known as Anonymous OS. We are not able to send it to any users, if you ask us to send it to you, we will not be able to assist with that request. As a courtesy to those who mistakenly commented on this thread with their email addresses, I'm removing your comments to protect your privacy.
1 year, 2 months ago on Anonymous-os project response
All: we just fixed the svn issue that was causing the "Can't find a temporary directory" errors.
digal: perhaps that was related to the issue you were seeing as well? I just tried an http:// checkout and it worked just fine for me.
2 years, 3 months ago on Various SourceForge services down – UPDATE, all services restored
If the access URL for the repository starts with "projectname.scm.sourceforge.net" it's a on the classic system. eg. https://scummvm.svn.sourceforge.net/svnroot/scummvm
If the URL for the repo starts with "code.scm.sf.net" (or "code.scm.sourceforge.net"), then it's on the new SourceForge platform. eg. git://git.code.sf.net/p/allura/git
For those who missed it, we sent an email out today with some clarification and updates. The info in the email can also be found here: https://sourceforge.net/p/forge/community-docs/Hosted%20Apps%20Retirement/
In short, 1) We're extending the deadline, see the info page above for a more detailed timeline
2) we clarified what we mean when we say "Hosted Apps", and now have a page that lists all your Hosted Apps: http://sourceforge.net/help/hostedapps/
2 years, 6 months ago on Hosted apps retirement
@bungeshea Not yet, but setting up redirects is part of the plan.
Bug is fixed, upgrades are re-enabled.
Hosted Apps specifically refers to applications which are installed to http://sourceforge.net/apps/<appname>/<projectname>/
If the URL of the tool in question does *not* match that, then it's not a Hosted App.
If you'd like to me to check on your project specifically, please let me know what project you're curious about.
We found a major bug in the forum upgrade, so we've disabled access to upgrades in the meantime.
@DaveGarratt This doesn't affect all projects, there are many where this just doesn't apply. That said, I agree it is crucial that all affected parties are aware. Our next step is that to send out emails to all the project admins with Hosted Apps enabled.
2 years, 7 months ago on Hosted apps retirement
@DaveGarratt Yes, I've gotten confirmation that the team has set backups for Hosted Apps as a priority item.
Please log a support ticket for this and I'll get it passed along to the proper team: https://sourceforge.net/apps/trac/sourceforge/newticket
We use the Short URL service quite extensively ourselves, so we're definitely going to work something out for this. The planning for just exactly how we're going to manage it isn't complete yet, I'll make sure the team working on that sees your feedback. More details when we have concrete plans for this service.
We're passing this feedback on to the team, though, I don't think we'll be able to extend this timeline, but if we are, we'll definitely update this post to reflect that.
@Robert Munteanu We do in face have plans to set-up redirects (and/or give projects the option to), though we haven't planned exactly how this is going to work. We'll keep this post updated with more detail on that as we have it.