[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 #21 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(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)

if four people contribute that's *FORTY* lines.


> Also, TOML has built-in
> date/time types, so we should use those instead of strings.

ah good.

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