should we open source our homebrew web based markdown file tree editor (with image support and soon, ics calendar editor)? or would it be a distraction and people are happy with the other solutions out there?
should we open source our homebrew web based markdown file tree editor (with image support and soon, ics calendar editor)? or would it be a distraction and people are happy with the other solutions out there?
@mntmn Yes! Any chance it has git integration? Like when you edit it becomes a commit?
@Tomhodson yes, but this is currently done with an autogit script that runs every 5 minutes, so not cleanly integrated yet. it is useful to recover from mistakes though.
@mntmn I prefer open source. People can choose what they prefer if they have a choice
@mntmn On MNT gitlab, sure, but not anywhere else where it's liable to be a maintenance burden.
My honest opinion is that you should expect to see some value *back* if you're going to do this.
@mntmn
Open source code is always nice even if it's not packaged into a user-friendly product, but it would be more interesting to understand why you went with homebrew over existing solutions?