11–20 of 84 posts
Any other projects affected ? Would be nice to start a list of all affected projects. This could also be a case of targeted attack on the gimp account.
People who host software there should move to a different platform.
Earlier quoted context omitted.
Even apache openoffice is using SourceForge for their downloads. There are quite a lot of s/w there at this moment.
OpenOffice has not been relevant for a while; development has moved to LibreOffice. See https://lwn.net/Articles/637735/
Here are some possibilities I can think of, but I'm curious if they're correct:
- Mailing list hosting
- Non-git repository hosting, for projects that prefer CVS or SVN
- Shell account (though it doesn't seem very useful)
- Features GitHub has but few others do (binary hosting, website hosting, etc.) and the project wants to avoid GitHub
Are there others?
Any other projects affected ? Would be nice to start a list of all affected projects. This could also be a case of targeted attack on the gimp account.
The safest thing to do would be to assume that all software there is similarly afflicted and to never use Sourceforge again. People who host software there should move to a different platform.
Any other projects affected ? Would be nice to start a list of all affected projects. This could also be a case of targeted attack on the gimp account.
http://sourceforge.net/u/sf-editor1/profile/ Nice list. Got Audacity there, for instance.
Earlier quoted context omitted.
The safest thing to do would be to assume that all software there is similarly afflicted and to never use Sourceforge again. People who host software there should move to a different platform.
The only issue is that Sourceforge made nice binaries available. Most people have no idea how to use git and/or build their own binaries.
Fortunately, we've moved to our mirror infrastructure since quite some time, and it's faster and way better.
Btw, if any other open source project needs help to distribute their binaries (because of the size), please contact me.
PS-EDIT: signing the installer was a good idea, I guess :)
Earlier quoted context omitted.
The safest thing to do would be to assume that all software there is similarly afflicted and to never use Sourceforge again. People who host software there should move to a different platform.
The only issue is that Sourceforge made nice binaries available. Most people have no idea how to use git and/or build their own binaries.
Earlier quoted context omitted.
The safest thing to do would be to assume that all software there is similarly afflicted and to never use Sourceforge again. People who host software there should move to a different platform.
The only issue is that Sourceforge made nice binaries available. Most people have no idea how to use git and/or build their own binaries.