[GEM-dev] financing Gem development

[Jack]

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-64bit
https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit
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-64bit
> 
> https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit
> 
> 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-64bit
>> : 1500$
>> https://www.bountysource.com/issues/6492784-native-image-reading-writing-on-osx-64bit
>> : 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 at lists.iem.at
> https://lists.puredata.info/listinfo/gem-dev