Date   

SPDX Beta Feedback (and Web Site Redesign)

Kim Weins
 

9:00 AM - 10:30 AM July 7, 2011
Location: See below

This replaces our biz team meeting on this day.  We'd like participation
from tech and legal teams to.

First hour will be Beta feedback
Last half hour will be review of ideas from team working on Web Site
redesign

Kim


US  866-740-1260
Int'l  http://www.readytalk.com/support/international-numbers.php

ID 2404502

Web Meeting
Www.readytalk.com
ID 2404502


Cancelled: SPDX Business (Rollout) Call 11ET/8PT

Kim Weins
 

We will replace this meeting with Beta feedback meeting for this one date.

Kim

-----



US  866-740-1260
Int'l  http://www.readytalk.com/support/international-numbers.php

ID 2404502

Web Meeting
Www.readytalk.com
ID 2404502

Agenda
We will be covering several areas on the rollout plan.

1. Beta process
2. User Content - what is needed
3. Evangelism and outreach


SPDX Beta Feedback Meeting on Jul 7

Kim Weins
 

Hi all

We will have a call to review all of the SPDX Beta feedback on Jul 7 at 11 ET/8PT.    We will try to get all of the Beta participants on the call.  In advance of the call, we will try to get Beta feedback sent out on the email lists.  I’m inviting all of the teams, since it will be important to have representation from all the workstreams.

This will replace the Business call for that date.  We will also extend the time by a half hour so that we can also cover feedback from the website redesign team.

Look for the invite, and please attend!

Kim







Kim Weins |
Senior Vice President, Marketing
kim.weins@...
Follow me on Twitter @KimAtOpenLogic

650 279 0410  |  cell
www.openlogic.com
Follow OpenLogic on Twitter @openlogic


Updated Invitation: SPDX Legal Workstream Call 11ET/10CT/8PT @ Wed Jun 22 8am - 9am (spdx@fossbazaar.org)

Esteban Rockett <mgia3940@...>
 

This event has been changed.

SPDX Legal Workstream Call 11ET/10CT/8PT

Changed: All:

Due to the Linux Foundation Member Counsel Meeting, I am moving this to next week

Many thanks,

Rockett

Motorola Inc.
E.A. Rockett
Senior Counsel
Software, Applications &
Digital Content Licensing
(408)541-6703 (O)
(408)541-6900 (F)
(415)508-7625 (M)
rockett@...

When
Changed: Wed Jun 22 8am – 9am Pacific Time
Where
Conference Bridge 1.877.825.8522 PIN:0376146 (map)
Calendar
spdx@...
Who
mgia3940@... - organizer
amanda.brock@... - creator
tony.gomes@...
sadams@...
feb.cabrasawan@...
jmcbroom@...
rfontana@...
linda.shih@...
Alexandra.Siegel@...
mpierovi@...
kathleen.mullins@...
JOHN ELLIS
rtiller@...
alastern@...
Mikko.Amper@...
adcohn@...
paul.madick@...
ilardi@...
areid@...
tom.incorvia@...
Mansour Ghomeshi
smortin@...
owen.james.boyle@...
scott.k.peterson@...
Guy.Colpitts@...
bgieseman@...
pmcbride@...
spaek@...
tcarlson@...
andrew.wilson@...
barbara.reilly@...
jwacha@...
bkahin@...
vmah@...
andrew.updegrove@...
mrc@...
mccoy.smith@...
ssemel@...
gsjones@...
kcopenhaver@...
spdx-legal-request@...
spdx@...

Going?   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account spdx@... because you are an attendee of this event.

To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.


Thursday SPDX General Meeting

Philip Odence
 

Apologies, but once again, I have a conflict and will not be able to join, however Kirsten will (once again) do a fine job chairing in my absence. In addition to reviewing the minutes from the last meeting, please also read over the License Field discussion prior to the meeting http://www.spdx.org/wiki/license-field-discussion.


Meeting Time: June 16, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be found: 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

 
Administrative Agenda
Attendance
Technical Team Report - Kate

Business Team Report - Kim

Legal Team Report - Rockett/Karen


Cross Functional Issues – Discussion
Website update- Kirsten/Pierre/Steve
License Field Discussion from Wiki


License Field Discussion

Philip Odence
 

There have been multiple discussions in different working groups about the nomenclature, meaning and intent of the package license fields. To ensure we are all on the right page, we want ot have some wiki-based discussion about the fields with perhaps some examples and use cases tha that we can capture for documentation, FAQs, etc. We may need to go thru this same exercise at the file level, but let's start here.
Go to:

We look forward to your comments on the Wiki.




Beyond copyright/licensing ?

Olivier Berger <olivier.berger@...>
 

Hi.

(I'm new here, so pardon me if this is some kind of FAQ.)

The SPDX acronym looks quite general, and the charter doesn't seem to
limit itself to licensing/copyright matters.

However, looking at the material online, it seems to me that it is the
main area of development of SPDX.

Are there other matters on the work bench ? For instance, I'm working on
standardization of the interfaces of tools used by FLOSS developers, and
SPDX looks like a major stepping stone for fostering interoperability in
the development / QA process, just as it provides a clean reference for
identification of packages (licensing issues aside). Think about tracing
which distribution packages contain copies of a particular version of a
package that exhibits a bug, etc.

Is there a summary of the different other aspects SPDX will be
addressing, after 1.0, beyond licensing ?

Thanks in advance.

Best regards,
--
Olivier BERGER <olivier.berger@...>
http://www-public.it-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingénieur Recherche - Dept INF
Institut TELECOM, SudParis (http://www.it-sudparis.eu/), Evry (France)


Re: Update on spdx subscriber numbers

Martin Michlmayr
 

Here's another update on the mailing list numbers:

spdx: 105
spdz-biz: 21
spdx-legal: 29
spdx-tech: 26

--
Martin Michlmayr
Open Source Program Office, Hewlett-Packard


SPDX as description for binary deliverables containing OSS artifacts

Mario Tokarz <mario@...>
 

Hi everyone,

this is a spin off of a discussion I was having with Peter and Garry
on the tech mailing list. I am considering how SPDX could form the
basis for the following example use case:

Customer A ordering a software with company B. B's software is closed
source but contains one file under 3-clause BSD. When A gets the
executable he may still have 'open source obligations' (like
e.g. non-endorsement) from the software even though not actually
receiving code. In fact in the scenario outlined here A might not even
be entitled to ever see/receive that sourcecode.

Still A of course needs to know about the licenses in play (besides
those agreed on between A and B upfront) and he might also want to
know about possible copyright holders.

So, I think what I am describing here can be clearly achieved with a
subset of SPDX, as your work has been really diligent. So I would like
to discuss with you
* whether the usecase makes sense, needs amendment or whether there
are similar use cases that I did not address here which could be
relevant as well
* how such a subset could look like. A subset would necessarily imply
changed cardinalities in the SPDX Spec and this would need to be part
of SPDX tooling in the long run. This is why I think one could also
describe this as an "SPDX Profile".


I may still need some time for this, but I can offer to come up with a
draft for requirement and then also a subset if this is something you
feel SPDX could support.

Best regards,
Mario

--
BMW Car IT GmbH
http://www.bmw-carit.de


Re: Licensing Workshop at LinuxTag 2011 (XML errors)

Jilayne Lovejoy <jilayne.lovejoy@...>
 

Yes, I have added this to my list of updates for the next license list
spreadsheet version.

This also makes me wonder if there are other "older" licenses that were OSI
certified and I may have missed, so I'll check the list of such licenses on
the OSI website against our list to be consistent.




On 5/31/11 8:12 AM, "Martin Michlmayr" <tbm@...> wrote:

* Joerg Schilling <Joerg.Schilling@...> [2011-05-26 10:25]:
BTW: Could you add a OSI tag to http://spdx.org/licenses/CPL-1.0?
This license is superceeded but it is used for the korn shell and other AT&T
software and for this reason, it is important to see that it is OSI approved.
Jilayne, are you the right person to take care of this?

For the overview table http://spdx.org/licenses/ it would also be
nice to have a one character marker column that flags wether a
license is OSI approved or not.
Gary, is this something you can add to your tool?
Jilayne Lovejoy | Corporate Counsel
jlovejoy@...

720 240 4545 | phone
720 240 4556 | fax
1 888 OpenLogic | toll free
www.openlogic.com

OpenLogic, Inc.
10910 W 120th Ave, Suite 450
Broomfield, Colorado 80021


Re: Licensing Workshop at LinuxTag 2011 (XML errors)

Jilayne Lovejoy <jilayne.lovejoy@...>
 

I will make sure the appropriate change is included in the next version of
the license list spreadsheet, which should be relatively soon!

Jilayne


On 5/31/11 8:12 AM, "Martin Michlmayr" <tbm@...> wrote:

* Joerg Schilling <Joerg.Schilling@...> [2011-05-26 10:25]:
BTW: Could you add a OSI tag to http://spdx.org/licenses/CPL-1.0?
This license is superceeded but it is used for the korn shell and other AT&T
software and for this reason, it is important to see that it is OSI approved.
Jilayne, are you the right person to take care of this?

For the overview table http://spdx.org/licenses/ it would also be
nice to have a one character marker column that flags wether a
license is OSI approved or not.
Gary, is this something you can add to your tool?
Jilayne Lovejoy | Corporate Counsel
jlovejoy@...

720 240 4545 | phone
720 240 4556 | fax
1 888 OpenLogic | toll free
www.openlogic.com

OpenLogic, Inc.
10910 W 120th Ave, Suite 450
Broomfield, Colorado 80021


Re: Licensing Workshop at LinuxTag 2011 (XML errors)

Gary O'Neall
 

I added 2 bugs in bugzilla:

-          Bug 811 -Produce an archive of license texts for SPDX licenses

-          Bug 812 -Add a column to the index of licenses to indicate if a license is OSI approved

 

I assigned the latter bug to myself.  I’ll take a look at this after Beta.

 

Gary

 

From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Esteban Rockett
Sent: Wednesday, June 01, 2011 7:40 AM
To: dmg
Cc: Jilayne Lovejoy; cdenicolo@...; sebastian@...; jmbsvicetto@...; Joerg Schilling; hoefel@...; vuntz@...; fatih@...; misc@...; zack@...; amanda.brock@...; n-roeser@...; spdx@...; jsstewar@...
Subject: Re: Licensing Workshop at LinuxTag 2011 (XML errors)

 

agreed.

On Tue, May 31, 2011 at 9:36 AM, dmg <dmg@...> wrote:

Hi Martin,

it will also help to have a simple tar file with all the licenses,
each in its own file, and without the HTML tagging.
Basically, the actual text of the license.

--dmg


On Tue, May 31, 2011 at 7:12 AM, Martin Michlmayr <tbm@...> wrote:
> * Joerg Schilling <Joerg.Schilling@...> [2011-05-26 10:25]:
>> BTW: Could you add a OSI tag to http://spdx.org/licenses/CPL-1.0?
>
>> This license is superceeded but it is used for the korn shell and other AT&T
>> software and for this reason, it is important to see that it is OSI approved.
>
> Jilayne, are you the right person to take care of this?
>
>> For the overview table http://spdx.org/licenses/ it would also be
>> nice to have a one character marker column that flags wether a
>> license is OSI approved or not.
>
> Gary, is this something you can add to your tool?
>
> --
> Martin Michlmayr
> Open Source Program Office, Hewlett-Packard
> _______________________________________________
> Spdx mailing list
> Spdx@...
> https://fossbazaar.org/mailman/listinfo/spdx
>


--
--dmg

---
Daniel M. German
http://turingmachine.org

_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx




--
Motorola Inc.
E.A. Rockett
Senior Counsel
Software, Applications &
Digital Content Licensing
(408)541-6703 (O)
(408)541-6900 (F)
(415)508-7625 (M)
rockett@...


Thursday SPDX General Meeting Reminder and Agenda.

Philip Odence
 

I have a conflict and will not be able to join, however Kirsten will do a fine job chairing in my absence..

Meeting Time: June 2, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html

Conf call dial-in:
Conference code:  7812589502
Toll-free dial-in number (U.S. and Canada):  (877) 435-0230
International dial-in number: (253) 336-6732
For those dialing in from other regions, a list of toll free numbers can be found: 
https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF

 
Administrative Agenda
Attendance
Technical Team Report - Kate

Business Team Report - Kim

Legal Team Report - Rockett/Karen


Cross Functional Issues – Discussion
Website update- Kirsten/Pierre/Steve

Action Items


  • MartinM- Report back on # of people on respective mailing lists. ONGOING

New

  • Kirsten- Notify Kim of need to clean up business section of website.
  • MartinM- Get master list of website pages to Kate
  • Legal/Biz Teams- Review and update Master Schedule


Re: Licensing Workshop at LinuxTag 2011 (XML errors)

Esteban Rockett <mgia3940@...>
 

agreed.


On Tue, May 31, 2011 at 9:36 AM, dmg <dmg@...> wrote:
Hi Martin,

it will also help to have a simple tar file with all the licenses,
each in its own file, and without the HTML tagging.
Basically, the actual text of the license.

--dmg

On Tue, May 31, 2011 at 7:12 AM, Martin Michlmayr <tbm@...> wrote:
> * Joerg Schilling <Joerg.Schilling@...> [2011-05-26 10:25]:
>> BTW: Could you add a OSI tag to http://spdx.org/licenses/CPL-1.0?
>
>> This license is superceeded but it is used for the korn shell and other AT&T
>> software and for this reason, it is important to see that it is OSI approved.
>
> Jilayne, are you the right person to take care of this?
>
>> For the overview table http://spdx.org/licenses/ it would also be
>> nice to have a one character marker column that flags wether a
>> license is OSI approved or not.
>
> Gary, is this something you can add to your tool?
>
> --
> Martin Michlmayr
> Open Source Program Office, Hewlett-Packard
> _______________________________________________
> Spdx mailing list
> Spdx@...
> https://fossbazaar.org/mailman/listinfo/spdx
>



--
--dmg

---
Daniel M. German
http://turingmachine.org
_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx



--
Motorola Inc.
E.A. Rockett
Senior Counsel
Software, Applications &
Digital Content Licensing
(408)541-6703 (O)
(408)541-6900 (F)
(415)508-7625 (M)
rockett@...


Re: Licensing Workshop at LinuxTag 2011 (XML errors)

dmg
 

Hi Martin,

it will also help to have a simple tar file with all the licenses,
each in its own file, and without the HTML tagging.
Basically, the actual text of the license.

--dmg

On Tue, May 31, 2011 at 7:12 AM, Martin Michlmayr <tbm@...> wrote:
* Joerg Schilling <Joerg.Schilling@...> [2011-05-26 10:25]:
BTW: Could you add a OSI tag to http://spdx.org/licenses/CPL-1.0?
This license is superceeded but it is used for the korn shell and other AT&T
software and for this reason, it is important to see that it is OSI approved.
Jilayne, are you the right person to take care of this?

For the overview table http://spdx.org/licenses/ it would also be
nice to have a one character marker column that flags wether a
license is OSI approved or not.
Gary, is this something you can add to your tool?

--
Martin Michlmayr
Open Source Program Office, Hewlett-Packard
_______________________________________________
Spdx mailing list
Spdx@...
https://fossbazaar.org/mailman/listinfo/spdx
--
--dmg

---
Daniel M. German
http://turingmachine.org


Re: Licensing Workshop at LinuxTag 2011 (XML errors)

Esteban Rockett <mgia3940@...>
 

Jilayne - lets discuss at your convinence. (today if possible)

Rockett


On Tue, May 31, 2011 at 7:12 AM, Martin Michlmayr <tbm@...> wrote:
* Joerg Schilling <Joerg.Schilling@...> [2011-05-26 10:25]:
> BTW: Could you add a OSI tag to http://spdx.org/licenses/CPL-1.0?

> This license is superceeded but it is used for the korn shell and other AT&T
> software and for this reason, it is important to see that it is OSI approved.

Jilayne, are you the right person to take care of this?

> For the overview table http://spdx.org/licenses/ it would also be
> nice to have a one character marker column that flags wether a
> license is OSI approved or not.

Gary, is this something you can add to your tool?

--
Martin Michlmayr
Open Source Program Office, Hewlett-Packard
_______________________________________________



--
Motorola Inc.
E.A. Rockett
Senior Counsel
Software, Applications &
Digital Content Licensing
(408)541-6703 (O)
(408)541-6900 (F)
(415)508-7625 (M)
rockett@...


Re: Licensing Workshop at LinuxTag 2011 (XML errors)

Martin Michlmayr
 

* Joerg Schilling <Joerg.Schilling@...> [2011-05-26 10:25]:
BTW: Could you add a OSI tag to http://spdx.org/licenses/CPL-1.0?
This license is superceeded but it is used for the korn shell and other AT&T
software and for this reason, it is important to see that it is OSI approved.
Jilayne, are you the right person to take care of this?

For the overview table http://spdx.org/licenses/ it would also be
nice to have a one character marker column that flags wether a
license is OSI approved or not.
Gary, is this something you can add to your tool?

--
Martin Michlmayr
Open Source Program Office, Hewlett-Packard


OSI adopts SPDX short names

Philip Odence
 


Re: Licensing Workshop at LinuxTag 2011 (XML errors)

Joerg Schilling <Joerg.Schilling@...>
 

Martin Michlmayr <tbm@...> wrote:

I've put the update in place now. However, the issues pointed out by
Juergen and Joerg are different to the known issue. I've fixed the
issues up manually now and verified that all licenses parse properly.
I'll work with Gary offline to make sure his tools get updated.
Thank you!

BTW: Could you add a OSI tag to http://spdx.org/licenses/CPL-1.0?

This license is superceeded but it is used for the korn shell and other AT&T
software and for this reason, it is important to see that it is OSI approved.

For the overview table http://spdx.org/licenses/ it would also be nice to have
a one character marker column that flags wether a license is OSI approved or
not.

Jörg

--
EMail:joerg@... (home) Jörg Schilling D-13353 Berlin
js@... (uni)
joerg.schilling@... (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily


Re: Licensing Workshop at LinuxTag 2011 (XML errors)

Martin Michlmayr
 

* Gary O'Neall <gary@...> [2011-05-25 18:05]:
Thanks for pointing out the errors. I believe this is a known encoding
error which should be fixed when we next update the licenses. This will be
fixed on the next update. We don't have a specific date for the next update
but it should be less than a week from now.
I've put the update in place now. However, the issues pointed out by
Juergen and Joerg are different to the known issue. I've fixed the
issues up manually now and verified that all licenses parse properly.
I'll work with Gary offline to make sure his tools get updated.

--
Martin Michlmayr
Open Source Program Office, Hewlett-Packard