The SDL forums have moved to discourse.libsdl.org.
This is just a read-only archive of the previous forums, to keep old links working.

FYI, I accepted an awesome job offer at 38 Studios and am in the process of moving to Rhode Island (movers arrive in 6 hours), and I'll be working full time on their upcoming MMO:
http://38studios.com/products/copernicus

This means that I'll be offline for a while during the process of moving.

It also means that SDL will be officially community supported going forward.  There are some things in place already to support this, such as the new zlib licensing, and I will be adding some more things to aid this, such as an official "how can I help" page, and coordinating official community maintainers for areas of the code.

Other good news is that SDL 1.3 is basically ready for beta, and all it lacks is somebody to build packages and coordinate things, as well as people dedicated to handling feedback and bug reports.

Cheers!
--Sam Lantinga

Hi Sam,

good luck for your new job.

--
Paulo

On Tue, Apr 26, 2011 at 10:30 AM, Sam Lantinga wrote:

Hello,


On 26/04/11 10:30, Sam Lantinga wrote:

Good luck with your new job. They look like a pretty cool company.


I'm a bit worried that this will delay things, but it is inevitable.
Hopefully people will step up and accept this opportunity and
responsibility. I will still try to maintain the haptic subsystem to the
best of my abilities (although I have no mac os x nor windows so that's
a bit hard to handle). Hopefully the GSoC project for SDL will be able
to help in this aspect.


Edgar
_______________________________________________
SDL mailing list

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

Congratulations Sam! Looks like a neat gig!

Please accept my apologies if there is an obvious answer I missed, but I couldn't find the info on the WIKI or google...

Can anyone post up a HOWTO contribute guide or something? I've never contributed to an open source project before and I'm now wrapping my head around the SDL internals as I clean up the iOS branch for my game, so I'd like to give back to the community. I just don't know how! I posted some bug reports and their solutions on this board but I don't even know if anyone will notice. Sam and (others whose names I don't know) have done an amazing job on a cross platform library that is used by a lot of people and organizations, I'd love to participate in it's future development.

Again, congrats Sam, and good luck!

Awesome, congratulations!

And thank you so much for your work on SDL over the years. It was invaluable to us


Thanks,
--Gabriel


On Tue, Apr 26, 2011 at 10:30 AM, Sam Lantinga wrote:

Thanks for all your work to get 1.3 where it is. Without the Galaxy
Gameworks experiment it wouldn't be nearly as far along.

I'm perhaps a bit surprised Blizzard didn't manage to get you back

Best of luck,

John

On Tue, Apr 26, 2011 at 3:30 AM, Sam Lantinga wrote:
_______________________________________________
SDL mailing list

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

Congratulations - looks like a fun and sizable game development project.

On 4/26/11 1:30 AM, Sam Lantinga wrote:

Hi,

On 4/26/11 10:30 AM, Sam Lantinga wrote:
May I recommend putting SDL on github/bitbucket or getting some kind of
fork registration system online? I already have two local branches for
SDL (XInput support and some iOS tweaks) I would love to share for code
review before proposing that for actual merging.

Also, I would still like to propose the documentation switch to Sphinx,
but for that I would need the raw wiki data (could scrape that if it's
okay for you).

And docs


Regards,
Armin
_______________________________________________
SDL mailing list

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

As long as they don't mess with the API, it should be perfectly valid to just supply Sam or Ryan with patches.

But the most interesting patches are the ones that *do* change the API!


From: Nathaniel J Fries
Subject: Re: [SDL] Availability and the future of SDL

As long as they don't mess with the API, it should be perfectly valid to just supply Sam or Ryan with patches.

I think we'll still accept API changes for 1.3 if they make sense.

Also: being Mercurial, feel free to put your clone on whatever server.
We'll take patches (preferably from "hg export"), or pull requests. I
would encourage people without their own servers to create accounts on
bitbucket.org and use that to publish changes.

--ryan.

_______________________________________________
SDL mailing list

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

Bitbucket can already clone from hg.libsdl.org. The fork registration
system is sending a message here that says, "please pull from my clone."


--ryan.


_______________________________________________
SDL mailing list

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

Generally if you have a contribution to make, you submit a patch at
http://bugzilla.libsdl.org/


_______________________________________________
SDL mailing list

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

Congrats' with your new job Sam!
SDL is by all means the greatest gift to the game development
community that you and your team could give
So a hearty "thank you" to all the SDL developers and a "good luck" to Sam!!!

Vittorio

On Tue, Apr 26, 2011 at 10:30 AM, Sam Lantinga wrote:
_______________________________________________
SDL mailing list

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

Sam

Well done on getting the new job, I am sure you will do very well there!

On SDL:

SDL needs stability - talk of forks here and there are worrying, there needs to be one central place for SDL and any source forks to be managed from there also.
Otherwise it will turn into what Linux now is - total spaghetti with different flavours everywhere, and people not knowing where to get a stable, managed (as far as possible) version.

I hope you can still find time to do some stuff with SDL, it needs a very skilled hand to keep a bit of control!

Cheers and best of luck

Ed

ebyard, I both agree and disagree.Since SDL 1.3 hasn't even been officially released, having forks everywhere is going to cause complete chaos.  There hasn't even been an official beta release (still in alpha, AFAIK).
Now, once SDL 1.3 has it's full feature set and a stable API, and is released as a "complete" project, and people want to add their own subset of features, it would make more sense to fork the project.

On Thu, Apr 28, 2011 at 6:28 AM, ebyard wrote:

I am in agreement with MyOzBarry and ebyard. If you make a modification and care to send it back, submit a patch to bugzilla and it will most likely be reviewed and added eventually.

Speaking of that "eventually", perhaps one thing that would benefit SDL is selecting a few trusted members of the community to review and test these modifications and give them commit rights to the repository so that they can be applied. This would make the case for making a fork much weaker, as the patches would be managed rather quickly.

An open-source game or media project that could be used as reference for the new API would probably increase use of the new API. For beginner programmers (a majority of which are referred to SDL for easier 2D game programming, as I was way back when), it is very difficult to learn an API without a good sample of how the code should look. And the best code sample is actual, used, functional code; right? That or a community-managed tutorial could work.

On Thu, Apr 28, 2011 at 5:28 AM, ebyard wrote:

Hmmm... is Gordon taking that role? I hope so.

Bob Pendleton





--
+-----------------------------------------------------------
+ Bob Pendleton: writer and programmer
+ email:
+ web: www.TheGrumpyProgrammer.com
_______________________________________________
SDL mailing list

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