2018-05-24 GnuCash IRC logs
00:49:21 *** chris1 has quit IRC
00:59:07 *** Mechtilde has joined #gnucash
01:19:59 *** fell has quit IRC
01:21:03 *** fell has joined #gnucash
01:34:19 *** gjanssens has joined #gnucash
01:34:19 *** ChanServ sets mode: +o gjanssens
01:56:27 *** Mechtilde has quit IRC
02:03:30 *** Cuare has quit IRC
02:16:24 <gjanssens> .
02:17:21 *** jotrago has quit IRC
02:30:42 *** mipesom has quit IRC
02:31:58 *** chris1 has joined #gnucash
02:45:36 *** mipesom has joined #gnucash
03:22:34 *** gour has joined #gnucash
03:26:58 *** gour has quit IRC
03:28:52 *** gour has joined #gnucash
03:31:04 *** fekepp has joined #gnucash
03:32:06 *** gour has quit IRC
03:34:37 *** oozer has quit IRC
03:35:45 *** bertbob has quit IRC
03:43:12 *** ncv has joined #gnucash
03:52:53 *** gour has joined #gnucash
04:14:14 *** bertbob has joined #gnucash
04:36:05 *** chris1 has quit IRC
04:49:46 *** harshitaneja has quit IRC
05:02:49 *** harshitaneja has joined #gnucash
05:06:09 *** harshitaneja has quit IRC
05:06:46 *** harshitaneja has joined #gnucash
05:15:39 *** harshitaneja has quit IRC
05:16:19 *** harshitaneja has joined #gnucash
05:19:39 *** chris1 has joined #gnucash
05:28:00 *** fekepp1 has joined #gnucash
05:28:59 *** fekepp has quit IRC
05:29:00 *** fekepp1 is now known as fekepp
05:50:45 *** pilotauto has quit IRC
05:57:26 *** chris1 has quit IRC
06:35:46 *** mikee has quit IRC
06:45:39 *** mipesom has quit IRC
06:55:54 *** mikee has joined #gnucash
06:55:54 *** gncbot sets mode: +o mikee
06:58:15 *** Jimraehl1 has joined #gnucash
06:59:26 *** Jimraehl1 has left #gnucash
07:00:17 *** mipesom has joined #gnucash
07:17:30 *** oozer has joined #gnucash
07:39:40 *** GabrieleV has quit IRC
07:46:24 *** chris1 has joined #gnucash
07:50:36 *** GabrieleV has joined #gnucash
08:29:46 *** mikee has quit IRC
08:46:08 *** oozer has quit IRC
08:46:13 *** jotrago has joined #gnucash
08:57:07 *** jotrago has quit IRC
09:18:33 *** kael has joined #gnucash
09:25:52 *** kael has quit IRC
09:28:10 *** Mechtilde has joined #gnucash
09:37:25 *** warlord has quit IRC
09:39:23 *** jotrago has joined #gnucash
09:40:06 *** warlord has joined #gnucash
09:44:43 *** storyjesse has joined #gnucash
09:47:53 *** fabior has joined #gnucash
10:15:14 *** Mechtilde has quit IRC
10:18:17 *** storyjesse has quit IRC
10:29:06 *** kael has joined #gnucash
10:33:14 *** Mechtilde has joined #gnucash
10:36:34 *** ArtGravity has joined #gnucash
10:44:40 *** Mechtilde has quit IRC
10:56:43 *** jotrago1 has joined #gnucash
10:57:50 *** jotrago has quit IRC
10:59:27 *** forty-two has joined #gnucash
11:10:37 *** luc14n0 has quit IRC
11:10:42 *** luc14n0 has joined #gnucash
11:29:53 *** fekepp has quit IRC
11:31:33 *** User has joined #gnucash
11:36:12 *** User has quit IRC
11:42:36 *** fekepp has joined #gnucash
11:47:57 *** fekepp has quit IRC
11:57:08 *** kael has quit IRC
11:57:28 *** calvinct has joined #gnucash
12:08:38 *** Mechtilde has joined #gnucash
12:16:47 *** gncbot sets mode: +o fell
12:24:48 *** calvinct has quit IRC
12:35:25 <jralls> gjanssens, chris1: That's never round except when displaying or to prevent overflow... and in the latter case, round minimally. Either way there's a lot of work to get there.
12:37:59 <jralls> warlord: If you're going to keep dropping the database then we need to record somewhere (the QA/BugzillaAdministration page?) all of the customizations.
12:38:21 <warlord> jralls: Have you made any customizations?
12:39:05 <warlord> Everything I've done is recorded either in my CHANGES file (because they are persistent changes), or encoded in the Migration script itself.
12:39:08 <jralls> Yes, I tweaked a few things on Tuesday.
12:39:08 *** boldstripe has quit IRC
12:39:33 <warlord> jralls: a) I did tell you to tell me if you change anything.
12:39:44 <warlord> b) I'm absolutely going to have to drop the DB for the final migration.
12:40:00 <gjanssens> jralls: re rounding, indeed lots of work ahead...
12:40:15 <forty-two> Grüsst Euch. Wie druckt man eine mehrteilige Buchung mit all ihren Teilbuchungen?
12:40:15 <forty-two> Über Berichte - Kontenbuch-Einzelbuchung krieg ich nur eine der Teilbuchungen angezeigt.
12:40:15 <forty-two> How can multi-line-bookings be printed with all its details? The option I found in the reports menu does not lead to the desired result. It is still one detail row only.
12:40:40 <jralls> warlord: Can't you just drop the Bugs, attachements, and comments tables?
12:40:53 <warlord> jralls: no
12:41:01 <warlord> the migration script touches everything.
12:41:07 <warlord> users. permissions.
12:41:09 <warlord> everythign
12:41:58 <warlord> There is some persistent storage (prefs)
12:42:11 <warlord> What exactly did you change Tuesday?
12:42:48 <warlord> For the record, this is why I'm working so hard to programatically set everything.
12:48:00 *** fiddlerwoaroof has quit IRC
12:48:01 <jralls> Some project and system parameters; I looked at just about everything and can't remember exactly what I touched without seeing what's available... I can't log in so I guess you've done a drop database. I'll go through it again and make notes on QA/BZAdmin this time.
12:48:53 *** fiddlerwoaroof has joined #gnucash
12:50:56 <warlord> jralls: Yes, I dropped it again today.
12:50:57 <jralls> gjanssens: Separately, a thought on patch status: Would having a flag work? That can be done easily enough without having to apply (and possibly port) the Gnome mods.
12:51:49 <warlord> jralls: the system parameters are (or should be) persistent.. But it would be nice to know what changes you made "just in case".
12:52:15 <warlord> The project parameters most likely got lost. Those would be useful to know so I can recreate them during the migration programatically.
12:52:50 <jralls> warlord: IIRC the project parameters had to do with setting up a Developer group.
12:53:20 <jralls> Like I said, I'll go through everything and make notes.
12:56:34 *** gour_ has joined #gnucash
12:57:30 <gjanssens> jralls: how would that flag work ?
12:59:00 *** gour has quit IRC
13:00:32 <jralls> IIUC, we'd have a flag for each status we want to use; I think that would be "needs work", "accepted-commit-now", "committed", and "rejected". The import script would derive the flag from the history and set it on import, and Developers would set the flags as they work through the bugs.
13:00:45 <warlord> jralls: okay. I do, now, create GnuCash_developers and add all the appropriate users to it.
13:01:24 <warlord> The import script would also have to programatically create those flags (in order to set them).
13:02:58 <jralls> warlord: Very nice. I'm going through the "Parameters" and see that a couple that I changed, defaultpriority and defaultseverity, did persist.
13:03:56 <warlord> jralls: yeah, most of those "Administration -> Parameters" settings do persist.
13:04:22 <jralls> Are they written to a file instead of stored in the DB?
13:05:19 <jralls> If so the quickest way to recover and document those would be to diff the file against the distribution version.
13:06:02 <jralls> BTW, why did you get 5.0.3 instead of 5.0.4? Package manager instead of direct download or clone?
13:06:20 <warlord> jralls: yes, they are stored in a json file in the filesystem
13:06:34 <warlord> jralls: yes, package manager
13:06:57 *** User has joined #gnucash
13:09:44 <jralls> Looking at the GnuCash project page I think the only change I made was to the default milestone: 3.2 (which seems to have not imported this time) instead of future.
13:09:51 *** bertbob has quit IRC
13:10:44 <gjanssens> chris1: I have worked on the rounding issues in gncEntry and by extension in gncInvoice
13:11:23 <gjanssens> chris1: With my pushed changes the rounding behaviour should now be consistent across gnucash regardless of where you start to create entries
13:12:07 <gjanssens> chris1: as a side-effect it fixes the rounding issue that was brought up on the mailing list a few days back.
13:12:57 *** harshitaneja has quit IRC
13:13:21 <gjanssens> chris1: yet at the same time I know we can't deal with all possible rounding variations in one algorithm so it will no doubt trigger requests for different rounding variations...
13:13:22 *** bertbob has joined #gnucash
13:14:24 *** harshitaneja has joined #gnucash
13:14:33 <gjanssens> chris1: IMO dealing with all of them will require the user's ability to manually correct tax values. That would mean both changes in the gui and in the data format so this won't happen for 3.x at least.
13:16:02 *** ncv has quit IRC
13:16:26 <gjanssens> jralls: a flag is probably good enough. As long as we can search on it.
13:18:14 <jralls> gjanssens: They're searchable but only in 'Custom Search'. That's also true of gnome_attachment_status.
13:18:36 *** User has quit IRC
13:27:10 <gjanssens> jralls: then that's suffcient for me.
13:29:00 <jralls> OK. warlord: Can you do that or shall I write a patch to the import script?
13:30:42 *** harshitaneja has quit IRC
13:31:49 *** harshitaneja has joined #gnucash
13:35:00 *** oozer has joined #gnucash
13:44:14 *** max has joined #gnucash
13:44:14 *** max has left #gnucash
13:57:19 *** fekepp has joined #gnucash
13:59:58 *** calvinct has joined #gnucash
14:06:40 *** frakturfreak has joined #gnucash
14:06:42 *** fabior has quit IRC
14:11:35 *** frakturfreak has quit IRC
14:12:53 *** frakturfreak has joined #gnucash
14:13:32 *** max has joined #gnucash
14:13:32 *** max has left #gnucash
14:17:05 *** fekepp1 has joined #gnucash
14:17:31 *** fekepp has quit IRC
14:19:09 <warlord> jralls: Was it at 3.0? That's something I think I hardcoded in -- which I just (think I) fixed.
14:19:21 *** fekepp1 is now known as fekepp
14:19:30 <jralls> warlord: Yes.
14:20:13 <fell> forty-two: the transaction report - at least in 3.x - should have enough options to do that.
14:20:22 <warlord> jralls: Actually, the default_milestone of "future" is what was in GnomeBZ.
14:20:27 <jralls> Err, sorry no, it was at "future".
14:21:00 <jralls> It is? I though on Gnome it's "---", i.e. unset.
14:21:11 <fell> yep, future should be the default.
14:21:35 <jralls> Just checked, and it's future on Gnome.
14:21:58 <warlord> jralls: I set product->version to 3.0 --- the default_milestone is coming from GnomeBZ
14:23:20 <warlord> jralls: So just to be clear, we want to create new attachment flag(s) for the status? The best way for you to help be with that would be to figure out how you would create those flags in the WebUI and tell me (URL of the creation page and the settings).. Then I can program that in.
14:23:41 *** frakturfreak has quit IRC
14:24:14 <jralls> warlord: OK. The milestones on Gnome are 3.1.(which I'll delete in a minute, there's no point in having a milestone that's already released), 3.2, 4.0, and future. Only 3.1 and future are in bz.gnucash.
14:25:31 <jralls> OK. The URI is https://bugzilla.gnucash.org/bugzilla/editflagtypes.cgi?action=enter&target_type=attachment. I'll set one up so you can see the fields.
14:25:32 *** fekepp has quit IRC
14:26:11 <warlord> jralls: when do you change it in GnomeBZ?
14:26:26 <warlord> Last time I pulled data was May 18
14:27:26 <jralls> When do I change what in GnomeBZ? Milestones? Last change would have been 4/28 when I released 3.1.
14:28:46 <warlord> The milestones come from the bugs. If there were any bugs with a milestone of 3.1 then that would add it in during import.
14:29:43 <fell> Is it still required after fix+release?
14:30:02 *** gour_ is now known as gour
14:31:46 <fell> Do we have for milestones the same restrictions, which forced jralls to map them to n.x to get free entries?
14:32:07 <fell> ... for the versions
14:32:45 <jralls> warlord: OK, but it would be better to populate it from the product if that's possible.
14:33:27 *** harshitaneja has quit IRC
14:33:32 *** harshitaneja_ has joined #gnucash
14:33:52 <warlord> jralls: the importer wont do that.
14:33:58 <warlord> sorry.
14:34:02 <jralls> fell: I collapse the versions to make the dropdown usable, not because of a limitation in BZ (aside from display, anyway).
14:34:12 <warlord> We'll just have to edit the list of milestones afterwards
14:34:23 <jralls> warlord: OK, I'll make a note on QA/BZA about that.
14:35:18 *** harshitaneja_ is now known as harshitaneja
14:36:20 *** max has joined #gnucash
14:36:20 *** max has left #gnucash
14:38:52 <jralls> warlord: I created an "accepted-commit-now" flag on attachements for your examination.
14:39:33 <warlord> jralls: yep, already looking at it.
14:41:11 <fell> if there is an ...commit-now, shouldn't there also be an -after-freeze-lift?
14:45:04 *** diego has quit IRC
14:45:37 *** diego has joined #gnucash
14:47:35 <warlord> jralls: Okay, I think I've got this written -- I just need the name / description / sort values for the desired flags.
14:50:46 <warlord> (of course I need to drop the database to test it)
14:51:31 <jralls> Let's do "needs-work", "A GnuCash developer has reviewed the proposed patch and requested changes", 101; "accepted-commit-now", "A GnuCash developer has reviewed the proposed patch and approved it for committing.", 102; "committed", "The patch has been committed to the canonical repository", 103; "rejected", "The proposed patch has been reviewed by a GnuCash developer and found irreparably unsuitable for incorporation into GnuCash.", 104.
14:56:07 <forty-two> Hi again. Sorry for having asked questions related to an older release (2.6.19 on ubuntu 18.04) that I haven't even mentioned before.
14:56:21 <forty-two> From reading the above conversation I understand there is a lot of improvement going on.
14:56:28 <forty-two> So I better try and get my installed version up to date before bothering again and make you hunt symptoms or problems that have been solved in the meantime :-)
14:56:32 <forty-two> Thank you for your incredibly valuable work which gives people the chance to survive the horror of bookkeeping :-)
14:56:49 *** Mechtilde has quit IRC
14:56:59 <warlord> forty-two: I believe 2.6.21 is current 2.6; 3.2 is latest stable
14:57:25 <warlord> jralls: do we need an "after freeze", like fell suggested?
14:58:35 <forty-two> warlord: great, thx
14:58:53 <jralls> warlord: Maybe, but let's see if we have anything...
15:00:33 <warlord> jralls: it was certainly used in GnomeBZ
15:01:09 *** max has joined #gnucash
15:01:09 *** max has left #gnucash
15:01:31 *** frakturfreak has joined #gnucash
15:02:27 *** fekepp has joined #gnucash
15:03:47 <jralls> warlord: We have 4 bugs, all "resolved" with attachments in that status. In all but one case (628444) the attachments are also marked "obsolete". I guess that means we should have the flag.
15:04:51 *** eagles0513875 has quit IRC
15:05:13 *** fekepp has joined #gnucash
15:06:41 <warlord> jralls: how about this description: The attachment is a patch and has been approved for committing by a GnuCash developer after the code freeze lifts
15:06:55 <jralls> Sounds fine.
15:07:24 <warlord> Where do you want it in the sort order?
15:07:40 <warlord> I put it between accepted-commit_now and committed
15:07:56 <jralls> Between "accepted-commit-now" and "committed".
15:09:38 <jralls> Since you've created GnuCash_Developers and populated it, and since my "admin" status persisted across drops, I suppose the note in QA/BZA that Developers, Admins, etc. "Will also need to be configured by hand" is no longer valid. Is that right?
15:11:46 <warlord> jralls: it didn't persist -- I added it manually
15:12:16 <warlord> BUT, membership in GnuCash_developers SHOULD be in the program now.
15:12:39 <warlord> I could add Admin privs -- I know how to do it.
15:12:53 <warlord> Right now I only add _dev privs to the list of people
15:13:56 <jralls> What's your preference? If you're planning several more drops it's probably easier to just persist admins and remove the note.
15:14:23 <warlord> Right now the only admin I'm adding is you.
15:14:32 <warlord> I can persist that.
15:14:45 <jralls> Otherwise I can just leave "Admins must be configured by hand".
15:15:07 <jralls> ISTM gjanssens and fell should get to play too...
15:16:03 <warlord> okay
15:18:19 <warlord> done.
15:18:22 <warlord> (for next round)
15:19:39 <fell> BTW: I will be traveling the next ~5 days.
15:20:00 <jralls> fell: Anywhere fun?
15:20:45 <fell> A round birthday in southern germany.
15:21:03 <warlord> I'm interesting in hearing how my re-categorization did for the new products/components.
15:28:59 <jralls> warlord: Well, the ones that went into Documentation all look right. (fell: I noticed https://bugzilla.gnome.org/show_bug.cgi?id=794389; is that still true for the 3.1 docs after I ran resize on them?)
15:29:31 <jralls> I'm not sure offhand how to find false negatives.
15:33:16 *** gour has quit IRC
15:34:23 <warlord> jralls: really, it's a question of: Website -> Translations and the various Documentation components.
15:35:54 <jralls> Some of the packaging ones are squishier. E.g. I don't know if 795253 is because something's missing or because somehow the register code messes up GtkEntry's interaction with the IM if another control is edited first.
15:36:59 <warlord> The packaging ones didn't change -- they already had a component of MacOS or Windows. So if those are misfiled then they already were.
15:37:40 <warlord> As I said in my email -- I searched for keywords in the bugs to file those.
15:39:05 *** kael has joined #gnucash
15:40:16 <jralls> MacOS and Windows components don't necessarily map to packaging. There is Mac and Windows specific code in GnuCash and some of the bugs in those categories may be about that code. It's probably too hard to separate that by hand and there are fewer than 80 so we can just go through and review them manually after the final import.
15:41:01 <warlord> jralls: Okay. I just made the assumption that Component MacOS == Mac Packaging (and similarly for Windows)
15:41:22 *** diego has quit IRC
15:48:11 <warlord> I guess, technically, that wasn't a good assumption.
15:49:00 <gjanssens> It's where we eventually want to arrive. I mentioned before the current gnomebz division was confusing
15:49:23 <jralls> 792226 is really a Documentation bug not a Website one. It's wrong in gnome, just fixed it.
15:49:45 *** calvinct has quit IRC
15:53:08 <warlord> jralls: okay. If it's wrong in Gnome there's not much I can do ;)
15:53:30 <warlord> Oh, right, I need the default cc lists from the components
15:54:06 *** fekepp has quit IRC
15:54:20 <jralls> Of course. But you'll do a new download of everything that's changed and it being fixed on Gnome will fix it here.
15:55:54 *** max has joined #gnucash
15:55:54 *** max has left #gnucash
15:57:26 *** harshitaneja has quit IRC
15:57:37 <warlord> jralls: indeed.
16:01:17 *** harshitaneja has joined #gnucash
16:09:33 <jralls> warlord: After reviewing more of the "packaging" bugs (and there are actually 354; I was using browse which shows only open ones) I think actual packaging issues are a small minority. I think gjanssens proposed that for bugs against gnucash-on-windows and gnucash-on-osx. ISTM we should leave the "windows" and "macos" components in the GnuCash product for now and just have the packaging product available to reassign to by humans.
16:10:09 <warlord> jralls: Okay.
16:10:17 <warlord> I'll not move those components
16:10:21 <fell> jralls about 794389:I just downloaded gnucash-help.epub from code. The screenshots are unreadable (too low res.). That is a separate issue and already in older docs.
16:10:46 <warlord> I'll create Packaging product but leave it empty. We can create the components by hand after the migration.
16:11:06 <jralls> warlord: OK.
16:11:57 <jralls> fell: So we need hi-res screenshots in the repository that get regenerated smaller for PDF?
16:13:51 *** max has joined #gnucash
16:13:52 *** max has left #gnucash
16:14:02 <fell> IMHO our resolution is OK. it is something in make epub|mobi which needs adjustment.
16:19:37 <warlord> jralls: Okay, I'll create the Windows and MacOS packaging components (duplicating the main ones) -- but I wont move any bugs over. Unless there are some keywords you think I can/should use to determine whether to do so?
16:21:08 *** fabior has joined #gnucash
16:21:43 <jralls> warlord: maybe "packaging" or mention of one of the gnucash-in-x repos in a comment? But I don't think it's worth putting in much effort.
16:25:43 <warlord> okay, I'll search for gnucash-on-
16:29:15 *** max has joined #gnucash
16:29:15 *** max has left #gnucash
16:31:04 <warlord> Only 18 bugs match the text "gnucash-on-" --- and at least one of them is definitely not related (and in a different component)
16:37:14 <warlord> jralls: mind if I dump and reload again to try my current code incarnation?
16:37:30 <jralls> warlord: Go ahead.
16:44:11 <gjanssens> jralls, warlord: I think the Windows and MacOS components are redundant in the gnucash product.
16:44:28 <gjanssens> We already have Windows and Macos in the OS selection.
16:44:56 <gjanssens> Isn't that sufficient to mark Windows or Macos specific bugs in the gnucash product ?
16:45:35 <gjanssens> Indeed my idea was to have bugs in gnucash-on-abc grouped in categories under the Packaging product.
16:45:37 <warlord> gjanssens: probably, yes, however we'd need to properly recategorize all of them
16:46:25 <gjanssens> I just wonder what's easiest: importing them as they are and drop the Windows/Macos categories after recategorizing
16:47:01 <gjanssens> Or move the bugs en masse to Packaging/(Windows/Macos) and do the recategorizing from there ?
16:47:17 <gjanssens> Can categories be removed once they have been used ?
16:47:24 <gjanssens> That's probably my core question
16:50:52 <warlord> gjanssens: yes, they can be removed
16:51:33 <warlord> it's probably easier to leave them in GnuCash/{Windows,MacOS} and recategorize from there.
16:51:52 <gjanssens> Ok
16:54:30 <jralls> Components can also be disabled for new bugs. That doesn't affect the existing bugs on the component but it does remove it from the pick list for (re)assignment.
16:55:24 <warlord> reload complete
16:55:25 <jralls> That would save us having to recategorize all of the old bugs.
16:58:17 <gjanssens> Ok that makes sense
16:58:24 <jralls> The new packaging heuristic results in only 3 bugs. No false positives.
16:58:36 <gjanssens> I'm off to bed, good luck further!
16:58:56 *** gjanssens has quit IRC
17:06:05 <warlord> No false positives is good. Any false negatives? ;)
17:08:02 <jralls> Too hard. ;-)
17:08:10 <warlord> LOL
17:08:29 <warlord> Anyways, I'll let other people examine this for now.
17:08:56 <warlord> I suppose I should re-fetch from GnomeBZ for my next trial.
17:10:07 *** max has joined #gnucash
17:10:07 *** max has left #gnucash
17:16:33 *** ncv has joined #gnucash
17:20:31 *** puck has quit IRC
17:21:46 *** fabior has quit IRC
17:27:31 *** puck has joined #gnucash
17:29:11 <warlord> We're up to 8611 bugs.
17:38:17 <forty-two> danke
17:39:01 <forty-two> very reassuring ;-)
17:43:49 <jralls> forty-two: Don't worry, only 1237 are open! ;-)
17:44:41 <fell> and some areenhancement requests.
17:45:03 <jralls> 506...
17:47:52 <fell> Bugs without a response 223
18:01:37 <warlord> Next time I'll refresh from GnomeBZ before I dump/reload ;)
18:01:44 <warlord> I still need to deal with the attachment flags.
18:03:09 <warlord> The only issue with the flags method is that you can set them independently.
18:03:19 <warlord> c.f. https://bugzilla.gnucash.org/bugzilla/attachment.cgi?id=1127&action=edit
18:06:43 <jralls> warlord: True. Not insurmountable as long as the history is presented in chrono order: The attachement_status handler can unset any already-set flag and we end up with the latest one. Doable?
18:07:16 *** User has joined #gnucash
18:07:17 <warlord> jralls: I'm just thinking "going forward" -- it's possible for a dev to set multiple flags.
18:07:33 <warlord> I'm not worried about the history -- I can code that up in chronological order.
18:07:48 <jralls> Possible, yes. Logical, not so much.
18:08:04 <warlord> (I also need to figure out what to translate it to, since there isn't a "field" to use)
18:17:32 *** forty-two has left #gnucash
18:30:12 *** User has quit IRC
18:51:17 <chris1> @tell gjanssens: thanks - the gncEntry taxes seem to work as per popular vote- unrounded in entries, added and displayed unrounded... but it does have side effect of creating total-amounts with high significant digits. see https://imgur.com/x52JztZ
18:51:17 <gncbot> chris1: The operation succeeded.
18:51:59 <chris1> @tell gjanssens ... I think is just an invoice report issue. my worry is how the Invoice Posting logic handle these total taxes
18:51:59 <gncbot> chris1: The operation succeeded.
18:53:00 <chris1> @tell gjanssens Xero seems to round individual tax entries. https://developer.xero.com/documentation/api-guides/rounding-in-xero
18:53:00 <gncbot> chris1: The operation succeeded.
19:15:17 *** puck has quit IRC
19:17:06 <jralls> chris: There's something wrong with that imgur.
19:20:26 *** puck has joined #gnucash
19:24:22 *** harshitaneja has quit IRC
19:31:17 *** harshitaneja has joined #gnucash
19:39:33 *** kael has quit IRC
19:49:38 <chris1> oops https://imgur.com/x52JztJ is what I get sending numbers via scheme... but sending numbers via UI seems fine
19:51:02 <chris1> but let me test further
19:51:07 <chris1> and I'll report back
19:52:54 *** ArtGravity has quit IRC
19:52:55 <fell> About GDPR:http://www.bbc.com/news/technology-44239126
19:55:06 <fell> before I leave over the weekend: I think we need to document: which services do we use/offer?
19:57:38 <fell> For that, which we offer: which "personal data" do we store there, how can the users a) download b) remove them?
19:59:30 <fell> I do not know, what to do with the right to become forgotten.
19:59:32 <jralls> fell: Yeah, saw that this morning. AFAIK we're clean on 3rd-party. All of the 3rd-party services we use deal directly with the user without us in the middle so we're clean. We don't even use Google Analytics.
20:00:49 <jralls> We ourselves collect real names and email addresses, as we discussed over the last 3 days. We're not really able to "forget" anyone.
20:00:51 *** pilotauto has joined #gnucash
20:01:40 <jralls> Nabble and GMane scrape our mailing lists (without permission) and therefore I think have a very serious GDPR problem: But it's their problem, not ours.
20:01:47 <fell> Finally we need to rework the create account process to inform the users about their rights and options.
20:02:09 <jralls> That we do. And write a privacy policy.
20:02:59 <fell> Yep, it should all be well documented, just in case a data security officer asks.
20:04:22 <jralls> But there's no need to panic. Nobody's coming after us next week.
20:06:15 <fell> E.g. the website needs to inform, it is storing a preferred language cooky and ask for consent.
20:07:19 <fell> I heard the EU wants to ask M. Zuckerberg a second. That is more lucrative for them. ;-)
20:21:40 *** kael has joined #gnucash
20:26:20 *** ncv has quit IRC
20:59:28 <warlord> fell: I wonder if we should work on a GDPR / Privacy Statement on the wiki?
21:01:18 <fell> warlord: I started already https://wiki.gnucash.org/wiki/General_Data_Protection_Regulation, but more to collect sources, what to do, ...
21:13:05 *** kael has quit IRC
21:36:17 *** kael has joined #gnucash
21:48:10 *** oozer has quit IRC
22:00:48 *** boldstripe has joined #gnucash
22:16:34 *** kael has quit IRC
22:35:26 *** badger92 has quit IRC
22:38:09 *** storyjesse has joined #gnucash
23:01:35 *** lmat has quit IRC
23:12:14 *** chris1 has quit IRC
23:13:07 *** chris1 has joined #gnucash