hiho,
Here are the meeting minutes from the May 8 Conference Call
for OpenUP/Basic Content Authors.
Participants:
Ricardo Balduino
Mark Dickson
Per Kroll
Brian Lyons
Ana Valente Pereira
Chris Sibbald
Kirti Vaidya
Context:
Bugs were created for the architecturally-significant changes for each
package. Here “architecturally-significant” means the
existence of elements, their relationships to other elements, and their names
and brief descriptions. We have been focusing on methodology content with
a package for each discipline plus one for overarching features.
These bugs were targeted for closure at the last milestone.
At this point we are working on completing the process elements and we should
open bugs for the authoring of the content. The bugs will be at a
granularity of reasonable work to be assigned to one person and completed within
an iteration. This ends up being “typically just larger than one
element” where a very small set of interrelated elements are assigned to
be authored in one bug. The idea is to have something like a work items
list where the summation of the open bugs covers the authoring of all
identified content.
Per-Discipline Status:
There was a lot of talk on the call regarding specific bugs for content
authoring and their status. As this area of discussion was at all levels
of abstraction and had gaps, I have left out that level of detail (with two
exceptions). Please keep track of the bugs via bugzilla.
Requirements
-
Updated content in based on conference
calls. Content has been incorporated into baseline available for download.
-
Discipline-level bug was closed.
-
A number of bugs for authoring
content are open.
-
Summary: moving along alright.
CM
-
Updated content in based on conference
calls. Content has been incorporated into baseline available for download.
-
Discipline-level bug for
architecturally-significant changes was closed.
-
CM stuff is harmonized with Work Items
List (WIL). Changes to WIL might require updates to CM method content.
-
There is detail in all method
elements. No open bugs
Architecture
-
Updated content in based on conference
calls. Content has been incorporated into baseline available for download.
-
Still need to write content.
Need bugs for content authoring.
-
Comments coming in raising the
question of whether we are moving too far from the Unified Process discipline
structure. This will be discussed via epf-dev and at the May 15 face-to-face
meeting.
Development
-
Ownership has changed hands and
this discipline is behind.
-
The architecturally significant
bug is still open.
Test
-
One plug-in was authored and it
required changes based on review. Updated content needs to be submitted.
-
The architecturally significant
bug is still open. After changes have been made and pushed out, it will
be closed.
-
Need to create bugs for authoring
content.
Project Management
-
Updated content in based on conference
calls. Content has been incorporated into baseline available for download.
-
Discipline-level bug for
architecturally-significant changes was closed.
-
Need to create bugs for authoring
content. Plan to create these this week.
Overarching
-
A set of elements were created
based on conference calls.
-
Package-level bug for
architecturally-significant changes was closed.
-
Created bugs for areas of work to
be performed and those have been parceled out to owners.
-
Work performed includes creation
of a welcome page.
Deployment discipline
-
Bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=140074)
was created to add a deployment discipline.
-
This is a notable change and will
be discussed at face-to-face meeting on May 15.
-
If accepted, structure will be done
by end of M3 (June 1).
MDD Plug-in
-
Although beyond the scope of this
OpenUP/Basic call, it was noted that ESI has uploaded plug-in to bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=138867).
-
All process authors are welcomed
to review and provide commentary.
Action Items:
We need to get to a point where we can close all “architecturally-significant”
bugs.
We should have bugs to cover all content authoring work before the
face-to-face on May 15.
There should be additional coverage of CVS usage issues at face-to-face.
----------- b