![]() Nobody ever said “if you dump that CLA, I’ll gladly contribute to Natron”. Has the signing of Contributor License Agreement ever been a problem (that you know of) for potential contributors?įrédéric: I don’t know. In April 2018, I already knew I would have to quit Natron a few months later. My hope was that if there were bounties, this could attract new developers, but it didn’t. Since when I started this in April 2018, no bounty has ever been offered. The fact that Alexandre still owns part of the code was due to an agreement between him and Inria during his first year on Natron.ĭid you try to find other funding sources?įrédéric: Any user can offer a bounty to solve a github issue (using bountysource, there’s a link at the bottom of every issue). Any code he produced was property of Inria, as with the code I produced. What were the conditions of Ole-André’s paid participation?įrédéric: He was paid as an engineer by Inria to work on his contribution to the Natron infrastructure (source code, build and test systems). In Dec 2017, Alexandre Gauthier left the project to start a closed-source commercial graphics software which I know nothing about. Inria still owns most of the Natron code (as it was my employer). Is that so? Why did they stop supporting it?įrédéric: Inria did not stop supporting it, since I kept maintaining Natron until I left Inria in September 2018. I think they paid for the first 12 months, then extended for at least another year. We spoke to both Alexandre and Frédéric about it.ĭevelopment of Natron was at some point paid by Inria. Now that neither original developers works for Inria or wants to continue contributing to this project, the question is: how could it have been prevented and where do we go next? Frédéric subsequently left Inria in September 2018. The personal clashes kicked in, and he left Inria in December 2017. Given that, Alexandre started working alone towards a more solid rendering engine that would become the staple of Natron 3, but says he never had the time to complete it.
0 Comments
Leave a Reply. |