Eddy Nigg (StartCom Ltd.) wrote, On 2008-04-27 11:14: > Basically I'd first of all automate much tracking and other manual work > (such as statuses of CAs (and generation of their pages), auditing, > reporting etc) so what we have a reliable tool for that. Besides that we > could harbor important information about each CA at known places > (through the management tool) which would allow for efficient processing > of everything (including history).
I submit that we already have a very powerful tool for this purpose. It is the bugzilla.mozilla.org (b.m.o) bug tracking system. It has powerful searching. It presents reports in readable and user-customizable tables (although I gather that few know how to customize those tables). It has specific fields in its forms for the recording of specific information, and most fields can be displayed in the report tables. It is publicly accessible, and has adequate access controls. One can review the detailed history of all changes to any bug. One can "see at a glance" the changes made to any and/or all bugs for any period of time. I think we should already be using that bug database as the PRIMARY repository of status information about bugs and inclusion requests for CA certs. It is relatively easy to get a report of recent changes to the CA cert bugs, and then use that information to update other web pages (although, I question the need for other web pages). (Perhaps Frank is already using b.m.o as the primary repository, but that's not entirely clear to me. I sometimes see changes to the Pending web page without corresponding changes to b.m.o) A useful tool might derive the Pending page contents from b.m.o. I would NOT want to see ANOTHER repository for the CA cert information. We already have two repositories, and a challenge keeping them in sync. /Nelson _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
