jsr358
  1. jsr358
  2. JSR358-7

Changes to Terms of Use associated with collaboration tools

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Component/s: None
    • Labels:
      None

      Description

      Process Document review

      line numbers: JCP-2.8-21SEP2011-Redlined.pdf

      205-207 - are contradictory. 205 requires Terms of Use to be provided so that "prospective EG members can judge whether they are compatible with the JSPA" but 207 allows the EG to change its collaboration tools after the EC begins. An EC member who believes the new tools' Terms of Use are not compatible with the JSPA has no recourse - after the IP cow is out of the barn - if they are in a minority (in fact no rules are provided for deciding how an EG can switch tools. Without rules the spec lead could do this dictatorially.

      PC> What are you suggesting? That EGs must be locked into their original choice of collaboration tools - and that moreover the terms of use for these tools must be cast in stone - for the possibly multiple-year lifetime of the JSR? This isn't reasonable. Please make a specific suggestion in a separate issue.

      SS> Suggest adding clause requiring unanimous vote of EC and past/present EG members to approve changes in licenses.

        Activity

        Hide
        pcurran added a comment -

        Following up on my last comment, the wording of this issue is extremely misleading (referring to "license" rather than "terms of use". I will re-word it.

        Show
        pcurran added a comment - Following up on my last comment, the wording of this issue is extremely misleading (referring to "license" rather than "terms of use". I will re-word it.
        Hide
        pcurran added a comment -

        This is not about licenses (as JSR358-8 was), but instead refers to the terms of use associated with the tools used to collaboratively develop the RI. Tools change over time. Requiring votes before adopting a new tool is unreasonable.

        We will need to define some processes to ensure that the collaborative development is happening "appropriately". Terms of Use and the choice of tools/platform can be addressed there.

        Show
        pcurran added a comment - This is not about licenses (as JSR358-8 was), but instead refers to the terms of use associated with the tools used to collaboratively develop the RI. Tools change over time. Requiring votes before adopting a new tool is unreasonable. We will need to define some processes to ensure that the collaborative development is happening "appropriately". Terms of Use and the choice of tools/platform can be addressed there.
        Hide
        pcurran added a comment -

        As with http://java.net/jira/browse/JSR348-137 it's too late to resolve this. I've marked it Deferred.

        Show
        pcurran added a comment - As with http://java.net/jira/browse/JSR348-137 it's too late to resolve this. I've marked it Deferred.

          People

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

            Dates

            • Created:
              Updated: