Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

2018-08-28 Thread MCEUEN, MATT
Sorry for the noise folks - the change was well-intentioned but uninformed! We will revert the changes. Thanks, Matt -Original Message- From: Jeremy Stanley Sent: Tuesday, August 28, 2018 12:00 PM To: openstack-dev@lists.openstack.org Cc: MCEUEN, MATT Subject:

Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

2018-08-28 Thread Jeremy Stanley
On 2018-08-28 10:11:18 -0700 (-0700), John Dickinson wrote: [...] > It would be *really* helpful to have a simple rule or pattern for > each file's header. Something like "Copyright (c) created>-present by contributors to this project". I applaud and share your desire for a clear rule on such

Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

2018-08-28 Thread Andreas Jaeger
In this context, there's also the question of copyright headers for documentation files which we do not require - see https://wiki.openstack.org/wiki/Documentation/Copyright This came up recently with: https://review.openstack.org/#/c/593662/ I'm happy to see a canonical place for this

Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

2018-08-28 Thread Doug Hellmann
Excerpts from Jeremy Stanley's message of 2018-08-28 16:59:56 +: > [Obligatory disclaimer: I am not a lawyer, this is not legal advice, > and I am not representing the OpenStack Foundation in any legal > capacity here.] > > TL;DR: You should not be putting "Copyright OpenStack Foundation" on

Re: [openstack-dev] [all][tc][openstack-helm] On the problem of OSF copyright headers

2018-08-28 Thread John Dickinson
On 28 Aug 2018, at 9:59, Jeremy Stanley wrote: [Obligatory disclaimer: I am not a lawyer, this is not legal advice, and I am not representing the OpenStack Foundation in any legal capacity here.] TL;DR: You should not be putting "Copyright OpenStack Foundation" on content in Git