<div dir="ltr">I've created a Git repository on www.<div><br></div><div>1. I created a new 'ledger' account on www.</div><div>2. I initialized a bare git repo.</div><div>3. I put a new public key of mine into authorized_keys.</div><div>4. I added www as origin, and set it to master's upstream on my local clone.</div><div>5. There is a summary.py file that will summarize the CSV file.</div><div><br></div><div>If there's anyone (other than Jim) who would like me to add their public key to the repo, please let me know. I will do so and send you the appropriate git-clone command.</div><div><br></div><div>Cheers!</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 9, 2017 at 12:36 PM, Jim Klassen <span dir="ltr"><<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Ok. CSV or maybe even just markdown. Whatever keeps it simple.<br>
</p><div><div class="h5">
<br>
<div class="m_8145527218991917413moz-cite-prefix">On 12/08/2017 01:47 PM, Dan Little
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">CSV is fine with me as well. That does allow for
easy diffing and use of spreadsheet programs as desired. I will
probably also include a "check balance" Python script for doing
some basic reporting. There are CLI and text based ledger
programs. I really don't want to go deep into a format debate
or over-do the accounting for what really is a simple
money-in-money-out + voting record.
<div><br>
</div>
<div>In terms of backup and redundancy, I will have the repo
cloned locally, which gets backed up regularly, and those who
have interest will also be able to do pulls. The bank account
should also have some information and I'll put Nancy and
Steve's contact information in the repository so that if
something unfortunate were to happen, someone will be able to
pick up the torch and continue on.</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Dec 8, 2017 at 11:55 AM, Eli
Adam <span dir="ltr"><<a href="mailto:eadam@co.lincoln.or.us" target="_blank">eadam@co.lincoln.or.us</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for
starting this Dan. Github doesn't seem quite right (unless<br>
open source projects also got one private repo for security,
finances,<br>
and other non-public issues)<br>
<span><br>
On Fri, Dec 8, 2017 at 7:25 AM, James Klassen <<a href="mailto:klassen.js@gmail.com" target="_blank">klassen.js@gmail.com</a>>
wrote:<br>
> Thoughts:<br>
><br>
> A plain text format might be better suited with git.
Org would be ideal (it<br>
<br>
</span>I was also thinking of some form of text format.<br>
<span><br>
> can save formulas and recalculate like spreadsheets)
except for most of the<br>
> magic only works in emacs, and despite emacs clearly
being the one true<br>
> editor, I realize not everyone is ready to accept
that yet. But, some other<br>
> format like CSV or markdown table could work too.
Mostly, I'd like to be<br>
<br>
</span>CSV is simple text and can still be used by
spreadsheet programs.<br>
<span><br>
> able to use diff/blame to make it easy to audit who
changed what when.<br>
<br>
</span>Yes, changesets was the point. I suppose that there
is not going to<br>
be a lot of churn on this file so I could download 10 copies
of binary<br>
files and open and look at them. But that is using me (a
human) to do<br>
diffs.<br>
<span><br>
><br>
> The <a href="http://geomoose.org" rel="noreferrer" target="_blank">geomoose.org</a>
server is only sporatically backed up right now (mostly<br>
> before and after larger system config changes and
GeoMoose releases). I<br>
> have been assuming the day to day changes are covered
by what is on github<br>
> and people's local clones. Thus is this isn't living
on github, we should<br>
> be extra sure we are maintaining a separate copies
(that are kept up to<br>
> date) off server.<br>
><br>
> I have no problem with git over ssh (or git over
email). That is how it was<br>
> designed to work in the first place. We could go as
simple as using the<br>
> geomoose account or even easily setup gitolite.<br>
<br>
<br>
</span>Every PSC meeting that has a report about finances
could be a prompt<br>
for PSC members to copy the repo somewhere.<br>
<span><br>
><br>
> We should maybe look at using GPG signed commits (git
commit -S) for this<br>
> repo.<br>
<br>
</span>Maybe. I don't expect that we'll have confusion over
who is making<br>
the commits.<br>
<br>
Best regards, Eli<br>
<div class="m_8145527218991917413HOEnZb">
<div class="m_8145527218991917413h5"><br>
><br>
> On Dec 8, 2017 8:44 AM, "Dan Little" <<a href="mailto:theduckylittle@gmail.com" target="_blank">theduckylittle@gmail.com</a>>
wrote:<br>
>><br>
>> Hey Folks,<br>
>><br>
>> I have put together the start of a 'ledger'.
Right now it's a spreadsheet<br>
>> in .ODS format. Barring objections, I'd like to
create a repository on the<br>
>> web-server which can be accessed over SSH to
store the ledger. This can<br>
>> give folks who are interested access without
putting _everything_ up on<br>
>> GitHub.<br>
>><br>
>> For those interested, we have $1,126 available
at present.<br>
>><br>
>> Thanks again!<br>
>><br>
>> ______________________________<wbr>_________________<br>
>> geomoose-psc mailing list<br>
>> <a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
>> <a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geomoose-psc</a><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> geomoose-psc mailing list<br>
> <a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank">geomoose-psc@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/geomoose-psc</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>