Summary

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

Details

Page properties

Content

...	...	@@ -67,7 +67,17 @@
67	67	** 80% of trademark enforcement can be done with no cash outlay, just by sending a letter - can OSI provide templates for these polite letters?
68	68	* Governance models
69	69	** Copyright aggregation - this can be dangerous if any one entity exercises too much control over code base copyright
	70	+** How do we organize our open source project
70	70	* Social responsibility of the open source movement / organizations within it
71	71	** Are codes of conduct something we should talk about as a best practice?
72		-** Free software and policy, e.g. bill introduced by a City Council member in New York advocating government prefer FOSS in procurement - cuts costs, use local contractors vs. big vendors, set target for amount of open source being used
	73	+** Free software and policy, e.g. bill introduced in New York City Council advocating government prefer FOSS in procurement - cuts costs, use local contractors vs. big vendors, set target for amount of open source being used, software produced by government should be released as open source
	74	+* How to tell if a particular project is "good" to engage with / contribute to
	75	+* How do we engage authentically with open source communities when we're a business using/creating open source software
	76	+* OSI has capacity and neutrality to compile and index this kind of best practices content, the question is where to start - we want to be the 'reference desk'
	77	+** Would there be a peer review process for this content?
	78	+** What is the approval process for a particular document / syllabus / piece of work?
	79	+*** Could be the committer model to avoid endless debate
	80	+* Employee and employer relationship around open source stuff - employment contracts, expectations of time to spend contributing, copyright assignment in work for hire situations, etc.
	81	+*
	82	+*
73	73	)))