Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Polarsys/Telcos/20120712"

(Next Polarsys telcos)
(Polarsys Top Level Project Proposal)
 
(One intermediate revision by the same user not shown)
Line 20: Line 20:
  
 
= Status about infrastructure and infrastructure test =
 
= Status about infrastructure and infrastructure test =
* Infrastructure
+
* Telco on GPM installation held on July 3 with Anne Haugommard, Mathieu Velten, Pierre Gaufillet, Gaël Blondelle and Denis Roy.
* Install GPM on a specific server
+
** Denis Roy will provide a virtual machine configured with the standard os from Eclipse so that Ann and Mathieu can install GPM and the missing components on this instance and test it on an "Eclipse" like infrastructure.
 
+
* Issue: Bugzilla, bugs for specific components
* Test infrastructure for OPEES members
+
** Define component categories is mandatory before creating more bugzilla components.
** GIT/HTTPS should be available when we have a correct official SSL certificate
+
** Create a Polarsys project to host the Polarsys bundle build tests on the test infrastructure
+
** Issue: Bugzilla, bugs for specific components
+
*** Define component categories is mandatory before creating more bugzilla components.
+
** GPM
+
*** Needs extra components like JDK6, postgresql, ...
+
*** '''Organize a short telco with Denis Roy, Anne Haugemmard, Mathieu Valten'''
+
* Setting up the official Polarsys infrastructure
+
** [http://wiki.eclipse.org/Polarsys/TLPProposal Top Level Project proposal is being written]
+
** Work on the Polarsys [[Polarsys/ReleaseEngineering | release engineering]] strategy
+
  
 
= Polarsys Top Level Project Proposal =
 
= Polarsys Top Level Project Proposal =
 
http://wiki.eclipse.org/Polarsys/TLPProposal  
 
http://wiki.eclipse.org/Polarsys/TLPProposal  
Commented and discussed by Maurice Heitz.
+
 
Need for an Polarsys Infrasturcutre sub project.
+
Comments and discussion with Maurice Heitz:
Long Term Archiving
+
* Need for a Polarsys Infrastructure sub project.
Long Term Build Infrastructure
+
** Not necessarily indicated in the proposal. We will put in place tags for the each component, and one tag should be polarsys_infra. We will keep in mind the fact that a given component like GPM can be part of both the infrastructure and the projects delivered by Polarsys.
Component Assessment Tools
+
In the TLP project presentation page, we will have to clearly identify and document:
Release Engineering
+
* Long Term Archiving
 +
* Long Term Build Infrastructure
 +
* Component Assessment Tools
 +
* Release Engineering
  
 
= Next Polarsys meetings =
 
= Next Polarsys meetings =

Latest revision as of 02:33, 11 September 2012

Attendees

  • Gaël Blondelle (Obeo)
  • Silvia Mazzini (Intecs)
  • Lei Pi (Intecs)
  • Patrick Moreau (Inria)
  • Maurice Heitz (C-S)

Polarsys membership

  • Membership agreement and charter are available on the Polarsys wiki page.
  • Currently members are:
    • Ericsson
    • Thales
    • Airbus
    • Obeo
  • Documents
    • Membership agreement is common with other IWGs
    • The first version of the Charter has been frozen.
    • Interested parties can now sign the participation agreement. Contact Ralph Mueller to initiate the process.
  • Next efforts to be done to get universities signing their membership agreement.

Status about infrastructure and infrastructure test

  • Telco on GPM installation held on July 3 with Anne Haugommard, Mathieu Velten, Pierre Gaufillet, Gaël Blondelle and Denis Roy.
    • Denis Roy will provide a virtual machine configured with the standard os from Eclipse so that Ann and Mathieu can install GPM and the missing components on this instance and test it on an "Eclipse" like infrastructure.
  • Issue: Bugzilla, bugs for specific components
    • Define component categories is mandatory before creating more bugzilla components.

Polarsys Top Level Project Proposal

http://wiki.eclipse.org/Polarsys/TLPProposal

Comments and discussion with Maurice Heitz:

  • Need for a Polarsys Infrastructure sub project.
    • Not necessarily indicated in the proposal. We will put in place tags for the each component, and one tag should be polarsys_infra. We will keep in mind the fact that a given component like GPM can be part of both the infrastructure and the projects delivered by Polarsys.

In the TLP project presentation page, we will have to clearly identify and document:

  • Long Term Archiving
  • Long Term Build Infrastructure
  • Component Assessment Tools
  • Release Engineering

Next Polarsys meetings

  • October 22nd in Ludwigsburg, with a common part with the Automotive IWG. That's the day before Eclipse Con Europe
  • OPEES meeting under planning in Rennes on October 15-17. Restricted to OPEES members to prepare the end of the project.


Misc

  • Polarsys is too young for the moment to apply as an organization for SOCIS.
    • Next year, we should apply when we have software online in Polarsys.

Back to the top