Re: [License-discuss] [Non-DoD Source] The License Talking-About List

2016-08-24 Thread Rick Moen
[cross-post to license-review, snipped.] Quoting Karan, Cem F CIV USARMY RDECOM ARL (US) (cem.f.karan@mail.mil): > What about GitHub? Using a proprietary hosting platform for outsourced tracking of open-source licenses? Could work, but that risks punishment by the Gods of Irony. BTW,

Re: [License-discuss] [Non-DoD Source] Re: [Non-DoD Source] Re: U.S. Army Research Laboratory Open Source License (ARL OSL) 0.4.0

2016-08-24 Thread Karan, Cem F CIV USARMY RDECOM ARL (US)
> -Original Message- > From: License-discuss [mailto:license-discuss-boun...@opensource.org] On > Behalf Of Tzeng, Nigel H. > Sent: Monday, August 22, 2016 5:02 PM > To: license-discuss@opensource.org > Subject: Re: [License-discuss] [Non-DoD Source] Re: [Non-DoD Source] Re: U.S. > Army

Re: [License-discuss] [Non-DoD Source] The License Talking-About List

2016-08-24 Thread Karan, Cem F CIV USARMY RDECOM ARL (US)
What about GitHub? There have been suggestions on the Python-ideas list to do this for any new python ideas. The idea is simple; each license becomes its own project. Issues can then be tracked via the issue tracker, making it easy to segregate the issues into individual threads, and as

Re: [License-discuss] [Non-DoD Source] Re: [Non-DoD Source] Re: U.S. Army Research Laboratory Open Source License (ARL OSL) 0.4.0

2016-08-24 Thread Karan, Cem F CIV USARMY RDECOM ARL (US)
OK, so it's the way I thought. First, propose a license on this list for discussion, but the actual review takes place on the license-review mailing list. Thanks, Cem Karan > -Original Message- > From: License-discuss [mailto:license-discuss-boun...@opensource.org] On > Behalf Of