Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • XWiki.XWikiComments[0]

Details

Page properties

Content

...	...	@@ -1,4 +1,4 @@
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. Note that the **license-review** list and corresponding that license review process in general distinct from the **license-discuss** mailing list, which this document does not address.
	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. Note that the **license-review** list, and corresponding license review process in general, is distinct from the **license-discuss** mailing list, which this document does not address.
2	2
3	3	The License Committee recommends hiring a person to aid in the identification and implementation of a better workflow for the review of licenses. We have decided that the current email-based system (Mailman) is inadequate as it is exceedingly difficult to follow discussions, which reduces participation. The tasks that this person will undertake are:
4	4
...	...	@@ -26,7 +26,6 @@
26	26	* Create a maintainable system for making machine-readable licenses available
27	27	* Create a complete, searchable database of all license-review emails
28	28
29		-
30	30	The OSI would (% style="background-color: inherit; color: inherit; font-family: inherit; font-size: inherit;" %)execute each stage in turn, retaining the option to re-evaluate or even potentially terminate the project at the end of each stage. For example, if it turns out that we cannot identify a solution at the end of Stage 1, the OSI would end the engagement.
31	31	)))
32	32

XWiki.XWikiComments[0]

Date

...	...	@@ -1,1 +1,1 @@
1		-2020-04-30 17:17:07.578
	1	+2020-04-30 17:17:07.0