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