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 ____________________