SDL Forum Index
SDL
Simple DirectMedia Layer Forums
Reply to topic
SDL 1.3 licensing terms
Sam Lantinga
Guest

Reply with quote
Going forward SDL 1.3 will be under licensing terms that are compatible with open source and commercial projects, the zlib license:
http://zlib.net/zlib_license.html

Galaxy Gameworks will no longer be selling licenses to SDL, but will continue to support our existing customers.

SDL development will continue, but will largely be community driven and Ryan and I will continue to coordinate patch integration and SDL releases.  We will be working to make it easier to contribute in a variety of ways, and are looking for people interested in helping out.

Oh, and Google Summer of Code is on!

Cheers!
--Sam Lantinga
SDL 1.3 licensing terms
Torsten Giebl


Joined: 12 Sep 2009
Posts: 171
Reply with quote
Hello !


Quote:
Going forward SDL 1.3 will be under licensing terms that are compatible with
open source and commercial projects, the zlib license:
http://zlib.net/zlib_license.html

Does the zlib license allow to develop for restricted systems like XBOX360 and PS3 ?


CU
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
View user's profileSend private messageSend e-mail
SDL 1.3 licensing terms
Sam Lantinga
Guest

Reply with quote
Yes.

On Thu, Apr 7, 2011 at 12:17 PM, Torsten Giebl wrote:
Quote:
Hello !


Quote:
Going forward SDL 1.3 will be under licensing terms that are compatible with
open source and commercial projects, the zlib license:
http://zlib.net/zlib_license.html


Does the zlib license allow to develop for restricted systems like XBOX360 and PS3 ?


CU
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
SDL 1.3 licensing terms
Mason Wheeler
Guest

Reply with quote
Woo! No more LGPL-shaped anchor around my neck when I develop custom features! I always did feel a bit nervous about that. (I will, of course, continue to submit new feature patches for review and possible inclusion in the "official" SDL anyway.)

Thanks!

BTW does this also cover related libraries such as SDL_Image, SDL_Mixer, etc?


From: Sam Lantinga
Subject: [SDL] SDL 1.3 licensing terms

Going forward SDL 1.3 will be under licensing terms that are compatible with open source and commercial projects, the zlib license:
http://zlib.net/zlib_license.html

Galaxy Gameworks will no longer be selling licenses to SDL, but will continue to support our existing customers.

SDL development will continue, but will largely be community driven and Ryan and I will continue to coordinate patch integration and SDL releases. We will be working to make it easier to contribute in a variety of ways, and are looking for people interested in helping out.

Oh, and Google Summer of Code is on!

Cheers!
--Sam Lantinga
SDL 1.3 licensing terms
Ryan C. Gordon
Guest

Reply with quote
Quote:
Does the zlib license allow to develop for restricted systems like XBOX360 and PS3 ?

Yes (although you would still need developer agreements with Sony or
Microsoft to develop for those platforms, but that has nothing to do
with SDL itself).

The more immediate benefit: you can statically link SDL, and you can
ship it on iOS.

The zlib license basically says this:

- Do what you want (but don't take our names off the source code).
- Don't sue us (no warranty).
- Mention us in the documentation if you like, but you don't have to.

It's a "BSD-like" license, but it's less restrictive than the BSD
license, believe it or not (BSD requires you to mention the license in
your documentation). It's WAY less restrictive than the LGPL (at the
risk of a holy war: the LGPL enforces freedom. The zlib license just
appreciates it. Frankly, that fits my personality better, but YMMV).

The zlib license is compatible with closed-source software and the GPL,
too. You can use zlib-licensed software in either type of project. For
most people using or developing SDL, nothing has changed: keep using SDL
as you have been.

But for those noticing changes, they should be positive changes.

--ryan.

_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
SDL 1.3 licensing terms
Sam Lantinga
Guest

Reply with quote
Yes, it will cover SDL related libraries that I maintain: SDL_image, SDL_mixer, SDL_ttf, SDL_rtf, SDL_net

For other libraries, you'll have to discuss it with the authors.  Remember that for libraries that are LGPL the author has to contact all prior contributors to get their permission to use a different license, which is why SDL 1.2 will remain LGPL.

See ya!

On Thu, Apr 7, 2011 at 12:25 PM, Mason Wheeler wrote:
Quote:
Woo!  No more LGPL-shaped anchor around my neck when I develop custom features!  I always did feel a bit nervous about that.  (I will, of course, continue to submit new feature patches for review and possible inclusion in the "official" SDL anyway.)

Thanks!

BTW does this also cover related libraries such as SDL_Image, SDL_Mixer, etc?


From: Sam Lantinga
Subject: [SDL] SDL 1.3 licensing terms


Going forward SDL 1.3 will be under licensing terms that are compatible with open source and commercial projects, the zlib license:
http://zlib.net/zlib_license.html

Galaxy Gameworks will no longer be selling licenses to SDL, but will continue to support our existing customers.

SDL development will continue, but will largely be community driven and Ryan and I will continue to coordinate patch integration and SDL releases.  We will be working to make it easier to contribute in a variety of ways, and are looking for people interested in helping out.

Oh, and Google Summer of Code is on!

Cheers!
--Sam Lantinga







_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

SDL 1.3 licensing terms
Torsten Giebl


Joined: 12 Sep 2009
Posts: 171
Reply with quote
Hello !


Quote:
Quote:
Does the zlib license allow to develop for restricted systems like XBOX360 and PS3 ?

Yes (although you would still need developer agreements with Sony or Microsoft to develop for those platforms, but that has nothing to do with SDL itself).

The more immediate benefit: you can statically link SDL, and you can ship it on iOS.

The zlib license basically says this:

- Do what you want (but don't take our names off the source code).
- Don't sue us (no warranty).
- Mention us in the documentation if you like, but you don't have to.

It's a "BSD-like" license, but it's less restrictive than the BSD license, believe it or not (BSD requires you to mention the license in your documentation). It's WAY less restrictive than the LGPL (at the risk of a holy war: the LGPL enforces freedom. The zlib license just appreciates it. Frankly, that fits my personality better, but YMMV).

The zlib license is compatible with closed-source software and the GPL, too. You can use zlib-licensed software in either type of project. For most people using or developing SDL, nothing has changed: keep using SDL as you have been.

But for those noticing changes, they should be positive changes.

Thanks Ryan, that sounds great !


CU
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
View user's profileSend private messageSend e-mail
SDL 1.3 licensing terms
Armin Ronacher
Guest

Reply with quote
Hi,

On 4/7/11 9:11 PM, Sam Lantinga wrote:
Quote:
Going forward SDL 1.3 will be under licensing terms that are compatible
with open source and commercial projects, the zlib license:
http://zlib.net/zlib_license.html
When I was asking for a BSD-ish license today I was not seriously
expecting a change in license anytime soon if at all. This is amazing
news to be honest.

Major props for making this move.

Quote:
We will be working to make it easier to contribute in a variety of ways,
and are looking for people interested in helping out.
I guess am going to propose something completely insane (and biased as
I'm one of the guys behind the Sphinx documentation tool) but what are
the odds of converting the currently moin based documentation into a
Sphinx[1] based documentation? I am already writing a bunch of articles
about my adventures with SDL currently and I would not mind too much
updating the SDL documentation along the way.

The reason I am asking is that right now the documentation is not
necessarily bad, but it could be greatly improved and I think Sphinx
provides a pretty good basis for writing documentation. The main
motivation here is that in combination with bitbucket/github pull
requests it's quite easy to integrate documentation fixes easily and you
can view the documentation offline easily and also convert them into a PDF.

Revamping the documentation and cleaning up might make a good GSOC
project as well.


Regards,
Armin

[1]: http://sphinx.pocoo.org/
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
SDL 1.3 licensing terms
Sam Lantinga
Guest

Reply with quote
Having offline/PDF documentation is something that I've been interested in for a while.  However there's the hurdle of converting a huge amount of existing documentation.

Do you have an easy way to mass convert a moin wiki to Sphinx?

On Thu, Apr 7, 2011 at 1:52 PM, Armin Ronacher wrote:
Quote:
Hi,

On 4/7/11 9:11 PM, Sam Lantinga wrote:
Quote:
Going forward SDL 1.3 will be under licensing terms that are compatible
with open source and commercial projects, the zlib license:
http://zlib.net/zlib_license.html

When I was asking for a BSD-ish license today I was not seriously
expecting a change in license anytime soon if at all.  This is amazing
news to be honest.

Major props for making this move.

Quote:
We will be working to make it easier to contribute in a variety of ways,
and are looking for people interested in helping out.

I guess am going to propose something completely insane (and biased as
I'm one of the guys behind the Sphinx documentation tool) but what are
the odds of converting the currently moin based documentation into a
Sphinx[1] based documentation?  I am already writing a bunch of articles
about my adventures with SDL currently and I would not mind too much
updating the SDL documentation along the way.

The reason I am asking is that right now the documentation is not
necessarily bad, but it could be greatly improved and I think Sphinx
provides a pretty good basis for writing documentation.  The main
motivation here is that in combination with bitbucket/github pull
requests it's quite easy to integrate documentation fixes easily and you
can view the documentation offline easily and also convert them into a PDF.

Revamping the documentation and cleaning up might make a good GSOC
project as well.


Regards,
Armin

[1]: http://sphinx.pocoo.org/

_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


SDL 1.3 licensing terms
Armin Ronacher
Guest

Reply with quote
Hi,

On 2011-04-08 12:35 AM, Sam Lantinga wrote:
Quote:
Do you have an easy way to mass convert a moin wiki to Sphinx?
When the Python documentation was converted from LaTeX to Sphinx Georg
wrote a tool that converts a node tree into .rst files. The code is
still around albeit hidden[1]. Modern version of the MoinMoin wiki
internally parse into some kind of DOM inspired tree, so it should be
possible to convert that one into a docutils one and then pass it over
to the old restwriter from the converter.

Assuming you could provide me with the text files for the latest
revisions of the MoinMoin documentation I could try to write a small
script together that does that.


Regards,
Armin

[1]: http://docutils.sourceforge.net/sandbox/py-rest-doc/converter/
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
SDL 1.3 licensing terms
Andreas Schiffler
Guest

Reply with quote
As a start, how about adding Doxygen markup to the functions and adding the content in the existing documentation to it via some /include hooks. Doxygen does create nice LaTeX, PDF and PS files (see http://www.doxygen.nl/output.html). Not sure what it would take to export the wiki existing documentation automatically into a doxygen consumable and parser-friendly format though and mark up the functions - but nothing a little perl script couldn't handle. Wink Would make a nice GSOC project too.
--Andreas

On 4/7/11 3:35 PM, Sam Lantinga wrote:
Quote:
Having offline/PDF documentation is something that I've been interested in for a while. However there's the hurdle of converting a huge amount of existing documentation.

Do you have an easy way to mass convert a moin wiki to Sphinx?

On Thu, Apr 7, 2011 at 1:52 PM, Armin Ronacher wrote:
Quote:
Hi,

On 4/7/11 9:11 PM, Sam Lantinga wrote:
Quote:
Going forward SDL 1.3 will be under licensing terms that are compatible
with open source and commercial projects, the zlib license:
http://zlib.net/zlib_license.html

When I was asking for a BSD-ish license today I was not seriously
expecting a change in license anytime soon if at all. This is amazing
news to be honest.

Major props for making this move.

Quote:
We will be working to make it easier to contribute in a variety of ways,
and are looking for people interested in helping out.

I guess am going to propose something completely insane (and biased as
I'm one of the guys behind the Sphinx documentation tool) but what are
the odds of converting the currently moin based documentation into a
Sphinx[1] based documentation? I am already writing a bunch of articles
about my adventures with SDL currently and I would not mind too much
updating the SDL documentation along the way.

The reason I am asking is that right now the documentation is not
necessarily bad, but it could be greatly improved and I think Sphinx
provides a pretty good basis for writing documentation. The main
motivation here is that in combination with bitbucket/github pull
requests it's quite easy to integrate documentation fixes easily and you
can view the documentation offline easily and also convert them into a PDF.

Revamping the documentation and cleaning up might make a good GSOC
project as well.


Regards,
Armin

[1]: http://sphinx.pocoo.org/
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org




_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
SDL 1.3 licensing terms
Armin Ronacher
Guest

Reply with quote
Hi,

On 4/8/11 5:01 AM, Andreas Schiffler wrote:
Quote:
As a start, how about adding Doxygen markup to the functions and adding
the content in the existing documentation to it via some /include hooks.
Doxygen does create nice LaTeX, PDF and PS files (see
I absolute despite doxygen based documentation. First of all, pulling
in documentation from comments means that people that want to write
documentation have to find the place of implementation in the file and
also their diffs for documentation will most likely clash with diffs for
implementation.

Secondly doxygen based documentation looks user unfriendly and is not
very helpful for a library like SDL which does not have a terrible high
number of functions.

I strongly prefer documentation structured into 'tutorial', 'prosaic
documentation', 'api documentation'.

Regarding documentation I strongly recommend listening to the talk of
Jacob Kaplan Moss about writing great documentation[1].


Regards,
Armin

[1]: http://pycon.blip.tv/file/4881071/
_______________________________________________
SDL mailing list

http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
SDL 1.3 licensing terms
Sam Lantinga
Guest

Reply with quote
The latest snapshot is now under the zlib license.
http://www.libsdl.org/tmp/SDL-1.3.zip

Cheers! Smile

On Thu, Apr 7, 2011 at 12:11 PM, Sam Lantinga wrote:
Quote:
Going forward SDL 1.3 will be under licensing terms that are compatible with open source and commercial projects, the zlib license:
http://zlib.net/zlib_license.html

Galaxy Gameworks will no longer be selling licenses to SDL, but will continue to support our existing customers.

SDL development will continue, but will largely be community driven and Ryan and I will continue to coordinate patch integration and SDL releases.  We will be working to make it easier to contribute in a variety of ways, and are looking for people interested in helping out.

Oh, and Google Summer of Code is on!

Cheers!
--Sam Lantinga
SDL 1.3 licensing terms
Patrick Baggett
Guest

Reply with quote
Quote:
Secondly doxygen based documentation looks user unfriendly and is not
very helpful for a library like SDL which does not have a terrible high
number of functions. 
I strongly prefer documentation structured into 'tutorial', 'prosaic
documentation', 'api documentation'.



Take it for what it is. Doxygen is documentation to the code and functions so that general relationships and short descriptions will help people browse through the code, i.e. mostly meant for developers. It is not a replacement for any of the above. All things considered, this is an improvement.
SDL 1.3 licensing terms
Patrick Baggett
Guest

Reply with quote
Quote:
Secondly doxygen based documentation looks user unfriendly and is not
very helpful for a library like SDL which does not have a terrible high
number of functions. 
I strongly prefer documentation structured into 'tutorial', 'prosaic
documentation', 'api documentation'.



Take it for what it is. Doxygen is documentation to the code and functions so that general relationships and short descriptions will help people browse through the code, i.e. mostly meant for developers. It is not a replacement for any of the above. All things considered, this is an improvement.
SDL 1.3 licensing terms
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT  
Page 1 of 2  

  
  
 Reply to topic