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
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 2. well define their scope and define what "job completed" entails 3. set up a system that doesn't come with a huge administration overhead
It almost seem there should be a platform for this out there... 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
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@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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
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@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@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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
--
antonio@hellocatfood.com http://www.hellocatfood.com ============================
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
I've got a quiet place to work at home, but thanks for the proposition! cheers c
Le 13/10/2017 à 01:36, me.grimm a écrit :
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@hellocatfood.com mailto:antonio@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@chnry.net <mailto:ch@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 <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@lists.iem.at <mailto:GEM-dev@lists.iem.at> >>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> >> >> >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> >> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> > > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> > https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> -- ============================ antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> http://www.hellocatfood.com ============================ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Hi,
regarding splitting things into small parts and have a sight on what should be done, what is on the road, and what is finish, github project https://github.com/umlaeute/Gem/projects/1is 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. But only Github project's members can edit it.
concerning the system to produce binary, Travis is already building Gem https://travis-ci.org/umlaeute/Gem on each push. We can setup some deployment rules to automatically upload binary to github release page and/or to deken. And we can do the same for Windows on Appveyor. Once this is setup is is easy to produce release as often as desired.
Best
Antoine
-- do it yourself http://antoine.villeret.free.fr
2017-10-16 16:33 GMT+02:00 cyrille henry ch@chnry.net:
I've got a quiet place to work at home, but thanks for the proposition! cheers c
Le 13/10/2017 à 01:36, me.grimm a écrit :
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@hellocatfood.com mailto:antonio@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@chnry.net <mailto:ch@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 < https://www.bountysource.com/teams/pure-data/issues%3E >> 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@lists.iem.at mailto:GEM-dev@lists.iem.at >>> https://lists.puredata.info/listinfo/gem-dev < https://lists.puredata.info/listinfo/gem-dev%3E >> >> >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at >> https://lists.puredata.info/listinfo/gem-dev < https://lists.puredata.info/listinfo/gem-dev%3E > > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at > https://lists.puredata.info/listinfo/gem-dev < https://lists.puredata.info/listinfo/gem-dev%3E
-- ============================ antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> http://www.hellocatfood.com ============================ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev%3E
-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
On 2017-10-17 10:38, Antoine Villeret wrote:
We can setup some deployment rules to automatically upload binary to github release page and/or to deken.
travis builds are already deployed automatically to http://git.puredata.info/cgit/deployment/Gem-snapshots/
this is not deken, and that's on purpose.
fgmadrt IOhannes
thanks, it's good to know!
Le 12/10/2017 à 23:16, Antonio Roberts a écrit :
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@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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
It took me a very long time to write all of the Quicktime code for pix_film/record/video and have it run well. I think pix_record took a few months to write working on it nearly full time. After that it was a lot more work to have them all run for months at a time without crashing. I was being paid to do it - along with the DirectShow code and a bunch of other things.
A lot of the issues stemmed from how far apart Apple's intended use for the code and what GEM needs to do were. I would expect the newer frameworks that are much more limited than the original ones to be a decent struggle for performance and stability.
Chris
PS - I have no interest in writing code for anything Apple or any other desktop OS again.
On Mon, Oct 30, 2017 at 12:38 PM, cyrille henry ch@chnry.net wrote:
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Why not instead focus on Jonathan's work on implementing WebGL inside Purr-Data canvas (which is already in node webkit) and by doing so obtain most of the Gem functionality in a way that does not mess with the audio interrupt?
On Nov 15, 2017 12:05, "cyrille henry" ch@chnry.net wrote:
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
i'm fighting to keep Gem alive, not to kill it.
Le 16/11/2017 à 03:57, Ivica Ico Bukvic a écrit :
Why not instead focus on Jonathan's work on implementing WebGL inside Purr-Data canvas (which is already in node webkit) and by doing so obtain most of the Gem functionality in a way that does not mess with the audio interrupt?
On Nov 15, 2017 12:05, "cyrille henry" <ch@chnry.net mailto:ch@chnry.net> wrote:
hello, i'm sorry it took so long, I have lot's of work. I found 2 platform : https://pledgie.com/ and : https://www.bountysource.com/ pledgie get 3% of the donation, bountysource get 10%. unless anyone have a better idea, i'll start to go with pledgie cheers c Le 30/10/2017 à 17:38, cyrille henry a écrit : Hello, I've check Iohannes github: There is not a lot's of release critical issue. Image, film and video under osX and having a way to compile for window and the main issues. There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform. Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts : 1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime. if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c Le 12/10/2017 à 10:34, cyrille henry a écrit : 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 <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@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>
Hello,
Pledgie seems ok. I'd be happy to contribute financially for the release of a new Gem and the development of the av plugin for osx. The analysis of Cyrille seems fine to me. Let's do it!
Best, Nicolas
Le 16/11/2017 à 09:42, cyrille henry a écrit :
i'm fighting to keep Gem alive, not to kill it.
Le 16/11/2017 à 03:57, Ivica Ico Bukvic a écrit :
Why not instead focus on Jonathan's work on implementing WebGL inside Purr-Data canvas (which is already in node webkit) and by doing so obtain most of the Gem functionality in a way that does not mess with the audio interrupt?
On Nov 15, 2017 12:05, "cyrille henry" <ch@chnry.net mailto:ch@chnry.net> wrote:
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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 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@lists.iem.at mailto:GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev https://lists.puredata.info/listinfo/gem-dev
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev https://lists.puredata.info/listinfo/gem-dev
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev https://lists.puredata.info/listinfo/gem-dev
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev https://lists.puredata.info/listinfo/gem-dev
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Yes I will donate too!
Sofy Yuditskaya The Source http://yuditskaya.com
On Thu, Nov 16, 2017 at 4:28 AM, Nicolas Montgermont list@nimon.org wrote:
Hello,
Pledgie seems ok. I'd be happy to contribute financially for the release of a new Gem and the development of the av plugin for osx. The analysis of Cyrille seems fine to me. Let's do it!
Best, Nicolas
Le 16/11/2017 à 09:42, cyrille henry a écrit :
i'm fighting to keep Gem alive, not to kill it.
Le 16/11/2017 à 03:57, Ivica Ico Bukvic a écrit :
Why not instead focus on Jonathan's work on implementing WebGL inside Purr-Data canvas (which is already in node webkit) and by doing so obtain most of the Gem functionality in a way that does not mess with the audio interrupt?
On Nov 15, 2017 12:05, "cyrille henry" <ch@chnry.net mailto:ch@chnry.net> wrote:
hello, i'm sorry it took so long, I have lot's of work. I found 2 platform : https://pledgie.com/ and : https://www.bountysource.com/ pledgie get 3% of the donation, bountysource get 10%. unless anyone have a better idea, i'll start to go with pledgie cheers c Le 30/10/2017 à 17:38, cyrille henry a écrit : Hello, I've check Iohannes github: There is not a lot's of releasecritical issue.
Image, film and video under osX and having a way to compilefor window and the main issues.
There is also lot's of stuff regarding FTGL, but they look tobe obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think weshould organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's ofcomputer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platformwe could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit : hello Max Le 12/10/2017 à 10:04, Max a écrit : Bonjour Cyrille, This sounds good, there was the idea of some bountysystem 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 "jobcompleted" entails
I think it imply that the push request is accepted, andthe code is merged upstream.
3. set up a system that doesn't come with a hugeadministration overhead
yes, this is a problem. The reduce amount of developers interested in this jobwill make things simpler.
It almost seem there should be a platform for thisout there...
yes, I don't think administration will be a show stopper. https://www.bountysource.com/teams/pure-data/issueshttps://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" ideaarise 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 allobject / 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, itwill 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, otherinstitutions, 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@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-devhttps://lists.puredata.info/listinfo/gem-dev
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-devhttps://lists.puredata.info/listinfo/gem-dev
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-devhttps://lists.puredata.info/listinfo/gem-dev
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-devhttps://lists.puredata.info/listinfo/gem-dev
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Thanks Cyrille!
I guess bountysource is easier because the fund is automatically distributed among issue solvers. There's the option to funnel the "bounty" back into another issue once you earned the bounty. But, in the end it is more expensive when you "cash out".
Pledgie sounds great. As far as i can tell you need someone to handle how the fund is split among devs once the upgrade is finished or most issues solved. Since it is very easy to see who contributed to the issues, i also think it is better to use and less expensive. It uses Paypal, and I don't see any objections to this.
Just a note on the campaign type: With pledgie it appears you can do two campaign types, 'everything helps' and 'all or nothing', i think the former is better in this case. Since pledgie uses Paypal, when using the latter type the donation is not withdrawn from the donor until the deadline (if the goal was met/surpassed). By then, if the donor's paypal acount changed, then you might not get the entire amount.
And yes, i will also contribute too as much as i can, cause Gem really excellent code and i learn a lot from it!
fdch.github.io/tv
it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation.
So, I went with bounty source. I create 4 bounty:
https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64... https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-...
They correspond to the 4 most important bug I found on the gitub bugtracker.
It's time to find money!
Le 15/11/2017 à 18:05, cyrille henry a écrit :
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
What about something for linux? Generally support a new release?
On 2017년 11월 17일 18:07, cyrille henry wrote:
it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation.
So, I went with bounty source. I create 4 bounty:
https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64...
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit
https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-...
They correspond to the 4 most important bug I found on the gitub bugtracker.
It's time to find money!
Le 15/11/2017 à 18:05, cyrille henry a écrit :
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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
- 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)
- 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.
- 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@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Or for all platforms ? In vertex processing with have : - vertex shader - geometry shader
What about tesselation shader ?
I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++
Jack
Le 20/11/2017 à 12:27, Max a écrit :
What about something for linux? Generally support a new release?
On 2017년 11월 17일 18:07, cyrille henry wrote:
it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation.
So, I went with bounty source. I create 4 bounty:
https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64...
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit
https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-...
They correspond to the 4 most important bug I found on the gitub bugtracker.
It's time to find money!
Le 15/11/2017 à 18:05, cyrille henry a écrit :
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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
- 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)
- 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.
- 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@lists.iem.at > https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
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. Time is not to add functionalities, but to keep Gem alive.
Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished.
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.
cheers c
Le 20/11/2017 à 16:58, Jack a écrit :
Or for all platforms ? In vertex processing with have :
- vertex shader
- geometry shader
What about tesselation shader ?
I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++
Jack
Le 20/11/2017 à 12:27, Max a écrit :
What about something for linux? Generally support a new release?
On 2017년 11월 17일 18:07, cyrille henry wrote:
it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation.
So, I went with bounty source. I create 4 bounty:
https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64...
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit
https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-...
They correspond to the 4 most important bug I found on the gitub bugtracker.
It's time to find money!
Le 15/11/2017 à 18:05, cyrille henry a écrit :
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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@lists.iem.at >> https://lists.puredata.info/listinfo/gem-dev > > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at > https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
On 2017-11-21 10:22, cyrille henry wrote:
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. Time is not to add functionalities, but to keep Gem alive.
Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished.
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.
+1
fgmasdr IOhannes
Yes sure ! ++
Jack
Le 21/11/2017 à 10:22, cyrille henry a écrit :
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. Time is not to add functionalities, but to keep Gem alive.
Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished.
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.
cheers c
Le 20/11/2017 à 16:58, Jack a écrit :
Or for all platforms ? In vertex processing with have :
- vertex shader
- geometry shader
What about tesselation shader ?
I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++
Jack
Le 20/11/2017 à 12:27, Max a écrit :
What about something for linux? Generally support a new release?
On 2017년 11월 17일 18:07, cyrille henry wrote:
it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation.
So, I went with bounty source. I create 4 bounty:
https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64...
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit
https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-...
They correspond to the 4 most important bug I found on the gitub bugtracker.
It's time to find money!
Le 15/11/2017 à 18:05, cyrille henry a écrit :
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit : > 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@lists.iem.at >>> https://lists.puredata.info/listinfo/gem-dev >> >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at >> https://lists.puredata.info/listinfo/gem-dev > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at > https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
+1
On Tue, Nov 21, 2017 at 4:22 AM, cyrille henry ch@chnry.net wrote:
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. Time is not to add functionalities, but to keep Gem alive.
Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished.
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.
cheers c
Le 20/11/2017 à 16:58, Jack a écrit :
Or for all platforms ? In vertex processing with have :
- vertex shader
- geometry shader
What about tesselation shader ?
I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++
Jack
Le 20/11/2017 à 12:27, Max a écrit :
What about something for linux? Generally support a new release?
On 2017년 11월 17일 18:07, cyrille henry wrote:
it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation.
So, I went with bounty source. I create 4 bounty:
https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/issues/4185679-native-video-cap turing-on-osx-64bit
https://www.bountysource.com/issues/4185729-native-film-read ing-on-osx-64bit
https://www.bountysource.com/issues/6492784-native-image-rea ding-writing-on-osx-64bit
They correspond to the 4 most important bug I found on the gitub bugtracker.
It's time to find money!
Le 15/11/2017 à 18:05, cyrille henry a écrit :
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
> 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@lists.iem.at >>> https://lists.puredata.info/listinfo/gem-dev >>> >> >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at >> https://lists.puredata.info/listinfo/gem-dev >> > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at > https://lists.puredata.info/listinfo/gem-dev >
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
+2
Let us know when the donation page is ready in case I missed it..
J
On 11/21/2017 04:41 PM, me.grimm wrote:
+1
On Tue, Nov 21, 2017 at 4:22 AM, cyrille henry <ch@chnry.net mailto:ch@chnry.net> wrote:
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. Time is not to add functionalities, but to keep Gem alive. Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished. 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. cheers c Le 20/11/2017 à 16:58, Jack a écrit : Or for all platforms ? In vertex processing with have : - vertex shader - geometry shader What about tesselation shader ? I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++ Jack Le 20/11/2017 à 12:27, Max a écrit : What about something for linux? Generally support a new release? On 2017년 11월 17일 18:07, cyrille henry wrote: it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation. So, I went with bounty source. I create 4 bounty: https://www.bountysource.com/issues/3383537-w32-build-msvc <https://www.bountysource.com/issues/3383537-w32-build-msvc> https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit <https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit> https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit <https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit> https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit <https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit> They correspond to the 4 most important bug I found on the gitub bugtracker. It's time to find money! Le 15/11/2017 à 18:05, cyrille henry a écrit : hello, i'm sorry it took so long, I have lot's of work. I found 2 platform : https://pledgie.com/ and : https://www.bountysource.com/ pledgie get 3% of the donation, bountysource get 10%. unless anyone have a better idea, i'll start to go with pledgie cheers c Le 30/10/2017 à 17:38, cyrille henry a écrit : Hello, I've check Iohannes github: There is not a lot's of release critical issue. Image, film and video under osX and having a way to compile for window and the main issues. There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform. Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts : 1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime. if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c Le 12/10/2017 à 10:34, cyrille henry a écrit : 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 <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@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Sorry, just saw the pages in the email chain. Are these going to be posted in the general pd mailing list as well?
thanks for your work!
J
On 11/21/2017 04:41 PM, me.grimm wrote:
+1
On Tue, Nov 21, 2017 at 4:22 AM, cyrille henry <ch@chnry.net mailto:ch@chnry.net> wrote:
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. Time is not to add functionalities, but to keep Gem alive. Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished. 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. cheers c Le 20/11/2017 à 16:58, Jack a écrit : Or for all platforms ? In vertex processing with have : - vertex shader - geometry shader What about tesselation shader ? I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++ Jack Le 20/11/2017 à 12:27, Max a écrit : What about something for linux? Generally support a new release? On 2017년 11월 17일 18:07, cyrille henry wrote: it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation. So, I went with bounty source. I create 4 bounty: https://www.bountysource.com/issues/3383537-w32-build-msvc <https://www.bountysource.com/issues/3383537-w32-build-msvc> https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit <https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit> https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit <https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit> https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit <https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit> They correspond to the 4 most important bug I found on the gitub bugtracker. It's time to find money! Le 15/11/2017 à 18:05, cyrille henry a écrit : hello, i'm sorry it took so long, I have lot's of work. I found 2 platform : https://pledgie.com/ and : https://www.bountysource.com/ pledgie get 3% of the donation, bountysource get 10%. unless anyone have a better idea, i'll start to go with pledgie cheers c Le 30/10/2017 à 17:38, cyrille henry a écrit : Hello, I've check Iohannes github: There is not a lot's of release critical issue. Image, film and video under osX and having a way to compile for window and the main issues. There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform. Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts : 1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime. if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c Le 12/10/2017 à 10:34, cyrille henry a écrit : 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 <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@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
I am getting errors in the bountysource page when trying to pay. I'll try again later with other browsers and report back. error says: {"error":"Internal server error."} best, J On 11/21/2017 05:04 PM, Jaime Oliver La Rosa wrote:
Sorry, just saw the pages in the email chain. Are these going to be posted in the general pd mailing list as well?
thanks for your work!
J
On 11/21/2017 04:41 PM, me.grimm wrote:
+1
On Tue, Nov 21, 2017 at 4:22 AM, cyrille henry <ch@chnry.net mailto:ch@chnry.net> wrote:
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. Time is not to add functionalities, but to keep Gem alive. Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished. 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. cheers c Le 20/11/2017 à 16:58, Jack a écrit : Or for all platforms ? In vertex processing with have : - vertex shader - geometry shader What about tesselation shader ? I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++ Jack Le 20/11/2017 à 12:27, Max a écrit : What about something for linux? Generally support a new release? On 2017년 11월 17일 18:07, cyrille henry wrote: it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation. So, I went with bounty source. I create 4 bounty: https://www.bountysource.com/issues/3383537-w32-build-msvc <https://www.bountysource.com/issues/3383537-w32-build-msvc> https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit <https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit> https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit <https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit> https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit <https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit> They correspond to the 4 most important bug I found on the gitub bugtracker. It's time to find money! Le 15/11/2017 à 18:05, cyrille henry a écrit : hello, i'm sorry it took so long, I have lot's of work. I found 2 platform : https://pledgie.com/ and : https://www.bountysource.com/ pledgie get 3% of the donation, bountysource get 10%. unless anyone have a better idea, i'll start to go with pledgie cheers c Le 30/10/2017 à 17:38, cyrille henry a écrit : Hello, I've check Iohannes github: There is not a lot's of release critical issue. Image, film and video under osX and having a way to compile for window and the main issues. There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform. Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts : 1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime. if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c Le 12/10/2017 à 10:34, cyrille henry a écrit : 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 <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@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Le 21/11/2017 à 23:04, Jaime Oliver La Rosa a écrit :
Sorry, just saw the pages in the email chain. Are these going to be posted in the general pd mailing list as well?
as soon as I have time to write a polite and convincing mail! feel free to do it before me! cheers c
thanks for your work!
J
On 11/21/2017 04:41 PM, me.grimm wrote:
+1
On Tue, Nov 21, 2017 at 4:22 AM, cyrille henry <ch@chnry.net mailto:ch@chnry.net> wrote:
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. Time is not to add functionalities, but to keep Gem alive. Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished. 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. cheers c Le 20/11/2017 à 16:58, Jack a écrit : Or for all platforms ? In vertex processing with have : - vertex shader - geometry shader What about tesselation shader ? I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++ Jack Le 20/11/2017 à 12:27, Max a écrit : What about something for linux? Generally support a new release? On 2017년 11월 17일 18:07, cyrille henry wrote: it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation. So, I went with bounty source. I create 4 bounty: https://www.bountysource.com/issues/3383537-w32-build-msvc <https://www.bountysource.com/issues/3383537-w32-build-msvc> https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit <https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit> https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit <https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit> https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit <https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit> They correspond to the 4 most important bug I found on the gitub bugtracker. It's time to find money! Le 15/11/2017 à 18:05, cyrille henry a écrit : hello, i'm sorry it took so long, I have lot's of work. I found 2 platform : https://pledgie.com/ and : https://www.bountysource.com/ pledgie get 3% of the donation, bountysource get 10%. unless anyone have a better idea, i'll start to go with pledgie cheers c Le 30/10/2017 à 17:38, cyrille henry a écrit : Hello, I've check Iohannes github: There is not a lot's of release critical issue. Image, film and video under osX and having a way to compile for window and the main issues. There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform. Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts : 1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime. if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c Le 12/10/2017 à 10:34, cyrille henry a écrit : 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 <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@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Are these going to be posted in the general pd mailing list as well?
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
On Wed, Nov 22, 2017 at 3:46 AM, cyrille henry ch@chnry.net wrote:
Le 21/11/2017 à 23:04, Jaime Oliver La Rosa a écrit :
Sorry, just saw the pages in the email chain. Are these going to be posted in the general pd mailing list as well?
as soon as I have time to write a polite and convincing mail! feel free to do it before me! cheers c
thanks for your work!
J
On 11/21/2017 04:41 PM, me.grimm wrote:
+1
On Tue, Nov 21, 2017 at 4:22 AM, cyrille henry <ch@chnry.net mailto: ch@chnry.net> wrote:
As I said in earlier mail, my aim is (for now) to be able to releasea Gem version that incorporate the development made in the last 5 years. Time is not to add functionalities, but to keep Gem alive.
Starting new development now is, imo, a nonsense since no releasecan be done before this 4 tasks will be finished.
I am, like you, only a linux user that have no interest in osX norwindows, but this is mandatory before being able to go forward.
cheers c Le 20/11/2017 à 16:58, Jack a écrit : Or for all platforms ? In vertex processing with have : - vertex shader - geometry shader What about tesselation shader ? I use Gem a lot so i will be happy to participate financially ifthat can help to add functionality to it. ++
Jack Le 20/11/2017 à 12:27, Max a écrit : What about something for linux? Generally support a newrelease?
On 2017년 11월 17일 18:07, cyrille henry wrote: it appear that pledgie is dedicatad to find money foryour work, better than financing other work. i.e, if I crete a project, I'll receive the donation.
So, I went with bounty source. I create 4 bounty: https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/ issues/3383537-w32-build-msvc https://www.bountysource.com/i ssues/4185679-native-video-capturing-on-osx-64bit < https://www.bountysource.com/issues/4185679-native-video-ca pturing-on-osx-64bit>
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit < https://www.bountysource.com/issues/4185729-native-film-rea ding-on-osx-64bit>
https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit < https://www.bountysource.com/issues/6492784-native-image-re ading-writing-on-osx-64bit>
They correspond to the 4 most important bug I found onthe gitub bugtracker.
It's time to find money! Le 15/11/2017 à 18:05, cyrille henry a écrit : hello, i'm sorry it took so long, I have lot's of work. I found 2 platform : https://pledgie.com/ and : https://www.bountysource.com/ pledgie get 3% of the donation, bountysource get 10%. unless anyone have a better idea, i'll start to gowith pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit : Hello, I've check Iohannes github: There is not a lot'sof release critical issue.
Image, film and video under osX and having a wayto compile for window and the main issues.
There is also lot's of stuff regarding FTGL, butthey look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, Ithink we should organize development in 2 parts :
1st : doing the minimum to have Gem usable onall platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look atthe platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit : hello Max Le 12/10/2017 à 10:04, Max a écrit : Bonjour Cyrille, This sounds good, there was the idea ofsome bounty system years ago too. I think it's crucial for this process to
1. break up the job in small manageableparts
yes, that's the idea of using the github bugtracker. Spiting jobs in bugs. (and use flags to create priorities)
2. well define their scope and definewhat "job completed" entails
I think it imply that the push request isaccepted, and the code is merged upstream.
3. set up a system that doesn't comewith a huge administration overhead
yes, this is a problem. The reduce amount of developers interestedin this job will make things simpler.
It almost seem there should be aplatform for this out there...
yes, I don't think administration will be ashow stopper.
https://www.bountysource.com/teams/pure-data/issues https://www.bountysource.com/ teams/pure-data/issues
this one looks like it parses githubissues.. kind of shady.
On 2017년 10월 12일 09:46, cyrille henrywrote:
Hello, Since the "get money, paid adeveloper" 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 : alist 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 NewBlankets, 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@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/li stinfo/gem-dev https://lists.puredata.info/listinfo/gem-dev
______________________________
GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/li stinfo/gem-dev https://lists.puredata.info/listinfo/gem-dev
______________________________
GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev https://lists.puredata.info/listinfo/gem-dev
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev < https://lists.puredata.info/listinfo/gem-dev%3E
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev%3E
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev%3E
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev%3E
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev%3E
_______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev%3E
-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
hello, I'm in discussion with joe deken from newblankets around an other/better way to deal with donation. So maybe we should wait a bit before making a wider announce of this bounty.
cheers c
Le 22/11/2017 à 21:45, me.grimm a écrit :
Are these going to be posted in the general pd mailing list as well?
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
On Wed, Nov 22, 2017 at 3:46 AM, cyrille henry <ch@chnry.net mailto:ch@chnry.net> wrote:
Le 21/11/2017 à 23:04, Jaime Oliver La Rosa a écrit : Sorry, just saw the pages in the email chain. Are these going to be posted in the general pd mailing list as well? as soon as I have time to write a polite and convincing mail! feel free to do it before me! cheers c thanks for your work! J On 11/21/2017 04:41 PM, me.grimm wrote: +1 On Tue, Nov 21, 2017 at 4:22 AM, cyrille henry <ch@chnry.net <mailto:ch@chnry.net> <mailto:ch@chnry.net <mailto:ch@chnry.net>>> wrote: 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. Time is not to add functionalities, but to keep Gem alive. Starting new development now is, imo, a nonsense since no release can be done before this 4 tasks will be finished. 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. cheers c Le 20/11/2017 à 16:58, Jack a écrit : Or for all platforms ? In vertex processing with have : - vertex shader - geometry shader What about tesselation shader ? I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++ Jack Le 20/11/2017 à 12:27, Max a écrit : What about something for linux? Generally support a new release? On 2017년 11월 17일 18:07, cyrille henry wrote: it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation. So, I went with bounty source. I create 4 bounty: https://www.bountysource.com/issues/3383537-w32-build-msvc <https://www.bountysource.com/issues/3383537-w32-build-msvc> <https://www.bountysource.com/issues/3383537-w32-build-msvc <https://www.bountysource.com/issues/3383537-w32-build-msvc>> https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit <https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit> <https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit <https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64bit>> https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit <https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit> <https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit <https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit>> https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit <https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit> <https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit <https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit>> They correspond to the 4 most important bug I found on the gitub bugtracker. It's time to find money! Le 15/11/2017 à 18:05, cyrille henry a écrit : hello, i'm sorry it took so long, I have lot's of work. I found 2 platform : https://pledgie.com/ and : https://www.bountysource.com/ pledgie get 3% of the donation, bountysource get 10%. unless anyone have a better idea, i'll start to go with pledgie cheers c Le 30/10/2017 à 17:38, cyrille henry a écrit : Hello, I've check Iohannes github: There is not a lot's of release critical issue. Image, film and video under osX and having a way to compile for window and the main issues. There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform. Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts : 1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime. if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c Le 12/10/2017 à 10:34, cyrille henry a écrit : 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 <https://www.bountysource.com/teams/pure-data/issues> <https://www.bountysource.com/teams/pure-data/issues <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@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> -- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net <http://megrimm.net> <http://megrimm.net> ____________________ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
2017-11-23 7:14 GMT-02:00 cyrille henry ch@chnry.net:
hello, I'm in discussion with joe deken from newblankets around an other/better way to deal with donation. So maybe we should wait a bit before making a wider announce of this bounty.
Hi, can you give us some more information about it? I don't understand what you mean.
Do you mean you will change the donation system from "bountysource.com"? I don't think so, cause, well, people already gave money to that... (me, for instance, gave 30$). But if that's the case, how do we deal with that (like, how to get the money back)?
And if that's not it, what prevents anyone from sharing this campaign on facebook, the pd list and whatever?
cheers
We can get our money back, if necessary, of course leaving 10% fee to bountysource, plus 3.4% (IMO) to paypal. Anyway I personally don't mind to change for an other way if it's worth it.
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
2017-11-25 15:32 GMT+01:00 Alexandre Torres Porres porres@gmail.com:
2017-11-23 7:14 GMT-02:00 cyrille henry ch@chnry.net:
hello, I'm in discussion with joe deken from newblankets around an other/better way to deal with donation. So maybe we should wait a bit before making a wider announce of this bounty.
Hi, can you give us some more information about it? I don't understand what you mean.
Do you mean you will change the donation system from "bountysource.com"? I don't think so, cause, well, people already gave money to that... (me, for instance, gave 30$). But if that's the case, how do we deal with that (like, how to get the money back)?
And if that's not it, what prevents anyone from sharing this campaign on facebook, the pd list and whatever?
cheers
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
2017-11-25 13:53 GMT-02:00 Antoine Rousseau antoine@metalu.net:
I personally don't mind to change for an other way if it's worth it.
yeah, I can't say I wouldn't mind it... :/
And if that's not it, what prevents anyone from sharing this campaign on
facebook, the pd list and whatever?
and also what might prevent multiple funding sources?
On Sat, Nov 25, 2017 at 9:32 AM, Alexandre Torres Porres porres@gmail.com wrote:
2017-11-23 7:14 GMT-02:00 cyrille henry ch@chnry.net:
hello, I'm in discussion with joe deken from newblankets around an other/better way to deal with donation. So maybe we should wait a bit before making a wider announce of this bounty.
Hi, can you give us some more information about it? I don't understand what you mean.
Do you mean you will change the donation system from "bountysource.com"? I don't think so, cause, well, people already gave money to that... (me, for instance, gave 30$). But if that's the case, how do we deal with that (like, how to get the money back)?
And if that's not it, what prevents anyone from sharing this campaign on facebook, the pd list and whatever?
cheers
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
and also what might prevent multiple funding sources?
Depending on how the money is being used maybe that wouldn't be a bad thing.
Using this Patreon as an example https://www.patreon.com/pippin the funding is to support the developer, not necessarily the GIMP software (even though the aforementioned person is a major developer of GIMP).
So, if we look at bountysource/this funding drive as a way to fund developers rather than the software (semantics, i know!) does that get over these potential issues?
On 25 November 2017 at 19:49, me.grimm megrimm@gmail.com wrote:
And if that's not it, what prevents anyone from sharing this campaign on facebook, the pd list and whatever?
and also what might prevent multiple funding sources?
On Sat, Nov 25, 2017 at 9:32 AM, Alexandre Torres Porres porres@gmail.com wrote:
2017-11-23 7:14 GMT-02:00 cyrille henry ch@chnry.net:
hello, I'm in discussion with joe deken from newblankets around an other/better way to deal with donation. So maybe we should wait a bit before making a wider announce of this bounty.
Hi, can you give us some more information about it? I don't understand what you mean.
Do you mean you will change the donation system from "bountysource.com"? I don't think so, cause, well, people already gave money to that... (me, for instance, gave 30$). But if that's the case, how do we deal with that (like, how to get the money back)?
And if that's not it, what prevents anyone from sharing this campaign on facebook, the pd list and whatever?
cheers
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Hi, so, what's up?
we already have 385$ thrown at bountysource, ditching it would mean throwing about 40$ in the thrash, plus taxes to paypal... it'd be weird and silly, not to mention a disrespect to some who felt like they wanted to help (I, for one, would feel like that and regretful I helped). Any word or idea on what's going on there?
I guess multiple sources could be a good way to go if you feel there's also a better parallel option, but please don't just do this without consulting people who have already pledged money, and while this is still out there in the air and others could give yet more money to it.
cheers
2017-11-26 0:03 GMT-02:00 Antonio Roberts antonio@hellocatfood.com:
and also what might prevent multiple funding sources?
Depending on how the money is being used maybe that wouldn't be a bad thing.
Using this Patreon as an example https://www.patreon.com/pippin the funding is to support the developer, not necessarily the GIMP software (even though the aforementioned person is a major developer of GIMP).
So, if we look at bountysource/this funding drive as a way to fund developers rather than the software (semantics, i know!) does that get over these potential issues?
On 25 November 2017 at 19:49, me.grimm megrimm@gmail.com wrote:
And if that's not it, what prevents anyone from sharing this campaign
on
facebook, the pd list and whatever?
and also what might prevent multiple funding sources?
On Sat, Nov 25, 2017 at 9:32 AM, Alexandre Torres Porres <
porres@gmail.com>
wrote:
2017-11-23 7:14 GMT-02:00 cyrille henry ch@chnry.net:
hello, I'm in discussion with joe deken from newblankets around an
other/better
way to deal with donation. So maybe we should wait a bit before making a wider announce of this bounty.
Hi, can you give us some more information about it? I don't understand what you mean.
Do you mean you will change the donation system from "bountysource.com"?
I
don't think so, cause, well, people already gave money to that... (me,
for
instance, gave 30$). But if that's the case, how do we deal with that
(like,
how to get the money back)?
And if that's not it, what prevents anyone from sharing this campaign on facebook, the pd list and whatever?
cheers
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
--
antonio@hellocatfood.com http://www.hellocatfood.com ============================
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
hello, sorry for being unresponsive. I don't have lot's of free time.
All money put on a bounty can be moved to an other bug, and there are lot's of bugs to fix : https://www.bountysource.com/trackers/1046360-umlaeute-gem So, don't worry about the money already in the bounty system : it will not be useless.
I put money on the 4 issues that prevent a new release. But I talk to Iohannes and it appear I may have made some mistake. Iohannes should organize a bit the github issue soon. We may have to moved some founding from 1 issue to an other after that. So, let's wait that Iohannes spend few time on github before we announce this bounty to a bigger audience.
About New Blanket, I fail to find a good way to go, since I already start the bounty system, and that I don't have enough free time. But having this new release in only a 1st steep : there is lot's of other bugs and feature request that are waiting for to long. So, next time, with a better organization, we will find a way to have NB help us on the founding.
I'm aware that thing moves slowly, but at least they are moving!
cheers Cyrille
Le 30/11/2017 à 02:54, Alexandre Torres Porres a écrit :
Hi, so, what's up?
we already have 385$ thrown at bountysource, ditching it would mean throwing about 40$ in the thrash, plus taxes to paypal... it'd be weird and silly, not to mention a disrespect to some who felt like they wanted to help (I, for one, would feel like that and regretful I helped). Any word or idea on what's going on there?
I guess multiple sources could be a good way to go if you feel there's also a better parallel option, but please don't just do this without consulting people who have already pledged money, and while this is still out there in the air and others could give yet more money to it.
cheers
2017-11-26 0:03 GMT-02:00 Antonio Roberts <antonio@hellocatfood.com mailto:antonio@hellocatfood.com>:
> and also what might prevent multiple funding sources? Depending on how the money is being used maybe that wouldn't be a bad thing. Using this Patreon as an example https://www.patreon.com/pippin the funding is to support the developer, not necessarily the GIMP software (even though the aforementioned person is a major developer of GIMP). So, if we look at bountysource/this funding drive as a way to fund developers rather than the software (semantics, i know!) does that get over these potential issues? On 25 November 2017 at 19:49, me.grimm <megrimm@gmail.com <mailto:megrimm@gmail.com>> wrote: >>> And if that's not it, what prevents anyone from sharing this campaign on >>> facebook, the pd list and whatever? > > and also what might prevent multiple funding sources? > > > > On Sat, Nov 25, 2017 at 9:32 AM, Alexandre Torres Porres <porres@gmail.com <mailto:porres@gmail.com>> > wrote: >> >> >> >> 2017-11-23 7:14 GMT-02:00 cyrille henry <ch@chnry.net <mailto:ch@chnry.net>>: >>> >>> hello, >>> I'm in discussion with joe deken from newblankets around an other/better >>> way to deal with donation. >>> So maybe we should wait a bit before making a wider announce of this >>> bounty. >> >> >> Hi, can you give us some more information about it? I don't understand >> what you mean. >> >> Do you mean you will change the donation system from "bountysource.com <http://bountysource.com>"? I >> don't think so, cause, well, people already gave money to that... (me, for >> instance, gave 30$). But if that's the case, how do we deal with that (like, >> how to get the money back)? >> >> And if that's not it, what prevents anyone from sharing this campaign on >> facebook, the pd list and whatever? >> >> cheers >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> >> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> >> > > > > -- > ____________________ > m.e.grimm, m.f.a, ed.m. > syracuse u., tc3 > megrimm.net <http://megrimm.net> > ____________________ > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> > https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> > -- ============================ antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> http://www.hellocatfood.com ============================ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
I'm aware that thing moves slowly, but at least they are moving!
agree!!!!
So, don't worry about the money already in the bounty system : it will
not be useless.
so.... do we then keep lobbying for bountysouce funding? again, we could have this pinned on the facebook group (12k subscribers) which could generate greater donations.
m
On Thu, Nov 30, 2017 at 9:29 AM, cyrille henry ch@chnry.net wrote:
hello, sorry for being unresponsive. I don't have lot's of free time.
All money put on a bounty can be moved to an other bug, and there are lot's of bugs to fix : https://www.bountysource.com/trackers/1046360-umlaeute-gem So, don't worry about the money already in the bounty system : it will not be useless.
I put money on the 4 issues that prevent a new release. But I talk to Iohannes and it appear I may have made some mistake. Iohannes should organize a bit the github issue soon. We may have to moved some founding from 1 issue to an other after that. So, let's wait that Iohannes spend few time on github before we announce this bounty to a bigger audience.
About New Blanket, I fail to find a good way to go, since I already start the bounty system, and that I don't have enough free time. But having this new release in only a 1st steep : there is lot's of other bugs and feature request that are waiting for to long. So, next time, with a better organization, we will find a way to have NB help us on the founding.
I'm aware that thing moves slowly, but at least they are moving!
cheers Cyrille
Le 30/11/2017 à 02:54, Alexandre Torres Porres a écrit :
Hi, so, what's up?
we already have 385$ thrown at bountysource, ditching it would mean throwing about 40$ in the thrash, plus taxes to paypal... it'd be weird and silly, not to mention a disrespect to some who felt like they wanted to help (I, for one, would feel like that and regretful I helped). Any word or idea on what's going on there?
I guess multiple sources could be a good way to go if you feel there's also a better parallel option, but please don't just do this without consulting people who have already pledged money, and while this is still out there in the air and others could give yet more money to it.
cheers
2017-11-26 0:03 GMT-02:00 Antonio Roberts <antonio@hellocatfood.com mailto:antonio@hellocatfood.com>:
> and also what might prevent multiple funding sources? Depending on how the money is being used maybe that wouldn't be a badthing.
Using this Patreon as an example https://www.patreon.com/pippin the funding is to support the developer, not necessarily the GIMP software (even though the aforementioned person is a major developer of GIMP). So, if we look at bountysource/this funding drive as a way to fund developers rather than the software (semantics, i know!) does that get over these potential issues? On 25 November 2017 at 19:49, me.grimm <megrimm@gmail.com <mailto:megrimm@gmail.com>> wrote: >>> And if that's not it, what prevents anyone from sharing this campaign on >>> facebook, the pd list and whatever? > > and also what might prevent multiple funding sources? > > > > On Sat, Nov 25, 2017 at 9:32 AM, Alexandre Torres Porres < porres@gmail.com mailto:porres@gmail.com> > wrote: >> >> >> >> 2017-11-23 7:14 GMT-02:00 cyrille henry <ch@chnry.net mailto: ch@chnry.net>: >>> >>> hello, >>> I'm in discussion with joe deken from newblankets around an other/better >>> way to deal with donation. >>> So maybe we should wait a bit before making a wider announce of this >>> bounty. >> >> >> Hi, can you give us some more information about it? I don't understand >> what you mean. >> >> Do you mean you will change the donation system from " bountysource.com http://bountysource.com"? I >> don't think so, cause, well, people already gave money to that... (me, for >> instance, gave 30$). But if that's the case, how do we deal with that (like, >> how to get the money back)? >> >> And if that's not it, what prevents anyone from sharing this campaign on >> facebook, the pd list and whatever? >> >> cheers >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at >> https://lists.puredata.info/listinfo/gem-dev < https://lists.puredata.info/listinfo/gem-dev%3E >> > > > > -- > ____________________ > m.e.grimm, m.f.a, ed.m. > syracuse u., tc3 > megrimm.net http://megrimm.net > ____________________ > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at > https://lists.puredata.info/listinfo/gem-dev < https://lists.puredata.info/listinfo/gem-dev%3E >
-- ============================ antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> http://www.hellocatfood.com ============================ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev%3E
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Hi,
I am an admin of the Pd Facebook group.
People have been asking for a sticky-post announcing this funding for GEM development. A poll confirmed this was overwhelming supported.
Can someone give me a SINGLE link which is best for the entire project? It should have some narrative about WHO is running the project and WHAT it is, and HOW people can contribute funds.
Also, is there a way people can contribute funds to the entire project, and not towards fixing specific bugs? (I am unfamiliar with this funding model).
I want to satisfy the request for a sticky post, but I'm not sure how to proceed.
Thanks, BH
-- William Huston: WilliamAHuston@gmail.com Binghamton NY
Public Service Mapping / Videography / Research WilliamAHuston.blogspot.com
On Thu, Nov 30, 2017 at 12:40 PM, me.grimm megrimm@gmail.com wrote:
I'm aware that thing moves slowly, but at least they are moving!
agree!!!!
So, don't worry about the money already in the bounty system : it will
not be useless.
so.... do we then keep lobbying for bountysouce funding? again, we could have this pinned on the facebook group (12k subscribers) which could generate greater donations.
m
On Thu, Nov 30, 2017 at 9:29 AM, cyrille henry ch@chnry.net wrote:
hello, sorry for being unresponsive. I don't have lot's of free time.
All money put on a bounty can be moved to an other bug, and there are lot's of bugs to fix : https://www.bountysource.com/trackers/1046360-umlaeute-gem So, don't worry about the money already in the bounty system : it will not be useless.
I put money on the 4 issues that prevent a new release. But I talk to Iohannes and it appear I may have made some mistake. Iohannes should organize a bit the github issue soon. We may have to moved some founding from 1 issue to an other after that. So, let's wait that Iohannes spend few time on github before we announce this bounty to a bigger audience.
About New Blanket, I fail to find a good way to go, since I already start the bounty system, and that I don't have enough free time. But having this new release in only a 1st steep : there is lot's of other bugs and feature request that are waiting for to long. So, next time, with a better organization, we will find a way to have NB help us on the founding.
I'm aware that thing moves slowly, but at least they are moving!
cheers Cyrille
Le 30/11/2017 à 02:54, Alexandre Torres Porres a écrit :
Hi, so, what's up?
we already have 385$ thrown at bountysource, ditching it would mean throwing about 40$ in the thrash, plus taxes to paypal... it'd be weird and silly, not to mention a disrespect to some who felt like they wanted to help (I, for one, would feel like that and regretful I helped). Any word or idea on what's going on there?
I guess multiple sources could be a good way to go if you feel there's also a better parallel option, but please don't just do this without consulting people who have already pledged money, and while this is still out there in the air and others could give yet more money to it.
cheers
2017-11-26 0:03 GMT-02:00 Antonio Roberts <antonio@hellocatfood.com mailto:antonio@hellocatfood.com>:
> and also what might prevent multiple funding sources? Depending on how the money is being used maybe that wouldn't be abad thing.
Using this Patreon as an example https://www.patreon.com/pippin the funding is to support the developer, not necessarily the GIMPsoftware (even though the aforementioned person is a major developer of GIMP).
So, if we look at bountysource/this funding drive as a way to fund developers rather than the software (semantics, i know!) does thatget over these potential issues?
On 25 November 2017 at 19:49, me.grimm <megrimm@gmail.com <mailto:megrimm@gmail.com>> wrote: >>> And if that's not it, what prevents anyone from sharing this campaign on >>> facebook, the pd list and whatever? > > and also what might prevent multiple funding sources? > > > > On Sat, Nov 25, 2017 at 9:32 AM, Alexandre Torres Porres < porres@gmail.com mailto:porres@gmail.com> > wrote: >> >> >> >> 2017-11-23 7:14 GMT-02:00 cyrille henry <ch@chnry.net mailto: ch@chnry.net>: >>> >>> hello, >>> I'm in discussion with joe deken from newblankets around an other/better >>> way to deal with donation. >>> So maybe we should wait a bit before making a wider announce of this >>> bounty. >> >> >> Hi, can you give us some more information about it? I don't understand >> what you mean. >> >> Do you mean you will change the donation system from " bountysource.com http://bountysource.com"? I >> don't think so, cause, well, people already gave money to that... (me, for >> instance, gave 30$). But if that's the case, how do we deal with that (like, >> how to get the money back)? >> >> And if that's not it, what prevents anyone from sharing this campaign on >> facebook, the pd list and whatever? >> >> cheers >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at >> https://lists.puredata.info/listinfo/gem-dev < https://lists.puredata.info/listinfo/gem-dev%3E >> > > > > -- > ____________________ > m.e.grimm, m.f.a, ed.m. > syracuse u., tc3 > megrimm.net http://megrimm.net > ____________________ > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at mailto:GEM-dev@lists.iem.at > https://lists.puredata.info/listinfo/gem-dev < https://lists.puredata.info/listinfo/gem-dev%3E >
-- ============================ antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> http://www.hellocatfood.com ============================ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev%3E
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Hello William,
Iohannes is still organizing things concerning the bugs to fix before to make a release. So the idea is to wait a bit before to announce the link. You can follow this thread if you want uptodate infos. n
Le 30/11/2017 à 19:16, William Huston a écrit :
Hi,
I am an admin of the Pd Facebook group.
People have been asking for a sticky-post announcing this funding for GEM development. A poll confirmed this was overwhelming supported.
Can someone give me a SINGLE link which is best for the entire project? It should have some narrative about WHO is running the project and WHAT it is, and HOW people can contribute funds.
Also, is there a way people can contribute funds to the entire project, and not towards fixing specific bugs? (I am unfamiliar with this funding model).
I want to satisfy the request for a sticky post, but I'm not sure how to proceed.
Thanks, BH
-- William Huston: WilliamAHuston@gmail.com mailto:WilliamAHuston@gmail.com Binghamton NY
Public Service Mapping / Videography / Research WilliamAHuston.blogspot.com http://WilliamAHuston.blogspot.com
On Thu, Nov 30, 2017 at 12:40 PM, me.grimm <megrimm@gmail.com mailto:megrimm@gmail.com> wrote:
>> I'm aware that thing moves slowly, but at least they are moving! agree!!!! >> So, don't worry about the money already in the bounty system : it will not be useless. so.... do we then keep lobbying for bountysouce funding? again, we could have this pinned on the facebook group (12k subscribers) which could generate greater donations. m On Thu, Nov 30, 2017 at 9:29 AM, cyrille henry <ch@chnry.net <mailto:ch@chnry.net>> wrote: hello, sorry for being unresponsive. I don't have lot's of free time. All money put on a bounty can be moved to an other bug, and there are lot's of bugs to fix : https://www.bountysource.com/trackers/1046360-umlaeute-gem <https://www.bountysource.com/trackers/1046360-umlaeute-gem> So, don't worry about the money already in the bounty system : it will not be useless. I put money on the 4 issues that prevent a new release. But I talk to Iohannes and it appear I may have made some mistake. Iohannes should organize a bit the github issue soon. We may have to moved some founding from 1 issue to an other after that. So, let's wait that Iohannes spend few time on github before we announce this bounty to a bigger audience. About New Blanket, I fail to find a good way to go, since I already start the bounty system, and that I don't have enough free time. But having this new release in only a 1st steep : there is lot's of other bugs and feature request that are waiting for to long. So, next time, with a better organization, we will find a way to have NB help us on the founding. I'm aware that thing moves slowly, but at least they are moving! cheers Cyrille Le 30/11/2017 à 02:54, Alexandre Torres Porres a écrit : Hi, so, what's up? we already have 385$ thrown at bountysource, ditching it would mean throwing about 40$ in the thrash, plus taxes to paypal... it'd be weird and silly, not to mention a disrespect to some who felt like they wanted to help (I, for one, would feel like that and regretful I helped). Any word or idea on what's going on there? I guess multiple sources could be a good way to go if you feel there's also a better parallel option, but please don't just do this without consulting people who have already pledged money, and while this is still out there in the air and others could give yet more money to it. cheers 2017-11-26 0:03 GMT-02:00 Antonio Roberts <antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> <mailto:antonio@hellocatfood.com <mailto:antonio@hellocatfood.com>>>: > and also what might prevent multiple funding sources? Depending on how the money is being used maybe that wouldn't be a bad thing. Using this Patreon as an example https://www.patreon.com/pippin the funding is to support the developer, not necessarily the GIMP software (even though the aforementioned person is a major developer of GIMP). So, if we look at bountysource/this funding drive as a way to fund developers rather than the software (semantics, i know!) does that get over these potential issues? On 25 November 2017 at 19:49, me.grimm <megrimm@gmail.com <mailto:megrimm@gmail.com> <mailto:megrimm@gmail.com <mailto:megrimm@gmail.com>>> wrote: >>> And if that's not it, what prevents anyone from sharing this campaign on >>> facebook, the pd list and whatever? > > and also what might prevent multiple funding sources? > > > > On Sat, Nov 25, 2017 at 9:32 AM, Alexandre Torres Porres <porres@gmail.com <mailto:porres@gmail.com> <mailto:porres@gmail.com <mailto:porres@gmail.com>>> > wrote: >> >> >> >> 2017-11-23 7:14 GMT-02:00 cyrille henry <ch@chnry.net <mailto:ch@chnry.net> <mailto:ch@chnry.net <mailto:ch@chnry.net>>>: >>> >>> hello, >>> I'm in discussion with joe deken from newblankets around an other/better >>> way to deal with donation. >>> So maybe we should wait a bit before making a wider announce of this >>> bounty. >> >> >> Hi, can you give us some more information about it? I don't understand >> what you mean. >> >> Do you mean you will change the donation system from "bountysource.com <http://bountysource.com> <http://bountysource.com>"? I >> don't think so, cause, well, people already gave money to that... (me, for >> instance, gave 30$). But if that's the case, how do we deal with that (like, >> how to get the money back)? >> >> And if that's not it, what prevents anyone from sharing this campaign on >> facebook, the pd list and whatever? >> >> cheers >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> >> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> >> > > > > -- > ____________________ > m.e.grimm, m.f.a, ed.m. > syracuse u., tc3 > megrimm.net <http://megrimm.net> <http://megrimm.net> > ____________________ > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> > https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> > -- ============================ antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> <mailto:antonio@hellocatfood.com <mailto:antonio@hellocatfood.com>> http://www.hellocatfood.com ============================ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> -- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net <http://megrimm.net> ____________________ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
On 2017-11-30 19:24, Nicolas Montgermont wrote:
Iohannes is still organizing things concerning the bugs to fix before to make a release.
i've started to mark tickets on github with "help wanted". these are good candidates for funded contributions (esp. when paired with the "release-critical" tag)
of course, if you find any other issues that *you* think must be solved to make a new Gem release usable on your platform, don't hesitate to leave a note at any such ticket.
amsdr IOhannes
thanks Iohannes,
what about the W32 build (both MSVC and minggw)? should we ask for this build or does "make filmDS consistent #180" will make things easier on this side? (Should I ask to move the bounty from the mingW bug to the filmDS issue?)
cheers
Le 05/12/2017 à 12:04, IOhannes m zmoelnig a écrit :
On 2017-11-30 19:24, Nicolas Montgermont wrote:
Iohannes is still organizing things concerning the bugs to fix before to make a release.
i've started to mark tickets on github with "help wanted". these are good candidates for funded contributions (esp. when paired with the "release-critical" tag)
of course, if you find any other issues that *you* think must be solved to make a new Gem release usable on your platform, don't hesitate to leave a note at any such ticket.
amsdr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
On 12/05/2017 04:06 PM, cyrille henry wrote:
thanks Iohannes,
what about the W32 build (both MSVC and minggw)? should we ask for this build or does "make filmDS consistent #180" will make things easier on this side? (Should I ask to move the bounty from the mingW bug to the filmDS issue?)
yes i think so.
the point is, that you cannot fix any filmDS issues if you don't have a working W32 build :-)
gfmsadr IOhannes
ok, so I put money on 2 other issues. For now, the most important issues are :
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64... https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-... https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit https://www.bountysource.com/issues/52336294-make-filmds-consistent
all issue are listed here : https://www.bountysource.com/trackers/1046360-umlaeute-gem
I think it's good to have a rough estimation of the cost of each task if we want to ask average user to fund this bounty.
My estimation based on various discussion I had is that the "native film reading on osX64bit" is very complex and should go up to 2000€ "native-video-capturing-on-osx-64bit" : 1500€ "native-image-reading-writing-on-osx-64bit" : 1000€ a developer all ready ask for 150$ for "w32 build msvc", so it's a good goal. "any-h-broken-on-osx-64bit" : ??? "make-filmds-consistent" : ???
But I may be completely wrong. Please correct me if you have an estimation.
cheers c
Le 05/12/2017 à 17:09, IOhannes m zmölnig a écrit :
On 12/05/2017 04:06 PM, cyrille henry wrote:
thanks Iohannes,
what about the W32 build (both MSVC and minggw)? should we ask for this build or does "make filmDS consistent #180" will make things easier on this side? (Should I ask to move the bounty from the mingW bug to the filmDS issue?)
yes i think so.
the point is, that you cannot fix any filmDS issues if you don't have a working W32 build :-)
gfmsadr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
On 12/05/2017 06:08 PM, cyrille henry wrote:
could we undo that? (despite the bountyhunter who already asks for 150€)?
https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit
i don't currently have access to an OSX system. could somebody confirm that this is actually a problem in the current "master"?
https://www.bountysource.com/issues/52336294-make-filmds-consistent
we have a kind of working plugin here (afaik), so it should be less work than "native film reading on OSX", but probably in the same range as what you setup for "native image reading/writing on OSX"
gfamdsr IOhannes
Le 05/12/2017 à 18:56, IOhannes m zmölnig a écrit :
On 12/05/2017 06:08 PM, cyrille henry wrote:
could we undo that? (despite the bountyhunter who already asks for 150€)?
there is 2 way : each bounty contributor can contact the bountysource team to ask to reallocate the money to an other bounty. (there is currently 4 contributor : me, porres, ant1r, Jonghyun kim. they should all be in this mailing list.)
the 2nd way it to mark the github issue as wontfix, so the money is refund.
I choose solution 1 and send a mail to support@bountysource.com asking to move my money to an other issue. Can porres, ant1r and kim do the same?
https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit
i don't currently have access to an OSX system. could somebody confirm that this is actually a problem in the current "master"?
https://www.bountysource.com/issues/52336294-make-filmds-consistent
we have a kind of working plugin here (afaik), so it should be less work than "native film reading on OSX", but probably in the same range as what you setup for "native image reading/writing on OSX"
so : https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit : 2000$ https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64... : 1500$ https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-... : 1000$ https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit : ??? https://www.bountysource.com/issues/52336294-make-filmds-consistent : 1000$
cheers c
gfamdsr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
2017-12-05 16:49 GMT-02:00 cyrille henry ch@chnry.net:
Le 05/12/2017 à 18:56, IOhannes m zmölnig a écrit :
On 12/05/2017 06:08 PM, cyrille henry wrote:
could we undo that? (despite the bountyhunter who already asks for 150€)?
there is 2 way : each bounty contributor can contact the bountysource team to ask to reallocate the money to an other bounty. (there is currently 4 contributor : me, porres, ant1r, Jonghyun kim. they should all be in this mailing list.)
the 2nd way it to mark the github issue as wontfix, so the money is refund.
I choose solution 1 and send a mail to support@bountysource.com asking to move my money to an other issue. Can porres, ant1r and kim do the same?
I can ;)
Le 05/12/2017 à 19:54, Alexandre Torres Porres a écrit :
Can porres, ant1r and kim do the same?I can ;)
thanks, and sorry for the inconvenience.
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Can porres, ant1r and kim do the same?
Of course I will do whatever you think it has to, but I don't understand, as IOhannes said:
you cannot fix any filmDS issues if you don't have a working W32 build
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
2017-12-05 19:49 GMT+01:00 cyrille henry ch@chnry.net:
Le 05/12/2017 à 18:56, IOhannes m zmölnig a écrit :
On 12/05/2017 06:08 PM, cyrille henry wrote:
could we undo that? (despite the bountyhunter who already asks for 150€)?
there is 2 way : each bounty contributor can contact the bountysource team to ask to reallocate the money to an other bounty. (there is currently 4 contributor : me, porres, ant1r, Jonghyun kim. they should all be in this mailing list.)
the 2nd way it to mark the github issue as wontfix, so the money is refund.
I choose solution 1 and send a mail to support@bountysource.com asking to move my money to an other issue. Can porres, ant1r and kim do the same?
https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit
i don't currently have access to an OSX system. could somebody confirm that this is actually a problem in the current "master"?
https://www.bountysource.com/issues/52336294-make-filmds-consistent
we have a kind of working plugin here (afaik), so it should be less work than "native film reading on OSX", but probably in the same range as what you setup for "native image reading/writing on OSX"
so : https://www.bountysource.com/issues/4185729-native-film-read ing-on-osx-64bit : 2000$ https://www.bountysource.com/issues/4185679-native-video-cap turing-on-osx-64bit : 1500$ https://www.bountysource.com/issues/6492784-native-image-rea ding-writing-on-osx-64bit : 1000$ https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit : ??? https://www.bountysource.com/issues/52336294-make-filmds-consistent : 1000$
cheers c
gfamdsr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
On 12/05/2017 10:58 PM, Antoine Rousseau wrote:
Can porres, ant1r and kim do the same?
Of course I will do whatever you think it has to, but I don't understand,
i'm not sure that *i* understand what you mean by this.
as IOhannes said:
you cannot fix any filmDS issues if you don't have a working W32 build
the point is, that i see little merit in handing out money to create a working W32 build now, when some things are still in flux.
i had the "working mingw build" and "working msvc build" issues tagged as "release critical" because this is what we need *at the end*. but they are not "goals per se" (they are also rather low hanging fruits).
gfasmdr IOhannes
I will do whatever you think it has to
sorry, I meant "I will do what you think I should do"
OK I understand better... I'll ask bountysource to redirect my bounty to "make-filmds-consistent".
Antoine Rousseau http://www.metalu.net http://metalu.net __ http://www.metaluachahuter.com/ http://www.metaluachahuter.com/compagnies/al1-ant1/
2017-12-06 0:08 GMT+01:00 IOhannes m zmölnig zmoelnig@iem.at:
On 12/05/2017 10:58 PM, Antoine Rousseau wrote:
Can porres, ant1r and kim do the same?
Of course I will do whatever you think it has to, but I don't understand,
i'm not sure that *i* understand what you mean by this.
as IOhannes said:
you cannot fix any filmDS issues if you don't have a working W32 build
the point is, that i see little merit in handing out money to create a working W32 build now, when some things are still in flux.
i had the "working mingw build" and "working msvc build" issues tagged as "release critical" because this is what we need *at the end*. but they are not "goals per se" (they are also rather low hanging fruits).
gfasmdr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Le 05/12/2017 à 18:56, IOhannes m zmölnig a écrit :
i don't currently have access to an OSX system. could somebody confirm that this is actually a problem in the current "master"?
It's important to have this information : we will not fund a bounty to debug a bug-free code.
I also don't have any osX computer, could anyone else test this soon? thanks Cyrille
hi all,
I'll try to build the current master from scratch and see if there what happen + a
-- do it yourself http://antoine.villeret.free.fr
2017-12-06 16:27 GMT+01:00 cyrille henry ch@chnry.net:
Le 05/12/2017 à 18:56, IOhannes m zmölnig a écrit :
i don't currently have access to an OSX system.
could somebody confirm that this is actually a problem in the current "master"?
It's important to have this information : we will not fund a bounty to
debug a bug-free code.
I also don't have any osX computer, could anyone else test this soon? thanks Cyrille
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
So it seems to be fine with current git.
Detailed report on the github issue.
Let me know if you need more test.
Cheers
Antoine
-- do it yourself http://antoine.villeret.free.fr
2017-12-06 18:17 GMT+01:00 Antoine Villeret antoine.villeret@gmail.com:
hi all,
I'll try to build the current master from scratch and see if there what happen
a
-- do it yourself http://antoine.villeret.free.fr
2017-12-06 16:27 GMT+01:00 cyrille henry ch@chnry.net:
Le 05/12/2017 à 18:56, IOhannes m zmölnig a écrit :
i don't currently have access to an OSX system.
could somebody confirm that this is actually a problem in the current "master"?
It's important to have this information : we will not fund a bounty to
debug a bug-free code.
I also don't have any osX computer, could anyone else test this soon? thanks Cyrille
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Since the "any.h brocken" issue have been closed, we have "only" this bounty left.
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit : 2000$ https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64... : 1500$ https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-... : 1000$ https://www.bountysource.com/issues/52336294-make-filmds-consistent : 1000$
if that's ok , i'll try to write a mail soon to announce this bountys.
Le 06/12/2017 à 22:46, Antoine Villeret a écrit :
So it seems to be fine with current git.
Detailed report on the github issue.
Let me know if you need more test.
Cheers
Antoine
-- do it yourself http://antoine.villeret.free.fr
2017-12-06 18:17 GMT+01:00 Antoine Villeret <antoine.villeret@gmail.com mailto:antoine.villeret@gmail.com>:
hi all, I'll try to build the current master from scratch and see if there what happen + a -- do it yourself http://antoine.villeret.free.fr <http://antoine.villeret.free.fr> 2017-12-06 16:27 GMT+01:00 cyrille henry <ch@chnry.net <mailto:ch@chnry.net>>: Le 05/12/2017 à 18:56, IOhannes m zmölnig a écrit : i don't currently have access to an OSX system. could somebody confirm that this is actually a problem in the current "master"? It's important to have this information : we will not fund a bounty to debug a bug-free code. I also don't have any osX computer, could anyone else test this soon? thanks Cyrille _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
hello, So, this is a proposition of mail to announce this bounty. fell free to correct it
Dear PD and Gem users, Gem is a Pd library for Pd that allow images and video processing and generation. It depend on OpenGL and various other library to decode images, film, movie etc. Maintaining such code is a lot's of work and this task rely on very few unpaid developers. For example, Gem was based on quicktime that was remove from apple OS few years ago. Gem need a major rewriting in order to work as it used to. It appear that this task is too huge for the current developers, but it's vital for Gem.
So, we are trying to hire developers that could handle this development. In order to finance this work, we put some bounty on specific issue:
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64... https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-... https://www.bountysource.com/issues/52336294-make-filmds-consistent
We believe that reaching 2000$ for the 1st bounty, 1500$ for the 2nd one and 1000$ each for the last 2 should be enough to attract developer.
If this operation is a success, we will try a second round of funding in order to fixes smaller issue and feature request to make Gem even better.
If you are a developer willing to help, you can reach us in the Gem-dev mailing list : https://lists.puredata.info/listinfo/gem-dev
Please forward this announcement to anyone interested in Pd/Gem.
The Gem community
Le 07/12/2017 à 18:44, cyrille henry a écrit :
Since the "any.h brocken" issue have been closed, we have "only" this bounty left.
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit : 2000$ https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64... : 1500$ https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-... : 1000$ https://www.bountysource.com/issues/52336294-make-filmds-consistent : 1000$
if that's ok , i'll try to write a mail soon to announce this bountys.
It could be :
Dear Pd and Gem users,
Gem is a realtime 3D library for Pd that allows, among other things, images and video processing. So, it depends on OpenGL and various other library to decode images, film, movie etc. Unfortunately, few years ago, Apple decided to remove Quicktime from MacOSX leaving a lot of pix_ objects unusable on this OS. Rewrite the code to make things work is a huge task for current developers, they need help. That's why we are trying to hire other developers who would be able to make the use of these pix_ objects on MacOSX (and Windows) possible again.
In order to finance this work, we put some bounty on specific issue:
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64... https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-... https://www.bountysource.com/issues/52336294-make-filmds-consistent
We believe that reaching 2000$ for the 1st bounty, 1500$ for the 2nd one and 1000$ each for the last 2 should be enough to attract developers.
If this operation is a success, we will try a second round of funding in order to fixes smaller issue and feature request to make Gem even better.
If you are a developer willing to help, you can reach us in the Gem-dev mailing list : https://lists.puredata.info/listinfo/gem-dev
Please forward this announcement to anyone interested in Pd/Gem.
The Gem community
++
Jack
Le 12/12/2017 à 15:53, cyrille henry a écrit :
hello, So, this is a proposition of mail to announce this bounty. fell free to correct it
Dear PD and Gem users, Gem is a Pd library for Pd that allow images and video processing and generation. It depend on OpenGL and various other library to decode images, film, movie etc. Maintaining such code is a lot's of work and this task rely on very few unpaid developers. For example, Gem was based on quicktime that was remove from apple OS few years ago. Gem need a major rewriting in order to work as it used to. It appear that this task is too huge for the current developers, but it's vital for Gem.
So, we are trying to hire developers that could handle this development. In order to finance this work, we put some bounty on specific issue:
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit
https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64...
https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-...
https://www.bountysource.com/issues/52336294-make-filmds-consistent
We believe that reaching 2000$ for the 1st bounty, 1500$ for the 2nd one and 1000$ each for the last 2 should be enough to attract developer.
If this operation is a success, we will try a second round of funding in order to fixes smaller issue and feature request to make Gem even better.
If you are a developer willing to help, you can reach us in the Gem-dev mailing list : https://lists.puredata.info/listinfo/gem-dev
Please forward this announcement to anyone interested in Pd/Gem.
The Gem community
Le 07/12/2017 à 18:44, cyrille henry a écrit :
Since the "any.h brocken" issue have been closed, we have "only" this bounty left.
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit : 2000$ https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64... : 1500$ https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-... : 1000$ https://www.bountysource.com/issues/52336294-make-filmds-consistent : 1000$
if that's ok , i'll try to write a mail soon to announce this bountys.
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
On 12/12/2017 09:12 PM, Jack wrote:
It could be :
[...]
before we are going to start sending multiple versions of the text to and fro, with nobody keeping track of what changes when, I've put up the prelaminary test onto an etherpad:
https://etherpad.servus.at/p/atoUItMxvV
pleas improve the text at will. it would also be great if some native speaker could read that through.
fgmdsar IOhannes
multiple versions of the text to and fro, with nobody keeping track of what changes when
sooooo.... where is this at? once agreed upon we can make announcement, assuming we are still going forward to fund.
On Fri, Dec 15, 2017 at 5:14 AM, IOhannes m zmölnig zmoelnig@iem.at wrote:
On 12/12/2017 09:12 PM, Jack wrote:
It could be :
[...]
before we are going to start sending multiple versions of the text to and fro, with nobody keeping track of what changes when, I've put up the prelaminary test onto an etherpad:
https://etherpad.servus.at/p/atoUItMxvVpleas improve the text at will. it would also be great if some native speaker could read that through.
fgmdsar IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Hello, sorry for being unresponsive,
The text have been edited multiple time, so I guess it is ok now.
but I have a concern about bounty source: I send them a mail about reallocating a bounty I initially post on a deprecated issue. I had no answer and the bounty is still on it's original place. https://www.bountysource.com/issues/3383537-w32-build-msvc
I also initially post a bounty on an issue that have been closed : https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit and I can't reallocate the bounty I put there.
But, few weeks ago, CanYa.io acquires Bountysource.com It appear that the website should be changed soon. So I think we should wait a bit to see it the new bountysource website will allow to do what I want. But that's just my opinion...
cheers C
Le 15/12/2017 à 11:14, IOhannes m zmölnig a écrit :
On 12/12/2017 09:12 PM, Jack wrote:
It could be :
[...]
before we are going to start sending multiple versions of the text to and fro, with nobody keeping track of what changes when, I've put up the prelaminary test onto an etherpad:
https://etherpad.servus.at/p/atoUItMxvVpleas improve the text at will. it would also be great if some native speaker could read that through.
fgmdsar IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
the bounty is still on it's original place
hey I saw that, but strangely, mine has been reallocated. I sent on 6/12 to support@bountysource.com:
subject: reallocate please Hi bountysource people,
could you reallocate my bounty, from: https://www.bountysource.com/issues/3383537-w32-build-msvc
to: https://www.bountysource.com/issues/52336294-make-filmds-consistent
https://www.bountysource.com/issues/52336294-make-filmds-consistent
and received on 10/12: Done! Take care, -- David Rappo
2018-01-05 18:21 GMT+01:00 cyrille henry ch@chnry.net:
Hello, sorry for being unresponsive,
The text have been edited multiple time, so I guess it is ok now.
but I have a concern about bounty source: I send them a mail about reallocating a bounty I initially post on a deprecated issue. I had no answer and the bounty is still on it's original place. https://www.bountysource.com/issues/3383537-w32-build-msvc
I also initially post a bounty on an issue that have been closed : https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit and I can't reallocate the bounty I put there.
But, few weeks ago, CanYa.io acquires Bountysource.com It appear that the website should be changed soon. So I think we should wait a bit to see it the new bountysource website will allow to do what I want. But that's just my opinion...
cheers C
Le 15/12/2017 à 11:14, IOhannes m zmölnig a écrit :
On 12/12/2017 09:12 PM, Jack wrote:
It could be :
[...]
before we are going to start sending multiple versions of the text to and fro, with nobody keeping track of what changes when, I've put up the prelaminary test onto an etherpad:
https://etherpad.servus.at/p/atoUItMxvVpleas improve the text at will. it would also be great if some native speaker could read that through.
fgmdsar IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
so did this one get fixed? looks like someone can claim bounty: https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit
right?
It appear that the website should be changed soon.
i mean how much? should we still try to promote and get $$$ for issues?
dan has been doing a bunch of work on the filmAVF stuff... maybe he should just claim any-h-broken one just to see how it all works out. (is it even really fixed? was there an issue?)
anyway... new year. lets keep pushing forward
cheers m
On Fri, Jan 5, 2018 at 4:34 PM, Antoine Rousseau antoine@metalu.net wrote:
the bounty is still on it's original place
hey I saw that, but strangely, mine has been reallocated. I sent on 6/12 to support@bountysource.com:
subject: reallocate please Hi bountysource people,
could you reallocate my bounty, from: https://www.bountysource.com/issues/3383537-w32-build-msvc
to: https://www.bountysource.com/issues/52336294-make-filmds-consistent
https://www.bountysource.com/issues/52336294-make-filmds-consistent
and received on 10/12: Done! Take care, -- David Rappo
2018-01-05 18:21 GMT+01:00 cyrille henry ch@chnry.net:
Hello, sorry for being unresponsive,
The text have been edited multiple time, so I guess it is ok now.
but I have a concern about bounty source: I send them a mail about reallocating a bounty I initially post on a deprecated issue. I had no answer and the bounty is still on it's original place. https://www.bountysource.com/issues/3383537-w32-build-msvc
I also initially post a bounty on an issue that have been closed : https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit and I can't reallocate the bounty I put there.
But, few weeks ago, CanYa.io acquires Bountysource.com It appear that the website should be changed soon. So I think we should wait a bit to see it the new bountysource website will allow to do what I want. But that's just my opinion...
cheers C
Le 15/12/2017 à 11:14, IOhannes m zmölnig a écrit :
On 12/12/2017 09:12 PM, Jack wrote:
It could be :
[...]
before we are going to start sending multiple versions of the text to and fro, with nobody keeping track of what changes when, I've put up the prelaminary test onto an etherpad:
https://etherpad.servus.at/p/atoUItMxvVpleas improve the text at will. it would also be great if some native speaker could read that through.
fgmdsar IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Hey, what's up? I was waiting to see an advertisement of this GEM fund raising thing on facebook, the Pd list and stuff... what's holding it back now?
I also just sent an email asking to reallocate my bounty the same way as Antoine Rousseau, let's see, are we really having issues reallocating it?
cheers
2018-01-20 16:21 GMT-02:00 me.grimm megrimm@gmail.com:
so did this one get fixed? looks like someone can claim bounty: https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit
right?
It appear that the website should be changed soon.
i mean how much? should we still try to promote and get $$$ for issues?
dan has been doing a bunch of work on the filmAVF stuff... maybe he should just claim any-h-broken one just to see how it all works out. (is it even really fixed? was there an issue?)
anyway... new year. lets keep pushing forward
cheers m
On Fri, Jan 5, 2018 at 4:34 PM, Antoine Rousseau antoine@metalu.net wrote:
the bounty is still on it's original place
hey I saw that, but strangely, mine has been reallocated. I sent on 6/12 to support@bountysource.com:
subject: reallocate please Hi bountysource people,
could you reallocate my bounty, from: https://www.bountysource.com/issues/3383537-w32-build-msvc
to: https://www.bountysource.com/issues/52336294-make-filmds-consistent
https://www.bountysource.com/issues/52336294-make-filmds-consistent
and received on 10/12: Done! Take care, -- David Rappo
2018-01-05 18:21 GMT+01:00 cyrille henry ch@chnry.net:
Hello, sorry for being unresponsive,
The text have been edited multiple time, so I guess it is ok now.
but I have a concern about bounty source: I send them a mail about reallocating a bounty I initially post on a deprecated issue. I had no answer and the bounty is still on it's original place. https://www.bountysource.com/issues/3383537-w32-build-msvc
I also initially post a bounty on an issue that have been closed : https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit and I can't reallocate the bounty I put there.
But, few weeks ago, CanYa.io acquires Bountysource.com It appear that the website should be changed soon. So I think we should wait a bit to see it the new bountysource website will allow to do what I want. But that's just my opinion...
cheers C
Le 15/12/2017 à 11:14, IOhannes m zmölnig a écrit :
On 12/12/2017 09:12 PM, Jack wrote:
It could be :
[...]
before we are going to start sending multiple versions of the text to and fro, with nobody keeping track of what changes when, I've put up the prelaminary test onto an etherpad:
https://etherpad.servus.at/p/atoUItMxvVpleas improve the text at will. it would also be great if some native speaker could read that through.
fgmdsar IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
hello,
Le 20/01/2018 à 19:21, me.grimm a écrit :
so did this one get fixed? looks like someone can claim bounty: https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit
right?
according to the discussion on the page you send, Antoine test and noticed that it was working, so Iohannes closed the bug. Nothing have been implemented and nobody will claim the bounty.
It appear that the website should be changed soon.
i mean how much? should we still try to promote and get $$$ for issues?
I have no idea. I want to go forward, but we need to do things right. And I'm not 100% sure that it's the good time with bountysource. what do other think?
dan has been doing a bunch of work on the filmAVF stuff... maybe he should just claim any-h-broken one just to see how it all works out. (is it even really fixed? was there an issue?)
that's a good idea.
cheers c
anyway... new year. lets keep pushing forward
cheers m
On Fri, Jan 5, 2018 at 4:34 PM, Antoine Rousseau <antoine@metalu.net mailto:antoine@metalu.net> wrote:
the bounty is still on it's original place hey I saw that, but strangely, mine has been reallocated. I sent on 6/12 to support@bountysource.com <mailto:support@bountysource.com>: subject: reallocate please Hi bountysource people, could you reallocate my bounty, from: https://www.bountysource.com/issues/3383537-w32-build-msvc <https://www.bountysource.com/issues/3383537-w32-build-msvc> to: https://www.bountysource.com/issues/52336294-make-filmds-consistent <https://www.bountysource.com/issues/52336294-make-filmds-consistent> <https://www.bountysource.com/issues/52336294-make-filmds-consistent> and received on 10/12: Done! Take care, -- David Rappo 2018-01-05 18:21 GMT+01:00 cyrille henry <ch@chnry.net <mailto:ch@chnry.net>>: Hello, sorry for being unresponsive, The text have been edited multiple time, so I guess it is ok now. but I have a concern about bounty source: I send them a mail about reallocating a bounty I initially post on a deprecated issue. I had no answer and the bounty is still on it's original place. https://www.bountysource.com/issues/3383537-w32-build-msvc <https://www.bountysource.com/issues/3383537-w32-build-msvc> I also initially post a bounty on an issue that have been closed : https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit <https://www.bountysource.com/issues/3303967-any-h-broken-on-osx-64bit> and I can't reallocate the bounty I put there. But, few weeks ago, CanYa.io acquires Bountysource.com It appear that the website should be changed soon. So I think we should wait a bit to see it the new bountysource website will allow to do what I want. But that's just my opinion... cheers C Le 15/12/2017 à 11:14, IOhannes m zmölnig a écrit : On 12/12/2017 09:12 PM, Jack wrote: It could be : [...] before we are going to start sending multiple versions of the text to and fro, with nobody keeping track of what changes when, I've put up the prelaminary test onto an etherpad: https://etherpad.servus.at/p/atoUItMxvV <https://etherpad.servus.at/p/atoUItMxvV> pleas improve the text at will. it would also be great if some native speaker could read that through. fgmdsar IOhannes _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
2018-01-23 17:16 GMT-02:00 cyrille henry ch@chnry.net:
I want to go forward, but we need to do things right. And I'm not 100% sure that it's the good time with bountysource. what do other think?
Why not go forward? I think this should move on ASAP. I'd like to see my money being used for and part of something :)
By the way, my bounty has been rellocated https://www.bountysource.com/issues/52336294-make-filmds-consistent
cheers
Le 29/01/2018 à 16:55, Alexandre Torres Porres a écrit :
2018-01-23 17:16 GMT-02:00 cyrille henry <ch@chnry.net mailto:ch@chnry.net>:
I want to go forward, but we need to do things right. And I'm not 100% sure that it's the good time with bountysource. what do other think?Why not go forward? I think this should move on ASAP. I'd like to see my money being used for and part of something :)
apart from the bounty source problem, I currently don't have lot's of time to spend for pd/Gem. (I fall into a huge project) If you fell it's ok, you can go forward without me!
cheers c
By the way, my bounty has been rellocated https://www.bountysource.com/issues/52336294-make-filmds-consistent
cheers
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Le 30/11/2017 à 19:16, William Huston a écrit :
Hi,
I am an admin of the Pd Facebook group.
People have been asking for a sticky-post announcing this funding for GEM development. A poll confirmed this was overwhelming supported.
i'm very glad of this support.
Can someone give me a SINGLE link which is best for the entire project? It should have some narrative about WHO is running the project and WHAT it is, and HOW people can contribute funds.
I'll do that when ready. thanks for your patience (last release is 6 years old, we can wait 1 or 2 more weeks)
Also, is there a way people can contribute funds to the entire project, and not towards fixing specific bugs? (I am unfamiliar with this funding model).
we all are : it's not the way free software usually work.
cheers c
I want to satisfy the request for a sticky post, but I'm not sure how to proceed.
Thanks, BH
-- William Huston: WilliamAHuston@gmail.com mailto:WilliamAHuston@gmail.com Binghamton NY
Public Service Mapping / Videography / Research WilliamAHuston.blogspot.com http://WilliamAHuston.blogspot.com
On Thu, Nov 30, 2017 at 12:40 PM, me.grimm <megrimm@gmail.com mailto:megrimm@gmail.com> wrote:
>> I'm aware that thing moves slowly, but at least they are moving! agree!!!! >> So, don't worry about the money already in the bounty system : it will not be useless. so.... do we then keep lobbying for bountysouce funding? again, we could have this pinned on the facebook group (12k subscribers) which could generate greater donations. m On Thu, Nov 30, 2017 at 9:29 AM, cyrille henry <ch@chnry.net <mailto:ch@chnry.net>> wrote: hello, sorry for being unresponsive. I don't have lot's of free time. All money put on a bounty can be moved to an other bug, and there are lot's of bugs to fix : https://www.bountysource.com/trackers/1046360-umlaeute-gem <https://www.bountysource.com/trackers/1046360-umlaeute-gem> So, don't worry about the money already in the bounty system : it will not be useless. I put money on the 4 issues that prevent a new release. But I talk to Iohannes and it appear I may have made some mistake. Iohannes should organize a bit the github issue soon. We may have to moved some founding from 1 issue to an other after that. So, let's wait that Iohannes spend few time on github before we announce this bounty to a bigger audience. About New Blanket, I fail to find a good way to go, since I already start the bounty system, and that I don't have enough free time. But having this new release in only a 1st steep : there is lot's of other bugs and feature request that are waiting for to long. So, next time, with a better organization, we will find a way to have NB help us on the founding. I'm aware that thing moves slowly, but at least they are moving! cheers Cyrille Le 30/11/2017 à 02:54, Alexandre Torres Porres a écrit : Hi, so, what's up? we already have 385$ thrown at bountysource, ditching it would mean throwing about 40$ in the thrash, plus taxes to paypal... it'd be weird and silly, not to mention a disrespect to some who felt like they wanted to help (I, for one, would feel like that and regretful I helped). Any word or idea on what's going on there? I guess multiple sources could be a good way to go if you feel there's also a better parallel option, but please don't just do this without consulting people who have already pledged money, and while this is still out there in the air and others could give yet more money to it. cheers 2017-11-26 0:03 GMT-02:00 Antonio Roberts <antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> <mailto:antonio@hellocatfood.com <mailto:antonio@hellocatfood.com>>>: > and also what might prevent multiple funding sources? Depending on how the money is being used maybe that wouldn't be a bad thing. Using this Patreon as an example https://www.patreon.com/pippin the funding is to support the developer, not necessarily the GIMP software (even though the aforementioned person is a major developer of GIMP). So, if we look at bountysource/this funding drive as a way to fund developers rather than the software (semantics, i know!) does that get over these potential issues? On 25 November 2017 at 19:49, me.grimm <megrimm@gmail.com <mailto:megrimm@gmail.com> <mailto:megrimm@gmail.com <mailto:megrimm@gmail.com>>> wrote: >>> And if that's not it, what prevents anyone from sharing this campaign on >>> facebook, the pd list and whatever? > > and also what might prevent multiple funding sources? > > > > On Sat, Nov 25, 2017 at 9:32 AM, Alexandre Torres Porres <porres@gmail.com <mailto:porres@gmail.com> <mailto:porres@gmail.com <mailto:porres@gmail.com>>> > wrote: >> >> >> >> 2017-11-23 7:14 GMT-02:00 cyrille henry <ch@chnry.net <mailto:ch@chnry.net> <mailto:ch@chnry.net <mailto:ch@chnry.net>>>: >>> >>> hello, >>> I'm in discussion with joe deken from newblankets around an other/better >>> way to deal with donation. >>> So maybe we should wait a bit before making a wider announce of this >>> bounty. >> >> >> Hi, can you give us some more information about it? I don't understand >> what you mean. >> >> Do you mean you will change the donation system from "bountysource.com <http://bountysource.com> <http://bountysource.com>"? I >> don't think so, cause, well, people already gave money to that... (me, for >> instance, gave 30$). But if that's the case, how do we deal with that (like, >> how to get the money back)? >> >> And if that's not it, what prevents anyone from sharing this campaign on >> facebook, the pd list and whatever? >> >> cheers >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> >> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> >> > > > > -- > ____________________ > m.e.grimm, m.f.a, ed.m. > syracuse u., tc3 > megrimm.net <http://megrimm.net> <http://megrimm.net> > ____________________ > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> > https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> > -- ============================ antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> <mailto:antonio@hellocatfood.com <mailto:antonio@hellocatfood.com>> http://www.hellocatfood.com ============================ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> -- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net <http://megrimm.net> ____________________ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Le 30/11/2017 à 18:40, me.grimm a écrit :
I'm aware that thing moves slowly, but at least they are moving!
agree!!!!
So, don't worry about the money already in the bounty system : it will not be useless.
so.... do we then keep lobbying for bountysouce funding? again, we could have this pinned on the facebook group (12k subscribers) which could generate greater donations.
please, wait a bit, Iohannes will reorganize git issue and we may have to change where to put money. I'll make an announcement when everything will be ready.
cheers c
m
On Thu, Nov 30, 2017 at 9:29 AM, cyrille henry <ch@chnry.net mailto:ch@chnry.net> wrote:
hello, sorry for being unresponsive. I don't have lot's of free time. All money put on a bounty can be moved to an other bug, and there are lot's of bugs to fix : https://www.bountysource.com/trackers/1046360-umlaeute-gem <https://www.bountysource.com/trackers/1046360-umlaeute-gem> So, don't worry about the money already in the bounty system : it will not be useless. I put money on the 4 issues that prevent a new release. But I talk to Iohannes and it appear I may have made some mistake. Iohannes should organize a bit the github issue soon. We may have to moved some founding from 1 issue to an other after that. So, let's wait that Iohannes spend few time on github before we announce this bounty to a bigger audience. About New Blanket, I fail to find a good way to go, since I already start the bounty system, and that I don't have enough free time. But having this new release in only a 1st steep : there is lot's of other bugs and feature request that are waiting for to long. So, next time, with a better organization, we will find a way to have NB help us on the founding. I'm aware that thing moves slowly, but at least they are moving! cheers Cyrille Le 30/11/2017 à 02:54, Alexandre Torres Porres a écrit : Hi, so, what's up? we already have 385$ thrown at bountysource, ditching it would mean throwing about 40$ in the thrash, plus taxes to paypal... it'd be weird and silly, not to mention a disrespect to some who felt like they wanted to help (I, for one, would feel like that and regretful I helped). Any word or idea on what's going on there? I guess multiple sources could be a good way to go if you feel there's also a better parallel option, but please don't just do this without consulting people who have already pledged money, and while this is still out there in the air and others could give yet more money to it. cheers 2017-11-26 0:03 GMT-02:00 Antonio Roberts <antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> <mailto:antonio@hellocatfood.com <mailto:antonio@hellocatfood.com>>>: > and also what might prevent multiple funding sources? Depending on how the money is being used maybe that wouldn't be a bad thing. Using this Patreon as an example https://www.patreon.com/pippin the funding is to support the developer, not necessarily the GIMP software (even though the aforementioned person is a major developer of GIMP). So, if we look at bountysource/this funding drive as a way to fund developers rather than the software (semantics, i know!) does that get over these potential issues? On 25 November 2017 at 19:49, me.grimm <megrimm@gmail.com <mailto:megrimm@gmail.com> <mailto:megrimm@gmail.com <mailto:megrimm@gmail.com>>> wrote: >>> And if that's not it, what prevents anyone from sharing this campaign on >>> facebook, the pd list and whatever? > > and also what might prevent multiple funding sources? > > > > On Sat, Nov 25, 2017 at 9:32 AM, Alexandre Torres Porres <porres@gmail.com <mailto:porres@gmail.com> <mailto:porres@gmail.com <mailto:porres@gmail.com>>> > wrote: >> >> >> >> 2017-11-23 7:14 GMT-02:00 cyrille henry <ch@chnry.net <mailto:ch@chnry.net> <mailto:ch@chnry.net <mailto:ch@chnry.net>>>: >>> >>> hello, >>> I'm in discussion with joe deken from newblankets around an other/better >>> way to deal with donation. >>> So maybe we should wait a bit before making a wider announce of this >>> bounty. >> >> >> Hi, can you give us some more information about it? I don't understand >> what you mean. >> >> Do you mean you will change the donation system from "bountysource.com <http://bountysource.com> <http://bountysource.com>"? I >> don't think so, cause, well, people already gave money to that... (me, for >> instance, gave 30$). But if that's the case, how do we deal with that (like, >> how to get the money back)? >> >> And if that's not it, what prevents anyone from sharing this campaign on >> facebook, the pd list and whatever? >> >> cheers >> >> _______________________________________________ >> GEM-dev mailing list >> GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> >> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> >> > > > > -- > ____________________ > m.e.grimm, m.f.a, ed.m. > syracuse u., tc3 > megrimm.net <http://megrimm.net> <http://megrimm.net> > ____________________ > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> > https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> > -- ============================ antonio@hellocatfood.com <mailto:antonio@hellocatfood.com> <mailto:antonio@hellocatfood.com <mailto:antonio@hellocatfood.com>> http://www.hellocatfood.com ============================ _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> <mailto:GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at>> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> <https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev> _______________________________________________ GEM-dev mailing list GEM-dev@lists.iem.at <mailto:GEM-dev@lists.iem.at> https://lists.puredata.info/listinfo/gem-dev <https://lists.puredata.info/listinfo/gem-dev>-- ____________________ m.e.grimm, m.f.a, ed.m. syracuse u., tc3 megrimm.net http://megrimm.net ____________________
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Le 20/11/2017 à 16:58, Jack a écrit :
Or for all platforms ? In vertex processing with have :
- vertex shader
- geometry shader
What about tesselation shader ?
can you please add all freature request on Gem github? thx
I use Gem a lot so i will be happy to participate financially if that can help to add functionality to it. ++
Jack
Le 20/11/2017 à 12:27, Max a écrit :
What about something for linux? Generally support a new release?
On 2017년 11월 17일 18:07, cyrille henry wrote:
it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation.
So, I went with bounty source. I create 4 bounty:
https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64...
https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit
https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-...
They correspond to the 4 most important bug I found on the gitub bugtracker.
It's time to find money!
Le 15/11/2017 à 18:05, cyrille henry a écrit :
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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@lists.iem.at >> https://lists.puredata.info/listinfo/gem-dev > > > _______________________________________________ > GEM-dev mailing list > GEM-dev@lists.iem.at > https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
Gem on Linux has no major problem that prevent a release.
Le 20/11/2017 à 12:27, Max a écrit :
What about something for linux? Generally support a new release?
On 2017년 11월 17일 18:07, cyrille henry wrote:
it appear that pledgie is dedicatad to find money for your work, better than financing other work. i.e, if I crete a project, I'll receive the donation.
So, I went with bounty source. I create 4 bounty:
https://www.bountysource.com/issues/3383537-w32-build-msvc https://www.bountysource.com/issues/4185679-native-video-capturing-on-osx-64... https://www.bountysource.com/issues/4185729-native-film-reading-on-osx-64bit https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-...
They correspond to the 4 most important bug I found on the gitub bugtracker.
It's time to find money!
Le 15/11/2017 à 18:05, cyrille henry a écrit :
hello, i'm sorry it took so long, I have lot's of work.
I found 2 platform :
https://pledgie.com/ and : https://www.bountysource.com/
pledgie get 3% of the donation, bountysource get 10%.
unless anyone have a better idea, i'll start to go with pledgie cheers c
Le 30/10/2017 à 17:38, cyrille henry a écrit :
Hello,
I've check Iohannes github: There is not a lot's of release critical issue.
Image, film and video under osX and having a way to compile for window and the main issues.
There is also lot's of stuff regarding FTGL, but they look to be obsolete. At least, we will know if they are obsolete after being able to compile Gem on the concerned platform.
Since Iohannes is currently too buzzy to help, I think we should organize development in 2 parts :
1st : doing the minimum to have Gem usable on all platform. We could then release a v0.94 and use it to test on lot's of computer and reporting all bugs. Then, a 2nd development round could create a 0.94.1 bugfix release with a longer lifetime.
if there is no objection, I will have a look at the platform we could use to centralize financing and stuff. cheers c
Le 12/10/2017 à 10:34, cyrille henry a écrit :
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
- 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)
- 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.
- 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@lists.iem.at > https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
On 2017-11-21 10:15, cyrille henry wrote:
Gem on Linux has no major problem that prevent a release.
can this be confirmed by all the other linux enthusiast?
personally i could think of a number of issues, all related to the new multi-context abilities. however, i'd say that these can be ignored for now, as long as things keep working with a single window.
fgmdasr IOhannes
Le 21/11/2017 à 11:15, IOhannes m zmoelnig a écrit :
On 2017-11-21 10:15, cyrille henry wrote:
Gem on Linux has no major problem that prevent a release.
can this be confirmed by all the other linux enthusiast?
personally i could think of a number of issues, all related to the new multi-context abilities. however, i'd say that these can be ignored for now, as long as things keep working with a single window.
I consider multiple windows to be a work in progress. I personally don't use it, since I can't share a patch that use this feature.
for sure, the next gem release will come with lot's of bug report and feature request...
cheers c
fgmdasr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
On my side, no big trouble to deplore on Linux. ++
Jack
Le 21/11/2017 à 11:15, IOhannes m zmoelnig a écrit :
On 2017-11-21 10:15, cyrille henry wrote:
Gem on Linux has no major problem that prevent a release.
can this be confirmed by all the other linux enthusiast?
personally i could think of a number of issues, all related to the new multi-context abilities. however, i'd say that these can be ignored for now, as long as things keep working with a single window.
fgmdasr IOhannes
GEM-dev mailing list GEM-dev@lists.iem.at https://lists.puredata.info/listinfo/gem-dev
-
Alexandre Torres Porres -
Antoine Rousseau -
Antoine Villeret -
Antonio Roberts -
Chris Clepper -
cyrille henry -
Federico Camara Halac -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Ivica Ico Bukvic -
Jack -
Jaime Oliver La Rosa -
Max -
me.grimm -
Nicolas Montgermont -
sonia yuditskaya -
William Huston