<div dir="ltr">Hi, <div><br><div>regarding splitting things into small parts and have a sight on what should be done, what is on the road, and what is finish, </div></div><div><a href="https://github.com/umlaeute/Gem/projects/1">github project </a>is a good challenger, it is already integrated into github where Gem is hosted, issue can be converted into task and we can add as many column as we need.</div><div>But only Github project's members can edit it.</div><div><br></div><div>concerning the system to produce binary, <a href="https://travis-ci.org/umlaeute/Gem">Travis is already building Gem</a> on each push.</div><div>We can setup some deployment rules to automatically upload binary to github release page and/or to deken.</div><div>And we can do the same for Windows on Appveyor.</div><div>Once this is setup is is easy to produce release as often as desired.</div><div><br></div><div>Best</div><div><br></div><div>Antoine</div><div><br></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">--<br>do it yourself <br><a href="http://antoine.villeret.free.fr" target="_blank">http://antoine.villeret.free.fr</a><br></div></div>
<br><div class="gmail_quote">2017-10-16 16:33 GMT+02:00 cyrille henry <span dir="ltr"><<a href="mailto:ch@chnry.net" target="_blank">ch@chnry.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've got a quiet place to work at home, but thanks for the proposition!<br>
cheers<br>
c<span class=""><br>
<br>
<br>
<br>
Le 13/10/2017 à 01:36, me.grimm a écrit :<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
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....<br>
<br>
thats the resource i can donate.... will prob need $$ for food and stuffs.<br>
<br>
if someone (cyrille?) wants to organize the list of what needs done and someone wants a quiet place to work let me know!<br>
<br>
cheers<br>
m<br>
.<br>
<br>
<br></span><span class="">
On Thu, Oct 12, 2017 at 5:16 PM, Antonio Roberts <<a href="mailto:antonio@hellocatfood.com" target="_blank">antonio@hellocatfood.com</a> <mailto:<a href="mailto:antonio@hellocatfood.com" target="_blank">antonio@hellocatfood.c<wbr>om</a>>> wrote:<br>
<br>
I known it's not the saviour of everything, but I have seen several<br>
open source softwares (Synfig, GIMP) use Patreon to help fund<br>
development.<br>
<br>
I've tried bountysource in the past with limited (i.e. no) result.<br>
<br></span><span class="">
On 12 October 2017 at 09:34, cyrille henry <<a href="mailto:ch@chnry.net" target="_blank">ch@chnry.net</a> <mailto:<a href="mailto:ch@chnry.net" target="_blank">ch@chnry.net</a>>> wrote:<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 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. Spiting jobs in bugs.<br>
> (and use flags to create priorities)<br>
><br>
><br>
>> 2. well define their scope and define what "job completed" entails<br>
><br>
> I think it imply that the push request is accepted, and the code is merged<br>
> upstream.<br>
><br>
>> 3. set up a system that doesn't come with a huge administration overhead<br>
><br>
><br>
> yes, this is a problem.<br>
> The reduce amount of developers interested in this job will make things<br>
> simpler.<br>
><br>
>><br>
>> It almost seem there should be a platform for this out there...<br>
><br>
><br>
> yes, I don't think administration will be a show stopper.<br>
><br>
><br>
><br></span>
>> <a href="https://www.bountysource.com/teams/pure-data/issues" rel="noreferrer" target="_blank">https://www.bountysource.com/t<wbr>eams/pure-data/issues</a> <<a href="https://www.bountysource.com/teams/pure-data/issues" rel="noreferrer" target="_blank">https://www.bountysource.com/<wbr>teams/pure-data/issues</a>><span class=""><br>
>> this one looks like it parses github issues.. kind of 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 arise on the mailing list, I<br>
>>> spend last weeks trying to think how to organize the last bit of development<br>
>>> that need to be done.<br>
>>><br>
>>> I think we need a clear roadmap : a list of all object / platform that<br>
>>> need to be fixed. My proposition is to use/update the bugtracker and to<br>
>>> organize everything that need to be done under the "release critical" tag.<br>
>>> There is a bit of work there. For example "native film reading in osX/64<br>
>>> bit" is not mark as release critical.<br>
>>> Also, there is 2 critical bug regarding W32 build : do we need to be able<br>
>>> to compile Gem on mingw AND mscv?<br>
>>><br>
>>> With this list of "release critical" bugs, it will be easier to estimate<br>
>>> the work that need to be done. It will allow to estimate the development<br>
>>> time, and the bounty we could offer for this work.<br>
>>><br>
>>> With the financial help of New Blankets, other institutions, associations<br>
>>> or users, I confident that we will be able to finance this work (or part of<br>
>>> this work).<br>
>>><br>
>>> does this sound good?<br>
>>><br>
>>> cheers<br>
>>> Cyrille<br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> GEM-dev mailing list<br></span>
>>> <a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a> <mailto:<a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a>><br>
>>> <a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/li<wbr>stinfo/gem-dev</a> <<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/l<wbr>istinfo/gem-dev</a>><br>
>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> GEM-dev mailing list<br>
>> <a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a> <mailto:<a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a>><br>
>> <a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/li<wbr>stinfo/gem-dev</a> <<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/l<wbr>istinfo/gem-dev</a>><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> GEM-dev mailing list<br>
> <a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a> <mailto:<a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a>><br>
> <a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/li<wbr>stinfo/gem-dev</a> <<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/l<wbr>istinfo/gem-dev</a>><br>
<br>
<br>
<br>
--<br>
============================<br>
<a href="mailto:antonio@hellocatfood.com" target="_blank">antonio@hellocatfood.com</a> <mailto:<a href="mailto:antonio@hellocatfood.com" target="_blank">antonio@hellocatfood.c<wbr>om</a>><span class=""><br>
<a href="http://www.hellocatfood.com" rel="noreferrer" target="_blank">http://www.hellocatfood.com</a><br>
============================<br>
<br>
______________________________<wbr>_________________<br>
GEM-dev mailing list<br></span>
<a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a> <mailto:<a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a>><br>
<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/li<wbr>stinfo/gem-dev</a> <<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/l<wbr>istinfo/gem-dev</a>><span class=""><br>
<br>
<br>
<br>
<br>
-- <br>
____________________<br>
m.e.grimm, m.f.a, ed.m.<br>
syracuse u., tc3<br>
</span><a href="http://megrimm.net" rel="noreferrer" target="_blank">megrimm.net</a> <<a href="http://megrimm.net" rel="noreferrer" target="_blank">http://megrimm.net</a>><br>
____________________<span class=""><br>
<br>
<br>
______________________________<wbr>_________________<br>
GEM-dev mailing list<br>
<a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a><br>
<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/li<wbr>stinfo/gem-dev</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<wbr>_________________<br>
GEM-dev mailing list<br>
<a href="mailto:GEM-dev@lists.iem.at" target="_blank">GEM-dev@lists.iem.at</a><br>
<a href="https://lists.puredata.info/listinfo/gem-dev" rel="noreferrer" target="_blank">https://lists.puredata.info/li<wbr>stinfo/gem-dev</a><br>
</div></div></blockquote></div><br></div>