Changes for page License Review Tool Requirements, Candidates and Selection
Last modified by Stefano Maffulli on 2021/08/14 00:21
Change comment:
Added comment
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. PamelaChestek1 +XWiki.XWikiGuest - Content
-
... ... @@ -1,45 +1,22 @@ 1 1 The [[License Review>>url:http://lists.opensource.org/mailman/listinfo/license-review_lists.opensource.org]] mailing list [[is considering>>url:http://lists.opensource.org/pipermail/license-review_lists.opensource.org/2018-June/003384.html]] using a project management tool for public tracking of the license review process. This page is for collecting information related to this tool selection. 2 2 3 - TheLicense Committee recommends hiring a person to aid in the identification and implementation of a better workflow for license review. We have decided that the current email listserve is inadequate becauseit is exceedingly difficult to follow discussions, whichreduces participation. Thetasksthat this person will undertake are:3 +== Requirements == 4 4 5 -* Identify an appropriate license-review vehicle with the below attributes 6 -* Implement the vehicle on an OSI-approved host 7 -* Create a complete, searchable database of all license-review emails, either incorporated into the tool or separate from the tool (currently emails are at at least three different urls) 5 +For now, simply list any requirements you believe this tool //should// have. After collecting potential requirements we can categorise them into actual-requirements, nice-to-haves, and not-actually-required. 8 8 9 -((( 10 -The person will also be asked to: 11 11 12 -* create a maintainable system for making machine-readable licenses available. 13 -))) 14 - 15 -== Requirements for license-review process == 16 - 17 -Must have 18 - 19 - 20 20 * Ability to submit a license for review 21 -* Being able to immediately identify the current state of review for a license (eg. "approved", "rejected", "new", "being redrafted", "invalid", "rejected", etc.) 9 +* Being able to immediately identify the current state of review for a license (eg. "approved", "rejected", "new", "brb; being redrafted", "invalid", "rejected", etc.) 22 22 * Ability to submit updated revisions of a license, without destroying previous ones or history 23 -* Ability to comment on a license generally 24 -* Time-stamping of all comments and submissions 25 -* Entirely separate discussions for each license 26 -* Easy to learn/refresh: this will be used intensively, but for many users only once (when they submit a license) or for most, 1-2x a year (current rate of seriously discussed license submisssions) 27 - 28 -Nice to have 29 - 30 - 31 - 11 +* Ability to comment on a license in a general sense 32 32 * Ability to comment on specific words/lines of a given draft of license 33 -* Ability to cross-reference a different comment in the same or different discussion 13 +* All comments and submissions are dated and named 14 +* Entirely separate discussions for each license 34 34 * Canonical URIs for each license for review 35 -* Not mandatory to use the tool in order to participate in review, i.e., system integrates with an email workflow 16 +* Not mandatory to use the tool in order to participate in review 17 +* Easy to learn/refresh: this will be used intensively, but for many users only once (when they submit a license) or for most, 1-2x a year (current rate of seriously discussed license submisssions). 36 36 * Low administrative overhead (OSI does not have a good track record of hosting/maintaining new services) 37 -* Previous license review emails can be added so that all license reviews are in the same place 38 38 39 -((( 40 - 41 -))) 42 - 43 43 == Candidates == 44 44 45 45 What tools are candidates for this? For now simply list tools without regard to whether they meet requirements, as the requirements are still being collected. Please provide links to tools as applicable.
- XWiki.XWikiComments[0]
-
- Date
-
... ... @@ -1,1 +1,1 @@ 1 -2019-11-16 08:34:14.0 1 +2019-11-16 08:34:14.103