Futures discussion on github


Someone from the Fritzing fab company (AISLER) has started a discussion on github about the future of Frtizing development. If you have interest, you may want to join in.



Thank you for describing the current situation with Fritzing. I’m curious to know if the proceeds/royalties from sale placed with Fritzing Fab help to support the effort? It was not clear to me from the video.


I’m not connected to any thing official in Fritzing, so this isn’t definitive, but I believe the funding from Ainsler is going in to the development funding pool. You may want to post this in the discussion issue on github as I don’t know if anyone who would know for sure reads the forums anymore. I have heard that the goal for a finished release of Fritzing is $40k euros and the pot is currently at $6K euros (some 4 years on) so I don’t hold much hope of help from that direction. At this point I’m not sure the pool of developers is still even available. If Fritzing is to survive we need to attract people to do development. The offer in the video to partially fund a manager is very encouraging if it can be done, but the problem is still people willing and able to contribute. There has been previous discussion on github about doing a fork (which he referred to in the video). I pointed out that until there is some development effort ongoing and a refusal to accept the commits on the current repository a fork appears pointless. No development activity that I am aware of has occurred after that point (and the fork discussion died out). Currently the development environment is broken, I’m working on a parts commit to correct that, and after that intend to try and get a fix for the libgit2 issue on Windows working and see if I can get it released. One issue there is going to be how to get a release candidate up for testing. The discussion on github may help that if they can get the attention of someone with commit access, or I may be able to get it done via a pull request when and if I have something that looks workable. I expect that is going to be a while though as there are a number of problems of which the parts update is only the first.



Finally some good news on the development front. Thanks to Patrick Franken (CTO at AISLER, the Fritzing fab) it looks like development will restart. See the projected roadmap in this issue on the github repo:

While comments had died out on the original thread (I was thinking it had died, with all talk and no action like all the rest :slight_smile: ), it appears work was going on in the background. Hopefully Fritzing will live and prosper.



For what it is worth, I wrote a version of my parts editor in C++/Qt5. Available on github: https://github.com/RobertPHeller/FritzingPartsSVGEditor-QT5. This is basically a port of my Tcl/Tk parts editor (https://github.com/RobertPHeller/FritzingPartsSVGEditor). I’m thinking it could possibly be integrated into Fritzing or could exist standalone. If anyone has questions about it, they should feel free to E-Mail me. heller@deepsoft.com


I don’t think any of the development team is reading the forum. Your best bet would be to open an issue in Fritzing-app on github I expect. As far as I know the current plan is to rewrite the parts editor in javascript whether that stays in javascript or is ported to c++ and Qt I don’t know, I don’t think they are as far as a working prototype at present. I tried the original javascript stuff when it came out a year or two ago and couldn’t make it work and decided to leave it to folks that know javascript. Too steep a learning curve for me to be useful.