Agreed and thanks for the suggestions! On Wed, May 2, 2018 at 7:52 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote:
> Thank you all for stepping up to correct this. > > With my mentor hat on... > > Trademark, licensing, and copyright hygiene are very important for ASF > projects. > > I’d encourage everyone to proactively research branding, release, and > other policies. > > ASF documentation can seem pretty scattered, but it is well indexed by > google (e.g. “Apache X policy”). It’s also open source, so there’s an > opportunity to improve it. > > It’s important that everyone strive to adopt the Apache Way. > > -Taylor > > > On May 2, 2018, at 1:59 PM, Ning Wang <wangnin...@gmail.com> wrote: > > > > Prepared two PRs to update license text so far: > > > > https://github.com/apache/incubator-heron/pull/2881 > > https://github.com/apache/incubator-heron/pull/2882 > > > > Other files to come. > > > > > > On Wed, May 2, 2018 at 10:40 AM, Karthik Ramasamy <kart...@streaml.io> > > wrote: > > > >> Dave - > >> > >> Task that we are working are > >> > >> - Convert namespace com.twitter.heron to org.apache.heron - completed > >> - Copyright on the source files - ongoing > >> - Binaries are being removed from the code base - ongoing > >> > >> Meetup last week was great. We had around 80 people attending and we had > >> three talks. > >> Another meetup is being organized by Sree in South Bay. > >> > >> Regarding meeting minutes, Ning sends out an update after every sync up. > >> > >> cheers > >> /karthik > >> > >> > >> > >> > >>> On Tue, May 1, 2018 at 6:50 PM, Dave Fisher <dave2w...@comcast.net> > wrote: > >>> > >>> Hi Ali, > >>> > >>> Where are pending tasks and plans discussed and recorded so that folks > >> can > >>> find out and participate. > >>> > >>> What I am saying is you are having sync ups and not publishing minutes. > >>> You also announce the sync up 5 minutes beforehand. Decisions need to > >> come > >>> to this mailing list. > >>> > >>> How was the Meetup last week? > >>> > >>> Apache projects are global which actually means that asynchronous > >>> communication and letting the world turn for three days is a common > rule > >> to > >>> the Apache Way. > >>> > >>> Regards, > >>> Dave > >>> > >>> Sent from my iPhone > >>> > >>>> On May 1, 2018, at 5:42 PM, Ali Ahmed <a.ah...@streaml.io> wrote: > >>>> > >>>> Hi Taylor , > >>>> > >>>> There are some tasks pending in this regard , the goal is to remove > all > >>> twitter copyright headers soon , some of the commits are in and some > are > >>> remaining . > >>>> > >>>> -Ali > >>>> > >>>>> On May 1, 2018, at 5:37 PM, P. Taylor Goetz <ptgo...@gmail.com> > >> wrote: > >>>>> > >>>>> Heron PPMC, > >>>>> > >>>>> I’ve mentioned this before, but IMO, this practice needs to stop. > >>>>> > >>>>> The community default seems to be to apply the Apache license header > >>> with a twitter copyright assertion on all files, even ones copied from > >>> other ALv2-licensed projects. > >>>>> > >>>>> Twitter can’t assert copyright on code their employees didn’t create, > >>> though, at least in this project, they continue to do so. I find this > >>> practice unacceptable. > >>>>> > >>>>> Please reconsider even including “Copyright Twitter $date” at all in > >>> license headers. That’s more suitable for the NOTICE file, and removed > >> from > >>> the source header. > >>>>> > >>>>> Aside from having a twitter account, I have no affiliation with > >>> twitter. As a mentor I was surprised and disappointed to see a Twitter > >>> copyright applied to my own (implicitly copyrighted) work. That’s not > >> cool, > >>> nor really (IANAL) legal. > >>>>> > >>>>> I would appreciate if this could be corrected. This kind of thing is > >>> something podlings need to know how to address proactively. > >>>>> > >>>>> -Taylor > >>>> > >>> > >>> > >> >
