[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
Mon Sep 7 01:34:09 BST 2020


--- Comment #20 from Jacob Lifshay <programmerjake at gmail.com> ---
(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. Also, TOML has built-in date/time
types, so we should use those instead of strings.

So, something like this:

amount = 567
date = 2020-08-01

amount = 432
date = 2020-08-06

Alternatively, we could just have the presence of the `submitted` and `paid`
fields indicate that that particular payment was submitted then paid:

amount = 123
# no submitted or paid fields means not yet submitted or paid

amount = 456
submitted = 2020-09-23
# submitted field without paid field indicates submitted but not yet paid

amount = 789
submitted = 2020-08-12T06:23:00-07:00 # different timezone
paid = 2020-09-13T13:46:23Z # person3 likes precision :)
# submitted field with paid field indicates both submitted and paid

JSON equivalent (JSON doesn't have separate date/time types, so those are
converted to strings):
  "person1": {
    "amount": 123
  "person2": {
    "amount": 456,
    "submitted": "2020-09-23"
  "person3": {
    "amount": 789,
    "paid": "2020-09-13T13:46:23+00:00",
    "submitted": "2020-08-12T06:23:00-07:00"

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

More information about the libre-soc-bugs mailing list