Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-pmc] Agenda for October 11 telecon

Agenda:

  • Community update (and capabilities discussion)
  • Procedural
    1. Carl Trieloff (IONA) invited to next week’s meeting
    2. Charter mods – see attached. Next board call is the 19th.
  • Requirements update
    1. Update status on compiler warnings and API tracking defects
  • Architecture update
    1. API scanning / reliance tool update
  • 1.0 planning
    1. API progress
    2. Defect status (will begin providing summary report next week with agenda)
  • JSF project status update
  • Additional topics

 

Naci sent his regrets for this meeting.

 

 

From: wtp-pmc-bounces@xxxxxxxxxxx on behalf of Arthur Ryman [ryman@xxxxxxxxxx]
Sent: Tuesday, October 11, 2005 6:19 AM
To: wtp-pmc@xxxxxxxxxxx
Subject: [wtp-pmc] Proposed Modification to WTP Charter Regarding DraftStandards.

PMC Members,

I'd like to discuss this today. Tim reported that there were some objections to the wording at the last members meeting. I'd like to propose a new wording and get agreement from the PMC, then we should all review it with our companies to ensure no more objections remain.

Here is the wording with the modifications proposed by Mike Milinkovich.

"WTP may implement draft standards provided that the scope of the final version 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. "

Here is my proposed wording:

"WTP may implement a draft standard at the time that the relevant standards body requests public review or feedback based on implementation experience, e.g. a W3C Candidate Recommendation [1] or a JCP Public Draft [2],  provided that the domain of the standard is within the scope of WTP as defined by this Charter and that the relevant standards body has published the draft standard under licence terms that allow it to be implemented in a manner consistent with a transparent Open Source project."

[1] http://www.w3.org/Consortium/Process/
[2] http://www.jcp.org/en/procedures/overview

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx

Back to the top