Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-FLOSS Entities Working Group
	1	+Practices in Open Source Software Crowd-funding Working Group

Content

...	...	@@ -1,44 +1,74 @@
1	1	{{toc/}}
2	2
	3	+
	4	+**Start date: **January 2015
	5	+
	6	+**Working Group Chair: **Patrick Masson
	7	+
	8	+**Working Group Sponsor: **Patrick Masson
	9	+
	10	+**OSI General Manager: **Patrick Masson
	11	+
	12	+**Initial members: **Patrick Masson
	13	+
	14	+= Description =
	15	+
	16	+After the various issues with crowd funding campaigns misleading the public related to open source software (think, Anonabox and Jolla Tablet), a [[small/simple survey>>attach:Crowdfunding.ods]] was undertaken on December 2014. The survey queried Kickstarter & Indiegogo on 12/20/2014...
	17	+
	18	+{{code}}
	19	+Kickstarter search: Show me “Software” projects on “Earth” tagged with “#Open source” sorted by “newest”
	20	+Indiegogo: Search results for ""open source"" in "Technology"
	21	+Indiegogo: Search results for ""open source" "software"" in "Technology"
	22	+Indiegogo: Search results for ""open source"" "software"" in "Technology", "75% - 100+%"
	23	+{{/code}}
	24	+
	25	+...and found 85 projects asking for support in the development of "open source" or "open source software."
	26	+
	27	+The total fund raising goal for all 85 projects is $5,086,090, the total committed was $6,664,242.
	28	+
	29	+Of these 85 projects, 46 carried OSI approved licenses and 39 carried either none, or some other license (e.g. CC-BY-SA)~-~-one even was proprietary.
	30	+
	31	+These 39 open washing / fauxpen projects were seeking $2,397,050 and raised, $2,967,167 from almost 30,000 contributors (file attached).
	32	+
	33	+I think there is a role for the OSI here.
	34	+
	35	+First, we should contact Kickstarter, Indiegogo and other crowd-funding sites to help them develop policy around claims of funding for open source projects. This would be a similar effort to working with GitHub on their open source licensing issues. Of course, this implies we should suggest to them a policy on what we believe to be best practices (can we do this?).
	36	+
	37	+Secondly, I think the OSI should reach out to the tech media (letters to editors pointing to a site explaining the issue and suggested approaches) to help them understand the importance of fact checking before promoting these projects. I'll add that just today, the Jolla Tablet and fauxpen SailfishOS was highlighted as how open source projects can succeed in crowd-funding efforts (Slide 3 at http:~/~/www.networkworld.com/article/2865755/opensource-subnet/why-crowdfunding-open-source-projects-isnt-as-easy-as-you-think.html ).
	38	+
	39	+Third, we should promote this activity within the open source communtiy as it highlights the OSI's value in promoting and protecting open source software licensing and develop it. It will also provide us with evidence of practice in explaining our own value proposition~-~-think next year's Annual Report.
	40	+
	41	+I, as an individual, was going to do take this on with a follow up to the open-washing article in opensource.com. But I think it would be much more powerful~-~-and rightly positioned~-~-as an OSI effort.
	42	+\\Comments?
	43	+Patrick\\
	44	+
	45	+
3	3	= Mission =
4	4
5		-Some of the most important organizations in the free, libre, and open source software (FLOSS) community are nonprofit, tax-exempt organizations that depend upon donations from individuals and foundations. Over the past several years, the IRS has denied tax-exempt status to a number new FLOSS organizations, while others have experienced long delays in the processing of their applications. If tax-exempt status becomes difficult or impossible for new FLOSS projects to obtain, the future production of FLOSS for the public benefit could be harmed.
	48	+The working group will work with crowd-funding sites to raise awareness, develop policy and instill good practice to address, the ambiguity in, or mis-representation of projects seeking funding for projects promoted as open source software.
6	6
7		-The FLOSS Entities Working Group will explore how the IRS position toward FLOSS organizations has changed, how these changes affect new and existing FLOSS nonprofits, and what alternatives to independent tax-exempt status are available to new projects. It will also produce informational materials and recommend advocacy initiatives to address this issue.
8	8
	51	+The working group will also reach out to the technology media (letters to editors, comments to articles, original posts, etc.) explaining the issue and suggested approaches to help the press and general public understand the importance of and assess authenticity before promoting projects.
	52	+\\The working group will promote this activity within the open source community as it highlights the OSI's value in promoting and protecting open source software licensing and development.
	53	+
9	9	= Communications =
10	10
11		-The group will primarily communicate via the [[entities-wg@opensource.org mailing list>>url:http://projects.opensource.org/cgi-bin/mailman/listinfo/entities-wg||rel="__blank"]]. It will also hold monthly conference calls, which will be announced on the mailing list.
	56	+The group will primarily communicate via the working group wiki page and related discussion forum.
12	12
13		-If you have questions about the group, please contact [[Aaron Williamson>>mailto:aaron@torekeland.com]], the working group chair, or [[Allison Randal>>mailto:allison@opensource.org]], the working group sponsor.
	58	+If you have questions about the group, please contact [[Patrick Masson>>mailto:masson@opensource.org]], the working group chair and sponsor.
14	14
15	15	= Resources =
16	16
17		-* The working group maintains a [[collection of documentation>>doc:IRS Ruling Documentation]] related to IRS rulings on FLOSS organizations' tax-exempt applications.
18		-* We are working on a [[survey>>doc:FLOSS entities survey]] of FLOSS nonprofits to quantify the needs of the community.
	62	+* Use of the OSI wiki to document our work and communicate through development.
	63	+* Communications through OSI channels (press releases, blog posts, tweets, etc.) related to the working group's activities.
19	19
20		-= Members =
	65	+= Deliverables =
21	21
22		-* Chair: Aaron Williamson
23		-* OSI Sponsor: Allison Randal
24		-* OSI General Manager: Patrick Masson
25		-* Mark Atwood (OpenStack and HP)
26		-* J.D. Bean (Software Freedom Law Center)
27		-* Michael Downey (OpenMRS)
28		-* Justin Erenkrantz (Apache and Bloomberg)
29		-* Eileen Evans (OpenStack Foundation and HP)
30		-* Rosemary Fei (Adler & Colvin)
31		-* Richard Fontana (OSI and HP)
32		-* Bradley Kuhn (Software Freedom Conservancy)
33		-* Carly Leinheiser (Perlman & Perlman)
34		-* John Lewis (Apereo Foundation)
35		-* Jeff McKenna (OSGeo Foundation)
36		-* Martin Michlmayr (HP)
37		-* Mike Milinkovich (Eclipse and OSI)
38		-* Diane Peters (Creative Commons)
39		-* Stephanie Petit (Adler & Colvin)
40		-* Simon Phipps (OSI)
41		-* Mark Radcliffe (DLAPiper)
42		-* Larry Rosen
43		-* Karen Sandler (Software Freedom Conservancy)
44		-* Aaron Wolf (Snowdrift.coop)
	67	+1. Press release explaining the OSI sponsored initiative.
	68	+1. Open letters to the media requesting increased fact checking and suggestions for referencing open source software projects.
	69	+1. Recommendations for crowd-funding sites for the assessment of projects they host that invoke "open source," "open source software" and related terms. (e.g. "[project name] is an open source project released under the [license name]")
	70	+1. Agreements with multiple crowd-funding sites to develop policy and good practice when invoking "open source," "open source software" and related terms in the projects they host.
	71	+1. Reference materials for those interested in supporting projects through crowd-funding to assess the authenticity of claims. (e.g. "Open-by-rule Benchmark, OSS Watch, Openness Index, etc.)
	72	+
	73	+
	74	+