jsr348
  1. jsr348
  2. JSR348-95

Section 1.1.2 needs a little rewording to alleviate ambiguities

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Component/s: None
    • Labels:
      None

      Description

      In section 1.1.2 it's stated that a publicly readable issue tracker should be used for the specification but implies users can add comments (doesn't say anything about the public being able to add issues). With all the explicit defining that has gone into the current drafts, should this be clarified a bit more to allow addition of issues / comments by the public or simple remove the word "readable" and simply go with "Issues must be tracked through a public issue tracking mechanism."?

        Issue Links

          Activity

          lightguard created issue -
          pcurran made changes -
          Field Original Value New Value
          Link This issue is related to JSR348-71 [ JSR348-71 ]
          Hide
          pcurran added a comment -

          The new wording proposed for section 1.1.2 in
          JSR348-71 Issue Tracker should be a defined term addresses this concern.

          I'm closing this issue. Further comments can be added to JSR348-71 if necessary.

          Show
          pcurran added a comment - The new wording proposed for section 1.1.2 in JSR348-71 Issue Tracker should be a defined term addresses this concern. I'm closing this issue. Further comments can be added to JSR348-71 if necessary.
          pcurran made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              lightguard
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: