The agenda of the first PTF meeting on 17 June was divided into a
discussion about requirements and a discussion about the proposed EGEE
services.  Activity representatives gave an overview of available
requirement documents in their domains.  From this discussion it was
clear that many documents exist to construct an prioritized overview
of all requirements, but that such an overview doesn't yet exist.
This discussion brought out several new requirements of which the
service developers were not yet aware, e.g. need for distribution and
use of commercial software on the grid.  The service developers also
pointed out that many of the requirements are often vague or contain
multiple requirements.  Part of the work of the PTF will be to clean
up the these requirements to maximize their usefulness to the service
developers.

The proposed services were presented by the research activity
representatives.  These talks spawned detailed discussions of the
various proposed services and the strategies for deployment.  The
feedback was valuable for the service developers.  Along these lines
the draft architecture document has been distributed to the PTF and
members have begun sending feedback.  Two other documents--the
operations plan and the common application layer documents--will be
distributed to the PTF when an early draft is available. 

The immediate short-term plans for the group are to provide feedback
to the architecture, operations, and common application layer
documents.  Similarly urgent is to define the procedures and methods
to manage the external service APIs and the requirement.  These topics
are currently being discussed on the PTF mailing list and a phone
conference will be arranged once we are near convergence.  Entry of
the service APIs and requirements into the systems will be followed by
full scale evaluation of the services with respect to the
requirements.