[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [epf-dev] Status from 3/30 BUP call with authors
|
Sorry for missing the call. Darn client stuff keeps getting in the way. ;-)
Anyway, I'm in the process of filling out the
comitter paperwork, so I'll hopefully be up and running early next week.
- Scott
At 08:51 AM 4/1/2006, you wrote:
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C65593.6B8736F3"
hiho,
On Thursday, 3/30 at 8am PST, there was a
conference call on assigning ownership to BUP
content as we modify and complete the IBM
donation for the 1.0 launch scheduled for 9/1/2006.
On the call were:
· Steve Adolph, UBC
· Ricardo Balduino, IBM
· Mark Dickson, Xansas/DSDM Consortium
· Chris Doyle, Synergy Plus
· Brian Lyons, Number Six Software, Inc.
· Bruce MacIsaac, IBM
· Jim Ruehl, IBM
· Chris Sibbald, Telelogic
We decided to have each content package in BUP
assigned to a committer (or based on duration
it is taking someone on track to be a
committer). We discussed that the templates
package is not really a logical separate area,
but only broken out for convenience of process
engineers; each template would be the
responsibility of the owner of the relevant
discipline. In this pass the Process is not the focus.
The assignment of a package does not imply that
the individual is solely responsible for
authoring all the content. The assignment of
the package is responsibility that the content gets authored.
Based on the participants on the call, the
responsible parties are shown below. One
addition is that we have a pending decision on
project management because Kirti Vaidya had
proclaimed an interest in that, but was not on the call.
Package
Owner
architecture
Chris Dickson, Xansas
change_management
<vacant>
development
<vacant>
general
Steve Adolph, UBC
project_management
Kirti Vaidya, Covansys (pending)
requirements
Chris Sibbald, Telelogic
test
Brian Lyons, Number Six Software
Ricardo Balduino of IBM will manage the overall
architecture of the process. Based on the way
EPF Composer works, Ricardo will be responsible
for managing all relationships between
elements. And he is responsible for creating
any additional elements that will subsequently
be assigned to reside in a package.
If you are a committer or on your way to
becoming one and you have an interest in being
responsible for cm or development, please reply.
Everyone interested in contributing content
should be getting Eclipse setup for CVS to
access BUP. That is the best way to get the
most up-to-date content. This is the real-time
development repository that committers check
their work into. Official committers have
read-write access, but anyone can use it to
regularly pull the very latest content.
There will be a conference call on Thursday, 4/6
at 8am PST to discuss updates and status of this
work. We have a milestone on 4/15 to be
underway with authoring content and have all
elements defined (albeit possibly
incomplete). As the various guidelines are
often driven by the detail in the other process
elements, we are giving ourselves some leeway in
not strictly baselining those by that date.
------------ b
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
====================================================
Scott W. Ambler
Senior Consultant, Ambysoft Inc.
www.ambysoft.com/scottAmbler.html
Refactoring Databases: Evolutionary Database
Design (www.ambysoft.com/books/refactoringDatabases.html) is now available!