License Review Tool Requirements, Candidates, and Selection

Version 3.1 by Chris Lamb on 2018/06/20 23:47

The License Review mailing list is considering using a project management tool for public tracking of the license review process. This page is for collecting information related to this tool selection.

Requirements

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.

  • Ability to submit a license for review
  • Being able to immediately identify the current state of review for a license (eg. "approved", "rejected", "new", "brb; being redrafted", "invalid", "rejected", etc.)
  • Ability to submit updated revisions of a license, without destroying previous ones or history
  • Ability to comment on a license in a general sense
  • Ability to comment on specific words/lines of a given draft of license
  • All comments and submissions are dated and named
  • Entirely separate discussions for each license
  • Canonical URIs for each license for review
  • Not mandatory to use the tool in order to participate in review

Candidates

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.

  • Gitlab (self-hosted, Gitlab.org, etc.)
  • Github
  • Taigo
  • Etherpad + similar
Tags:
    

Submit feedback regarding this wiki to [email protected]

This wiki is licensed under a Creative Commons 2.0 license
XWiki 14.10.13 - Documentation