> I liked this idea, as moving to a JSON/YAML/CSV/etc datafile,
> would get us 90% of the benefits of using a database, but without
> the maintenance and development overhead. (I think there may have
> been some concerns last time I raised this, but I don't recall
> anything insurmountable.)
One problem is that the only syntax checking will be done by editors
highlighting syntax, and they get it wrong some times.
Apart from that, sure, it's a step. Make it one file per sponsor,
possibly employing symlinks to manage main workflow categories.
When I think about it more, however, then it'll get hard to add
dated notes with ownership like sponsors-table has.
2014-07-07:
madduck: > the note I want to add, remembering how to do
multi-line input in YAML…
--
.''`. martin f. krafft <madduck@debconf.org> @martinkrafft
: :' : DebConf orga team
`. `'`
`- DebConf14: Portland, OR, USA: http://debconf14.debconf.org
DebConf15: Heidelberg, Germany: http://debconf15.debconf.org
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)