Re: [ee4j-pmc] Proposal: Request for explanations

[Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>]

Hi,

On 10/12/19 12:51 PM, Ivar Grimstad wrote:
> Hi,
>
> *spec + api in one repo*
> The reasoning for keeping /spec+api/ in the same repository is for 
> simplicity and assuming that you would always release them together.

> The TCK needs to go in a separate repository since it has a different 
> license

Does this mean that if api project has different license (ie 
EPL2.0/EDL1.0 or EDL1.0 only) than spec project (EPL2.0/GPLv2wCPE) then 
the only option is to use separate directory? Or is it enough, in case 
one repository hosts projects with different licenses (api+spec+tck), to 
explicitly mention this on some prominent place?

thanks,
--lukas

> Ivar
>
> On Sat, Oct 12, 2019 at 6:02 AM Markus KARG <markus@xxxxxxxxxxxxxxx 
> <mailto:markus@xxxxxxxxxxxxxxx>> wrote:
>
>     Dear Spec Committee and PMC,____
>
>     __ __
>
>     it would be great to have some explanations for recommendations, so
>     committers and contributors would better and more easily understand
>     the drivers behind each recommendation.____
>
>     __ __
>
>     For example, the document
>     https://github.com/jakartaee/specification-committee/blob/master/operations.adoc#recommended-specification-project-repository-structure
>     says that it is recommended to have one repo with spec + api plus a
>     second repo with tck. This looks rather arbitraty. There could also
>     be three repos, or just one, or one with api and one with spec +
>     tck. While everybody might assume a good reson behind each
>     recommendation, the document does not explain the actual
>     aniticipated (or measured) benefit of exactly that solution compared
>     to the other solutions.____
>
>     __ __
>
>     *So it would be great if all recommendation documents would have
>     some explanative text telling the exact reason for each
>     recommendation / rule (for example in italics). :-)____*
>
>     __ __
>
>     Thanks____
>
>     -Markus____
>
>     _______________________________________________
>     ee4j-pmc mailing list
>     ee4j-pmc@xxxxxxxxxxx <mailto:ee4j-pmc@xxxxxxxxxxx>
>     To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     https://www.eclipse.org/mailman/listinfo/ee4j-pmc
>
>
>
> --
>
> Ivar Grimstad
>
> Jakarta EE Developer Advocate | Eclipse Foundation, Inc.
>
> Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open 
> Innovation and Collaboration
>
> _______________________________________________
> ee4j-pmc mailing list
> ee4j-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/ee4j-pmc