Forums » Suggestions
Maybe if all of the big name plugins were at least available on voupr, it'd make more sense to write companion apps for it for the mobile platforms.
The underlying code for VOUPR is open source, so it theoretically could be improved by the rest of the community:
https://code.launchpad.net/~voupr/voupr/trunk
I believe Calder's intention for using an XML framework with VOUPR is to allow for the possibility of an in-game plugin management/updater tool.
https://code.launchpad.net/~voupr/voupr/trunk
I believe Calder's intention for using an XML framework with VOUPR is to allow for the possibility of an in-game plugin management/updater tool.
+1 to Guild host its own plugin repository.
Was proposed before, and something as VOUPR should be present in main VO site, with an icon for each plataform on plugins' details page.
Terms and conditions should be set to be open, similar to LGPL guidelines. Plugins published there become public domain, and are provided as-is, use at your own risk and noSLA/ support provided.
Was proposed before, and something as VOUPR should be present in main VO site, with an icon for each plataform on plugins' details page.
Terms and conditions should be set to be open, similar to LGPL guidelines. Plugins published there become public domain, and are provided as-is, use at your own risk and noSLA/ support provided.
Alloh, if you want the plugins that you write to be LGPL and public domain then you go ahead and do that, otherwise don't try and tell me what rights I must give up for my code.
Alloh: Maybe things are different in Brazil, but in the USA there is a VERY large difference between LGPL and Public Domain.
LGPL prevents people from modifying your code and then distributing as closed-source or otherwise restricted software.
In the USA, Public Domain allows them to do whatever they want with your code, since nobody owns it anymore.
---
As for Alloh's actual suggestion, requiring plugins submitted to an official repository to be released under an open source license of some sort makes sense. For one thing, it reduces concerns about copying other people's code, so that GS doesn't have to deal with figuring out whether somebody violated somebody else's rights. For another, it ensures that people can update and maintain plugins long after the plugin's original author has lost interest in the game.
Anybody who wants to release their plugins under a restrictive license can always do so on their own webspace.
LGPL prevents people from modifying your code and then distributing as closed-source or otherwise restricted software.
In the USA, Public Domain allows them to do whatever they want with your code, since nobody owns it anymore.
---
As for Alloh's actual suggestion, requiring plugins submitted to an official repository to be released under an open source license of some sort makes sense. For one thing, it reduces concerns about copying other people's code, so that GS doesn't have to deal with figuring out whether somebody violated somebody else's rights. For another, it ensures that people can update and maintain plugins long after the plugin's original author has lost interest in the game.
Anybody who wants to release their plugins under a restrictive license can always do so on their own webspace.
I said "similar to LGPL", not "LGPL"... and GS can setup whatever rules they want, also community can create a license that satisfies both. And I agree on public domain, so replace it with "Chosen open license"
Still, no.
Even if they could come up with terms and conditions that were amenable to everyone, as I already said it would divert too much of their already limited time away from the game.
Even if they could come up with terms and conditions that were amenable to everyone, as I already said it would divert too much of their already limited time away from the game.
You could advertise some plugins in stations under some roleplay explanation - "Add this-and-this to your ship today! Created by Itani engineers, it does this-and-this..." etc. And you could download it in-game, but automatically /lua ReloadInterface().