incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roy Lenferink <rlenfer...@apache.org>
Subject Re: [IP CLEARANCE] Apache Celix - Websocket pubsub admin
Date Fri, 23 Aug 2019 06:09:56 GMT
Thanks for your input as well Matt! Next time we'll discuss upfront whether
IP clearance is necessary or not.
Consider this case as a "better safe than sorry" one.

With that said, 72 hours have passed so the vote is closed with the
following results:

+1:
Furkan Kamaci
Matt Sicker
Roy Lenferink (hereby adding my +1)

No -1 votes have been cast.

Thanks all for your input,
Roy

Op wo 21 aug. 2019 om 20:21 schreef Matt Sicker <boards@gmail.com>:

> I would think that if the person who submits the PR has the rights to
> make that contribution, then their ICLA should cover that. See
> https://www.apache.org/licenses/contributor-agreements.html for more
> info.
>
> On Wed, 21 Aug 2019 at 11:49, Roy Lenferink <lenferinkroy@gmail.com>
> wrote:
> >
> > > Given it was already had a ASF license header and from a ASF project
> why
> > was IP clearance even needed? I assume the person involved has signed a
> > ICLA?
> >
> > The individual contributors all submitted an ICLA and a CCLA for the
> > company is already present. We were following IP clearance
> > because the written software was developed outside of the ASF version
> > control system (company internal VCS). After that, we squashed everything
> > into a single commit and submitted it as a PR to Celix.
> >
> > Would IP clearance be necessary in this case (duplication of an already
> > existing component)? Would IP clearance be necessary for new components
> > which already have ASF headers in place?
>
>
>
> --
> Matt Sicker <boards@gmail.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message