On Sat, Jan 28, 2023 at 3:01 AM Stefano Zacchiroli <[email protected]> wrote:
> On Fri, Jan 27, 2023 at 10:19:20PM -0500, Martin Blais wrote: > > I have no opinion on this, happy to move the polarmutex repo into the > > beancount org as well if you want, and it's true you've been at this for > > a long while and very active. > > (Can you choose unique names? Looks like you both choose the very same > repo > > name.) > > FWIW, "official" isn't all that meaningful other than it makes it easier > > for people to find related repos to Beancount, especially things like > > syntax parsers. > > If I may, as a mere user, having a repo located under > github.com/beancount/ is quite meaningful to me, precisely because it's > more prominent than other repos out there (both on github and > elsewhere). It comes with an expectation that the repo implements the > "recommended" Beancount way of doing something for which alternative > implementations exist. I understand you Martin doesn't mean it that way, > but it *will* be interpreted that way by users, especially those who are > not following closely this list. > > Re tree-sitter (which is something I might be interested in using myself > in the future), I'd be better served by having either 0 or exactly 1 > tree sitter grammar implementation available under beancount/ on github. > The ideal way forward here would be for Daniele and polarmutex to work > together into a single project and having that one located at > https://github.com/beancount/tree-sitter-something. > Alright, fair enough. Daniele has pretty strong views about how he likes to do things (and that's okay), so asking these two to collaborate is not something I want to get involved in. And it's true polarmutex has been at this for a VLT (I followed the changes for a while) so doesn't deserve to get eclipsed. I also see no less than FOUR "tree-sitter-beancount" repos on github (once again, amazed, I supposed I'm going to have to get on with the times at some point and check it out too, but it seems the last few years there's bursts of excitement over new parser generators). I think we should - remove the newly created repo to avoid confusion - update the dedicated section for alternative parser in the contribs doc (done) - https://docs.google.com/document/d/1Z37bQ45wDtjTPaMQ_x-f33p1trH9fNosEAUgbQXwp30/edit#heading=h.vdgjwzkgrfcy If you have yet another alternative parser with <insert-fancy-new-parser-generator-here> let me know I'll add to the doc. (I managed to do a little tiny bit of work over advancing the v3 state of the world over the holiday down under, I'll try to send an update soon.) > Just my 0.02 EUR, > Cheers > -- > Stefano Zacchiroli . [email protected] . https://upsilon.cc/zack _. ^ ._ > Full professor of Computer Science o o o \/|V|\/ > Télécom Paris, Polytechnic Institute of Paris o o o </> <\> > Co-founder & CTO Software Heritage o o o o /\|^|/\ > https://twitter.com/zacchiro . https://mastodon.xyz/@zacchiro '" V "' > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/beancount/20230128080135.sldrzkksgrhomzhu%40upsilon.cc > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAK21%2BhOCrcmqxnn00-S-U8k0zmR9TiLgnvbbtRmsytMAVE-eJQ%40mail.gmail.com.
