<div dir="ltr">Yes I will donate too!</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Sofy Yuditskaya<br><a href="http://yuditskaya.com" target="_blank">The Source</a><br><div><div><br></div></div></div></div></div></div>
<br><div class="gmail_quote">On Thu, Nov 16, 2017 at 4:28 AM, Nicolas Montgermont <span dir="ltr"><<a href="mailto:list@nimon.org" target="_blank">list@nimon.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
Pledgie seems ok.<br>
I'd be happy to contribute financially for the release of a new Gem and<br>
the development of the av plugin for osx.<br>
The analysis of Cyrille seems fine to me.<br>
Let's do it!<br>
<br>
Best,<br>
Nicolas<br>
<br>
<a href="http://nimon.org" rel="noreferrer" target="_blank">http://nimon.org</a><br>
<div class="HOEnZb"><div class="h5"><br>
Le 16/11/2017 à 09:42, cyrille henry a écrit :<br>
> i'm fighting to keep Gem alive, not to kill it.<br>
><br>
><br>
> Le 16/11/2017 à 03:57, Ivica Ico Bukvic a écrit :<br>
>> Why not instead focus on Jonathan's work on implementing WebGL inside<br>
>> Purr-Data canvas (which is already in node webkit) and by doing so<br>
>> obtain most of the Gem functionality in a way that does not mess with<br>
>> the audio interrupt?<br>
>><br>
>> On Nov 15, 2017 12:05, "cyrille henry" <<a href="mailto:ch@chnry.net">ch@chnry.net</a><br>
>> <mailto:<a href="mailto:ch@chnry.net">ch@chnry.net</a>>> wrote:<br>
>><br>
>> hello,<br>
>> i'm sorry it took so long, I have lot's of work.<br>
>><br>
>> I found 2 platform :<br>
>><br>
>> <a href="https://pledgie.com/" rel="noreferrer" target="_blank">https://pledgie.com/</a><br>
>> and :<br>
>> <a href="https://www.bountysource.com/" rel="noreferrer" target="_blank">https://www.bountysource.com/</a><br>
>><br>
>> pledgie get 3% of the donation, bountysource get 10%.<br>
>><br>
>> unless anyone have a better idea, i'll start to go with pledgie<br>
>> cheers<br>
>> c<br>
>><br>
>><br>
>><br>
>> Le 30/10/2017 à 17:38, cyrille henry a écrit :<br>
>><br>
>> Hello,<br>
>><br>
>> I've check Iohannes github: There is not a lot's of release<br>
>> critical issue.<br>
>><br>
>> Image, film and video under osX and having a way to compile<br>
>> for window and the main issues.<br>
>><br>
>> There is also lot's of stuff regarding FTGL, but they look to<br>
>> be obsolete. At least, we will know if they are obsolete after being<br>
>> able to compile Gem on the concerned platform.<br>
>><br>
>> Since Iohannes is currently too buzzy to help, I think we<br>
>> should organize development in 2 parts :<br>
>><br>
>> 1st : doing the minimum to have Gem usable on all platform.<br>
>> We could then release a v0.94 and use it to test on lot's of<br>
>> computer and reporting all bugs.<br>
>> Then, a 2nd development round could create a 0.94.1 bugfix<br>
>> release with a longer lifetime.<br>
>><br>
>> if there is no objection, I will have a look at the platform<br>
>> we could use to centralize financing and stuff.<br>
>> cheers<br>
>> c<br>
>><br>
>><br>
>><br>
>> Le 12/10/2017 à 10:34, cyrille henry a écrit :<br>
>><br>
>> hello Max<br>
>><br>
>> Le 12/10/2017 à 10:04, Max a écrit :<br>
>><br>
>> Bonjour Cyrille,<br>
>><br>
>> This sounds good, there was the idea of some bounty<br>
>> system years ago too.<br>
>> I think it's crucial for this process to<br>
>><br>
>> 1. break up the job in small manageable parts<br>
>><br>
>> yes, that's the idea of using the github bug tracker.<br>
>> Spiting jobs in bugs.<br>
>> (and use flags to create priorities)<br>
>><br>
>><br>
>> 2. well define their scope and define what "job<br>
>> completed" entails<br>
>><br>
>> I think it imply that the push request is accepted, and<br>
>> the code is merged upstream.<br>
>><br>
>> 3. set up a system that doesn't come with a huge<br>
>> administration overhead<br>
>><br>
>><br>
>> yes, this is a problem.<br>
>> The reduce amount of developers interested in this job<br>
>> will make things simpler.<br>
>><br>
>><br>
>> It almost seem there should be a platform for this<br>
>> out there...<br>
>><br>
>><br>
>> yes, I don't think administration will be a show stopper.<br>
>><br>
>><br>
>> <a href="https://www.bountysource.com/teams/pure-data/issues" rel="noreferrer" target="_blank">https://www.bountysource.com/<wbr>teams/pure-data/issues</a><br>
>> <<a href="https://www.bountysource.com/teams/pure-data/issues" rel="noreferrer" target="_blank">https://www.bountysource.com/<wbr>teams/pure-data/issues</a>><br>
>> this one looks like it parses github issues.. kind of<br>
>> shady.<br>
>><br>
>><br>
>><br>
>> On 2017년 10월 12일 09:46, cyrille henry wrote:<br>
>><br>
>> Hello,<br>
>><br>
>> Since the "get money, paid a developer" idea<br>
>> arise on the mailing list, I spend last weeks trying to think how to<br>
>> organize the last bit of development that need to be done.<br>
>><br>
>> I think we need a clear roadmap : a list of all<br>
>> object / platform that need to be fixed. My proposition is to<br>
>> use/update the bugtracker and to organize everything that need to be<br>
>> done under the "release critical" tag. There is a bit of work there.<br>
>> For example "native film reading in osX/64 bit" is not mark as<br>
>> release critical.<br>
>> Also, there is 2 critical bug regarding W32 build<br>
>> : do we need to be able to compile Gem on mingw AND mscv?<br>
>><br>
>> With this list of "release critical" bugs, it<br>
>> will be easier to estimate the work that need to be done. It will<br>
>> allow to estimate the development time, and the bounty we could offer<br>
>> for this work.<br>
>><br>
>> With the financial help of New Blankets, other<br>
>> institutions, associations or users, I confident that we will be able<br>
>> to finance this work (or part of this work).<br>
>><br>
>> does this sound good?<br>
>><br>
>> cheers<br>
>> Cyrille<br>
>><br>
>> ______________________________<wbr>_________________<br>
>> GEM-dev mailing list<br>
>> <a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a> <mailto:<a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a>><br>
>> <a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a><br>
>> <<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a>><br>
>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> GEM-dev mailing list<br>
>> <a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a> <mailto:<a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a>><br>
>> <a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a><br>
>> <<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> GEM-dev mailing list<br>
>> <a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a> <mailto:<a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a>><br>
>> <a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a><br>
>> <<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> GEM-dev mailing list<br>
>> <a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a> <mailto:<a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a>><br>
>> <a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a><br>
>> <<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> GEM-dev mailing list<br>
>> <a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a> <mailto:<a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a>><br>
>> <a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a><br>
>> <<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a>><br>
>><br>
><br>
> ______________________________<wbr>_________________<br>
> GEM-dev mailing list<br>
> <a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a><br>
> <a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
GEM-dev mailing list<br>
<a href="mailto:GEM-dev@lists.iem.at">GEM-dev@lists.iem.at</a><br>
<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/<wbr>listinfo/gem-dev</a><br>
</div></div></blockquote></div><br></div>