, Duncan Thomas <duncan.tho...@gmail.com>
wrote:
> On 12 December 2016 at 16:35, Ash <a...@wildernessvoice.com> wrote:
>
>> I tend to agree with you, Sean. Also, if there's a concern that some
>> project has changed its license, then just create a fork. In the case
I tend to agree with you, Sean. Also, if there's a concern that some
project has changed its license, then just create a fork. In the case of
this previously GPL code, it will at least be re-distributable. In the end,
I just don't think this is a huge issue that cannot be easily managed.
On Mon,
On Wed, Nov 9, 2016 at 3:14 AM, Chris Dent <cdent...@anticdent.org> wrote:
> On Tue, 8 Nov 2016, Ash wrote:
>
> I couldn't agree more. I don't like change for the sake of change (in any
>> aspect of my life). So in my mind this would have to be a way to better
>> bind
On Tue, Nov 8, 2016 at 2:27 AM, Thierry Carrez <thie...@openstack.org>
wrote:
> Ash wrote:
> > [...]
> > Here's another take on the situation. If there are people who genuinely
> > wish to see a CI pipeline that can support something like Go, perhaps
> >
On Mon, Nov 7, 2016 at 9:58 AM, Hayes, Graham wrote:
> On 07/11/2016 17:14, Flavio Percoco wrote:
> > Greetings,
> >
> > I literally just posted a thing on my blog with some thoughts of what
> I'd expect
> > any new language being proposed for OpenStack to cover before it