Re: [openstack-dev] Storing license information in openstack/requirements

2014-03-19 Thread Joshua Harlow
e questions)" mailto:openstack-dev@lists.openstack.org>> Date: Monday, February 17, 2014 at 5:21 PM To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] Storing li

Re: [openstack-dev] Storing license information in openstack/requirements

2014-02-19 Thread Doug Hellmann
On Wed, Feb 19, 2014 at 6:13 AM, Thierry Carrez wrote: > Sean Dague wrote: > > Honestly, if we are going to track this, we should probably do the set > > of things that reviewers tend to do when running through these. > > > > License: > > Upstream Location: > > Ubuntu/Debian Package: Y/N? (url) >

Re: [openstack-dev] Storing license information in openstack/requirements

2014-02-19 Thread Thierry Carrez
Sean Dague wrote: > Honestly, if we are going to track this, we should probably do the set > of things that reviewers tend to do when running through these. > > License: > Upstream Location: > Ubuntu/Debian Package: Y/N? (url) > Fedora Package: Y/N? (url) > Suse Package: Y/N? (url) > Last Release:

Re: [openstack-dev] Storing license information in openstack/requirements

2014-02-19 Thread Thierry Carrez
David Koo wrote: > >> Should we store licensing information as a comment in the >> *-requirements files ? Can it be stored on the same line ? Something >> like: >> >> oslo.messaging>=1.3.0a4 # Apache-2.0 > > Since it's licenses we're tracking shouldn't we be tracking indirect > dependencies too

Re: [openstack-dev] Storing license information in openstack/requirements

2014-02-17 Thread David Koo
> Should we store licensing information as a comment in the > *-requirements files ? Can it be stored on the same line ? Something > like: > > oslo.messaging>=1.3.0a4 # Apache-2.0 Since it's licenses we're tracking shouldn't we be tracking indirect dependencies too (i.e. packages pulled in by r

Re: [openstack-dev] Storing license information in openstack/requirements

2014-02-17 Thread Joshua Harlow
+1 for yaml instead of shoving all kinds of package metadata in comments. Sent from my really tiny device... > On Feb 17, 2014, at 4:12 PM, "Sean Dague" wrote: > > Honestly, if we are going to track this, we should probably do the set > of things that reviewers tend to do when running through

Re: [openstack-dev] Storing license information in openstack/requirements

2014-02-17 Thread Sean Dague
Honestly, if we are going to track this, we should probably do the set of things that reviewers tend to do when running through these. License: Upstream Location: Ubuntu/Debian Package: Y/N? (url) Fedora Package: Y/N? (url) Suse Package: Y/N? (url) Last Release: Date (in case of abandonware) Pytho

Re: [openstack-dev] Storing license information in openstack/requirements

2014-02-17 Thread Doug Hellmann
On Mon, Feb 17, 2014 at 11:01 AM, Thierry Carrez wrote: > Hi everyone, > > A year ago there was a discussion about doing a license inventory on > OpenStack dependencies, to check that they are compatible with our own > license and make sure any addition gets a proper license check. > > Back then I