[Monotone-devel] notes on "automate certs"

[Nathaniel Smith]

1) Grahame, can you add a test case, please?  It's even more important
for automate commands than for others.  (See tests/README and/or bug
msh to get started...)

2) The values that the "status" field can take on are not documented.
As a rule of thumb, the output format documentation for 'annotate'
commands should be sufficiently detailed that the reader can predict,
byte-for-byte, what the output will be in any given case.  It'd
probably be good to individually describe each field's name and
semantics, as well... but the "status" thing otherwise can't be
figured out except by looking at the code.

3) Right now, the output looks like:

   key "address@hidden"
status "ok"
  name "author"
 value "address@hidden"

It seems like it would be better to rename 'status' to 'sig' or
'signature', since that's what it's actually informing on.  I think it
would also be good to add another entry, "trusted", that says whether
this monotone, with its current (arbitrarily complex) trust rules,
would believe in this cert or not.  (Sort of similar to "monotone
trusted".  Ugh, this stuff really needs to be refactored, too,
looking at erase_bogus_certs and CMD(trusted) and all...)

-- Nathaniel

-- 
- Don't let your informants burn anything.
- Don't grow old.
- Be good grad students.
  -- advice of Murray B. Emeneau on the occasion of his 100th birthday