realthunder wrote: ↑
Fri Oct 05, 2018 10:58 pm
abdullah wrote: ↑
Fri Oct 05, 2018 4:20 pm
He most probably won't forever. Hopefully, he will keep interest until it is merged. Hopefully everything will match in the not so distant future. It is very difficult to maintain a single man band.
I feel the same. Developing FC is taking more and more of my time. It has stretched far beyond of my originally intention. It is hard to start something without finish it, but then it seems never ending, which is not surprising. Maybe I can make a career out of it, looking for some funding on this. Maybe the university I live nearby will be interested...
From a financial point of view, I can perfectly understand you. As far as I know, this kind of collaborations manage to get public funding when there is a ( company + university ) interest, which run together for public funding, but the company also puts money in. This gives credibility to public funding. Other times it is just a private company paying the developer to boost the project development. I do not have a way to secure any of this for you, but maybe somebody is reading and can. I guess the CERN is not interested in funding another public project (they do fund KiCAD).
Regarding just FreeCAD, I can talk about the other side. When it is not only you, but you can leverage community help, it does not feel like the project is eating you up (or your time if you wish). You can manage your time and the rate of contribution, and focus on coding, if that is what you want to do (I understand from what I have seen so far, it is).
Of course it is up to you, and up to the opportunities you find in life (heartedly much luck there), whether to make a career on FC development, or you find another nice job and want to dedicate it part of your free time when your life allows and you want to, or none of the above (hopefully it is not this last one the one you choose).
In any case, splitting resources, community, FreeCAD versions (forks) is a good short-term development tool (short-term it is probably a must when it involves drastic paradigm changes), but it is generally not the best long-term scenario. It is my opinion that not even in the mid-term scenario, as it leads to inefficient use of resources (testing, bug reports, lack of integration, divergence, long PR review times) and an ever increasing risk that work has diverged so much that it is simply thrown down the sink. A one man band can then leverage the whole community by his charm and make a successful fork that becomes The Thing (tm), or silently vanish from the project.
Apart from the loss of work, which is indeed important, there is the human aspect of it. The person who sees its work going down the sink is not specially happy, losses motivation, is less active in the community, and generally is a person that could have been leveraged to the greatness of FC, but may be rendered "unrecoverable" by such events. For me the latter is much worse that the former. From a human point of view, because we are humans and I think we should show some empathy and humanity (you may well point out this is my particular wish, as 4000+ years of "humanity" have shown us we are rather prolific at enslaving and destroying than at showing humanity). But even merely from a pure egoistic productivity point of view, just project development, the potential lost is way higher than the lost work, as a happy high potential individual (like you) can long-term give more to the project than a "medium-term" single shot.
A third aspect that is not good for either part is "uncertainty". We all hate it. Unfortunately managing certainty in a FOSS project is the most difficult thing to do, because none of us knows if tomorrow we will have to work 60 hours a week in our "day job" because something is off, or we will need all our free-time to some other important matter. Here I hope that uncertainty is not driving you to depart from the project before your code is reviewed.
I do not have a magic wand to resolve this on my own, I would if I could.
I know you are smart and have a lot of potential. Your modifications to FreeCAD touch several aspects of it and go to the core of it. You understand what you are doing. Very little individuals have the courage and capabilities to undertake such development. I haven't seen many. For example, I haven't (I am mostly locked in my little Sketcher space, with some incursions into PartDesign). Additional to the size of the undertaking, is that you managed to do it successfully from a functionality point of view (I simply do not judge the underlying code, as I have not reviewed it). You have a nice group of followers of your work and they tend to love it. Moreover, you are not afraid to speak up to other developers, you are not overwhelmed by their abilities and you can defend your position from a technical point of view.
I know that all that is simply just not enough to guarantee a merge, but it makes me believe that you still have great chances to have your code merged, and FreeCAD still has a chance to retain you. I would really love to see v0.18 released and at the very beginning of the v0.19 cycle your work properly reviewed.