| *** bkuhn is now known as bkuhnIdle | 01:57 | |
| *** bkuhnIdle has quit IRC | 04:22 | |
| *** pokoli has joined #npoacct | 09:28 | |
| *** tbm_ is now known as tbm | 11:26 | |
| *** bkuhn has joined #npoacct | 11:29 | |
| joar | bkuhn: I've been working on the API stuff lately. | 13:11 |
|---|---|---|
| bkuhn | joar: great, how's it going? | 13:11 |
| joar | made a small P-o-C GTK client, started on a flexible storage system that could let you use ledger, SQL or anything else. | 13:11 |
| joar | realized that editing transactions will be hard with ledger. | 13:12 |
| joar | I will try to solve that issue. | 13:12 |
| bkuhn | Yeah, I knew that would be coming. Ledger is bad at that in some ways, but it would be ok if you made extra rules. | 13:13 |
| joar | It will probably end up with a regular expression looking for the transaction ID, which will be a tag in the ledger file and then finding out the bounds of the transaction in the text file, possibly changing it in place or placing it in a temporary file, deleting it from the main file and let ledger parse it then edit it and write it to the end of the file again. | 13:13 |
| bkuhn | For example: you could demand that the entries be valid for Ledger but not as free-form. | 13:14 |
| bkuhn | joar: another idea: you could insist that every transaction is in its own file. | 13:14 |
| joar | I also contemplated that you could provide a way to simply reverse the transaction. | 13:14 |
| bkuhn | This would be annoying to command line users, but solvable. | 13:14 |
| joar | I think that would make it a hurdle for people migrating from ledger-cli. | 13:15 |
| tbm | joar: ofx has the concept of a unique id for each transaction; it might be worth looking into that and adopting that to identify transactions | 13:15 |
| joar | tbm: I use uuids at the moment :) | 13:15 |
| tbm | if you can import ofx from your bank, you'd get a unique id for many transactions automatically | 13:15 |
| tbm | and it would wave the way towards exporting ledger as ofx, which might be useful to import it into other software | 13:15 |
| joar | that's good. The IDs do not have a restriction on them, I use UUIDs to programmatically generate them, but a few are set to nonsense strings by me. | 13:16 |
| bkuhn | tbm: do you have any other thoughts on how to handle the issue of editing the ledger file in place by the API? | 13:17 |
| joar | https://gitorious.org/conservancy/accounting-api/source/873cff4229e3ca1b04e28ea6ec712deeebc59fc0:non-profit-test-data.ledger#L2 | 13:17 |
| tbm | bkuhn: I don't | 13:18 |
| joar | here is an ofx python module: https://github.com/kedder/ofxstatement/blob/master/src/ofxstatement/ofx.py | 13:24 |
| joar | bkuhn: Regarding licensing, for example the ofxstatment project only mentions its license in one place, and that's in https://github.com/kedder/ofxstatement/blob/master/setup.py#L49. Is that enought for the project to be considered AGPLv3? | 13:34 |
| joar | I suspect it's a fluid line, and that would generally not be seen as enough. | 13:35 |
| * bkuhn loks | 13:38 | |
| bkuhn | jelmer: BTW, are you around? | 13:38 |
| bkuhn | joar: are you asking: "is that text copyrightable"? | 13:38 |
| bkuhn | The answer there is surely yes. | 13:39 |
| joar | I'm not sure I understand? | 13:39 |
| jelmer | hi bkuhn, joar | 13:39 |
| joar | hi jelmer! | 13:39 |
| joar | I was wondering about the license of ofxstatement, and saw that it was "licensed" under AGPLv3, but it only makes it clear in that one place. | 13:40 |
| bkuhn | jelmer: Hey, so did you see my introduction to scott_gonzalez yesterday? scott_gonzalez is Javascript hacker I know who has done a lot of work on jQuery and is working on a side-project for bug tracking software.https://github.com/scottgonzalez/debt You and I had discussed bug tracking software recently and thought you and Scott might have a lot to talk about. | 13:40 |
| joar | reading http://oss-watch.ac.uk/resources/opensourceyourcode#applying-the-licence it seems that there's some things missing | 13:40 |
| bkuhn | Relevance to this project is we haven't picked a bugtracker yet and we want a good one that's Free Software. :) | 13:40 |
| jelmer | bkuhn: no, I missed that - scrolling up now - thanks! | 13:41 |
| bkuhn | joar: So, the URL you pointed me to is someone else's code, right? | 13:46 |
| bkuhn | So I thought you were asking me about that. | 13:46 |
| joar | yes | 13:47 |
| joar | I have some work to do with applying the license correctly to accounting-api too. I will do that now. | 13:49 |
| bkuhn | joar: actually, I was just looking that tissue | 13:51 |
| bkuhn | so | 13:51 |
| bkuhn | here's what I suggest | 13:51 |
| bkuhn | I don't suggest copyright notice in each file | 13:51 |
| bkuhn | rather a top level file | 13:51 |
| * joar was just preparing for a find -name '*.py' | xargs | 13:52 | |
| bkuhn | haha | 13:52 |
| bkuhn | so | 13:52 |
| bkuhn | let me add a COPYRIGHT file now | 13:52 |
| bkuhn | joar: ok, I just pushed my commits | 14:03 |
| bkuhn | https://gitorious.org/conservancy/accounting-api/source/44a2c02706ca2b2d6952c5053d3e5b279beaa9c8:LICENSE | 14:03 |
| bkuhn | joar: so, I suggest adding this to each file that you've written: | 14:04 |
| bkuhn | 14:04 | |
| bkuhn | Part of accounting-api project: | 14:04 |
| bkuhn | https://gitorious.org/conservancy/accounting-api | 14:04 |
| bkuhn | License: AGPLv3-or-later | 14:04 |
| bkuhn | 14:04 | |
| bkuhn | at the top | 14:04 |
| joar | will do | 14:10 |
| bkuhn | joar: I noted the Spinx stuff you included mentions BSD license | 14:28 |
| bkuhn | you should copy their LICENSE file into something like 3-Clause-BSD and change it to refer to that rather than LICENSE | 14:28 |
| bkuhn | OR | 14:28 |
| bkuhn | add to LICENSE file info that says: | 14:28 |
| bkuhn | "Some files in the docs/ directory were borrowed from Spinx, which is licensed under 3-Clause-BSD [or 2-Clause-BSD... I didn't check]. See the file [N]-Clause-BSD for details | 14:29 |
| joar | done | 15:11 |
| joar | oh | 15:11 |
| joar | concurrent work | 15:11 |
| joar | bkuhn: should I add a license notice pointing out the Sphinx license in docs/source/conf.py and docs/Makefile or should I add that pointer in LICENSE? | 15:16 |
| bkuhn | I'd say it makes sense to add it to LICENSE | 15:16 |
| bkuhn | just to keep all LICENSE info in one place | 15:16 |
| bkuhn | but | 15:16 |
| bkuhn | you could say in LICENSE: | 15:16 |
| bkuhn | "Spinx's license can be found in docs/source/conf.py" | 15:17 |
| bkuhn | or somesuch | 15:17 |
| bkuhn | It's ok if there's a lot of pointer indirection. :() | 15:17 |
| bkuhn | :) | 15:17 |
| joar | bkuhn: this is the sphinx license: https://bitbucket.org/birkenfeld/sphinx/raw/c411c343dd216f41d263b5f5a14ad14d3ff5dad7/LICENSE | 15:21 |
| bkuhn | The top license (the one labeled "License for Sphinx") is 2-Clause-BSD | 15:22 |
| joar | should I include the entire file or just the 2-clause BSD? | 15:22 |
| joar | only the 2-clause, since the files in accounting-api does not have anything to do with the software incorporated in sphinx. | 15:24 |
| joar | bkuhn: pushed | 15:30 |
| bkuhn | thanks! | 15:30 |
| bkuhn | (and you answered your own question correctly, as I think you know :) | 15:31 |
| joar | :) | 15:31 |
| joar | bkuhn: one thought I had was to simply reverse the transaction instead of updating it. | 16:26 |
| bkuhn | joar: ugh, it drives me nuts when accounting systems won't allow you to change a transaction. | 16:26 |
| bkuhn | That's such a hold-over from paper-based ledger systems. | 16:27 |
| bkuhn | better to keep a log of what happened. | 16:27 |
| joar | in sweden you aren't allowed to change transactions in your accounting system. | 16:27 |
| bkuhn | (there are probably some accounts who would see that as a feature rather than a bug, though, I should admit.) | 16:27 |
| bkuhn | Really!?!? | 16:27 |
| bkuhn | I mean, GAAP in the USA tends seems to indicate that it's acceptable to change it if the books for that period aren't closed and there's a record of who did it. | 16:27 |
| joar | That's what I hear from my father and brother-in-law at least | 16:27 |
| bkuhn | joar: I'm not entirely surprised... I suppose it's a 'mode' we should support... but I don't think we want to insist that it works that way, either. What do you think? | 16:29 |
| bkuhn | ilan: I'm sorry to say that I was really busy this weekend and missed the SCALE deadline. But I just submitted a talk on this project there, so | 16:29 |
| bkuhn | ... I just submitted it. If it's too late, I understand. | 16:29 |
| joar | bkuhn: if we implement both then people may decide for themselves. | 16:36 |
| joar | reversal would be technically easier with ledger, and probably easy to do with every other backend, but not everyone likes that behaviour. | 16:37 |
| *** nesciens has joined #npoacct | 16:37 | |
| *** bkuhn is now known as bkuhnIdle | 20:33 | |
| *** bkuhnIdle is now known as bkuhn | 21:07 | |
| *** zernia has joined #npoacct | 22:32 | |
| *** zernia has quit IRC | 22:44 | |
Generated by irclog2html.py 2.12.1 by Marius Gedminas - find it at mg.pov.lt!