Business Team/Minutes/2011-03-17 - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-02-28T20:52:11Z

Convert to MediaWiki syntax

Kweins at 16:07, 17 March 2011

2011-03-17T16:07:07Z

Kweins at 15:18, 17 March 2011

2011-03-17T15:18:47Z

New page

Attendees
<ul><li>Kim Weins</li><li>Phil Odence</li><li>Kate Stewart</li><li>Gary O'Neall</li><li>Jilayne Lovejoy</li><li>Kirsten Newcomer</li><li>Kamal Hassin</li><li>Mahshad Koohgoli</li><li>Esteban Rockett</li><li>Scott Lamons</li></ul>BMW Questions -- We will add these to the FAQ in the Wiki<ul><li>Q: Do you have to include every file in the SPDX file?</li><li>A: Yes -- although you can define the package to include whatever files you want and can have unknown info</li><li>Q: Is there a way to include notes on on how files are linked?</li><li>A:  There is a free form comment field that can be used for this</li></ul>Kim to add these to FAQ in wiki and broadcast to various listsTraining <ul><li>Business training materials -- Kim started with Beta Orientation deck -- will add stuff as needed</li><li>Technical training materials -- Kim to ping Peter W</li><li>Tools training materials -- Kristen has materials from Gary and will be working on it</li></ul>

@@ Line 1: / Line 1: @@
-<p><strong>Attendees</strong></p>
+== Attendees ==
-<ul><li>Kim Weins</li><li>Phil Odence</li><li>Kate Stewart</li><li>Gary O'Neall</li><li>Jilayne Lovejoy</li><li>Kirsten Newcomer</li><li>Kamal Hassin</li><li>Mahshad Koohgoli</li><li>Esteban Rockett</li><li>Scott Lamons</li></ul><p><strong>BMW Questions</strong> -- We will add these to the FAQ in the Wiki</p><ul><li>Q: Do you have to include every file in the SPDX file?</li><li>A: Yes -- although you can define the package to include whatever files you want and can have unknown info</li><li>Q: Is there a way to include notes on on how files are linked?</li><li>A:&nbsp; There is a free form comment field that can be used for this</li></ul><p>Kim to add these to FAQ in wiki and broadcast to various lists</p><p><strong>Training</strong> </p><ul><li>Business training materials -- Kim started with Beta Orientation deck -- will add stuff as needed</li><li>Technical training materials -- Kim to ping Peter W</li><li>Tools training materials -- Kristen has materials from Gary and will be working on it</li></ul><p>
-<strong>&nbsp;</strong></p><p><strong>Process for Adding New Standard Licenses.</strong></p>
+* Kim Weins
-<p>We did not finish discussion, so will continue at next meeting.&nbsp; Notes so far are below.</p>
+* Phil Odence
-<ul><li>Anyone can request license to be added through a web form (possibly Bugzilla).<ul><li>Protecode might be able to implement web form to integrate to Bugzilla</li></ul></li><li>Information- some will be required fields<br /><ul><li>Person Name</li><li>Email</li><li>Organization - community/company</li><li>License name</li><li>Actual license text</li><li>URL for where they found license text</li><li>Comments -- why they want it</li><li>Example(s) of open source packages/files that use it</li><li>Why they want it -- is it their own license or is it something they have encountered in audits</li><li>Is it going thru OSI approval?</li><li>Other notes or we need to know</li><li>Make application as close to Wiki page as possibe</li></ul></li><li>Process
+* Kate Stewart
-<ul><li>First validation/vetting for complete/correct info - contact person who submitted it</li><li>&nbsp;Decision making by group
+* Gary O'Neall
-<ul><li>Allow comments in a timeline</li><li>Start with an open ended time</li><li>Have business team make decision initially until we see what the volume is
+* Jilayne Lovejoy
-<ul><li>Shoot for doing this first year unless it's getting out of hand</li></ul></li><li>Way to batch it - handle at biz team meetings</li><li>Can have some where we decide to "defer" for now.</li><li>Business team will decide -- likely based on majority vote for people that attended the meeting (at least 5 people and 1 legal)</li><li>Publish the ones we will vote on 2 weeks in advance to full list.&nbsp; Discussion/comments on biz list.
+* Kirsten Newcomer
-<ul><li>Set up a separate wiki page to keep the list tracked of what we are voting on when</li></ul></li></ul></li><li>Later -- Have a more formal committee that makes a decision - 5-7 people
+* Kamal Hassin
-<ul><li>Should have 2 legal spots on community</li><li>Might want at least one community spot</li><li>Nominations (including self nominations) make clear the requirements</li><li>Way to adjust if someone is not participating</li></ul></li><li></li><li>Assignment of standard name<ul><li>Have pilot propose a standard name (short and long) based on our rules</li><li>Review and agree on that when we vote</li></ul></li><li>Data entered into repo and templatizing is done<ul><li>Templatizing should be automated process</li></ul></li><li>Review/QA of the data in the repo<ul><li>Have a legal person look to make sure it's OK and nothing is broken</li></ul></li></ul></li><li>Suggested Criteria
+* Mahshad Koohgoli
-<ul><li>Center of gravity is OSS license but will consider freeware or
+* Esteban Rockett
-other licenses that are widely encountered.&nbsp; For example would consider
+* Scott Lamons
-Sun Binary Licenses.&nbsp; Things that share many/all of OSI attributes -
-but may have additional requirements</li><li>Not for purely commercial licenses (ex EULA, or Oracle license)</li><li>License must be publicly accessible</li><li>License that is seen across multiple projects or on a heavily used project</li><li>License that will be popular in future (eg new version of GPL, Apache)</li></ul></li><li>Need a statement that we don't necessarily consider all these
+== BMW Questions ==
 licenses to be open source - just trying to facilitate a way to refer
-to them.&nbsp; Check how Fedora does this (talk to Spot)</li><li>Who does stuff<ul><li>Could have one person "pilot" assigned to a license and have them follow it through process&nbsp; all the way to finish to put in repo</li><li>List of volunteers willing to be pilots and rotate through that list -- show list on site</li><li>Assign the Bugzilla issue to someone (manually initially) -- Kim will assign names manually</li><li>Automatically send comments to mailing list when bugzilla form is updated</li></ul></li><li>Timeframe
+We will add these to the FAQ in the Wiki
-<ul><li>Will need to set expectations for turnaround time</li><li>Likely a 2-3 month period (rough target -- not a guarantee)<br /><ul><li>2 weeks -- Time to vet</li><li>2 weeks to comment (min)</li><li>2 weeks in advance to schedule a vote</li><li>2-4 weeks to enter in repo and QA after approval</li></ul></li></ul>
-</li></ul>
+* Q: Do you have to include every file in the SPDX file?

← Older revision		Revision as of 16:07, 17 March 2011
Line 2:		Line 2:
	<ul><li>Kim Weins</li><li>Phil Odence</li><li>Kate Stewart</li><li>Gary O'Neall</li><li>Jilayne Lovejoy</li><li>Kirsten Newcomer</li><li>Kamal Hassin</li><li>Mahshad Koohgoli</li><li>Esteban Rockett</li><li>Scott Lamons</li></ul><p><strong>BMW Questions</strong> -- We will add these to the FAQ in the Wiki</p><ul><li>Q: Do you have to include every file in the SPDX file?</li><li>A: Yes -- although you can define the package to include whatever files you want and can have unknown info</li><li>Q: Is there a way to include notes on on how files are linked?</li><li>A:  There is a free form comment field that can be used for this</li></ul><p>Kim to add these to FAQ in wiki and broadcast to various lists</p><p><strong>Training</strong> </p><ul><li>Business training materials -- Kim started with Beta Orientation deck -- will add stuff as needed</li><li>Technical training materials -- Kim to ping Peter W</li><li>Tools training materials -- Kristen has materials from Gary and will be working on it</li></ul><p>		<ul><li>Kim Weins</li><li>Phil Odence</li><li>Kate Stewart</li><li>Gary O'Neall</li><li>Jilayne Lovejoy</li><li>Kirsten Newcomer</li><li>Kamal Hassin</li><li>Mahshad Koohgoli</li><li>Esteban Rockett</li><li>Scott Lamons</li></ul><p><strong>BMW Questions</strong> -- We will add these to the FAQ in the Wiki</p><ul><li>Q: Do you have to include every file in the SPDX file?</li><li>A: Yes -- although you can define the package to include whatever files you want and can have unknown info</li><li>Q: Is there a way to include notes on on how files are linked?</li><li>A:  There is a free form comment field that can be used for this</li></ul><p>Kim to add these to FAQ in wiki and broadcast to various lists</p><p><strong>Training</strong> </p><ul><li>Business training materials -- Kim started with Beta Orientation deck -- will add stuff as needed</li><li>Technical training materials -- Kim to ping Peter W</li><li>Tools training materials -- Kristen has materials from Gary and will be working on it</li></ul><p>

−	<strong> </strong></p>	+	<strong> </strong></p><p><strong>Process for Adding New Standard Licenses.</strong></p>
		+	<p>We did not finish discussion, so will continue at next meeting.  Notes so far are below.</p>
		+	<ul><li>Anyone can request license to be added through a web form (possibly Bugzilla).<ul><li>Protecode might be able to implement web form to integrate to Bugzilla</li></ul></li><li>Information- some will be required fields<br /><ul><li>Person Name</li><li>Email</li><li>Organization - community/company</li><li>License name</li><li>Actual license text</li><li>URL for where they found license text</li><li>Comments -- why they want it</li><li>Example(s) of open source packages/files that use it</li><li>Why they want it -- is it their own license or is it something they have encountered in audits</li><li>Is it going thru OSI approval?</li><li>Other notes or we need to know</li><li>Make application as close to Wiki page as possibe</li></ul></li><li>Process
		+	<ul><li>First validation/vetting for complete/correct info - contact person who submitted it</li><li> Decision making by group
		+	<ul><li>Allow comments in a timeline</li><li>Start with an open ended time</li><li>Have business team make decision initially until we see what the volume is
		+	<ul><li>Shoot for doing this first year unless it's getting out of hand</li></ul></li><li>Way to batch it - handle at biz team meetings</li><li>Can have some where we decide to "defer" for now.</li><li>Business team will decide -- likely based on majority vote for people that attended the meeting (at least 5 people and 1 legal)</li><li>Publish the ones we will vote on 2 weeks in advance to full list.  Discussion/comments on biz list.
		+	<ul><li>Set up a separate wiki page to keep the list tracked of what we are voting on when</li></ul></li></ul></li><li>Later -- Have a more formal committee that makes a decision - 5-7 people
		+	<ul><li>Should have 2 legal spots on community</li><li>Might want at least one community spot</li><li>Nominations (including self nominations) make clear the requirements</li><li>Way to adjust if someone is not participating</li></ul></li><li></li><li>Assignment of standard name<ul><li>Have pilot propose a standard name (short and long) based on our rules</li><li>Review and agree on that when we vote</li></ul></li><li>Data entered into repo and templatizing is done<ul><li>Templatizing should be automated process</li></ul></li><li>Review/QA of the data in the repo<ul><li>Have a legal person look to make sure it's OK and nothing is broken</li></ul></li></ul></li><li>Suggested Criteria
		+	<ul><li>Center of gravity is OSS license but will consider freeware or
		+	other licenses that are widely encountered.  For example would consider
		+	Sun Binary Licenses.  Things that share many/all of OSI attributes -
		+	but may have additional requirements</li><li>Not for purely commercial licenses (ex EULA, or Oracle license)</li><li>License must be publicly accessible</li><li>License that is seen across multiple projects or on a heavily used project</li><li>License that will be popular in future (eg new version of GPL, Apache)</li></ul></li><li>Need a statement that we don't necessarily consider all these
		+	licenses to be open source - just trying to facilitate a way to refer
		+	to them.  Check how Fedora does this (talk to Spot)</li><li>Who does stuff<ul><li>Could have one person "pilot" assigned to a license and have them follow it through process  all the way to finish to put in repo</li><li>List of volunteers willing to be pilots and rotate through that list -- show list on site</li><li>Assign the Bugzilla issue to someone (manually initially) -- Kim will assign names manually</li><li>Automatically send comments to mailing list when bugzilla form is updated</li></ul></li><li>Timeframe
		+	<ul><li>Will need to set expectations for turnaround time</li><li>Likely a 2-3 month period (rough target -- not a guarantee)<br /><ul><li>2 weeks -- Time to vet</li><li>2 weeks to comment (min)</li><li>2 weeks in advance to schedule a vote</li><li>2-4 weeks to enter in repo and QA after approval</li></ul></li></ul>
		+	</li></ul>