jsr348
  1. jsr348
  2. JSR348-98

Ensure that Spec Lead has flexibility in logging and responding issues

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Component/s: None
    • Labels:
      None

      Description

      From Mark Reinhold:

      Ensure that the requirement to log and respond to issues gives Spec Leads the freedom to ignore blatantly off-topic or deliberately obstructive comments.

        Activity

        Hide
        pcurran added a comment -

        Closed, as agreed at the September 21 Working Group meeting.

        Show
        pcurran added a comment - Closed, as agreed at the September 21 Working Group meeting.
        Hide
        eduardo added a comment -

        The changes have been incorporated

        Show
        eduardo added a comment - The changes have been incorporated
        Hide
        pcurran added a comment -

        Doing the hokey-cokey...

        Show
        pcurran added a comment - Doing the hokey-cokey...
        Hide
        pcurran added a comment -

        Section 1.1.2 currently reads (in the September 8 draft)

        "Issues must be tracked through a publicly readable Issue Tracker. The Expert Group may choose to use a publicly writable Issue Tracker, thereby permitting the public to log issues directly, or alternatively to identify formal comments in some other manner and to enter them into the Issue Tracker on behalf of the submitter. Whenever a Spec Lead or a Maintenance Lead submits materials to the PMO for review or ballot they must also provide an Issue List indicating the disposition of all of the Issues that have been logged against the JSR. In order to enable EC members to judge whether Issues have been adequately addressed the Issue List must make a clear distinction between Issues that are still open, those that have been resolved, and those that are closed, and must indicate the reason for any change of state."

        Replace this with

        "Issues must be tracked through a publicly readable Issue Tracker. The Expert Group may choose to use a publicly writable Issue Tracker, thereby permitting the public to log issues directly, or alternatively to identify formal comments in some other manner and to enter them into the Issue Tracker on behalf of the submitter. Whatever mechanism is used, a publicly-readable audit trail of all comments and Issues must be maintained.

        Whenever a Spec Lead or a Maintenance Lead submits materials to the PMO for review or ballot they must also provide an Issue List indicating the disposition of all of the Issues that have been logged against the JSR. It is permissible for Issues logged late in the review cycle to be deferred for later consideration, and for Issues that are blatantly off-topic or that appear to have been submitted maliciously to be ignored.

        In order to enable EC members to judge whether Issues have been adequately addressed the Issue List must make a clear distinction between Issues that are still open, that have been resolved, that have been deferred, and those that are closed, and must indicate the reason for any change of state."

        Show
        pcurran added a comment - Section 1.1.2 currently reads (in the September 8 draft) "Issues must be tracked through a publicly readable Issue Tracker. The Expert Group may choose to use a publicly writable Issue Tracker, thereby permitting the public to log issues directly, or alternatively to identify formal comments in some other manner and to enter them into the Issue Tracker on behalf of the submitter. Whenever a Spec Lead or a Maintenance Lead submits materials to the PMO for review or ballot they must also provide an Issue List indicating the disposition of all of the Issues that have been logged against the JSR. In order to enable EC members to judge whether Issues have been adequately addressed the Issue List must make a clear distinction between Issues that are still open, those that have been resolved, and those that are closed, and must indicate the reason for any change of state." Replace this with "Issues must be tracked through a publicly readable Issue Tracker. The Expert Group may choose to use a publicly writable Issue Tracker, thereby permitting the public to log issues directly, or alternatively to identify formal comments in some other manner and to enter them into the Issue Tracker on behalf of the submitter. Whatever mechanism is used, a publicly-readable audit trail of all comments and Issues must be maintained. Whenever a Spec Lead or a Maintenance Lead submits materials to the PMO for review or ballot they must also provide an Issue List indicating the disposition of all of the Issues that have been logged against the JSR. It is permissible for Issues logged late in the review cycle to be deferred for later consideration, and for Issues that are blatantly off-topic or that appear to have been submitted maliciously to be ignored. In order to enable EC members to judge whether Issues have been adequately addressed the Issue List must make a clear distinction between Issues that are still open, that have been resolved, that have been deferred, and those that are closed, and must indicate the reason for any change of state."

          People

          • Assignee:
            eduardo
            Reporter:
            pcurran
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: