Eclipse OS.bea Working Group Charter
February 25, 2018 Christophe Loetz (Compex Systemhaus GmbH)
Revised March 10, 2018 Ralph Mueller (Eclipse Foundation)
Revised March 16, 2018 Christophe Loetz (Compex Systemhaus GmbH)
Revised April 04, 2018 Christophe Loetz (for final release as community review draft)
Scope, Goals and Vision
The OS.bea Working Group will drive the evolution and broad adoption of technologies of the Open Standard Business Platform (OSBP).
The working group will:
- Manage the overall technical and business strategies for OSBP driven projects.
- Define and manage a specification process to formalize the specifications that are defined within the scope of this working group.
- Define compatibility rules and branding process for implementations of these specifications to ensure application portability.
- Promote the "OS.bea" brand and its value in the marketplace.
- Provide vendor-neutral marketing and other services to the OS.bea ecosystem.
- Establish and drive a funding model that enables this working group and its community to operate on a sustainable basis.
The OS.bea Working Group (OS.bea WG) wants to foster and support an open and innovative eco-system providing tools and systems, and adapters for standardized, openly-available and vendor-neutral OSB Platform as described above.
In particular, the OS.bea WG will
- Help to support OS.bea related Eclipse projects that develop the related software components
- Provide the resources for managing the quality and the maturity of these components throughout the life-cycle
- Ensure open innovation through the sharing of the research, development, and maintenance efforts as far as possible
- Foster exchanges between academics, standardization organizations, industry partners and community
Definitions
OS.bea
stands for "Open Standard Business and Enterprise Application".
Bodies
Gremia, etc.
Eclipse Members
Eclipse Members have signed the Eclipse Membership Agreement and have signed the Eclipse Foundation Membership Agreement and are in good standing. For a complete overview over the Eclipse Membership process and the current Eclipse members refer to the Eclipse Home Page.
OS.bea WG Members
OS.bea WG members have signed the OS.bea WG participation agreement and have fulfilled the requirements as stated in the WG participation agreement exhibit.
OS.bea WG deliverables and results
The services and goods (software, documents) to be delivered hereunder are referred to in this document as OS.bea WG deliverables / results.
OS.bea related Eclipse projects
The Eclipse Foundation provides a framework for defining, driving and executing projects. "OS.bea related Eclipse projects" means Eclipse projects that are of interest for the OS.bea WG.
OS.bea WG participation agreement
Eclipse members have to sign OS.bea WG participation agreement to participate in the OS.bea WG.
OS.bea Software
OS.bea Software is software using OSBP technology and its related frameworks, projects and technologies as appropriate.
Project Lead
A natural person that leads an OS.bea related Eclipse project. The Project Lead may be an employee of a WG member.
Open Standard Business Platform (OSBP)
Stands for the Eclipse Open Standard Business Platform (OSBP) project.
Governance
The OS.bea working group is designed as:
- a working group driven by its strategic members,
- a means to foster a vibrant and sustainable ecosystem of users, contributors and service providers,
- a means to organize the community of each project or component so that strategic users and developers define the roadmap collaboratively.
In order to implement these principles, the following governance bodies have been defined (each a "Body"):
- The Steering Committee
- The Specification Committee
- The Marketing and Brand Committee
Membership
An entity must have executed the OS.bea Participation Agreement once defined, and adhere to the requirements set forth in this Charter to participate. Every entity must be at least an Eclipse Solution member.
There are three classes of OS.bea membership - Strategic, Participant, and Committer. Each of these classes is described in detail below.
The fees associated with each of these OS.bea membership classes is also shown below.
In addition, all matters related to Membership in the Eclipse Foundation and this OS.bea working group will be governed by the Eclipse Foundation Bylaws, Membership Agreement and Eclipse Working Group Process. These matters include, without limitation, delinquency, payment of dues, termination, resignation, reinstatement, and assignment.
Member of | Strategic Consumer Member | Strategic Developer Member | Participant Member |
---|---|---|---|
Steering Committee | Appointed | Appointed | Elected |
Specification Committee | Appointed | Appointed | Elected |
Marketing Committee | Appointed | Appointed | Elected |
Members who resign, or otherwise terminate their membership in the working group, lose their rights to access and use any private assets and data of the working group after the effective date of the termination.
Strategic Consumer Member
Strategic Consumer Members want to influence the definition and further development of the OS.bea brand and technology as well as all its deliverables.
They are members of the Steering Committee and invest an essential amount of resources to sustain the WG activities. Typically Strategic Consumer members include users of the technologies and results provided by the OS.bea Working Group. Most of them use OS.bea technology at large.
Strategic Developer Member
Strategic Developer Members consider the OS.bea technology stack and the related business opportunities essential to the success of the company. Typically they invest heavily in definition and development of the OS.bea related technology.
Participant Members
Participant Members consider the OS.bea technology a relevant addition to their business. They are either users of the related technology and service offerings or they are interested in adoption, extension and service provisioning for the OS.bea technology stack.
Guest Members
Guests are organizations who have been invited for one year by the OS.bea Steering Committee to participate in particular aspects of the activities of the Working Group. Typically guests includes R&D partners, Universities, academic research centers, and potential full-fledged members who want to have a closer look before deciding on their participation strategy. Guest membership is free of charge and invitations may be renewed once by the Steering Committee. Guests are required to sign an Eclipse and OS.bea Membership Agreement, but when participating in meetings of a OS.bea body, they have no voting rights.
Bodies
Steering Committee
Powers and Duties
Steering Committee members are required to:
- Define and manage the strategy of the working group
- Define and execute the marketing strategy for the working group
- Define and manage the technical roadmap
- Review and execute the specification process
- Review and approve this charter
- Define the budget and fees for all classes of working group membership each year.
Composition
- Each Strategic (Consumer and Developer) Member of the working group has a seat on the Steering Committee.
- "Transferable Vote", as defined in the Eclipse Bylaws.
- At least one seat is allocated to Participant Members. Participant Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.
Specification Committee
Will be defined in Powers and Duties as one of the first tasks
Powers and Duties
Specification Committee Members are required to:
- Define the specification process to be used by the OS.bea WG, and refer to it for approval by the Steering Committee.
- Ensure that all specification expert groups operate in an open, transparent, and vendor-neutral fashion in compliance with the specification process.
- Approve specifications for adoption by the community.
- Approve profiles which define collections of specifications which meet a particular market requirement.
- Work with the OSBP to ensure that the specification process is complied with by all specification projects.
Composition
- Each Strategic Member of the working group has a seat on the Specification Committee.
- At least one seat is allocated to Participant Members. Participant Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.
- The Committee elects a chair who reports to the Steering Committee. This chair is elected among the members of the Committee. They will serve from April 1 to March 31 of each calendar year, or until their successor is elected and qualified, or as otherwise provided for in this Charter.
Marketing and Brand Committee
Powers and Duties
The Marketing and Brand Committee members are required to:
- Define and implement marketing and communication activities for the working group
- Define and implement developer and end user outreach programs
- Provide requirements to the Eclipse Foundation for conferences and events related to the OS.bea WG
Composition
- Each Strategic Member of the working group has a seat on the Marketing Committee.
- At least one seat is allocated to Participant Members. Participant Member seats are allocated following the Eclipse "Single Transferable Vote", as defined in the Eclipse Bylaws.
- The Committee elects a chair who reports to the Steering Committee. This chair is elected among the members of the Committee. They will serve from April 1 to March 31 of each calendar year, or until their successor is elected and qualified, or as otherwise provided for in this Charter.
Meeting Management
Common Dispositions
For all matters related to membership action, including without limitation: meetings, quorum, voting, electronic voting action without meeting, vacancy, resignation or removal, the terms set forth in Section 6 of the Eclipse Foundation Bylaws apply.
Meeting frequency
All bodies meet in person at least twice a year.
Invitation and quorum
No Body meeting will be deemed to have been validly held unless a notice of same has been provided to each of the representative in Good Standing at least thirty (30) calendar days prior to such meeting, which notice will identify all potential actions to be undertaken by the Body at the Body meeting. No representative will be intentionally excluded from Body meetings and all representatives shall receive notice of the meeting as specified above; however, Body meetings need not be delayed or rescheduled merely because one or more of the representatives cannot attend or participate so long as at least a quorum of the Body (as defined in the Common Dispositions section) is represented at the Body meeting. Electronic voting shall be permitted in conjunction with any and all meetings of the Body, the subject matter of which requires a vote of the Body to be delayed until each such representative in attendance thereat has conferred with his or her respective Member organization as set forth in Section Voting above.
Place of Meetings
All meetings may be held at any place that has been designated from time-to-time by resolution of the corresponding body. All meetings may be held remotely using phone calls, video calls, or any other means as designated from time-to-time by resolution of the corresponding body.
Actions
The body may undertake an action only if it was identified in a body meeting notice or otherwise identified in a notice of special meeting.
Invitations
The body may invite any OS.bea member to any of its meetings. These invited attendees have no right of vote.
Decisions
Decisions shall be taken by simple majority vote, unless specified otherwise. The body has a quorum if all representatives have properly been invited. Decisions shall be reported in writing. Guests do not have any voting rights.
Term and Dates of Elections
This section only applies to the Steering Committee, Specification Committee, and the Marketing Committee.
All representatives shall hold office until their respective successors are appointed or elected, as applicable. There shall be no prohibition on re-election or re-designation of any representative following the completion of that representative's term of office.
Strategic Members
Strategic Members Representatives shall serve in such capacity on committees until the earlier of their removal by their respective appointing Member organization or as otherwise provided for in this Charter.
Elected representatives
Elected representatives shall each serve one-year terms and shall be elected to serve from April 1 to March 31 of each calendar year, or until their respective successors are elected and qualified, or as otherwise provided for in this Charter. Procedures governing elections of Representatives may be established pursuant to resolutions of the Steering Committee provided that such resolutions are not inconsistent with any provision of this Charter.
Applicable Documents
- Eclipse Bylaws
- Industry Working Group Process
- Eclipse Membership Agreement
- Eclipse Intellectual Property Policy
- Eclipse Anti-Trust Policy
- Eclipse Development Process
All Members must be parties to the Eclipse Foundation Membership Agreement, including the requirement set forth in Section 2.2 to follow the Bylaws and then-current policies of the Eclipse Foundation, including but not limited to the Intellectual Property and Anti-Trust Policies.
In the event of any conflict between the terms set forth in this Working Group's Charter and the Eclipse Foundation Bylaws, Membership Agreement, Eclipse Development Process, Eclipse Industry Working Group Process, or any policies of the Eclipse Foundation, the terms of the Eclipse Foundation Bylaws, Membership Agreement, process, or policy shall take precedence.
OS.bea Working Group Fees
In year one the fees will be $ 0.--