All code will be available, that don't mean everyone will have to merge it to their server... We will not take any code outside of 14.1. For what comes after we are done, read post 57 again.
All code will be available, that don't mean everyone will have to merge it to their server... We will not take any code outside of 14.1. For what comes after we are done, read post 57 again.
Lolindir
SWGEmu Admin
SWGEmu is a non-profit, open source community project.
How to report bugs | Mantis (Bug Tracker) | Live Support
Install SWGEmu | Fix SWGEmu | Submit a ticket
As it was already stated, scripts/data should not be subject to AGPL, only changes made to the core files. Also, as i stated before, if you are worried about your individualism, or you don't want to share your work, just put on hold any changes you want to make to the core till 1.0 is released.Originally Posted by Khieran
OR... Keep your changes private... Correct? (knowing full well this is non-official ATM)...
No, by law you are obligated to make all changes made to the core3 open source and available to everyone or risk legal actions being taken against you. There is no legal way around it, and yes it is all very official.
Well, its not worth it to me just for a timer removal that i dont mind in the first place. I guess ill keep working in my current env and hold onto it till 1.0. Sounds like my best option.
so since it's official, can you start answering specific questions?
I think I'm probably boarding the same train as you, although I do have a couple QOL mods I'm working on that would be MUCH easier to test if I could leave the server going for a couple days. Still, scripts to reboot the core if it's down are easy enough to implement, and the only testing that gets the short end are the logged in AFK tests... Still, I'm giddy with anticipation to see how this all works out. :-)
-Duff
Like why had it gone from, 'thanks for donating your time and work' to 'donation is mandatory or go to court'?
So entitled.
Same mindset that made things like Bloodfin happen. A group of entitled people using SWGEmu code close sourced, trash talking SWGEmu in the process, especially about how closed the engine is and how it's time locked, then using Emu code to pretend to have JTL working, etc, etc. In the end people legit thought Bloodfin was some kind of emulator, lol, competing with SWGEmu, and now believe SWGEmu is trying to steal them contents/codes, cause SWGEmu could never do it themselves and are stuck.
SWGEmu has every right to control their engine, the terms aren't even evil and as it's been said before, if you can't deal with it, just wait for 1.0.
Last edited by Timbab; 04-27-2015 at 02:06 PM.
We let you use our Engine3 and in return we expect nothing more from you than to make changes made to the core available to everyone. I don't see how that is a bad thing, engine without time restrictions, having access to latest bug and stability fixes, and being able to update your server with patches that will bring you closer to a final release aka 1.0. Everyone will befit from this.
Last edited by Vlada; 04-27-2015 at 03:09 PM.
How about it being just like live? Why did some people chose to play on Bria while others chose to play on Kauri? And some were fiercely loyal to their servers. All had the same exact code.
It will end up with certain niches that the specific developers and community creates. There will be PVP servers, PVE servers, RP servers, etc etc, just like live.
Correct, yet not quite accurate. SOE's live SWG was one game, one set of rules, one set of code. if server populations chose to segregate themselves into RP/PVP/PVE/Other categories, they did so using the exact same code and rule set.
SWGEmu is and will continue to be different in that respect. Without having any specifics "officially" available yet, the jist of what I've been led to believe by those who appear to know what's going on, is that ONLY changes to the base CORE3 code branch (prior to v1.0) will need to be made open source and either submitted back to SWGEmu by Gerrit patch / upload, or some other means to maintain an Open Source status of some type. All the scripting, .tre file content, additional non-core3 files will probably not be required to be open sourced. Again, this is all "Non-Official" right now in that no announcement has been made. It's just various bits posted here and there I've managed to glean.
Further, if you read the AGPL license itself, and any subsequent adaptations & implementations thereof, it seems that there are specific cases of private use being legit. Read up on it at Wikipedia, it's a good source, then do some googling. It seems that corporations who use AGPL opensource code to create custom, proprietary, internal applications, are not required to make their customizations Open source as long as the scope of their use remains internal, and is not distributed outside of the corporation. Granted, this is a tad different than what SWGEmu is doing, but still relevant to some extent I think. but I could be wrong, I"m no lawyer, and I could have completely misinterpreted the legal mumbo-jumbo easy enough.
My main interest is only in what I would be required to provide if I continue to hack / repurpose core3 like I have been doing now for ... many ... years. Primarily in generating MODS, custom or otherwise, for a non-14.1 standard environment. (new assets, new systems, etc..)
-Duff
If you read the entire thread, TA already said it would only apply to servers that are open to the public. Those who use the dev environment for their own playtoy (for whatever reason) or just to mess around with the code base would not be required to provide their source.
The rest of the speculation is pretty pointless until the actual announcement is made. Expecting those who use our open source code to keep that code open source to the public is not an unfair request. It would be smart for those servers to keep their code on a repository such as git or svn anyways, as it would allow them easy ability to track and, if necessary, revert code changes to their code base. It also allows us, if asked, to assist in resolving any stability issues other servers are having.
If you really want to keep your changes private, then wait until 1.0 is released. Your custom content or need for individuality is not our concern, completing the project is.
Miztah
Developer
SWGEmu is a non-profit, open source community project.
miztah@swgemu.com | How to report bugs | Mantis (Bug Tracker)
Here is a legal opinion of AGPL being used on another application. Martindale.com has some others but is more of a atty resource. On this opinion link, there is also a link to the FAQs on AGPL site. I tend to stay far away from wikis.
https://civicrm.org/agpl-license-faqs
Last edited by Esquire; 04-27-2015 at 04:19 PM.
Ok thanks guys, your answers sound promising at least. Admittedly i poked you a bit just to see the responses without sugarcoating. Thanks for the honesty. And Tim i have nothing in common with bloodfin lol. They are getting what they deserve imo since they caused problems for others. I regained some respect for you all from this convo, thanks again!
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
