On Mon, Nov 21, 2016 at 06:31:00AM -0800, Simon Michael wrote: > just on the general idea: I think it's a good one! At least in my workflow, > it's surprisingly easy to make this mistake and to lose time tracking it > down during reconciliation. I'm going to start doing a similar check.
Thanks Simon, I'm glad it's useful for your workflow too! Martin: can you please advise on how you want to go about contributed plugins? I see various options, e.g.: - people just publish them independently (or keep them private) - you declare a fairly liberal policy into accepting contributed plugins (similar with what the docs say about additional SQL functions), and all plugins get collected in the main Beancount repo. In this case, I'll be happy to submit file_ordering via an issue on bitbucket - some sort of "beancount forge" emerges, possibly blessed by you, as central place where non-mainline plugins get contributed, with some sanity checking on namespace to avoid naming clashes Do you have any preference? Cheers -- Stefano Zacchiroli . [email protected] . upsilon.cc/zack . . o . . . o . o Computer Science Professor . CTO Software Heritage . . . . . o . . . o o Former Debian Project Leader . OSI Board Director . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club » -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/20161202080355.5rfm4c32wlenwiqa%40upsilon.cc. For more options, visit https://groups.google.com/d/optout.
