On Thu, Dec 1, 2016 at 10:42 PM, Dominik Aumayr <domi...@aumayr.name> wrote:
> > - 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 > > We could create a separate repository under https://github.com/beancount > for plugins from the community. > +1 > > - Dominik > > > > Am 02.12.2016 um 09:03 schrieb Stefano Zacchiroli <z...@upsilon.cc>: > > > > 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) > Best to start this way IMHO. See http://furius.ca/beancount/doc/contrib Publish it and I'll add a link there. This does seem like something that could go into the main source code eventually. > - 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 > The main difference there is testing. My experience with various OSS projects is that many people who share things often provide an insufficient amount of testing, and invariably, adding good test coverage leads to much more work afterwards - you always discover flaws with tests. If you build good test coverage it makes it much, much easier to integrate a submission. Beancount has great support for building tests using Beancount syntax in docstrings; see the source code itself for examples. > - 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 > I kind-of tried that with Ledgerhub - for sharing importers, I thought this would be popular, alas, so now it's gone - so I think the way it's built now it's very flexible (anything in your pythonpath) and I prefer to keep a hands-off approach. I would say, start by building plugins which are useful to you in a separate repo. Share them if you like. I like the idea of putting things under github.com/beancount/*, that's why it's there. Maybe in the future banding together with others to make a consolidated repo of plugins might be a good idea, if there's a theme. If some of those provide broadly useful functionality and have good test coverage, I'd be happy to fold them into the main source code. In general, I like the idea of letting the dust settle a bit and get a fair amount of real usage before doing that. > > > > Do you have any preference? > Thanks for asking. > > > > Cheers > > -- > > Stefano Zacchiroli . z...@upsilon.cc . 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 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/20161202080355.5rfm4c32wlenwiqa%40upsilon.cc. > > For more options, visit https://groups.google.com/d/optout. > > -- > 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/39D793D4-11BF-4FDB-9C92-BF4047A91FF3%40aumayr.name. > For more options, visit https://groups.google.com/d/optout. > -- 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/CAK21%2BhP4VoFJkB7tXFQRW5ZxA8qU%3DE60fsU8HSqsBOJ7%2BXg%3DcQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
