[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [polarsys-iwg] Polarsys Top Level Project creation
|
The steering committee members are known (it is just a matter of Polarsys membership).
We nevertheless need to elect at least the TOPCASED PPC representative to the AC to get ready to elect a first chairman, but it will probably take something like one month. And some other PPC will probably start soon.
I therefore propose to start with a temporary chairman who will dismiss as soon as the initial PPCs will be known and will have elected their representatives (and not more of course than one year).
If it is ok for you, it means that the AC chairman (aka PMC Leader) may be known on Oct. 19th, as steering committee members meet this day.
---
Pierre
-----Message d'origine-----
De : Mike Milinkovich [mailto:mike.milinkovich@xxxxxxxxxxx]
Envoyé : mercredi 3 octobre 2012 19:23
À : GAUFILLET, Pierre; 'Polarsys IWG'; wayne.beaton@xxxxxxxxxxx; 'Ralph Mueller'
Cc : 'Eclipse Webmaster'
Objet : RE: [polarsys-iwg] Polarsys Top Level Project creation
It seems that we may have a chicken-and-egg problem here. I know that there
is interest in provisioning the top-level project and to start processing
project proposals as soon as possible. However, to do so we need a
functioning PMC with a leader. (Wayne, please correct me if I'm wrong.)
How quickly can the Polarsys group put the Architecture committee in place?
> -----Original Message-----
> From: GAUFILLET, Pierre [mailto:pierre.GAUFILLET@xxxxxxxxxx]
> Sent: October-03-12 12:52 PM
> To: mike.milinkovich@xxxxxxxxxxx; Polarsys IWG; wayne.beaton@xxxxxxxxxxx;
> 'Ralph Mueller'
> Cc: 'Eclipse Webmaster'
> Subject: RE: [polarsys-iwg] Polarsys Top Level Project creation
>
> Hello!
>
> Given the governance schema of Polarsys, it should be the chairman of the
> Architecture committee of the Architecture committee itself.
> But for that, we need first to boot the Architecture Committee :-)
>
> To begin with, the initial members of the Architecture Committee are known
> right now, as described below:
>
> [...]
> Architecture Committee
> Powers and Duties
>
> Architecture Committee members are required to
>
> Ensure the technical consistency of Polarsys projects
> Ensure that Polarsys projects achieve VLTS objectives
> Recommend technologies
> Establish technical guidelines
> Validate new project proposals
>
> Composition
>
> Each Steering Committee Member of the IWG has a seat on the
> Architecture Committee.
> Each Project Planning Committee elects one of its members to the
> Architecture Committee.
> The Architecture Committee elects a chairman who reports to the
> Steering Committee. This chairman is elected among the members of the
> Architecture Committee. He will serves from April 1 to March 31 of each
> calendar year, or until his successor is elected and qualified, or as
otherwise
> provided for in this charter.
>
> Meeting Management
>
> The Architecture Committee meets at least twice a year.
>
> [...]
>
> As far as I know, only one PPC has been started until now, so the AC has a
> maximum of 5 members.
>
> ---
> Pierre
>
>
> -----Message d'origine-----
> De : polarsys-iwg-bounces@xxxxxxxxxxx [mailto:polarsys-iwg-
> bounces@xxxxxxxxxxx] De la part de Mike Milinkovich
> Envoyé : mercredi 3 octobre 2012 18:32
> À : 'Polarsys IWG'; wayne.beaton@xxxxxxxxxxx; 'Ralph Mueller'
> Cc : 'Eclipse Webmaster'
> Objet : Re: [polarsys-iwg] Polarsys Top Level Project creation
>
> Gael,
>
> Actually, one of the next steps is to nominate a PMC Leader for approval
by
> the Eclipse Board of Directors. Who will be the person or persons who will
> lead the PMC?
>
>
> > -----Original Message-----
> > From: polarsys-iwg-bounces@xxxxxxxxxxx [mailto:polarsys-iwg-
> > bounces@xxxxxxxxxxx] On Behalf Of Gaël Blondelle
> > Sent: October-02-12 9:50 AM
> > To: wayne.beaton@xxxxxxxxxxx; Ralph Mueller
> > Cc: polarsys-iwg@xxxxxxxxxxx; Eclipse Webmaster
> > Subject: [polarsys-iwg] Polarsys Top Level Project creation
> >
> > Dear Ralph, Wayne,
> >
> > On September 20th, Ralph sent an email to the Polarsys mailing list in
> order
> > to tell us that the Polarsys TLP proposal was adopted by the Eclipse
board
> of
> > Directors.
> >
> > Can you tell us what are the next steps?
> > I guess that we need some provisionning for a clean official Polarsys
> platform
> > infrastructure.
> >
> > For your information, some Polarsys members (and potential partners)
> want
> > to submit new project proposals in this context. I'll point them to the
> project
> > proposal template http://www.eclipse.org/proposals/templates/proposal-
> > template.zip.
> >
> > Best regards,
> > Gaël Blondelle
> > _______________________________________________
> > polarsys-iwg mailing list
> > polarsys-iwg@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/polarsys-iwg
>
>
> _______________________________________________
> polarsys-iwg mailing list
> polarsys-iwg@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/polarsys-iwg
>
> This mail has originated outside your organization, either from an
external
> partner or the Global Internet.
> Keep this in mind if you answer this message.
>
>
>
> The information in this e-mail is confidential. The contents may not be
> disclosed or used by anyone other than the addressee. Access to this
e-mail
> by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus immediately
and
> delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or completeness
of
> this e-mail as it has been sent over public networks. If you have any
concerns
> over the content of this message or its Accuracy or Integrity, please
contact
> Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated virus
> scanning software but you should take whatever measures you deem to be
> appropriate to ensure that this message and any attachments are virus
free.
>
This mail has originated outside your organization, either from an external partner or the Global Internet.
Keep this in mind if you answer this message.
The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.
