[GEM-dev] financing Gem development

[me.grimm]

i put this out there once (couple years ago) but I could offer
housing/residency/lodging or whatever you want to call it for someone
wanting to dedicate the time and spend a couple weeks in the beautiful
finger lake of upstate ny (my sales pitch) this winter....

thats the resource i can donate.... will prob need $$ for food and stuffs.

if someone (cyrille?) wants to organize the list of what needs done and
someone wants a quiet place to work let me know!

cheers
m
.


On Thu, Oct 12, 2017 at 5:16 PM, Antonio Roberts <antonio at hellocatfood.com>
wrote:

> I known it's not the saviour of everything, but I have seen several
> open source softwares (Synfig, GIMP) use Patreon to help fund
> development.
>
> I've tried bountysource in the past with limited (i.e. no) result.
>
> On 12 October 2017 at 09:34, cyrille henry <ch at chnry.net> wrote:
> > hello Max
> >
> > Le 12/10/2017 à 10:04, Max a écrit :
> >>
> >> Bonjour Cyrille,
> >>
> >> This sounds good, there was the idea of some bounty system years ago
> too.
> >> I think it's crucial for this process to
> >>
> >> 1. break up the job in small manageable parts
> >
> > yes, that's the idea of using the github bug tracker. Spiting jobs in
> bugs.
> > (and use flags to create priorities)
> >
> >
> >> 2. well define their scope and define what "job completed" entails
> >
> > I think it imply that the push request is accepted, and the code is
> merged
> > upstream.
> >
> >> 3. set up a system that doesn't come with a huge administration overhead
> >
> >
> > yes, this is a problem.
> > The reduce amount of developers interested in this job will make things
> > simpler.
> >
> >>
> >> It almost seem there should be a platform for this out there...
> >
> >
> > yes, I don't think administration will be a show stopper.
> >
> >
> >
> >> https://www.bountysource.com/teams/pure-data/issues
> >> this one looks like it parses github issues.. kind of shady.
> >>
> >>
> >>
> >> On 2017년 10월 12일 09:46, cyrille henry wrote:
> >>>
> >>> Hello,
> >>>
> >>> Since the "get money, paid a developer" idea arise on the mailing
> list, I
> >>> spend last weeks trying to think how to organize the last bit of
> development
> >>> that need to be done.
> >>>
> >>> I think we need a clear roadmap : a list of all object / platform that
> >>> need to be fixed. My proposition is to use/update the bugtracker and to
> >>> organize everything that need to be done under the "release critical"
> tag.
> >>> There is a bit of work there. For example "native film reading in
> osX/64
> >>> bit" is not mark as release critical.
> >>> Also, there is 2 critical bug regarding W32 build : do we need to be
> able
> >>> to compile Gem on mingw AND mscv?
> >>>
> >>> With this list of "release critical" bugs, it will be easier to
> estimate
> >>> the work that need to be done. It will allow to estimate the
> development
> >>> time, and the bounty we could offer for this work.
> >>>
> >>> With the financial help of New Blankets, other institutions,
> associations
> >>> or users, I confident that we will be able to finance this work (or
> part of
> >>> this work).
> >>>
> >>> does this sound good?
> >>>
> >>> cheers
> >>> Cyrille
> >>>
> >>> _______________________________________________
> >>> GEM-dev mailing list
> >>> GEM-dev at lists.iem.at
> >>> https://lists.puredata.info/listinfo/gem-dev
> >>
> >>
> >>
> >> _______________________________________________
> >> GEM-dev mailing list
> >> GEM-dev at lists.iem.at
> >> https://lists.puredata.info/listinfo/gem-dev
> >
> >
> > _______________________________________________
> > GEM-dev mailing list
> > GEM-dev at lists.iem.at
> > https://lists.puredata.info/listinfo/gem-dev
>
>
>
> --
> ============================
> antonio at hellocatfood.com
> http://www.hellocatfood.com
> ============================
>
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at lists.iem.at
> https://lists.puredata.info/listinfo/gem-dev
>



-- 
____________________
m.e.grimm, m.f.a, ed.m.
syracuse u., tc3
megrimm.net
____________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20171012/2cf893c9/attachment.html>