- re. documentation: baking it into reST/Sphinx is going to result in less
up-to-date docs. Years of people contributing fixes have made that clear to
me (I can't write three words without a mistake and years after people were
still submitting typo changes). Maybe though it's a thing whereby during
its development it's sufficient but maintenance is harder? I doubt it'll
solve a problem. The right person to say something with heft about this
would be someone who... wrote a lot of documentation. I really don't like
the resistance to Google Docs for political reasons I've seen in the past
(socialists) and feel quite strongly about kicking back unless it's clearly
made for technical reasons.
<https://groups.google.com/d/msgid/beancount/3ac4293f-66c0-4176-b91b-d4bed6d059dfn%40googlegroups.com?utm_medium=email&utm_source=footer>
Martin,
your documentation for beancount is definately a blueprint for project
documentation.
But for *beanquery*, can we then at least spin off the new version of a
document from the current one,
<https://docs.google.com/document/d/1s0GOZMcrKKCLlP29MD7kHO4L88evrwWdIO0p4EwRBE0/edit#heading=h.7aru55j2c7dz>
the new version shall be applicable for a new standalone version of
*beanquery*
And then probably a policy can be introduce to always update a document in
a draft mode, when submitting a pull request?
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/beancount/35ab2f6f-4720-4433-99cb-7a65c041e65bn%40googlegroups.com.
