Re: [isabelle] Moving the AFP away from SourceForge
Could we not maintain a skeleton web site at afp.sf.net that simply
forwards the afp.sf.net URLs to the new location?
I also think that it would be prudent to move away from hosting any
actual content on Sourceforge as soon as possible.
On 28/05/15 11:30, David Cock wrote:
Could we get a stable domain now, and point it at afp.sf.net, so that
people can start citing that instead, and if/when a move is necessary,
no new dangling citations are created?
On 28/05/15 11:24, Gerwin Klein wrote:
Weâve already thought about that, itâs not the first malware incident
So far, Iâm monitoring the situation for the AFP - content-wise weâre
not dependent on anything SF is doing and could move any time.
The problem is URL stability: lots of papers have citations pointing
to afp.sf.net, which would then all be dead or worse, point to
On 28.05.2015, at 19:16, Lars Hupel <hupel at in.tum.de> wrote:
I think we should seriously consider moving the AFP away from
SourceForge. The final nail in the coffin is that the company behind
SF.net started replacing genuine downloads with their own versions with
added adware. The latest evidence is from the GIMP project:
In that particular case, it affected an inactive project. The AFP is
very much not inactive, but nonetheless, nobody guarantees that SF.net
won't further extend this practice. They will probably not touch the
Mercurial source repositories, but the official AFP download uses
SF.net's download facility:
Better alternatives exist, for example Bitbucket. They also offer
repository hosting, web hosting, and file download.
The information in this e-mail may be confidential and subject to
legal professional privilege and/or copyright. National ICT Australia
Limited accepts no liability for any damage caused by this email or
This archive was generated by a fusion of
Pipermail (Mailman edition) and