[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[hyades-dev] Planning Group & PMC Group Notes for September 7th, 2004
|
1) Apologies etc.
Attending:
Tyler Thessin, Intel
Gian Franco Bonini, SAP
Don Ebright, Compuware
Serge Lucio, IBM
Harm Sluiman, IBM
Jim Saliba, CA
Observing:
Melanie Woods, Scapa
Apologies:
Rob Sinclair, IBM
George Din, FOKUS
Mike Norman, Scapa
2) Minutes and matters arising
Nothing to report
3) PMC and Eclipse interaction
Draft committer lists have been received from Harm, Serge, Mike and Don.
The TPTP planning and requirements groups are currently 'designated at
will', rather than requiring committer elections. This may mean that a
tweak to the current charter is required.
Contributors to planning, architecture and requirements council groups
need to be finalized, and representatives from all current contributing
companies are eligible. Representatives from new contributing companies
will be considered. The representatives at these groups can be the same
as those representing their companies at the planning group meetings.
Please send details of your representatives to Tyler.
Discussion regarding the transitioning of current, available 'Hyades'
and 'TPTP' mailing lists and newsgroups. The current 'Hyades' mailing
list and newsgroup could be utilised for 'platform'-specific information
and the TPTP mailing list and newsgroup could be used for
'project'-specific information. The team might also consider having
separate mailing lists and newsgroups for each project.
There is an immediate requirement for some website updates, including
moving links to mailing lists and newsgroups to one area (i.e. TPTP
area) and transitioning information on the eclipse tools projects page.
The marketing group will look into this and devise a phased plan of
action with regard to immediate and future requirements.
The finalised planning and requirements groups and the immediate website
updates should be completed by the F2F meeting (28-30 September).
An update from the Eclipse council group meetings was provided. These
meetings were scheduled to identify membership and processes and define
future group plans. These plans are targeted for completion by
EclipseCon in February 2005. The TPTP council groups will try to
interleave their future meetings with the Eclipse council meetings.
Some opportunities that have arisen from the Eclipse Council meetings
are as follows:
- TPTP project intention is to leverage reporting capabilities from the
BIRT project. Current reporting capabilities will be migrated into the
BIRT project.
- Eclipse testing was again proposed, and other projects have expressed
an interest in using TPTP to test their work. In particular, it was
mentioned that QNX are interested in GUI testing capabilities and are
willing to help with any Abbot requirements.
Harm has already sent out his notes from the Eclipse Architecture
Council meeting. In summary, these discuss the concept of mapping out
functionality and uses and dependencies for all Eclipse projects and
improvements to the record resource support (documentation dependencies
and support) for other projects. The council will provide guiding
principles for charters, so that no new projects overlap (e.g. reporting
capabilities). TPTP will build a dependency on reporting and feed this
into the BIRT project. It arose that the CDT project is interested in
the TPTP profiling capabilities. The architecture council was supportive
of TPTP proposals.
ACTION: All to send details of planning and requirements council group
members
ACTION: Tyler to finalise members of planning and requirements groups
ACTION: Harm to look into potential disruption to mailing list/newsgroup
through name change, and to possible new mailing lists/newsgroups for
each project
4) Operation of the current plan
Another drop is required to re-instigate a fix that had been removed.
The feature work is going well. Some of the specification documents that
were supposed to be completed by this iteration, will not make it. The
teams are aiming to have the backlog of open issues completed. There are
currently 180 low priority defects and no major defects. The 3.1 release
is expected to be very stable.
It was mentioned that the Core platform has devised an algorithm for
closing off irrelevant or outdated issues. TPTP is tackling all issues,
assessing for validity and assigning as required. We currently have 286
outstanding enhancement requests, 283 of which are future requests.
5) Technical forward plan
The next face-to-face (F2F) is scheduled for w/c September 27th. The F2F
meeting will aim to finish at or around 3.30/4pm on Thursday 30th
September, so attendees are advised to try to accommodate this in their
travel arrangements. PMC leads plus representatives to the planning,
architecture and requirements groups are invited.
An email was sent to hyades-dev to request suggestions for requirements
in the post 3.1 release timeframe. No feedback has been posted to
hyades-dev. The planning group is encouraged to use the current roadmap
as a reference point to identify additional requirements. The project
needs to have suggested requirements by the F2F meeting.
It as noted that the design phase for 3.2 begins in the week commencing
September 20th.
ACTION: Tyler to create and distribute F2F meeting agenda
ACTION: All to confirm attendance at the upcoming F2F
ACTION: All to send suggested requirements to Mike/Tyler
ACTION: Harm to advise on requirements for 3.2 timeline
6) Internal and external communication
The marketing group held its first meeting last Thursday, and discussed
a number of events, awards, and PR and communications opportunities that
will require further consideration. The planning group would like to see
an events calendar and plan of action, in particular for events in the
short-term (to end of 2004).
ACTION: Marketing Group to define events calendar and action plan and
deliver to the planning group
Next Planning Group meeting: Tuesday, 14th September 2004, - 5pm CET /
4pm BST / 11am EST / 8am PST