Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "LTS/March27 2012"

< LTS
(New page: =Meeting @ EclipseCon= ==Time and Location== Tuesday March 27, 12:00 to 15:00 Eastern. Mixed locations. ==Related== There is a closely related meeting regarding the [http://wiki.eclips...)
 
(Minutes)
 
(6 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
Tuesday March 27, 12:00 to 15:00 Eastern. Mixed locations.
 
Tuesday March 27, 12:00 to 15:00 Eastern. Mixed locations.
  
==Related==
 
  
There is a closely related meeting regarding the [http://wiki.eclipse.org/CBI/March28_2012 CBI initiative] taking place in the morning. Also, the [http://wiki.eclipse.org/LTS/March28_2012 LTS meeting] taking place at 2pm.
 
  
 
==Agenda==
 
==Agenda==
Line 17: Line 15:
 
The following people plan to attend:
 
The following people plan to attend:
  
* Mike Milinkovich (part, near the end)
+
* Mike Milinkovich, Eclipse Foundation (in part)
 
* Andrew Ross, Ralph Mueller - Eclipse Foundation
 
* Andrew Ross, Ralph Mueller - Eclipse Foundation
 
* Karsten Schmidt, Jutta Bindewald, Thomas Rastetter - SAP
 
* Karsten Schmidt, Jutta Bindewald, Thomas Rastetter - SAP
 
* Gael Blondelle, Obeo
 
* Gael Blondelle, Obeo
 
* Pierre Gaufillet, Airbus
 
* Pierre Gaufillet, Airbus
 
  
 
==Minutes==
 
==Minutes==
 +
 +
NOTE: This is a wiki, if something is missing, incorrect, or not clear, please adjust as needed.
 +
 +
Please see an update from the minutes for the meeting on [http://wiki.eclipse.org/LTS/March29_2012 March 29, 2012].
  
 
We started discussing the relationship between Polarsys and LTS.
 
We started discussing the relationship between Polarsys and LTS.
Line 31: Line 32:
  
 
Refreshing memories, LTS has 3 levels:
 
Refreshing memories, LTS has 3 levels:
1) SC: all-access to forge & build farm, budget & governance control, change control committee
+
 
2) Premium: all access to forge and build farm
+
# SC: all-access to forge & build farm, budget & governance control, change control committee
3) Participating: binaries only
+
# Premium: all access to forge and build farm
 +
# Participating: binaries only
  
 
We had three main concerns:
 
We had three main concerns:
a) High complexity & ample opportunity for confusion.
+
# High complexity & ample opportunity for confusion.
b) Potential for one IWG providing the same services for cheaper than the other. (we noticed this was already so)
+
# Potential for one IWG providing the same services for cheaper than the other. (we noticed this was already so)
c) We need this to scale smoothly to many IWGs. Service providers potentially stuck paying twice, or further increasing complexity to avoid just seemed like a bad idea.
+
# We need this to scale smoothly to many IWGs. Service providers potentially stuck paying twice, or further increasing complexity to avoid just seemed like a bad idea.
  
 
We discussed a few ways around this, the idea that the team felt positive about was:
 
We discussed a few ways around this, the idea that the team felt positive about was:
  
 
Like usual:
 
Like usual:
i) Organizations are members of Eclipse (see ii for possible exceptions).
+
# Organizations are members of Eclipse
ii) IWG SC's can invite organizations to participate in their IWG without additional fees. e.g. a service provider, Universities, non-profits, etc.
+
# IWG SC's can invite organizations to participate in their IWG without additional fees. e.g. a service provider, Universities, non-profits, etc.
iii) Organizations needing/desiring influence satisfy the conditons for IWG SC, which may involve additional fees.
+
# Organizations needing/desiring influence satisfy the conditons for IWG SC, which may involve additional fees.
  
 
And:
 
And:
iv) Organizations needing forge, build farm, and other such services pay for LTS in addition to membership dues. LTS becomes the central hub for share services and infrastructure for all IWGs. We may consider a different name to reflect this. This is the natural entry point for service providers as they can provide support/maintenance/other services for all IWGs and the broader ecosystem.
+
# Organizations needing forge, build farm, and other such services pay for LTS in addition to membership dues. LTS becomes the central hub for shared services and infrastructure for all IWGs. We may consider a different name to reflect this. This is the natural entry point for service providers as they can provide support/maintenance/other services for all IWGs and the broader ecosystem.

Latest revision as of 13:47, 1 April 2012

Meeting @ EclipseCon

Time and Location

Tuesday March 27, 12:00 to 15:00 Eastern. Mixed locations.


Agenda

  • Discuss LTS, Polarsys relationship and business models

Attendees

The following people plan to attend:

  • Mike Milinkovich, Eclipse Foundation (in part)
  • Andrew Ross, Ralph Mueller - Eclipse Foundation
  • Karsten Schmidt, Jutta Bindewald, Thomas Rastetter - SAP
  • Gael Blondelle, Obeo
  • Pierre Gaufillet, Airbus

Minutes

NOTE: This is a wiki, if something is missing, incorrect, or not clear, please adjust as needed.

Please see an update from the minutes for the meeting on March 29, 2012.

We started discussing the relationship between Polarsys and LTS.

Our thinking was to have Polarsys SC members automatically receive LTS participating. This would *not* provide forge access. We flirted with Polarsys SC getting Premium LTS.

Refreshing memories, LTS has 3 levels:

  1. SC: all-access to forge & build farm, budget & governance control, change control committee
  2. Premium: all access to forge and build farm
  3. Participating: binaries only

We had three main concerns:

  1. High complexity & ample opportunity for confusion.
  2. Potential for one IWG providing the same services for cheaper than the other. (we noticed this was already so)
  3. We need this to scale smoothly to many IWGs. Service providers potentially stuck paying twice, or further increasing complexity to avoid just seemed like a bad idea.

We discussed a few ways around this, the idea that the team felt positive about was:

Like usual:

  1. Organizations are members of Eclipse
  2. IWG SC's can invite organizations to participate in their IWG without additional fees. e.g. a service provider, Universities, non-profits, etc.
  3. Organizations needing/desiring influence satisfy the conditons for IWG SC, which may involve additional fees.

And:

  1. Organizations needing forge, build farm, and other such services pay for LTS in addition to membership dues. LTS becomes the central hub for shared services and infrastructure for all IWGs. We may consider a different name to reflect this. This is the natural entry point for service providers as they can provide support/maintenance/other services for all IWGs and the broader ecosystem.

Back to the top