Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "LTS/Sept26 2012"
(→Actions) |
(→Agenda) |
||
| Line 35: | Line 35: | ||
==Agenda== | ==Agenda== | ||
| − | + | Website - Andrew: we will have one set up in time for EclipseCon - it should be ready in a couple weeks. | |
| − | + | ||
| − | + | Membership - Jochen had a call with SAP and SpringSource to talk about requirements for joining LTS. Need to be on the release train, which might not be practical for runtime projects. They usually only have a little tooling in the release train, but not the runtime, because that would not typically be installed as part of the IDE. The release train focuses on the IDE. So maybe that requirement doesn't make sense? This should be discussed in the steering committee meeting. We want to encourage as many projects as possible to participate - we want to be inclusive, not exclusive. But we do need some rules to be sure that they are able to conform to LTS. SAP's Virgo is an example - it's a runtime, not on the release train, but we certainly want them to be part of LTS. Jochen told SAP that we would discuss this at the next Steering Committee. Maybe the rule is that you have to be on the release train, or you can be designated by the steering committee as exceptions to the rule. How important is it to be in simultaneous release? Maybe the underlying need is that they are compatible with the simultaneous release and to have an automated repeatable build with repeatable test cases. Orion is another big exception. Release train has been a quick way to sort out mainstream projects from less active projects. | |
| − | + | ||
| − | + | We will need to provide a mechanism for people to request other projects and/or release levels that they want LTS for. For example, there could be a need for a 3.6.2-based LTS | |
| − | + | ||
| − | + | Prep for EclipseCon | |
| − | + | We should try to get a meeting of the steering committee before EclipseCon. As of today, Steering Committee members of LTS include: SAP, CA Technologies, IBM, Innoopract. In the 2 hour slot that we have at EclipseCon, make the first hour be for the steering committee, second hour general interest | |
| − | + | ||
| − | + | We'll want to put the EclipseCon agenda on the LTS wiki, dates, times, locations of the sessions. | |
| − | + | ||
| − | + | Agenda for Steering Committee meeting | |
| − | + | how to determine which projects are part of LTS - define criteria, publish the list. (we do already have a list of projects that are currently building with LTS forge) | |
| + | |||
| + | how do participants make a commitment to be part of LTS? Is it enough for them to qualify and be part of the build forge (infrastructure ready), or do they need to make a commitment to actually provide the support (whether themselves or via 3rd parties). | ||
| + | |||
| + | Steering committee needs to define what are the next steps after a project is LTS-ready. Identifying service providers, etc. Maybe there are two tiers - ready for self-service, vs. having service providers identified. Consumer / provider / consumer-provider | ||
| + | |||
| + | Agenda for EclipseCon general session | ||
| + | overview of LTS IWG - what we're trying to accomplish - | ||
| + | |||
| + | Target date for steering committee meeting - schedule for the week of Oct 8. | ||
| + | |||
| + | Updates from Andrew after the call: | ||
| + | |||
| + | LTS meeting agenda wiki page: | ||
| + | The page is started here: | ||
| + | http://wiki.eclipse.org/LTS/SC_1_Agenda | ||
| + | |||
| + | Once we confirm the date for our next IWG/SC meeting, we can move the | ||
| + | page to a more sensible name following the convention we've been using. | ||
| + | e.g. http://wiki.eclipse.org/LTS/July30_2012 | ||
Revision as of 12:59, 23 October 2012
DRAFT This meeting is for the Long Term Support Industry Working group at Eclipse.
Contents
Time and Location
See the conference bridge details
Attendees
The following people are planning to attend:
Attended
- Pat Huff - IBM (co-chair)
- Jochen Krause - EclipseSource/Innopract (co-chair)
- Andrew Ross - Eclipse Foundation
- Steve Francisco - IBM
- Lisa Lasher - IBM
Absent
- Paul Lipton, Kurt Thys - CA Technologies
Regrets sent
Actions
Existing
New
- Jochen and Andrew, please send Lisa a note with the best times to set up a recurring 1 hour call for the next three weeks
Agenda
Website - Andrew: we will have one set up in time for EclipseCon - it should be ready in a couple weeks.
Membership - Jochen had a call with SAP and SpringSource to talk about requirements for joining LTS. Need to be on the release train, which might not be practical for runtime projects. They usually only have a little tooling in the release train, but not the runtime, because that would not typically be installed as part of the IDE. The release train focuses on the IDE. So maybe that requirement doesn't make sense? This should be discussed in the steering committee meeting. We want to encourage as many projects as possible to participate - we want to be inclusive, not exclusive. But we do need some rules to be sure that they are able to conform to LTS. SAP's Virgo is an example - it's a runtime, not on the release train, but we certainly want them to be part of LTS. Jochen told SAP that we would discuss this at the next Steering Committee. Maybe the rule is that you have to be on the release train, or you can be designated by the steering committee as exceptions to the rule. How important is it to be in simultaneous release? Maybe the underlying need is that they are compatible with the simultaneous release and to have an automated repeatable build with repeatable test cases. Orion is another big exception. Release train has been a quick way to sort out mainstream projects from less active projects.
We will need to provide a mechanism for people to request other projects and/or release levels that they want LTS for. For example, there could be a need for a 3.6.2-based LTS
Prep for EclipseCon We should try to get a meeting of the steering committee before EclipseCon. As of today, Steering Committee members of LTS include: SAP, CA Technologies, IBM, Innoopract. In the 2 hour slot that we have at EclipseCon, make the first hour be for the steering committee, second hour general interest
We'll want to put the EclipseCon agenda on the LTS wiki, dates, times, locations of the sessions.
Agenda for Steering Committee meeting how to determine which projects are part of LTS - define criteria, publish the list. (we do already have a list of projects that are currently building with LTS forge)
how do participants make a commitment to be part of LTS? Is it enough for them to qualify and be part of the build forge (infrastructure ready), or do they need to make a commitment to actually provide the support (whether themselves or via 3rd parties).
Steering committee needs to define what are the next steps after a project is LTS-ready. Identifying service providers, etc. Maybe there are two tiers - ready for self-service, vs. having service providers identified. Consumer / provider / consumer-provider
Agenda for EclipseCon general session overview of LTS IWG - what we're trying to accomplish -
Target date for steering committee meeting - schedule for the week of Oct 8.
Updates from Andrew after the call:
LTS meeting agenda wiki page: The page is started here: http://wiki.eclipse.org/LTS/SC_1_Agenda
Once we confirm the date for our next IWG/SC meeting, we can move the page to a more sensible name following the convention we've been using. e.g. http://wiki.eclipse.org/LTS/July30_2012