Transparency

The release of fman's first closed alpha is taking longer than hoped, but that is not to say that there has been no progress. Since the last post, fman has successfully been ported to Windows and Linux from OS X. The only tasks that remain before the closed alpha can be released are to implement an auto-update functionality (so you can get bug fixes / improvements instantly) and to package fman for the various operating systems. The latter involves codesigning the distributables so your OS recognises them as safe and doesn't show warnings "This software is not trusted". Codesigning and auto-updating in conjunction are unfortunately a bit painful. But we'll get there!

In the meantime, there has been a small update to the web site. On the home page you can now see the latest surce code commits made to fman!

Latest commits
  • Update post-commit script to show latest commit on fman.io

    mherrmann committed on Jul 01, 2016

  • Fix a typo in Info.plist file.

    mherrmann committed on Jun 29, 2016

This gives you more insight into fman's development (and in particular, how actively it is being developed). What's more, it enables:

fman's Open Source Promise

Some users of Sublime Text have complained that if its creator ever stopped working on it, they would be stuck in an ecosystem that is no longer being maintained. fman makes the following promise to address this issue:

If no commit is made to fman in more than 6 months, then it will be open sourced under a BSD license.

When you obtain a license, this means that if development on fman ever stops, you will be free to extend and keep using it. If you also have a subscription for updates, then the promise means that you either get regular updates or can use fman for free. Finally, if you develop plugins for fman, then the promise guarantees that your work won't become obsolete. (In case I am unable to release the source code, my family knows how to do it.)

Let's hope that the next post will be about the release of fman's closed alpha!