<div dir="ltr">>> Are these going to be posted in the general pd mailing list as well?<div> </div><div>also i am trying to get a post top pinned to the facebook group. if anyone on gem-dev is on facebook can you add your 2 cents to antonios post? i guess there are 12k facebook pd group subscribers and maybe we can get some of those that seem to keep complaining to put some $$ up</div><div><br></div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 22, 2017 at 3:46 AM, cyrille henry <span dir="ltr"><<a href="mailto:ch@chnry.net" target="_blank">ch@chnry.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
<br>
Le 21/11/2017 à 23:04, Jaime Oliver La Rosa a écrit :<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Sorry, just saw the pages in the email chain. Are these going to be posted in the general pd mailing list as well?<br>
</blockquote></span>
as soon as I have time to write a polite and convincing mail!<br>
feel free to do it before me!<br>
cheers<br>
c<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
<br>
thanks for your work!<br>
<br>
J<br>
<br>
<br>
On 11/21/2017 04:41 PM, me.grimm wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
+1<div><div class="gmail-h5"><br>
<br>
On Tue, Nov 21, 2017 at 4:22 AM, 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>
<br>
As I said in earlier mail, my aim is (for now) to be able to release a Gem version that incorporate the development made in the last 5 years.<br>
Time is not to add functionalities, but to keep Gem alive.<br>
<br>
Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished.<br>
<br>
I am, like you, only a linux user that have no interest in osX nor windows, but this is mandatory before being able to go forward.<br>
<br>
cheers<br>
c<br>
<br>
<br>
<br>
<br>
Le 20/11/2017 à 16:58, Jack a écrit :<br>
<br>
Or for all platforms ?<br>
In vertex processing with have :<br>
- vertex shader<br>
- geometry shader<br>
<br>
What about tesselation shader ?<br>
<br>
I use Gem a lot so i will be happy to participate financially if that<br>
can help to add functionality to it.<br>
++<br>
<br>
Jack<br>
<br>
<br>
<br>
<br>
Le 20/11/2017 à 12:27, Max a écrit :<br>
<br>
What about something for linux? Generally support a new release?<br>
<br>
<br>
On 2017년 11월 17일 18:07, cyrille henry wrote:<br>
<br>
it appear that pledgie is dedicatad to find money for your work,<br>
better than financing other work.<br>
i.e, if I crete a project, I'll receive the donation.<br>
<br>
So, I went with bounty source.<br>
I create 4 bounty:<br>
<br></div></div>
<a href="https://www.bountysource.com/issues/3383537-w32-build-msvc" rel="noreferrer" target="_blank">https://www.bountysource.com/i<wbr>ssues/3383537-w32-build-msvc</a> <<a href="https://www.bountysource.com/issues/3383537-w32-build-msvc" rel="noreferrer" target="_blank">https://www.bountysource.com/<wbr>issues/3383537-w32-build-msvc</a>><br>
<a href="https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit" rel="noreferrer" target="_blank">https://www.bountysource.com/i<wbr>ssues/4185679-native-video-cap<wbr>turing-on-osx-64bit</a> <<a href="https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit" rel="noreferrer" target="_blank">https://www.bountysource.com/<wbr>issues/4185679-native-video-ca<wbr>pturing-on-osx-64bit</a>><br>
<br>
<a href="https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit" rel="noreferrer" target="_blank">https://www.bountysource.com/i<wbr>ssues/4185729-native-film-read<wbr>ing-on-osx-64bit</a> <<a href="https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit" rel="noreferrer" target="_blank">https://www.bountysource.com/<wbr>issues/4185729-native-film-rea<wbr>ding-on-osx-64bit</a>><br>
<br>
<a href="https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit" rel="noreferrer" target="_blank">https://www.bountysource.com/i<wbr>ssues/6492784-native-image-rea<wbr>ding-writing-on-osx-64bit</a> <<a href="https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit" rel="noreferrer" target="_blank">https://www.bountysource.com/<wbr>issues/6492784-native-image-re<wbr>ading-writing-on-osx-64bit</a>><div><div class="gmail-h5"><br>
<br>
<br>
They correspond to the 4 most important bug I found on the gitub<br>
bugtracker.<br>
<br>
It's time to find money!<br>
<br>
<br>
Le 15/11/2017 à 18:05, cyrille henry a écrit :<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 critical<br>
issue.<br>
<br>
Image, film and video under osX and having a way to compile for<br>
window and the main issues.<br>
<br>
There is also lot's of stuff regarding FTGL, but they look to be<br>
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 should<br>
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 release<br>
with a longer lifetime.<br>
<br>
if there is no objection, I will have a look at the platform we<br>
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 system years<br>
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<br>
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<br>
merged upstream.<br>
<br>
3. set up a system that doesn't come with a huge administration<br>
overhead<br>
<br>
<br>
yes, this is a problem.<br>
The reduce amount of developers interested in this job will make<br>
things 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></div></div>
<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>><div><div class="gmail-h5"><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<br>
list, I spend last weeks trying to think how to organize the last<br>
bit of development that need to be done.<br>
<br>
I think we need a clear roadmap : a list of all object / platform<br>
that need to be fixed. My proposition is to use/update the<br>
bugtracker and to organize everything that need to be done under<br>
the "release critical" tag. There is a bit of work there. For<br>
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 : do we need to<br>
be able to compile Gem on mingw AND mscv?<br>
<br>
With this list of "release critical" bugs, it will be easier to<br>
estimate the work that need to be done. It will allow to estimate<br>
the development time, and the bounty we could offer for this work.<br>
<br>
With the financial help of New Blankets, other institutions,<br>
associations or users, I confident that we will be able to<br>
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></div></div>
<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>
______________________________<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>
______________________________<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>
______________________________<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>
______________________________<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>><span class="gmail-"><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>><span class="gmail-"><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><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>
</span></blockquote>
<br>
<br>
<br><span class="gmail-">
______________________________<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="gmail-HOEnZb"><div class="gmail-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><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>____________________<br>m.e.grimm, m.f.a, ed.m.</div><div>syracuse u., tc3</div><div><a href="http://megrimm.net" target="_blank">megrimm.net</a><br>____________________</div></div></div>
</div></div></div>