Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
What will all the new License changes mean for us?
#1
Subject says it all. With the move to AGPL and the lifting of the 2.5hr restriction, what will it mean to those of us who (when we're motivated anyway) build, mod, and tinker?

so far everyone seems to think that if we're not providing it for public use we're fine, and won't have to report our changes back to the EMU crew.

however, might it be possible that they require that everyone who wishes to download and use their AGPL code, have to prove that they have the ability / service to provide their code per the license terms?

*shrug* I have no idea personally. I think it sounds great on the surface, but i'm sceptical that it will remain open to everyone. Instead being a "Prove you have development in mind and can share your code, then we'll let you down load it..." type of thing.

anyone else have any insight or opinions?

-Duff
 
Reply
#2
There's nothing to suggest, in anything that I've read at least (written by Emu staff), that it will affect single users at all. The project remains open source. The licence change is aimed purely at anyone who wishes to use the code for running a public server, which it allows as long as said server makes their code open source too.
 
Reply
#3
Lasko is right. Additionally for public servers any custom scripts/data you create will be excluded from the AGPL license to allow unique or hidden content. There are more details on the particulars of this in the works. Smile
 
Reply
#4
(2015-04-23, 12:05 PM)Sytner Wrote: Lasko is right. Additionally for public servers any custom scripts/data you create will be excluded from the AGPL license to allow unique or hidden content. There are more details on the particulars of this in the works. Smile

This is the bit I just don't get, if the only code the public servers have to make OS is the code that's been DL'd from the Emu and not stuff they have added then there seems little gain for the Emu (or anybody else). As you say though, more details in the works. I cant wait to see what they are.
 
Reply
#5
That's my initial interpretation as well. I just worry about what might be considered the "Proper" methods of keeping my updates/changes/revisions "Open".

(Just assuming that I run a public server):
does "Open" mean that I'm willing to zip and copy my stuff to them when requested? or would I be required to maintain an active SVN / source safe styled versioning program for the code?

to be honest, I don't know how to use those programs. :-) I know how to manage a source library manually. copy the files, back up files, etc...

So for example, if I were to resurrect my "Iron Dominion" server, which I spent two months on code rewrites, custom content, jedi rewrite, etc... , and make it public (which I can easy enough), what then?

how do I share it back to them and be in compliance? see... that's my big question / fear... and would I have to show that ability BEFORE I download their latest source to start with?

-Duff
 
Reply
#6
(2015-04-23, 12:48 PM)Lasko Wrote:
(2015-04-23, 12:05 PM)Sytner Wrote: Lasko is right. Additionally for public servers any custom scripts/data you create will be excluded from the AGPL license to allow unique or hidden content. There are more details on the particulars of this in the works. Smile

This is the bit I just don't get, if the only code the public servers have to make OS is the code that's been DL'd from the Emu and not stuff they have added then there seems little gain for the Emu (or anybody else). As you say though, more details in the works. I cant wait to see what they are.

Well it's only the scripts and data that are excluded as far as I know. If the server developers do something more in-depth requiring code changes then it is necessary to share those changes. For example if they implement new systems that aren't a part of 14.1. Sharing these implementations means that they could then be added to SWGEmu as options for everyone. Personally I think this is a good idea - it would be pretty cool for SWGEmu to have a bunch of variants out of the box.

(2015-04-23, 01:03 PM)duffstone Wrote: (Just assuming that I run a public server):
does "Open" mean that I'm willing to zip and copy my stuff to them when requested? or would I be required to maintain an active SVN / source safe styled versioning program for the code?

If you want to look legitimate I imagine using proper source control would be expected, at least if you want to apply for the unrestricted engine.
 
Reply
#7
CoolSmile

In my Utopian little world, I'd like to see open source meaning open source where everything is shared, but that's not likely...

But the closer we get to that is good for meSmile

Maybe we should have a new section for content modding??
 
Reply
#8
(2015-04-23, 03:22 PM)Lasko Wrote: In my Utopian little world, I'd like to see open source meaning open source where everything is shared, but that's not likely...

But the closer we get to that is good for meSmile

It would be nice... I can hardly comment though Tongue

(2015-04-23, 03:22 PM)Lasko Wrote: Maybe we should have a new section for content modding??

Talked to Timbab about this a while back - I think it's a good idea, at least as a temporary solution in lieu of something better.
 
Reply
#9
Yeah mentioned it ages ago too.

Currently there's very little about apart from a few fan sites here an there and a few guides on this very fine forum, but nothing organised as such. Bare minimum on the Emu forum too, enough to dip your toe in but that's about it.

Having talked to quite a few people over the years about it, there seems to be an appetite to make this stuff for others to use, while not necessarily wanting to work for either the Emu or a public server.

Gets my vote anyways.
 
Reply
#10
I initially wanted to make one, but there were only like two content threads.

I'll gladly open one though if you and perhaps others post stuff! Smile
 
Reply
  



Forum Jump:


Browsing: 1 Guest(s)