SLOODLE is breaching the GPL
Posted by Peter | Filed under SLOODLE
As SLOODLE is a GPL project, we are required to make source code available for everything we produce. This allows users to look at how things work, and it allows other developers to work on tools and contribute to the project and so on. Withholding this means we are breaching our own licence and damaging the future of SLOODLE.
However, since September 2009, SLOODLE has been breaching the GPL in exactly this way. I have made many repeated attempts since then via the issues tracker, forums, IMs, emails, and community meetings to have this resolved, but I have been ignored. Random other development sidetracks have been happily pursued while the responsibility for what we already have has been cast aside.
The problem is related to permissions on the SLOODLE in-world tools and scripts. Up to and including the latest “SLOODLE 1.0 Set revision 13″ the following issues exist:
- The Vending Machine script is no-copy/no-mod, and it is not clear whether an up-to-date copy is in the repository.
- The “Toolbar Giver” script is no-copy/no-mod and it is not in the repository.
- The error message handler script in the LoginZone is no-copy/no-mod.
I know that in themselves, these are quite minor. And some of these issues can be worked around. However, there is a FOSS principle to be upheld, and there is the future of the project to consider.
I appreciate that it is sometimes difficult to identify every little detail of SL perms, and that it is often time-consuming. However, these issues have been explicitly identified (mostly by me) but consciously neglected for 4 months now. If I could have fixed them myself I would have done, but the perms issues mean that even I am prevented from doing so. (They also mean I am prevented from releasing SLOODLE Set updates myself, even if there is a critical bug to be resolved.)
So I ask yet again, please let’s get this sorted.
Leave a Reply
You must be logged in to post a comment.
