[SDL] Feature of SDL

[Nicholas Rishel]

Overkill certainly if that is all they do; I assume an individual
contracted would not necessarily do these tasks alone, or at all.

In my eyes the problem is that, with good reason, there is no project
accountability. If you would tend to agree with this I would appreciate
hearing alternate ideas on how to solve it. :)

On Thu, May 24, 2012 at 2:44 PM, Alex Barry <alex.barry at gmail.com> wrote:

> I don't think we need a dedicated developer - that seems like overkill for
> someone who would only (Essentially) test patches and approve features.  A
> community-driven model would work just as well for this, and it wouldn't
> cost us a dime.  It would just feel like we're overcomplicating a simple
> problem, but I may be completely wrong.
>
> -Alex
>
>
> On Thu, May 24, 2012 at 2:30 PM, Nicholas Rishel <rishel.nick at gmail.com>wrote:
>
>> A dedicated developer for the project would help SDL significantly. As
>> already stated, Sam and Ryan have already dedicated so much to this project
>> and owe nothing to us. In the end no one who is justifiably accountable for
>> the project, and adding a community base does not solve this problem. A
>> single paid, full-time developer could fill this void.
>>
>> I would propose that we consider investing the effort into a Kickstarter
>> project to organize funding for such a role, specifically proposing
>> Kickstarter due to it being a publicly accepted "middleman". I do believe
>> we should elicit input from Sam and Ryan on this before proceeding
>> (hopefully they'll notice this conversation), and should in the meantime
>> begin setting up a community base as proposed preiously.
>>
>>
>> On Thu, May 24, 2012 at 11:54 AM, Dimitris Zenios <
>> dimitris.zenios at gmail.com> wrote:
>>
>>> I totally agree that the development should shift to a more
>>> community-driven project
>>>
>>> On Thu, May 24, 2012 at 5:19 PM, Alex Barry <alex.barry at gmail.com>
>>> wrote:
>>> > Do we have any sort of documentation (by Sam or anyone, really) that
>>> > describes or demonstrates what should be in a patch (how many bugs can
>>> one
>>> > patch include, what sort of review process should be use, etc etc)?
>>> > I think Sam made if fairly clear a few months ago that we'll be
>>> shifting to
>>> > a community-driven project, rather than a one man show, but I think he
>>> needs
>>> > us to come up with some strict but work-able guidelines on how we deal
>>> with
>>> > individual patches (submitting and reviewing).
>>> > -Alex
>>> >
>>> >
>>> > On Thu, May 24, 2012 at 10:08 AM, Brian Barnes <ggadwa at charter.net>
>>> wrote:
>>> >>
>>> >> I've used SDL 2 successfully on both an OS X game in the OS X app
>>> store
>>> >> (the only problem is the cmd-q beep, which is in bugzilla) and I have
>>> an iOS
>>> >> game waiting for review right now using it (I had to patch it, which
>>> I've
>>> >> put up here before.)  It's also used in dim3, my free 3D development
>>> >> environment.
>>> >>
>>> >> If somebody somewhere would make a decision on which patch to use --
>>> mine
>>> >> for instance -- the iOS stuff would be ready to go.  After that,
>>> people have
>>> >> worked up patches for the game center problem, that can go on top of
>>> that.
>>> >>  Then iOS should be good.  Android can just use the same framework.
>>> >>
>>> >> SDL 2 still isn't useful on windows because relative mouse movement
>>> still
>>> >> isn't in.  That's the big hold up.
>>> >>
>>> >> Here's the problem, and I'll be pretty frank about this.  There *are*
>>> >> patches that will fill in the missing holes, but nobody but Sam is
>>> really
>>> >> the guy (at this point) that has the authority to say what patch goes
>>> in or
>>> >> out.  He needs to make a decision.  I'm not sure what Ryan's say is.
>>> >>  There's no clear chain of command except that it's Sam's baby.
>>> >>
>>> >> I think we in the community can fix the holes, we just need the
>>> chance to
>>> >> do it.
>>> >>
>>> >> Like the iOS stuff, there's competing patches, but most do what they
>>> are
>>> >> supposed to do.  Just somebody has to say OK and land it in the trunk.
>>> >>
>>> >> NOW: Important notes.  Sam owes us nothing, and has given us a lot.
>>> Same
>>> >> with Ryan.  This is not to construed as anything but an assessment of
>>> the
>>> >> current state of affairs as I know it, and could be wrong.
>>> >>
>>> >> [>] Brian
>>> >>
>>> >> _______________________________________________
>>> >> SDL mailing list
>>> >> SDL at lists.libsdl.org
>>> >> http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > SDL mailing list
>>> > SDL at lists.libsdl.org
>>> > http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
>>> >
>>> _______________________________________________
>>> SDL mailing list
>>> SDL at lists.libsdl.org
>>> http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
>>>
>>
>>
>> _______________________________________________
>> SDL mailing list
>> SDL at lists.libsdl.org
>> http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
>>
>>
>
> _______________________________________________
> SDL mailing list
> SDL at lists.libsdl.org
> http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20120524/84ce3086/attachment.htm>