Mike’s proposed deltas to the Charter language are in the attached
email thread.
------------------------------------------------------------------------
*From:* Tim Wagner
*Sent:* Tuesday, August 23, 2005 3:53 AM
*To:* 'WTP PMC communications (including coordination, announcements,
and Group discussions)'; raghunathan.srinivasan@xxxxxxxxxx
*Subject:* [wtp-pmc] August 23rd telecon agenda
Welcome back to the weekly WTP PMC calls!
*Agenda:*
* Community update and 0.7 release feedback
* 0.7.1 status and planning
* 1.0 release planning (see attached)
* releng issues (see attached)
* charter revision amendment from Mike Milinkovich
* requirements update/planning
* architecture update/planning
* other items
I’m just returned from vacation, so apologies in advance if I’ve
missed agenda items…still working through the 1000’s of emails that
accrued.
------------------------------------------------------------------------
*From:* Mike Milinkovich [mike.milinkovich@xxxxxxxxxxx]
*Sent:* Friday, August 05, 2005 1:03 PM
*To:* Ed Cobb; Tim Wagner; Janet Campbell
*Cc:* 'Bjorn Freeman-Benson'; 'WTP PMC communications (including
coordination, announcements, and Group discussions)'
*Subject:* RE: Revised WTP charter for Eclipse Board consideration
As per my last note, I would like to have someone from the WTP PMC
send me a revised draft. Since I am going on vacation for a week,
please ask Janet Campbell to forward the draft to the board email list.
Also, I would like to propose one additional change to the sentence
regarding implementing draft specifications. Something to the effect:
"WTP may implement draft standard specifications provided that the
intended scope of the final version of the specification remains
consistent with this Charter, and provided that the relevant standards
body will grant Eclipse sufficient rights to the draft specification
to implement them in a manner consistent with a transparent open
source project. "
Mike Milinkovich
Executive Director,
Eclipse Foundation, Inc.
Office: 613-224-9461 x228
Cell: 613-220-3223
mike.milinkovich@xxxxxxxxxxx <mailto:mike.milinkovich@xxxxxxxxxxx>
blog: http://milinkovich.blogspot.com/
------------------------------------------------------------------------
*From:* Ed Cobb [mailto:ecobb@xxxxxxx]
*Sent:* August 3, 2005 6:20 PM
*To:* mike.milinkovich@xxxxxxxxxxx; Tim Wagner
*Cc:* Bjorn Freeman-Benson; WTP PMC communications (including
coordination, announcements, and Group discussions)
*Subject:* RE: Revised WTP charter for Eclipse Board consideration
Mike, consensus here is that your proposed changes are
reasonable, so unless you hear from someone else on the PMC, I
suggest we go with them.
*Edward Cobb*
VP, Architecture & Standards
Office of the CTO
Phone: +1-408.570.8264
Mobile: +1-408.464.0733
IM: sfgiants_2002
ed.cobb@xxxxxxx <mailto:ed.cobb@xxxxxxx>
*BEA Systems, Inc.*
Corporate Office, USA
2315 North First Street
San Jose, CA 95131
Fax: +1-408.570.8914
www.bea.com <http://www.bea.com>
------------------------------------------------------------------------
*From:* Mike Milinkovich [mailto:mike.milinkovich@xxxxxxxxxxx]
*Sent:* Monday, August 01, 2005 2:35 PM
*To:* Tim Wagner
*Cc:* Ed Cobb; 'Bjorn Freeman-Benson'; 'WTP PMC communications
(including coordination, announcements, and Group discussions)'
*Subject:* RE: Revised WTP charter for Eclipse Board consideration
Tim,
I would like to suggest the following revisions before taking this
to the Board. (I apologize if you receive different or additional
guidance from Bjorn. I am writing this in an airplane.)
* Replace "Additional projects will be created within the
overall Scope where resources and interest allow." with
"Additional projects will be created //as per the
then-current Eclipse Development Process //within the
overall Scope where resources and interest allow." This is
to make it clear that the final approval resides with the
EMO as the current development process says:
If a new Project is being proposed and the PMC is
satisfied with its Creation Review and its proposed
Project Lead, the PMC asks the EMO to approve the Project.
The EMO may approve a Project that is consistent with the
Top Level Project’s Charter. If the proposed Project is
inconsistent with the Top Level Project’s Charter, then
the EMO may either reject the Proposal or propose an
extension of the Charter to the Board, which would then
determine whether or not to approve the extension. The EMO
may not approve any Project that is inconsistent with the
Purposes. If any Member believes that the EMO has acting
incorrectly in approving or rejecting a proposed Project,
that Member may appeal to the Board to review the EMO’s
decision.
And this way, it is clear that if the overall process changes,
the process of adding projects to WTP changes.
* This sentence is ambiguous: "WTP may implement draft
standards provided the final version remains consistent with
this Charter. " Is the "final version" referring to the
spec? Would "WTP may implement draft standard specifications
provided that the intended scope of the final version of the
specification remains consistent with this Charter. " be
clearer? I admit that I am guessing a little bit w.r.t. what
you mean here.
Thanks.
Mike Milinkovich
Executive Director,
Eclipse Foundation, Inc.
Office: 613-224-9461 x228
Cell: 613-220-3223
mike.milinkovich@xxxxxxxxxxx <mailto:mike.milinkovich@xxxxxxxxxxx>
blog: http://milinkovich.blogspot.com/
------------------------------------------------------------------------
*From:* Tim Wagner [mailto:twagner@xxxxxxx]
*Sent:* July 29, 2005 9:36 PM
*To:* mike.milinkovich@xxxxxxxxxxx
*Cc:* Ed Cobb; Bjorn Freeman-Benson; WTP PMC communications
(including coordination, announcements, and Group discussions)
*Subject:* Revised WTP charter for Eclipse Board consideration
Mike,
Please ask the Eclipse Board of Directors to consider this
revision to the WTP charter on behalf of the WTP PMC.
In the attached zip you will find:
* *Revised WTP Charter.html* – the revised content of the
charter. “images/subprojects.gif” is required to view
this page.
* *Original Charter.htm* – the original (current charter).
Files in the “Original Charter_files” directory are
required to view this page.
* *Delta.doc* – a Word document showing the differences
between the two charter files above as markup.
(Normative material; “Revised WTP Charter.html” should
be considered definitive.)
These are the modifications we discussed previously and which
the WTP PMC has voted to accept. I will be on vacation through
8/19; please address any logistical questions or problems to
the WTP PMC mailing list in the interim.
In the event of problems that prevent the acceptance of this
revision in its entirety in the August meeting, please make a
request to the Board that at least the modification to accept
additional subprojects be granted, so that the JSF project can
proceed subsequent to its creation review.
Thanks for your help in this matter,
Tim Wagner, on behalf of the WTP PMC
------------------------------------------------------------------------
_______________________________________________
wtp-pmc mailing list
wtp-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-pmc
