* Dominik Aumayr <domi...@aumayr.name> [2018-03-24 11:10]: > As for the code, moving to git (and github.com/beancount/beancount? > We already "own" that org) would further lower the barriers to > help/contribute for many more people. Please (you, dear reader) do > not take this as a starting-point for another lengthy discussion > about this. I just want to friendly remind you, Martin, what > possible ways of lowering the amount of work beancount takes up > could be.
I was actually going to ask Martin about this in private (in private because I didn't want to start a bike-shedding discussion). I've submitted some minor pull requests and while hg is not too hard if you know git, remembering the right hg commands and signing up for bitbucket is a small barrier that imho could easily be avoided by moving to GitHub. If Martin says no, we should accept that without further discussion. But if it's a maybe or yes, I'd be happy to look into the migration (unless someone has experience with this already). There is a script that can be used to import bitbucket issues into GitHub: https://github.com/jeffwidman/bitbucket-issue-migration/blob/master/migrate.py And the mercurial repo is mirrored already. -- Martin Michlmayr http://www.cyrius.com/ -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To post to this group, send email to beancount@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20180324151416.vmhnrm6j3w6yyy2c%40jirafa.cyrius.com. For more options, visit https://groups.google.com/d/optout.
