Re: [osgi-wg-specification-committee] An update to the Eclipse Foundatio

["Daniel Bandera" <bandera@xxxxxxxxxx>]

Hi Wayne,

Something I think would be extremely good to change are the definitions of Final Specification and Final TCK so they are completely separate but paired deliverables (i.e., Siamese Twins). They should be paired; and versioned identically.  The Eclipse Foundation is the only organization in the industry that I and many others have seen where the TCK is included in (subsumed by) the "Specification" and almost everyone I talk to finds it very confusing.

Best regards,
Dan

Dan Bandera
(512) 286-5228
Program Director, Blockchain, Istio, Java technologies, Node.js
IBM Open Technologies, Austin, Texas;          OSGi Laureate;
Interim Chair Eclipse OSGi Working Group Steering Committee



Wayne Beaton ---2021/06/17 01:08:36 PM---Greetings OSGi Specification Committee. I've started work on a new revision of the EFSP.

From: Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
To: OSGI WG Specification Committee <osgi-wg-specification-committee@xxxxxxxxxxx>
Date: 2021/06/17 01:08 PM
Subject: [EXTERNAL] [osgi-wg-specification-committee] An update to the Eclipse Foundation Specification Process
Sent by: "osgi-wg-specification-committee" <osgi-wg-specification-committee-bounces@xxxxxxxxxxx>

---

Greetings OSGi Specification Committee. I've started work on a new revision of the EFSP. My primary interest is to focus the EFSP itself more on the intellectual property flows and less on prescribing the specific nature of specifications ZjQcmQRYFpfptBannerStart 
This Message Is From an External Sender 
This message came from outside your organization. 
ZjQcmQRYFpfptBannerEnd
Greetings OSGi Specification Committee.

I've started work on a new revision of the EFSP.

My primary interest is to focus the EFSP itself more on the intellectual property flows and less on prescribing the specific nature of specifications themselves. As we apply the process to other domains, we're finding that much of our earlier understanding just doesn't apply generally.

Note that rolling out a new version of the EFSP does not automatically impose anything on specification committees already engaged in a specification process. Following the approval of a new version of the EFSP, the specification committee will have an opportunity to adopt the new process and integrate it into their own.

I'm tracking the effort in a GitHub board. A diff of the work-in-progress is here.

I invite all members of the specification committee to add their comments on the open issues and create new issues if there are specific things that you believe need to be addressed. Pull requests are welcome.

I'm assembling a committee with representatives from each of the working groups engaged in specification development to produce this update. My intent is to set up a one hour meeting as soon as I have representatives from each working group to go over what I've done with the draft so far. 

BJ has volunteered to represent the interests of the OSGi specification committee. 

Thanks,

Wayne

-- 
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation_______________________________________________
osgi-wg-specification-committee mailing list
osgi-wg-specification-committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/osgi-wg-specification-committee