[Libre-soc-bugs] [Bug 464] document the budget used for the project by analysing bugzilla

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=464

--- Comment #22 from Jacob Lifshay <programmerjake at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #21)
> (In reply to Jacob Lifshay from comment #20)
> > (In reply to Luke Kenneth Casson Leighton from comment #19)
> > > give me a day or so to think about it.  database field design takes time,
> > > to consider the information needed to be stored as well as the cleanest
> > > way to store it.
> > > 
> > > the date of the payment and submission also needs to be stored, which
> > > tends to suggest that alongside cf_payee_list two more TOML fields
> > > might do the trick: one cf_payee_submitdate and the other cf_payee_paiddate.
> > > these of the format "name" = "23jan2021"
> > 
> > we won't need any more bugzilla fields alongside cf_payee_list since all
> > that's needed is to add another level of nesting.
> 
> which increases the number of lines, filling the page with even more
> chatter, and requires a number of already-filled-in fields to be changed.
> 
> if you think it through, you'll find that adding those two proposed fields
> results in a very compact use of screen space.
> 
> for two people, six lines are used up with (three) TOML fields. the
> bugzilla field description at the left provides a visual field break,
> as does the box around the data.
> 
> if it is one field with [brackets] format it's *20* lines.  10 per person,
> 3-4 per "section" (including blank line dividers to provide clarity)

wait, wait, you're waay overestimating the amount of space required per person.
By my calculations, including blank lines, the least dense format mentioned so
far takes 5 lines per person.

if you want one line per person:
"person1" = 123
"person2" = 456
...

on submission becomes (using inline tables):
"person1" = { amount = 123, submitted = 2020-04-05 }
"person2" = 456
...

on payment becomes:
"person1" = { amount = 123, submitted = 2020-04-05, paid = 2020-06-08 }
"person2" = 456
...

or, if we leave out the submitted date for paid amounts:
"person1" = { amount = 123, paid = 2020-06-08 }
"person2" = 456
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.