Re: [jakarta.ee-spec.committee] JCP Members

["MDeNicola@xxxxxxxxxxxxxx" <MDeNicola@xxxxxxxxxxxxxx>]

I should mention that the JCP Process also has an Observer status. It is spelled out in Section 3.1 of the JCP Process Doc.

It lets individuals who are not JCP Members observe and comment on JSR activities. They are not allowed to join Expert Groups, but take advantage of the public mailing lists and Issue trackers.

MikeD

-----Original Message-----
From: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx [mailto:jakarta.ee-spec.committee-bounces@xxxxxxxxxxx] On Behalf Of Mark Little
Sent: Wednesday, September 12, 2018 11:42 PM
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Subject: Re: [jakarta.ee-spec.committee] JCP Members

I've mentioned this in the past but will repeat: at least in my experience with OASIS, if someone has access to post to a standards mailing list then they can be contributing IP and influencing the specification development that way too, which is why in OASIS there are observers and contributors; the former cannot discuss with the latter because they have not signed IP agreements.

Mark.

On Thu, Sep 13, 2018 at 1:39 PM, Ivar Grimstad <ivar.grimstad@xxxxxxxxx> wrote:
>
>
> On Thu, Sep 13, 2018 at 1:25 AM Bill Shannon <bill.shannon@xxxxxxxxxx>
> wrote:
>>
>> MDeNicola@xxxxxxxxxxxxxx wrote on 09/12/18 04:00 PM:
>>
>> An Associate Member is an individual who wants to participate in
>> activities of the JCP without requiring an employer’s permission.
>> They must sign an Associate Member Agreement, which involves only a
>> personal IP commitment. Associate Members cannot join an Expert
>> Group, but Spec Leads can list an Associate Member as a Contributor to a JSR.
>>
>> (A Contributor is someone who is not a member of an Expert Group, but
>> who the Spec Lead recognizes as having contributed to the JSR.)
>>
>>
>> How do you ensure that you have the rights to the IP in a
>> Contributor's contributions and that the Contributor's employer
>> doesn't own the IP?  Isn't this why an Employer Contribution Agreement is needed?
>
>
> I don't know if it makes any difference legally, but a contributor
> would not be given commit rights to the API or Specification repos so
> there should be no "physical" contributions.
>
>
>>
>>
>> _______________________________________________
>> jakarta.ee-spec.committee mailing list
>> jakarta.ee-spec.committee@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_
>> mailman_listinfo_jakarta.ee-2Dspec.committee&d=DwIGaQ&c=09aR81AqZjK9F
>> qV5BSCPBw&r=zT7aZHP-AD1KLPDR5gQV4INUwxtApC587a8Sa32AvB0&m=C0e1yA933Qe
>> 6OKvsMfzVzxC7TP4kDQguq_xjYi0mM4w&s=ApCwK5bkjk_BGpc5VdOZY9LGTgWTKw_heG
>> OT2A3vJcs&e=
>
> --
>
> Java Champion, JCP EC/EG Member, EE4J PMC, JUG Leader
>
>
> _______________________________________________
> jakarta.ee-spec.committee mailing list
> jakarta.ee-spec.committee@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_m
> ailman_listinfo_jakarta.ee-2Dspec.committee&d=DwIGaQ&c=09aR81AqZjK9FqV
> 5BSCPBw&r=zT7aZHP-AD1KLPDR5gQV4INUwxtApC587a8Sa32AvB0&m=C0e1yA933Qe6OK
> vsMfzVzxC7TP4kDQguq_xjYi0mM4w&s=ApCwK5bkjk_BGpc5VdOZY9LGTgWTKw_heGOT2A
> 3vJcs&e=
>
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_jakarta.ee-2Dspec.committee&d=DwIGaQ&c=09aR81AqZjK9FqV5BSCPBw&r=zT7aZHP-AD1KLPDR5gQV4INUwxtApC587a8Sa32AvB0&m=C0e1yA933Qe6OKvsMfzVzxC7TP4kDQguq_xjYi0mM4w&s=ApCwK5bkjk_BGpc5VdOZY9LGTgWTKw_heGOT2A3vJcs&e=
________________________________

This e-mail and any attached files are only for the use of its intended recipient(s). Its contents are confidential and may be privileged. Fujitsu does not guarantee that this e-mail has not been intercepted and amended or that it is virus free. If you have received this e-mail and are not the intended recipient, please contact the sender by e-mail and destroy all copies of this e-mail and any attachments. / Le présent courriel, ainsi que ses pièces jointes, ne peut être utilisé que par le ou les destinataires auxquels il a été transmis. Les renseignements qu'il contient sont confidentiels, voire même protégés. Fujitsu ne peut garantir que ce courriel n'a pas été intercepté ou modifié, ou qu'il ne contient aucun virus. Si vous avez reçu ce courriel sans en être le destinataire prévu, veuillez communiquer par courriel avec son expéditeur et en détruire toutes les copies et pièces jointes.