|
Re: Mailing list archive
Peter,
I'm responsible for the hierarchy, so I'll weigh in. I'd rather change the name to "Getting Started" or something like that (if it's the "Guidelines" that bothers you) rather than moving it. I
Peter,
I'm responsible for the hierarchy, so I'll weigh in. I'd rather change the name to "Getting Started" or something like that (if it's the "Guidelines" that bothers you) rather than moving it. I
|
By
Philip Odence
·
#117
·
|
|
Re: Mailing list archive
Does anyone object to moving the content of <http://www.spdx.org/wiki/spdx/participation-guidelines> to the main participation page, <http://www.spdx.org/node/2240>? A page named "guidelines" seems
Does anyone object to moving the content of <http://www.spdx.org/wiki/spdx/participation-guidelines> to the main participation page, <http://www.spdx.org/node/2240>? A page named "guidelines" seems
|
By
Peter Williams <peter.williams@...>
·
#116
·
|
|
Re: Some SPDX 1.0 beta examples
This is good. It can start some discussion on the standard.
First, one question:
I scanned the file for zlib and I found some issues with it, but I
think are worth discussing:
1. Some files do not
This is good. It can start some discussion on the standard.
First, one question:
I scanned the file for zlib and I found some issues with it, but I
think are worth discussing:
1. Some files do not
|
By
dmg
·
#115
·
|
|
Re: Mailing list archive
Actually I was replying to Peter's question. I guess that your mail
client might not have shown that it was a reply.
But, to actually make it a question: is there an archive available of
the period
Actually I was replying to Peter's question. I guess that your mail
client might not have shown that it was a reply.
But, to actually make it a question: is there an archive available of
the period
|
By
Armijn Hemel <armijn@...>
·
#114
·
|
|
Re: Mailing list archive
Sweet, thanks. I added a link to the participation guidelines page in the wiki. Hopefully one more link will make google pick it up.
Peter
Sweet, thanks. I added a link to the participation guidelines page in the wiki. Hopefully one more link will make google pick it up.
Peter
|
By
Peter Williams <peter.williams@...>
·
#113
·
|
|
Re: Mailing list archive
Armijn,
Now that you have appeared in the NY Times with a Boston Red Sox hat http://www.nytimes.com/2010/09/26/business/26ping.html?src=busln, I feel I must respond quickly.
There are a number of
Armijn,
Now that you have appeared in the NY Times with a Boston Red Sox hat http://www.nytimes.com/2010/09/26/business/26ping.html?src=busln, I feel I must respond quickly.
There are a number of
|
By
Philip Odence
·
#112
·
|
|
Re: Mailing list archive
https://fossbazaar.org/pipermail/spdx/
armijn
--
---------------------------------------------------------------------------
armijn@... || http://www.gpl-violations.org/
https://fossbazaar.org/pipermail/spdx/
armijn
--
---------------------------------------------------------------------------
armijn@... || http://www.gpl-violations.org/
|
By
Armijn Hemel <armijn@...>
·
#111
·
|
|
Mailing list archive
Is the spdx mailing list archived anywhere? I was looking to read up on the past debate around a particular part of the spec and I was unable to locate an archive of the mailing list.
It is crucial
Is the spdx mailing list archived anywhere? I was looking to read up on the past debate around a particular part of the spec and I was unable to locate an archive of the mailing list.
It is crucial
|
By
Peter Williams <peter.williams@...>
·
#110
·
|
|
Re: Some SPDX 1.0 beta examples
I moved it to
Home » Wiki » Software Package Data Exchange (SPDX) » Spec Development » Sandbox For Sharing Examples, Ideas, Etc.
Not sure if it way my knowledge or permissions or both, but
I moved it to
Home » Wiki » Software Package Data Exchange (SPDX) » Spec Development » Sandbox For Sharing Examples, Ideas, Etc.
Not sure if it way my knowledge or permissions or both, but
|
By
Philip Odence
·
#109
·
|
|
Some SPDX 1.0 beta examples
Hi all,
I have posted some examples, along with some notes about them at <http://spdx.org/wiki/openlogic-spdx-10-beta-examples>. The examples are intended to conform to the 1.0 beta version of the
Hi all,
I have posted some examples, along with some notes about them at <http://spdx.org/wiki/openlogic-spdx-10-beta-examples>. The examples are intended to conform to the 1.0 beta version of the
|
By
Peter Williams <peter.williams@...>
·
#108
·
|
|
SPDX RDF Sub-group Mtg 4 concall / gotomeeting details
Colleagues,
Sorry for sending out the call-in details late.
The call will be at the usual Tuesday time the RDF subgroup has been
meeting the last 3 weeks.
We'll be discussing mechanism for
Colleagues,
Sorry for sending out the call-in details late.
The call will be at the usual Tuesday time the RDF subgroup has been
meeting the last 3 weeks.
We'll be discussing mechanism for
|
By
Bill Schineller
·
#107
·
|
|
Minutes from Sept 23 SPDX call
L. Philip Odence
Vice President of Business Development
Black Duck Software, inc.
265 Winter Street, Waltham, MA 02451
Phone: 781.810.1819, Mobile:
L. Philip Odence
Vice President of Business Development
Black Duck Software, inc.
265 Winter Street, Waltham, MA 02451
Phone: 781.810.1819, Mobile:
|
By
Philip Odence
·
#106
·
|
|
Re: HTML Spec page weird look on spdx.org
Kate is doing her best to fix it up asap.
Kate is doing her best to fix it up asap.
|
By
Philip Odence
·
#105
·
|
|
HTML Spec page weird look on spdx.org
All:
this is most likely a known problem, but the draft web page for the spec at http://www.spdx.org/wiki/spdx/specification seems to be quite hard to read (many empty lines), the paragraph numbers
All:
this is most likely a known problem, but the draft web page for the spec at http://www.spdx.org/wiki/spdx/specification seems to be quite hard to read (many empty lines), the paragraph numbers
|
By
Philippe Ombredanne
·
#104
·
|
|
Re: Spec comments and suggestions
Good point on the copyright holder/copyright information. We could have all
of the copyrights combined in one field - e.g. if a file or package has 3
copyrights A, B, and C - we could have a single
Good point on the copyright holder/copyright information. We could have all
of the copyrights combined in one field - e.g. if a file or package has 3
copyrights A, B, and C - we could have a single
|
By
Gary O'Neall
·
#103
·
|
|
Spec comments and suggestions
Hello All,
I am getting up to speed, have taken a close look at the current spec,
and have some comments noted below.
3.4 Download URL
COMMENT: We may want to have some guideline as to which
Hello All,
I am getting up to speed, have taken a close look at the current spec,
and have some comments noted below.
3.4 Download URL
COMMENT: We may want to have some guideline as to which
|
By
Jilayne Lovejoy <Jlovejoy@...>
·
#102
·
|
|
SPDX - License List Discussion (special topic call on 9/24 at 11MT/12CT/13ET, )
Hi,
Following up from last week and from SPDX call today,
we'll be having a special topic call tomorrow on the licenses.
Here's the dial in information for the call tomorrow:
US
Hi,
Following up from last week and from SPDX call today,
we'll be having a special topic call tomorrow on the licenses.
Here's the dial in information for the call tomorrow:
US
|
By
kate.stewart@...
·
#101
·
|
|
launchpad.net RDF
All:
as discussed during today's call here are some pointers to Launchpad RDF:
This is an example of a project page:
https://launchpad.net/do
and the matching RDF
All:
as discussed during today's call here are some pointers to Launchpad RDF:
This is an example of a project page:
https://launchpad.net/do
and the matching RDF
|
By
Philippe Ombredanne
·
#100
·
|
|
SPDX field Proposal: Optional SPDX author comment field.
Issue: Not clear how to include SPDX author commentsto the consumers of the SPDX file. For example, a SPDX author may like toinclude a disclaimer, assumptions made, context of the analysis performed
Issue: Not clear how to include SPDX author commentsto the consumers of the SPDX file. For example, a SPDX author may like toinclude a disclaimer, assumptions made, context of the analysis performed
|
By
Mark Gisi
·
#99
·
|
|
Agenda for Sept 23 call
Meeting Time: Sept 23, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC
Conf call dial-in:
Conference code: 7812589502
Toll-free dial-in number (U.S. and Canada): (877) 435-0230
International dial-in
Meeting Time: Sept 23, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC
Conf call dial-in:
Conference code: 7812589502
Toll-free dial-in number (U.S. and Canada): (877) 435-0230
International dial-in
|
By
Philip Odence
·
#98
·
|