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.
Difference between revisions of "Planning Council/March 20 2011"
(→Introduction and Introductions) |
|||
| Line 1: | Line 1: | ||
| − | == Introduction and Introductions == | + | == Introduction and Introductions == |
| + | This is our annual, traditional EclipseCon Face-Face Meetings, Sunday, March 20, At Hyatt, Napa Room. | ||
| − | + | ::3-4 (Pacific Time) PC face-to-face meeting, followed by | |
| − | ::3-4 (Pacific Time) PC face-to-face meeting, followed by | + | |
::4-5 (Pacific Time) Joint Councils Meeting (See [http://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg01858.html Donald's note to list]). | ::4-5 (Pacific Time) Joint Councils Meeting (See [http://dev.eclipse.org/mhonarc/lists/eclipse.org-planning-council/msg01858.html Donald's note to list]). | ||
| − | == Logistics == | + | == Logistics == |
{| cellspacing="0" cellpadding="4" border="1" | {| cellspacing="0" cellpadding="4" border="1" | ||
| Line 16: | Line 16: | ||
| Wednesday, March 20, 2011, at [http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=03&day=20&hour=19&min=0&sec=0&p1=179 3:00 PMC Pacific time. Napa Room] | | Wednesday, March 20, 2011, at [http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=03&day=20&hour=19&min=0&sec=0&p1=179 3:00 PMC Pacific time. Napa Room] | ||
|- | |- | ||
| − | | <del>Dial-in: </del> No dial in. | + | | <del>Dial-in: </del> No dial in. |
| − | | <del>For the call-in numbers, see the "Project Review" number on [https://dev.eclipse.org/portal/myfoundation/portal/portal.php Foundation Portal] page.</del> | + | | <del>For the call-in numbers, see the "Project Review" number on [https://dev.eclipse.org/portal/myfoundation/portal/portal.php Foundation Portal] page.</del> |
|} | |} | ||
== Attendees == | == Attendees == | ||
| − | {| cellpadding=" | + | |
| + | |||
| + | {| width="80%" cellspacing="1" cellpadding="1" border="3" | ||
| + | |+ Attendees | ||
| + | |- | ||
| + | | | ||
| + | | | ||
| + | |- | ||
| + | | | ||
| + | | | ||
| + | |} | ||
| + | |||
| + | {| border="1" align="center" | ||
|- valign="top" | |- valign="top" | ||
| width="30%" | | | width="30%" | | ||
| − | + | <br> | |
{| border="1" | {| border="1" | ||
| + | |+ PMC (and Strategic) Reps | ||
|- | |- | ||
| Chris Aniszczyk | | Chris Aniszczyk | ||
| Technology (PMC) | | Technology (PMC) | ||
| − | | | + | | <br> |
|- | |- | ||
| − | | John Arthorne | + | | John Arthorne |
| Eclipse (PMC) | | Eclipse (PMC) | ||
| − | | | + | | <br> |
|- | |- | ||
| Oliver Cole | | Oliver Cole | ||
| Tptp (PMC) | | Tptp (PMC) | ||
| − | | X | + | | X |
|- | |- | ||
| − | | Mik Kersten | + | | Mik Kersten |
| − | | Mylyn (ALM) PMC | + | | Mylyn (ALM) PMC |
| − | | | + | | <br> |
|- | |- | ||
| Brian Payton | | Brian Payton | ||
| Datatools (PMC) | | Datatools (PMC) | ||
| − | | | + | | <br> |
|- | |- | ||
| Anthony Hunter | | Anthony Hunter | ||
| Tools (PMC) | | Tools (PMC) | ||
| − | | | + | | <br> |
|- | |- | ||
| Adrian Mos | | Adrian Mos | ||
| SOA (PMC) | | SOA (PMC) | ||
| − | | | + | | <br> |
|- | |- | ||
| Ed Merks | | Ed Merks | ||
| Modeling (PMC) | | Modeling (PMC) | ||
| − | | | + | | <br> |
|- | |- | ||
| Thomas Watson | | Thomas Watson | ||
| Rt (PMC) | | Rt (PMC) | ||
| − | | | + | | <br> |
|- | |- | ||
| David Williams | | David Williams | ||
| WTP (PMC) (appointed Chair) | | WTP (PMC) (appointed Chair) | ||
| − | | | + | | <br> |
|- | |- | ||
| Gary Xue | | Gary Xue | ||
| Birt (PMC) | | Birt (PMC) | ||
| − | | | + | | <br> |
|} | |} | ||
| − | + | ||
{| width="30%" border="1" | {| width="30%" border="1" | ||
| + | |+ Strategic Reps | ||
|- | |- | ||
| Cedric Brun | | Cedric Brun | ||
| OBEO (Strategic Developer) | | OBEO (Strategic Developer) | ||
| − | | | + | | <br> |
|- | |- | ||
| Stefan Daume | | Stefan Daume | ||
| Cloudsmith Inc.(Strategic Developer) | | Cloudsmith Inc.(Strategic Developer) | ||
| − | | | + | | <br> |
| − | |- | + | |- |
| Neil Hauge | | Neil Hauge | ||
| Oracle (Strategic Developer) | | Oracle (Strategic Developer) | ||
| − | | | + | | <br> |
|- | |- | ||
| Kaloyan Raev | | Kaloyan Raev | ||
| SAP AG (Strategic Developer) | | SAP AG (Strategic Developer) | ||
| − | | | + | | <br> |
|- | |- | ||
| Pascal Rapicault | | Pascal Rapicault | ||
| Sonatype (Strategic Developer) | | Sonatype (Strategic Developer) | ||
| − | | | + | | <br> |
|- | |- | ||
| − | | Markus Knauer | + | | Markus Knauer |
| Innoopract (Strategic Developer) | | Innoopract (Strategic Developer) | ||
| − | | | + | | <br> |
|- | |- | ||
| Christian Kurzke | | Christian Kurzke | ||
| Motorola (Strategic Developer) | | Motorola (Strategic Developer) | ||
| − | | | + | | <br> |
|- | |- | ||
| − | | Achim Loerke | + | | Achim Loerke |
| − | | BREDEX (Strategic Developer) | + | | BREDEX (Strategic Developer) |
| − | | | + | | <br> |
|} | |} | ||
| − | + | ||
{| width="30%" border="1" | {| width="30%" border="1" | ||
| + | |+ Appointed | ||
|- | |- | ||
| Wayne Beaton | | Wayne Beaton | ||
| Eclipse Foundation (appointed) | | Eclipse Foundation (appointed) | ||
| − | | | + | | <br> |
|} | |} | ||
| − | <br><small>Note: feel free to correct any errors/omissions in above attendance record.</small><br><small>Y = Yes, attended</small><br><small>N = No, did not</small><br><small>R = regrets sent ahead of time</small><br><small>X = not expected</small> | + | <br><small>Note: feel free to correct any errors/omissions in above attendance record.</small><br><small>Y = Yes, attended</small><br><small>N = No, did not</small><br><small>R = regrets sent ahead of time</small><br><small>X = not expected</small> |
|} | |} | ||
| Line 130: | Line 145: | ||
| width="30%" | | | width="30%" | | ||
{| border="1" | {| border="1" | ||
| + | |+ Inactive | ||
|- | |- | ||
| ? | | ? | ||
| Line 148: | Line 164: | ||
|} | |} | ||
| − | <br> | + | <br> |
| − | == Announcements == | + | == Announcements == |
| − | * ? | + | * ? |
| − | == Indigo Status == | + | == Indigo Status == |
| − | * ? | + | * ? |
== Misc business == | == Misc business == | ||
| − | * Name that release; Indigo+1. We'll examine votes, and be sure there is a clear winner, and that the winner is not objectionable in some way we didn't think of before. Remember, once we come up with the name, it will have to be "vetted" by Ian/Mike to make sure there would be no trademark infringement, etc. (They might be able to do this "in days", before EclipseCon is over ... but not sure.) (Pascal?) | + | *Name that release; Indigo+1. We'll examine votes, and be sure there is a clear winner, and that the winner is not objectionable in some way we didn't think of before. Remember, once we come up with the name, it will have to be "vetted" by Ian/Mike to make sure there would be no trademark infringement, etc. (They might be able to do this "in days", before EclipseCon is over ... but not sure.) (Pascal?) |
| − | * Status, plans, and urgency of moving from CVS to GIT. Why it is required, again? (Denis, Wayne?) | + | *Status, plans, and urgency of moving from CVS to GIT. Why it is required, again? (Denis, Wayne?) |
| − | * [http://www.eclipse.org/org/councils/roadmap_v6_0/| V6 of the Eclipse Road Map] ... mostly here for reference. Any feedback should have already been given, I believe, if I understand the dates ... board review is next day. | + | *[http://www.eclipse.org/org/councils/roadmap_v6_0/| V6 of the Eclipse Road Map] ... mostly here for reference. Any feedback should have already been given, I believe, if I understand the dates ... board review is next day. |
| − | * [http://wiki.eclipse.org/RequirementsCouncilThemesAndPriorities| Themes and Priorities]. (Again, here for reference, may be discussed at joint meeting.) | + | *[http://wiki.eclipse.org/RequirementsCouncilThemesAndPriorities| Themes and Priorities]. (Again, here for reference, may be discussed at joint meeting.) |
| − | == Eclipse 4.2 vs. 3.8 == | + | == Eclipse 4.2 vs. 3.8 == |
| − | Next year, what's primary, what's secondary? Do we buy-in to the [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg05597.html Eclipse Project's (implied) proposal]? | + | Next year, what's primary, what's secondary? Do we buy-in to the [http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg05597.html Eclipse Project's (implied) proposal]? |
Think of it in these terms ... there may be a test ... on a scale of 1 to 10, how important is it to your projects and strategic member companies you represent to use 3.8 or 4.2? Think of 1 as very important to stay on 3.8 as primary, 5 is don't care, they are happy to go along with what others need, and 10 is very important to move to 4.2 as the primary? | Think of it in these terms ... there may be a test ... on a scale of 1 to 10, how important is it to your projects and strategic member companies you represent to use 3.8 or 4.2? Think of 1 as very important to stay on 3.8 as primary, 5 is don't care, they are happy to go along with what others need, and 10 is very important to move to 4.2 as the primary? | ||
| + | <br> | ||
| − | == Long Term Planning discussion == | + | == Long Term Planning discussion == |
| − | + | ||
| − | + | ||
| − | + | EclipseCon face-to-face is good time to discuss high level, long term issues. The following items are seeds to brainstorming ... please add any of your own. They can range from a thought, question, or a well developed proposal. | |
| − | * | + | *[We will start with a reminder of our mission, purpose, goals, etc.] |
| − | * | + | *How are we doing? Beside 'being on time' are we achieving the best quality that we can? By focusing our projects on items that have biggest return for investment, for Eclipse as a whole? |
| − | * | + | *Should we have "must do" items at all? Or, are they just recommendations? |
| − | * | + | *Are the requirements about right? Too many? Too few? |
| − | * | + | *Should we have requirement related to bug fix rate? Backlog reduction? unit test coverage? |
| − | * | + | *Is the release tracking checklist on Portal worthwhile? Should we do away with it? Should we make it better? (More "auto fill-in" ... more "testing" results provide the data for forms, projects provide the exceptions/documentation. |
| − | * | + | *Who is the audience(s)? (Projects, PMCs, Planning Council, Adopters). |
| − | + | *Is yearly release (with two service releases) the right interval? Should maintenance be quarterly? Should releases be every other year? Or, perhaps, every other year be a LTS releases with "off" year having less maintenance emphasis? | |
| + | == Next Meeting == | ||
| − | * April 6, 2011 (our regular "first Wednesday" meeting, at Noon Easter). | + | *April 6, 2011 (our regular "first Wednesday" meeting, at Noon Easter). |
== Reference == | == Reference == | ||
| − | :[http://www.eclipse.org/indigo/planning/EclipseSimultaneousRelease.php Indigo Requirements] | + | :[http://www.eclipse.org/indigo/planning/EclipseSimultaneousRelease.php Indigo Requirements] |
| − | :[[ | + | :[[Indigo|Indigo Wiki page]] |
| − | :[[ | + | :[[Planning Council/Helios retrospective]] |
| − | :[[Indigo/ | + | :[[Indigo/Simultaneous Release Plan|Indigo Simultaneous Release]] |
| − | :[http://www.eclipse.org/org/foundation/council.php#planning Planning Council Members] | + | :[http://www.eclipse.org/org/foundation/council.php#planning Planning Council Members] |
:[[Simultaneous Release Roles]] and [[Simultaneous Release Roles/EMO]] | :[[Simultaneous Release Roles]] and [[Simultaneous Release Roles/EMO]] | ||
Revision as of 03:11, 16 March 2011
Contents
Introduction and Introductions
This is our annual, traditional EclipseCon Face-Face Meetings, Sunday, March 20, At Hyatt, Napa Room.
- 3-4 (Pacific Time) PC face-to-face meeting, followed by
- 4-5 (Pacific Time) Joint Councils Meeting (See Donald's note to list).
Logistics
| Meeting Title: | Planning Council EclipseCon face-to-face meeting |
| Date & Time: | Wednesday, March 20, 2011, at 3:00 PMC Pacific time. Napa Room |
| |
|
Attendees
|
|
Inactive
|
Announcements
- ?
Indigo Status
- ?
Misc business
- Name that release; Indigo+1. We'll examine votes, and be sure there is a clear winner, and that the winner is not objectionable in some way we didn't think of before. Remember, once we come up with the name, it will have to be "vetted" by Ian/Mike to make sure there would be no trademark infringement, etc. (They might be able to do this "in days", before EclipseCon is over ... but not sure.) (Pascal?)
- Status, plans, and urgency of moving from CVS to GIT. Why it is required, again? (Denis, Wayne?)
- V6 of the Eclipse Road Map ... mostly here for reference. Any feedback should have already been given, I believe, if I understand the dates ... board review is next day.
- Themes and Priorities. (Again, here for reference, may be discussed at joint meeting.)
Eclipse 4.2 vs. 3.8
Next year, what's primary, what's secondary? Do we buy-in to the Eclipse Project's (implied) proposal?
Think of it in these terms ... there may be a test ... on a scale of 1 to 10, how important is it to your projects and strategic member companies you represent to use 3.8 or 4.2? Think of 1 as very important to stay on 3.8 as primary, 5 is don't care, they are happy to go along with what others need, and 10 is very important to move to 4.2 as the primary?
Long Term Planning discussion
EclipseCon face-to-face is good time to discuss high level, long term issues. The following items are seeds to brainstorming ... please add any of your own. They can range from a thought, question, or a well developed proposal.
- [We will start with a reminder of our mission, purpose, goals, etc.]
- How are we doing? Beside 'being on time' are we achieving the best quality that we can? By focusing our projects on items that have biggest return for investment, for Eclipse as a whole?
- Should we have "must do" items at all? Or, are they just recommendations?
- Are the requirements about right? Too many? Too few?
- Should we have requirement related to bug fix rate? Backlog reduction? unit test coverage?
- Is the release tracking checklist on Portal worthwhile? Should we do away with it? Should we make it better? (More "auto fill-in" ... more "testing" results provide the data for forms, projects provide the exceptions/documentation.
- Who is the audience(s)? (Projects, PMCs, Planning Council, Adopters).
- Is yearly release (with two service releases) the right interval? Should maintenance be quarterly? Should releases be every other year? Or, perhaps, every other year be a LTS releases with "off" year having less maintenance emphasis?
Next Meeting
- April 6, 2011 (our regular "first Wednesday" meeting, at Noon Easter).