Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.PamelaChestek
	1	+XWiki.ElanaHashman

Content

...	...	@@ -4,6 +4,7 @@
4	4
5	5	* Identify an appropriate license-review vehicle with the below attributes
6	6	* Implement the vehicle on an OSI-approved host
	7	+* Document the solution and any maintenance tasks so they can be handed off to a new maintainer
7	7	* Evaluate feasibility of creating 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)
8	8
9	9	(((
...	...	@@ -15,9 +15,8 @@
15	15
16	16	== Requirements for license-review process ==
17	17
18		-Must have
	19	+==== Must have ====
19	19
20		-
21	21	* Ability to submit a license for review
22	22	* Being able to immediately identify the current state of review for a license (eg. "approved", "rejected", "new", "being redrafted", "invalid", "rejected", etc.)
23	23	* Ability to submit updated revisions of a license, without destroying previous ones or history
...	...	@@ -24,11 +24,14 @@
24	24	* Ability to comment on a license generally
25	25	* Time-stamping of all comments and submissions
26	26	* Entirely separate discussions for each license
27		-* 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	+* Easy to learn/refresh by non-technical users
	28	+* Must not assume experience with specific technical tools (i.e. requirement to use git, XML, a specific programming language, etc.)
28	28
29		-Nice to have
	30	+(((
30	30
	32	+)))
31	31
	34	+==== Nice to have ====
32	32
33	33	* Ability to comment on specific words/lines of a given draft of license
34	34	* Ability to cross-reference a different comment in the same or different discussion