Menu

#165 Move off of Sourceforge

1.0
closed
nobody
None
2017-02-06
2015-06-15
Ram Rachum
No

Sourceforge has recently started to bundle malware with downloads.

See this site: http://helb.github.io/goodbye-sourceforge/

I suggest that Msys2 find a new home. GitHub is the obvious choice. (And there are other choices if GitHub is not good enough for some reason.)

Related

Tickets: #165

Discussion

  • Alexx83

    Alexx83 - 2015-06-16

    Currently I don't know where we can move as we need large file storage and big traffic.

     
  • Ram Rachum

    Ram Rachum - 2015-06-16

    I'm guessing that "large file storage" applies to serving binaries? And the big traffic is to those binaries?

    I used to serve binary downloads of my open-source project PythonTurtle (much smaller than Msys2) on Sourceforge, and I moved them to Bintray a couple of weeks ago. Seems to be working fine.

    I see on this blog post that GitHub does seem to provide binary downloads: https://github.com/blog/1547-release-your-software

    What do you think?

     
  • Alexx83

    Alexx83 - 2015-06-16

    We have lot of files currently and upload new files avery day. Also some packages very big - about 500Mb. To upload packages we need at least ftp or ssh not web interface.

     
  • Ram Rachum

    Ram Rachum - 2015-06-16

    I understand. I think that the problem is solvable, but it's up to you and I understand that the transfer costs might not be worth it. Thanks for listening!

     
    • Ram Rachum

      Ram Rachum - 2015-06-16

      Another thing to consider is using both GitHub and Sourceforge, keeping the
      downloads on Sourceforge but using GitHub's issue track instead of
      Sourceforge's. See those annoying lines below my message? They wouldn't
      appear on GitHub.

      On Tue, Jun 16, 2015 at 8:44 PM, Ram Rachum coolrr@users.sf.net wrote:

      I understand. I think that the problem is solvable, but it's up to you and
      I understand that the transfer costs might not be worth it. Thanks for
      listening!


      Status: open
      Milestone: 1.0
      Created: Mon Jun 15, 2015 06:48 PM UTC by Ram Rachum
      Last Updated: Tue Jun 16, 2015 05:42 PM UTC
      Owner: nobody

      Sourceforge has recently started to bundle malware with downloads.

      See this site: http://helb.github.io/goodbye-sourceforge/

      I suggest that Msys2 find a new home. GitHub is the obvious choice. (And
      there are other choices if GitHub is not good enough for some reason.)


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/msys2/tickets/165/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Tickets: #165

  • Alexx83

    Alexx83 - 2015-06-16

    We already use github as issue tracker for packages.

     
  • Alexx83

    Alexx83 - 2015-06-16

    For MSYS2 core you can also create issues on github on msys2-packages.

     
  • Tony Kelman

    Tony Kelman - 2015-06-17

    Homebrew moved to Bintray for large file storage several months ago, they have an API you can use to programmatically upload packages. In addition to sourceforge being sleazy, it's horribly unreliable, going down multiple times a week - totally unsuitable to be relied upon if msys2 packages are going to be used in a production setting.

     
  • Maximus5

    Maximus5 - 2015-06-19

    If you want to try GitHub downloads, you may try my script. I'm using PowerShell to upload ConEmu binaries to GitHub for a long time.

    https://github.com/Maximus5/Scripts/tree/master/PowerShell/GitHub-Release-Upload

     
  • Maximus5

    Maximus5 - 2015-06-19

    BTW, how do you upload binaries to sourceforge? I get a weird bug with scp hang a few months ago...
    https://sourceforge.net/p/forge/site-support/10647/

     
  • Alexx83

    Alexx83 - 2015-06-19

    I'm use rsync+ssh like:

    rsync -avP -e ssh *.* lexx83@frs.sourceforge.net:/home/frs/project/msys2/REPOS/MINGW/Sources/
    
     
  • Omega

    Omega - 2015-08-05

    Just wanted to say that on top of hoping to see this project move to github, that I did encounter some unavailable servers while trying things out yesterday. You'd probably benefit from a lot of positive attention by being there too. My gut is telling me that msys2 seems like the best option for FOSS tools on Windows ATM.

    If Google is shutting down code, Microsoft is ditching codeplex...Moving to github is a no-brainer here! :)

     
  • Ray Donnelly

    Ray Donnelly - 2015-08-05

    It's not a no-brainer. github doesn't support binary packages with the arbitrary filenames and comprehensive upload methods that we require.

     
  • Omega

    Omega - 2015-08-05

    I'm confident that if homebrew can pull it off, so can you.

     
  • Ray Donnelly

    Ray Donnelly - 2015-08-05

    Homebrew doesn't use github for binary packages, they use bintray.

    We use github as the source for our packages the same way that homebrew do (please read this whole thread as this has all been said here already).

     
  • Omega

    Omega - 2015-08-05

    Hey, no need to get so defensive man, I'm just trying to show some positive support.

    Is there something about bintray that wouldn't work?

     
  • Ray Donnelly

    Ray Donnelly - 2015-08-05

    I'm not. Please read entire threads before posting and adding to the confusion.

    Bintray might work, I'm hopeful. Thanks for the support.

     
  • Ed

    Ed - 2016-08-29

    I find Sourceforge as an issue tracker much less user-friendly than GitHub.

    Given that the issues for packages already live on GitHub, please can we move the canonical location for MSYS2 base installer/archive/... to GitHub too? The packages themselves can remain on SourceForge for now - let's not overcomplicate the issue tracker move :-)

    ie please can:

    • someone decide whether MSYS2 base/installer/archive issues belong in https://github.com/Alexpux/MSYS2-packages/issues or whether another repo's issue section (even a dummy repo just for issues) would be more appropriate
    • documentation be updated to point at this chosen issues page on GitHub
    • tickets on sourceforge be closed out, through a combination of refiling (if obviously still an issue) or else "please refile at X if this still affects you" type comments
    • this issue tracker be deleted / switched to read-only or otherwise made obviously not the canonical location

    .

    As a potential follow-on, the project home (ie description/landing page) could be changed from https://sourceforge.net/projects/msys2/ to somewhere on GitHub, meaning that SourceForge is then only used for file hosting.

    Many thanks!

     

    Last edit: Ed 2016-08-29
  • David Macek

    David Macek - 2017-02-06
    • status: open --> closed
     
  • David Macek

    David Macek - 2017-02-06

    The move has been on for some time now and is currently happening more intensively (I'm trying to filter and move the issues). I will investigate if we can use BinTray (there's already some account: https://bintray.com/alexpux/msys2) as an alternative mirror.