Archive | Site News RSS for this section

Introducing SourceForge Deals

Screen Shot 2015-05-11 at 10.29.04 AM

What is SourceForge Deals?

It’s pretty simple:

SourceForge Deals is an online storefront with merchandise that’s chosen, stocked, and fulfilled by a third-party with products that are intended to be of interest to you.

To amplify this:

While we might have used some of the products on offer, we can’t offer an endorsement of any product that we haven’t used. You may remember that for a long time SourceForge was linked to ThinkGeek  (a service of Geeknet) and you’ll see that SourceForge Deals has some similarities to ThinkGeek’s service. For example, SourceForge makes money if you buy any of the product deals through the store, which helps us bring you more of the free downloads that you have come to expect. With that said, SourceForge Deals is not SourceForge and vice versa, but we hope you enjoy it!

SourceForge’s Ongoing Effort to Eliminate Misleading Ads

SourceForge is home to over 400,000 Open Source projects. Our site and our work to support software development projects is funded in part through advertising. We’d like to give you an update on our advertising initiatives to date and discuss what’s coming next.

Here’s what we’ve been doing to eliminate misleading ads

In November 2013, we launched our BlockThis initiative to remove misleading and confusing ads. For example, ads that appear on our download page and feature a big green download button, which clearly seeks to draw users away from the legitimate download flow. Since starting this initiative, we’ve discovered that approximately 95% of the few dozen ad complaints we’ve received have been legitimate, resulting in the removal of these offending ads. We plan to continue our BlockThis initiative and our work with advertising partners to identify and prevent misleading ads.

We’re taking a new approach to unwanted Web space ads

images-1We’re extending the BlockThis program to include advertising that appears on our Project Web. While we had routed these complaints to project teams in the past, certain recent uses of the Project Web have triggered ad concerns, resource abuses, and Chrome security issues, which is why we are taking direct action.

Here’s how you can help!

If you see a confusing ad, drop us an email at blockthis@sourceforge.net providing a screenshot and, more importantly, the full link to the ad. To copy it: Right click on the link and choose “Copy Link Location” in FireFox; “Copy Shortcut” in Internet Explorer; “Copy Link” in Safari; and, “Copy Link Address” in Chrome. We’ll be sure to review all requests and, if we agree with your complaint, we will take immediate action.

How to migrate from Google Code to SourceForge

Today Google announced that it is bidding farewell to Google Code by disabling new project creation and officially shutting down the service on January 25th, 2016. That means if you want to keep your project up-to-date, you’ll need to prepare to migrate off of Google Code by August 24, 2015, when the site goes read-only. As noted in the announcement, Google recommends some very good migration path options, including the option to migrate from Google Code to SourceForge.

What can I expect when migrating to SourceForge?

Consider that, while the GitHub importer will convert any SVN or Mercurial project to Git, only SourceForge offers a migration path from Google Code that allows you to keep your Git, Mercurial, or SVN project repos intact. And the SourceForge importer converts all your wiki pages, issues including attachments, and download files.

What does SourceForge offer, beyond free code hosting?

For starters, SourceForge welcomes you to distribute your releases via SourceForge even if your code is developed elsewhere. Back in 2012, we began supporting other ecosystems like BerliOS and we’ve always provided options for projects hosted on Github, even when they changed their file upload feature-set. And, we extended that offer to projects hosted on Google Code, when Google deprecated the download part of the Google Code service. We did this by offering the ability to fully import Google Code downloads, including the option to simply distribute downloads via SourceForge.

To date, almost 500 projects from Google Code have used our tools to import their project (either in part or whole) to SourceForge. For example, mplayerx uses SourceForge to keep their community up-to-date on their latest releases for OSX. Some other benefits that go along with migrating your project to SourceForge are that we offer editorial support for videos and reviews, and an enterprise directory listing for qualified Open Source projects.

As we welcome you to migrate from Google Code to SourceForge, we strengthen our promise to continue to create a culture of inclusivity that brings innovative people together for a long time to come. We certainly aren’t resting on our laurels; rather, our fully Open Source platform is developed at Apache (under the Apache Allura label) with the aim to continually upgrade our performance, appearance, and scalability. That’s why we think it’s worth your time to look into Sourceforge and see for yourself!

Let us know if you have any questions at communityteam@sourceforge.net.

For additional information, see: How to sync a GitHub or Google Code repo to a SourceForge project

How to use webhooks for Git, Mercurial, and SVN repositories

We are excited to announce that SourceForge now supports webhooks for all Git, Mercurial, and Subversion repositories!

What are WebHooks?

Webhooks are custom URLs that project admins specify for their repo so that, when a commit occurs on that repo, you are notified via that URL. The advantage of webhooks is that you can set up automatic interactions with 3rd-party services to run tests, generate documentation, notify a chat room of your commits, and much more.

How to configure a webhook

Configure a webhook in the Admin section of your project by clicking on Tools. That’s where you’ll find your repository’s Webhooks link. All you need to do is enter your webhook URL and you’re good to go!

admin-webhooks

Many services work with webhooks, particularly those that use the URL as a trigger including Read the Docs or any Jenkins instance, without relying on specific details in the POST body. Some services use a webhook POST payload to see details like the commit message, branch, or user. Our webhook’s POST payload is similar to that of GitHub, so many services (e.g. Slack, etc.) will work when you manually configure a GitHub integration and paste the URL into the SourceForge webhook configuration page. However, if a service doesn’t work, for SourceForge compatibility, just ask its admin to update that service’s webhook handling to support the Allura webhook format.

When creating a service to listen to SourceForge webhooks, refer to the Allura webhook documentation for detailed examples of POST payloads and instructions on validating a webhook signature.

POST payload sample

Here’s a quick example of the POST content for Git, to whet your appetite:

{
    "after": "a72ab8566ed1a81e485a8451868ee9364069ea6b", 
    "before": "27bc571ceb56beeda796e0069bfba84581f55770",
    "size": 1,
    "commits": [
      {
        "id": "a72ab8566ed1a81e485a8451868ee9364069ea6b", 
        "message": "Update README", 
        "added": [], 
        "copied": [], 
        "removed": [], 
        "modified": [
          "README.md"
        ], 
        "author": {
          "email": "jetmind@example.com", 
          "name": "Igor Bondarenko", 
          "username": "jetmind"
        }, 
        "committer": {
          "email": "jetmind@example.com", 
          "name": "Igor Bondarenko", 
          "username": "jetmind"
        }, 
        "timestamp": "2015-02-23T14:30:42Z", 
        "url": "http://sourceforge.net/p/test/git/ci/a72ab8566ed1a81e485a8451868ee9364069ea6b/"
      }
    ], 
    "ref": "refs/heads/master", 
    "repository": {
      "full_name": "/p/test/git/", 
      "name": "Git", 
      "url": "http://sourceforge.net/p/test/git/"
    }
}

We also offer a Webhook management API to programmatically add, update, and remove webhooks. This is ideal if you’re creating an app or service and want to offer users a super-easy webhook configuration via an OAuth application and our webhooks APIs.

SourceForge runs on Apache Allura’s Open-Source Platform, which includes webhooks functionality.  You could contribute improved payloads, entirely new webhook events, and run your own internal project hosting site with the advanced features of Allura!

We hope you enjoy using webhooks at SourceForge!

New Hardware Platform Migration Continues

SourceForge.net is continuing to improve its hardware platform. The next phase of migration effects the Web area of projects

(e.g. http://project_UNIX_name.sourceforge.net). These projects will be put into Read Only mode for maintenance between 14:00 and 23:00 UTC on 12/17.

For updates, follow our @sfnet_ops twitter account.

Thanks,
SourceForge Support