Skip to Content.
Sympa Menu

cacert-sysadm - Re: [Cacert-sysadm] cacert systems strategy

cacert-sysadm AT lists.cacert.org

Subject: CAcert System Admins discussion list

List archive

Re: [Cacert-sysadm] cacert systems strategy


Chronological Thread 
  • From: "Ian G (Audit)" <iang AT cacert.org>
  • To: Daniel Black <daniel AT cacert.org>
  • Cc: cacert-sysadm AT lists.cacert.org
  • Subject: Re: [Cacert-sysadm] cacert systems strategy
  • Date: Sat, 14 Mar 2009 16:05:46 +0100
  • Authentication-results: lists.cacert.org; dkim=neutral header.i= AT cacert.org; dkim-asp=none
  • List-archive: <http://lists.cacert.org/pipermail/cacert-sysadm>
  • List-id: CAcert System Admins discussion list <cacert-sysadm.lists.cacert.org>

On 14/3/09 04:12, Daniel Black wrote:

If its a urgent requirement should the be fortnightly or monthly board
reports on progress? At least this will stress how important it is.
I think I would rather see a tracing of the requirements back to the
above board and audit priorities.

whats the best way to link to these requirements?


Well, in that wiki page, I would simply write how it relates to the board's priorities.

However, I am confused by one thing. There have been discussions in the past about how to get things done in software development and the answer has often been to put them into bugs.c.o.

What then is the relationship between these two places?

(And, how many other places are there?)

(note that the new SP has a section on software assessment that should inform a lot of this in the future.)


Otherwise, it is liable to be
deferred for now.  It's also a bit controversial to talk about this sort
of stuff because while we are talking about that, critical things like
lack of the test1 service, the dropping of old assurers and the mailouts
of the assurer and contract letters aren't getting done.

ok so prioritizing has to be done.

Short of any objection within a few days. I'll setup the following categories
on the SystemTasks wiki. I'll give people a week or two to reorganise these
according to priority. Within a week or two I'll cleanup the UnPrioritized
tasks.

Major headings:

Maybe you are better off by adding them not as headings but as tags to each entry. That is, some tasks will fall into many categories.

If you try and drive all of these things into a perfectly organised tree-structured ontological marvel, you'll run the risk of going the same way as the last 3 that tried to reorganise CAcert doco ... carted off to the loonie bin after loosing a week and a mind, moving everything around to zero effect.


Audit Tasks

CAcert Community Members Tasks

CAcert staff tasks

UnPrioritized (temporarly): - use this until stuff is moved into one of the
above or below.

Create a separate page for LessCriticalSystemTasks

with the remaining tasks under the headings:

Features for CAcert community members

Development to Promote Certificates

Features for CAcert staff

Development to Benefit CAcert systems


I'm also wondering whether the tasks there are "outsourcable" and that's why they are there in this list, and not in bugs.co.


iang

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature




Archive powered by MHonArc 2.6.16.

Top of Page