I've created a new mailing list for SPDX which is public for everyone and for which public archives are available. I've subscribed everyone from the package-facts list to this new list. The address

More good. (although he should have mentioned Kate.) http://m.zdnet.com/blog/open-source/linux-foundation-launches-license-compliance-effort/7063?tag=mantle_skin;content

I uploaded the pretty printer java program to the sourceauditor ftp server. It’s a secure web server, so I apologize in advance if it’sa bit inconvenient to download. The ftp server is at

Hello spdx mailing list I guess I am the first new subscriber, since you went public? My name is Soeren Rabenstein, I am in ASUSTeK's legal department since early 2009 and responsible for European

I have to agree with Soeren (welcome!). A standard can't be complete without it and the Beerware License Rev.42 (in a template form). -- --dmg --- Daniel M. German http://turingmachine.org

Hi, just one point about this license - it was a problem for one of our major OEM customers. Through bugzilla, they requested that we change the expletive to something less problematic for them

Welcome, Soeren. Glad to have you aboard. This is certainly fair discussion. The goal has been to have the standard license list cover a large majority of cases (Kate's been talking about 90%

I know that the Ruby license is pretty common. I would vote to add that one. Kim Sent from my Verizon Wireless Phone ----- Reply message ----- From: "Philip Odence" <podence@...> Date: Wed, Aug 11,

Soeren, welcome, and thanks for the incremental licenses -- Licenses that come up in day-to-day practice are high value for SPDX. Thanks, Tom Tom Incorvia tom.incorvia@... Direct:  (512)

Hi Phil Wouldn’t it make sense to include as many licenses aspossible? (except maybe the very strange ones) Sure this will all more data to the specification. But limitingthe specification may

Hi Soren, Welcome. Glad to have your input :) Wiki version of spec needs to be refreshed to correspond to the latest draft, and I'll try to work on it this weekend. If anyone else

Hi, (First, happy to join this list after attending the LinuxCon session yesterday.) Of the ones Soeren listed, the OpenSSL license (or, I guess, conjunction-of-licenses) stands out to me as one of

Kate was right, I should have gone l,to LinuxConf in the same line as Richard comment, why not include every license found in the Linux kernel? I am sure many of you have customers that need this

Thanks Gary – thrilled that you contributed our first tool. Although I explicitly specified ssl/tls, port 21, and accepted certificate, seems to be rejecting the password spdx1 for user

Thanks Bill for the reply. Sorry - I sent out the wrong username - it's spdx@.... Give that a try and let me know if you have any problems. Gary <bschineller@...>

Yes, that's clearly the tradeoff, Soeren. I think the question is how "expensive" it is to add licenses to the list and maintain them. I suspect that as with the spec, we'll have a working area for

Sorry about any confusion. As per the minutes of the 7/29 meeting, no meeting today. Next meeting is normal time, two weeks from today. L. Philip Odence Vice President of Business Development Black

Hi all, While looking at the draft spec, i noticed that the specification examples page, <http://spdx.org/spec/examples>, is empty. However, there do seem to be some examples at

Peter, The examples you cite are, as you speculated, out of date. We need to create some current ones. Getting the site up and running before LinuxCon was a bit of a scramble, though Martin did a

Just out of curiousity, what kind of wiki is FOSSBazaar using? It doesn't seem very full featured, so a lot of what I discussed doing at LinuxCon is going to be much more complicated. However,