[Fwd: Re: draft of Process Flow Specification]

From: Kurt Baty (kurt@wsfdb.com)
Date: Wed Jan 21 2004 - 09:17:42 PST

  • Next message: Kathy McKinley: "Three EGG Proposals"

    attached mail follows:

    On Mon, 2004-01-12 at 13:21, Francoise Martinolle wrote:
    > A few questions:
    >
    > 1. At various states of your process flow state machine, there is an action
    > of HOLD which is mentioned. Can you describe what would be the reasons for
    > an action of HOLD? Does it mean it would be postponed to another version of
    > the standard? Does it mean that it is in hold until a future vote?

    HOLD means Table, as in Roberts Rules of Order. In a Task Force or
    sub-committee if the draft proposal is Tabled then it may or may not
    be looked at in the next meeting.

    I have added the following to Step 4. C:

    Step 4.

    C: Table the draft proposal till a later date. Hold at step 4.
      (if the draft proposal is tabled, it maybe looked at in the next
       meeting,or it might be tabled indefinitely.)

    >
    > 2. In your process flow description, there is no notion of time, neither
    > mention of a schedule for creating a proposal, nor references to certain
    > milestones that may have to do with creating the next revision of the standard.
    > Is this intentional? Wouldn't be useful to insert some time limit for an
    > enhancement to be kept alive so that a proposal can be generated within
    > some reasonable time or some crossing time points with a standard overall
    > milestone.
    > There are a few reasons for this:
    > a) This can help accelerate the standardization process (but also can be
    > dangerous if we don't ensure that proposals are sound).
    > b) It can ensure that late proposals are not included in the standard which
    > can potentially avoid some inconsistency in the standard for lack of review
    > time.

    No mention of schedule or time limits is made in the process flow.

    >
    > 3. State of a proposal: it would be good to make sure that the database web
    > page represents all the possible final or intermediate states of the
    > process flow.

    I have no problem with this. Tracking the current state of an
    enhancement request in the database. No need to make a change
    to the process flow.

    >
    > Francoise
    > '

    For voting on a draft of:

             Process Flow Specification

    from your friendly EGG sub-committee, is at:

             http://24.242.132.51/draft_flow_spec.pdf

    this is rev 0.9c 1/21/2004

          kurt

    This archive was generated by hypermail 2.1.4 : Wed Jan 21 2004 - 08:55:36 PST and
    sponsored by Boyd Technology, Inc.