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

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Wed Sep 9 01:00:19 BST 2020


Jacob Lifshay <programmerjake at gmail.com> changed:

           What    |Removed                     |Added
       The table of|                            |# commented out test case:
  payments (in EUR)|                            |#"person1"={amount=123,paid
     for this task;|                            |=2020-06-08}
        TOML format|                            |

--- Comment #25 from Jacob Lifshay <programmerjake at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #24)
> (In reply to Jacob Lifshay from comment #23)
> > > or, if we leave out the submitted date for paid amounts:
> > > "person1" = { amount = 123, paid = 2020-06-08 }
> > > "person2" = 456
> > > ...
> <snip>
> yeah it looks very reasonable. it may get a little long (line-wrap), 

We could also leave out unnecessary spaces:

I'm adding a commented version of the above to this bug so we can try it out.

> if it
> can be done as a list "person = [123, 2020-06-08]" that's shorter, and we
> know (implicitly) that 1 date means "submitted", 2 dates means "paid".

I strongly think we should not use implicit field naming, though I'm fine with
coming up with shorter names.

Do we really need 2 dates for every payment, can't we just rely on bugzilla's
history function or just asking the relevant person if we really need the
submitted date for a payment that's already paid?

> that stands a chance of fitting on a single line without wrapping and thus
> making it readable in a web browser.

I shortened the bugzilla field short descriptions as part of mitigating that:
    NLnet milestone
    total budget (EUR) for completion of task and all subtasks
    budget (EUR) for this task, excluding subtasks' budget
    parent task for budget allocation
    The table of payments (in EUR) for this task; TOML format

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

More information about the libre-soc-bugs mailing list