Hi Nelson,
Nelson B Bolyard:
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 view bugzilla absolutely time consuming, unhandy and inefficient for
this purpose. If I'd had to manage the StartCom CA with bugzilla I would
be a dead man by now...
What I suggest doesn't even come close to bugzilla and the problem
bugzilla tries to solve, but managing the aspects of CA governance. It's
like you are asking me to produce a milk shake with a barbecue
grill...(It might be possible, but good luck then...this is about how
our CA process looks about)
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).
Which a decent management utility geared to the purpose of handling the
tasks of CA inclusion, removal, control this will be MUCH easier than
just searching a few bug pages. Besides that it doesn't provide an
overview and search capabilities needed for this task, has not automated
features like reminders, pre-formated mail messages, clickable forms for
settings the status (at least not as I'd like to have it) etc...
(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)
Well, we'd give up the pending pages in favor of something better.
Something auto-generated with the help of a few clicks....using CVS to
update this pages....OMG...
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.
Nope, we'd have one tool for managing the CAs and one tool for handling
bugs. This is how it should be and bugzilla serves our purpose not so
good IMO...Bugzilla is for bugs and ill-suited for the task we have to
achieve here...
--
Regards
Signer: Eddy Nigg, StartCom Ltd. <http://www.startcom.org>
Jabber: [EMAIL PROTECTED] <xmpp:[EMAIL PROTECTED]>
Blog: Join the Revolution! <http://blog.startcom.org>
Phone: +1.213.341.0390
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
