Ortho is a python based app that renders orthographic templates from existing 3d models, akin to a ‘blueprint creator’. It’s free and requires only python and a browser. No coding or commands, just run the launcher, then drag and drop your file or zip,then configure in the browser. Runs on PC and Mac, pretty much fool proof.
No more googling for low res watermarked inaccurate paywalled. Templates. Not AI.
This model was conceived in 2010, now more than 10 years ago, and not very long after Git itself came into being. In those 10 years, git-flow (the branching model laid out in this article) has become hugely popular in many a software team to the point where people have started treating it like a standard of sorts — but unfortunately also as a dogma or panacea.
During those 10 years, Git itself has taken the world by a storm, and the most popular type of software that is being developed with Git is shifting more towards web apps — at least in my filter bubble. Web apps are typically continuously delivered, not rolled back, and you don't have to support multiple versions of the software running in the wild.
This is not the class of software that I had in mind when I wrote the blog post 10 years ago. If your team is doing continuous delivery of software, I would suggest to adopt a much simpler workflow (like GitHub flow) instead of trying to shoehorn git-flow into your team.
If, however, you are building software that is explicitly versioned, or if you need to support multiple versions of your software in the wild, then git-flow may still be as good of a fit to your team as it has been to people in the last 10 years. In that case, please read on.
To conclude, always remember that panaceas don't exist. Consider your own context. Don't be hating. Decide for yourself.
A collection of Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
Meshroom is a free, open-source 3D Reconstruction Software based on the AliceVision framework.
This is based on an article I wrote for Make magazine at their request in early 2008. An article based on this content was published in Make Magazine issue 20 in late 2009 - more than a year and a half after I submitted it to them.