Well ... imho, the only safe way to handle such issues is to check whether there is an
open sourced license clause in the source code. Only then you can safely use code after
an account is expired.
I consider all my work as published under GPLv3, although not everywhere I included the
license clause (I should definitely make work of it).
Regards
Annabel
----- Original Message ----
From: Mike.lifeguard <mike.lifeguard(a)gmail.com>
To: toolserver-l(a)lists.wikimedia.org
Sent: Thu, February 4, 2010 8:14:09 PM
Subject: Re: [Toolserver-l] Changes to expired accounts web hosting
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10-02-04 03:07 PM, Jesse (Pathoschild) wrote:
Synchbot registers an account on every wiki in two
minutes (faster
with changes), which I wouldn't want in the hands of our crosswiki
attack username vandals.
I didn't think you ran that from the toolserver, since that bot requires
the user's login data.
Regardless, keep in mind that even if the code is freely licensed, there
is no requirement for you to distribute it. Simply don't publish the code.
But now we get into questions of how to know which code should be
published and which shouldn't be if the author is gone... Do we simply
assume it can be redistributed safely unless there's a note in the
header? I have a headache, I leave the pondering on this to others
- -Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAktrHH4ACgkQst0AR/DaKHu3AACfUixZVXW6jhquOTFMaHVZlbZD
JI8An2Dvju6GU8XDug/QKgo9l2m3tSlP
=sKSy
-----END PGP SIGNATURE-----
_______________________________________________
Toolserver-l mailing list (Toolserver-l(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/toolserver-l
Posting guidelines for this list:
https://wiki.toolserver.org/view/Mailing_list_etiquette