FLOSS Entities Working Group Proposal

The group needs a mailing list, which has already been created at [[entities-wg@opensource.org>>url:http://projects.opensource.org/cgi-bin/mailman/listinfo/entities-wg||rel="__blank"]].

41

42

The group may use the OSI wiki for works in progress, and may at a later date need a page on the main opensource.org website to host a set of whitepapers, or other informational publications.

43

44

We will partly rely on pro-bono work from several open source lawyers, but in addition will hire some legal resources to ensure dedicated attention. Our target budget is $50k for 12 months, which works out to about $20k for the remainder of 2014. Some funding will come from OSI, but also from OSI affiliates, and other sources. The current proposal is to start with a 2 month pilot budget from OSI, for work to proceed while seeking additional funding.

45

46

= Deliverable that will be created =

47

48

The group plans to produce documentation benefitting several audiences:

49

50

* For FLOSS projects: educational material (such as wiki documentation) on their options for formalizing a supporting entity for their development and community activities.

51

* For the wider community and established organizations: informational material on the results of our research into the IRS's recent responses and current stance on FLOSS non-profit entities.

52

* For the IRS: educational material (such as whitepapers) on the nature of FLOSS non-profit activities

53

54

= Description of how that deliverable satisfies a part of OSI's mission =

55

56

This working group is aligned with the OSI's misson to promote and protect Open Source, especially focusing on the "protect" aspects. Applying for 501(c)(3) or (c)(6) status has become the norm for new FLOSS projects. If that route were no longer feasible, it could result in serious harm to the future growth of Open Source. It is critical both to research the recent responses from the IRS and determine if we are in the midst of a trend-shift, and to explore alternatives to IRS 501(c) status for young projects.

57

58

= Target completion date =

59

60

We are planning a 12-month run of the working group, covering the core research and discussion topics, and for completion of the listed deliverables. After 12 months, we will evaluate next steps for the group.

Wiki source code of FLOSS Entities Working Group Proposal

Applications

Navigation

author	version	line-number	content
		1	{{toc/}}
		2
		3	= Start date =
		4
		5	The first meeting of the group was held on July 21st, at OSCON (prior to the official formation of a working group).
		6
		7	The official start date will be the first meeting after the charter is approved (late August or early September).
		8
		9	= Initial members =
		10
		11	Working Group Chair: Aaron Williamson
		12
		13	Working Group Sponsor: Allison Randal
		14
		15	OSI General Manager: Patrick Masson
		16
		17	Other Contributors:
		18
		19	* Aaron Wolf (Snowdrift)
		20	* Bradley Kuhn (Software Freedom Conservancy)
		21	* Diane Peters (Creative Commons)
		22	* Eileen Evans (OpenStack Foundation and HP)
		23	* Jeff McKenna (OSGeo Foundation)
		24	* John Lewis (Apereo Foundation)
		25	* Justin Erenkrantz (Apache and Bloomberg)
		26	* Karen Sandler (Software Freedom Conservancy)
		27	* Larry Rosen
		28	* Mark Atwood (OpenStack and HP)
		29	* Mark Radcliffe (DLAPiper)
		30	* Martin Michlmayr (HP)
		31	* Mike Milinkovich (Eclipse and OSI)
		32	* Michael Downey (OpenMRS)
		33	* Richard Fontana (OSI and Red Hat)
		34	* Rosemary Fei (Adler & Colvin)
		35	* Simon Phipps (OSI)
		36	* Stephanie Petit (Adler & Colvin)\\
		37
		38	= Resources needed by group =
		39
		40	The group needs a mailing list, which has already been created at [[entities-wg@opensource.org>>url:http://projects.opensource.org/cgi-bin/mailman/listinfo/entities-wg\|\|rel="__blank"]].
		41
		42	The group may use the OSI wiki for works in progress, and may at a later date need a page on the main opensource.org website to host a set of whitepapers, or other informational publications.
		43
		44	We will partly rely on pro-bono work from several open source lawyers, but in addition will hire some legal resources to ensure dedicated attention. Our target budget is $50k for 12 months, which works out to about $20k for the remainder of 2014. Some funding will come from OSI, but also from OSI affiliates, and other sources. The current proposal is to start with a 2 month pilot budget from OSI, for work to proceed while seeking additional funding.
		45
		46	= Deliverable that will be created =
		47
		48	The group plans to produce documentation benefitting several audiences:
		49
		50	* For FLOSS projects: educational material (such as wiki documentation) on their options for formalizing a supporting entity for their development and community activities.
		51	* For the wider community and established organizations: informational material on the results of our research into the IRS's recent responses and current stance on FLOSS non-profit entities.
		52	* For the IRS: educational material (such as whitepapers) on the nature of FLOSS non-profit activities
		53
		54	= Description of how that deliverable satisfies a part of OSI's mission =
		55
		56	This working group is aligned with the OSI's misson to promote and protect Open Source, especially focusing on the "protect" aspects. Applying for 501(c)(3) or (c)(6) status has become the norm for new FLOSS projects. If that route were no longer feasible, it could result in serious harm to the future growth of Open Source. It is critical both to research the recent responses from the IRS and determine if we are in the midst of a trend-shift, and to explore alternatives to IRS 501(c) status for young projects.
		57
		58	= Target completion date =
		59
		60	We are planning a 12-month run of the working group, covering the core research and discussion topics, and for completion of the listed deliverables. After 12 months, we will evaluate next steps for the group.