Re: [orbit-dev] Evolving Orbit's Process/Policy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [orbit-dev] Evolving Orbit's Process/Policy

From: Roland Grunberg <rgrunber@xxxxxxxxxx>
Date: Wed, 23 Oct 2019 12:27:38 -0400
Delivered-to: orbit-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/orbit-dev>
List-help: <mailto:orbit-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/orbit-dev>, <mailto:orbit-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/orbit-dev>, <mailto:orbit-dev-request@eclipse.org?subject=unsubscribe>

From the talk I attended it looks like contributions will become much easier in the future. CQs are likely to go away entirely and license certification will become the norm.

I would like to at the very least (for now) confirm with Eclipse Legal that we are basically filing initial CQs to get content in and will proceed immediately to push it in under the assumption that the new library is simply an updated version and would always qualify for the parallel IP process.

Cheers,

Roland Grunberg

References:
- [orbit-dev] Evolving Orbit's Process/Policy
  - From: Gunnar Wagenknecht

Prev by Date: Re: [orbit-dev] Evolving Orbit's Process/Policy
Next by Date: Re: [orbit-dev] Evolving Orbit's Process/Policy
Previous by thread: Re: [orbit-dev] Evolving Orbit's Process/Policy
Next by thread: [orbit-dev] Declaring Build: S20191025144108 (2019-12 M2)
Index(es):
- Date
- Thread

Breadcrumbs