* Will Middleton <
wi...@radicalxchange.org> [2019-03-10 06:31]:
> <
https://www.google.com/url?q=https%3A%2F%2Fk.sfconservancy.org%2FNPO-Accounting%2Fnpo-ledger-cli&sa=D&sntz=1&usg=AFQjCNEp2069OybTvmdiQ2z6NN5VNroc7A>
> to the GitHub repository?
I'm not sure this makes sense. The repo contains a guide on how to
use ledger for non-profits, including a proposed tagging mechanism.
It's not something that needs to be part of the ledger repo, though.
> Anyways, I have only recently started maintaining my own code on Github,
> never contributed to a project.
> What is the protocol here?
> Fork the codebase and start working like bkuhn did here
> *tree/next/contrib/non-profit-audit-reports* or start a new repository?
It depends. If it makes sense for your contribution to be part of the
repo, you can fork and send the changes back (via GitHub pull
request). But not everything needs to be part of the repo. If it's
an independent effort, you can just have your own standalone repo.
> I have* attached a deep chart of accounts * *fund_accounts.dat* with
> codes that I created but I am hesitant to start using it as it seems
> a bit verbose
Are the codes made up or do they refer to anything specific? (i.e. are
there pre-defined codes, e.g. defined by the IRS or someone)
> I am not yet too familiar with the MetaData Tagging "tags" but perhaps
> these can be used to show Program Level and/or Grant Related Revenues and
> Expenditures.
Yes, they can. There are two different philosophies: one is to put
such kind of information in the account name itself; the other is to
have a simple chart of account and put the rest into metadata. My
impression is that the professional accounting world prefers a simple
chart of accounts.
If you look at bkuhn's tutorial, you'll see that he uses the Program
tag to specify some meta information.
--
Martin Michlmayr
https://www.cyrius.com/