Toni,
I have a couple of concerns about this
request.
Some of the proposed committers have no
prior experience as committers on an Eclipse project. At a minimum, we
need to assure that any of this group who are not seasoned committers from
other Eclipse projects has an assigned mentor who can provide advice and review
their work as they grow more familiar with the committer role. This will
head off problems with IP policy, CVS pollution, etc.
Another factor that makes it much more likely
that we could run into trouble is that the COSMOS project has not achieved much
process maturity at this point. For example, we haven’t defined CVS
directory naming conventions or our processes and practices regarding approvals,
planning, architecture review, code review, etc. In this environment, it
is necessary for the committers to be extremely disciplined until the
supporting process infrastructure matures.
I vote +1 with the caveats that:
1. We assign a seasoned committer to
mentor each new committer’s contributions (I believe that this list would
be Vasya, David, and Seva).
2. We define our CVS directory structure
and specifically isolate components that are intended for the demo from more
permanent contributions.
3. No component is committed to CVS prior
to approval of the proposed design (including an assigned location in the CVS
tree) by the weekly Thursday COSMOS project meeting.
Regards,
Don Ebright
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Toni Drapkin
Sent: Monday, January 22, 2007
2:50 PM
To: cosmos-dev@xxxxxxxxxxx
Subject: [cosmos-dev] New
committer nomination/call for vote
I am posting this note to the COSMOS-Dev mailing list
to document the people we'd like to nominate as new committers to the COSMOS
components. I'd like to ask you to reply with your vote for adding these
folks to our project. Once the votes are in, we will forward this
input to the Technology PMC lead (Bjorn). Thank you.
|
New Committer name
|
eMail address:
|
Sub Component
|
Why each person would be a value to the overall
project
|
|
Ali Mehregani
|
amehrega@xxxxxxxxxx
|
org.eclipse.cosmos.rm
org.eclipse.cosmos.dc
|
Ali brings a history of solid tool building
experience as well a involvement with the SML workgroup members to his code
contributions in the rm component. He has already contributed to the COSMOS
wiki in this area.
Ali
also has a long background in the data collection component of TPTP which
will be mined for the dc component.
|
|
Marius Slavescu
|
slavescu@xxxxxxxxxx
|
org.eclipse.cosmos.dc
|
Marius is the main developer for the persistence
models in TPTP as well as the api to load these models. He will be
responsible for ensure the api and impl done in the dc component is
consistent and shareable with TPTP.
The
design work for this effort is already evolving in the wiki.
|
|
Sheldon Lee-Loy
|
sleeloy@xxxxxxxxxx
|
org.eclipse.cosmos.rm
org.eclipse.cosmos.dc
|
Sheldon is a commiter in the BIRT and TPTP projects
and responsible for several data bindings and reports. This experience is
what he will leverage to create common reusable reports and web UI for the rm
component as shown is the mockups he has posted in the wiki.
As
a key consumer of the data collection apis in the creation of reports,
Sheldon will have a role in defining the apis he will consume from the dc
component in the rm component.
|
|
Valentina Popescu
|
popescu@xxxxxxxxxx
|
org.eclipse.cosmos.rm
|
Valentina is a member of the SML workgroup and a key
contributor to the design, spec and impl of the resource modeling support.
She also bring her strong TPTP background in this area to enable potential
interop between the projects.
|
|
Vasya Gorshkov
|
vvg@xxxxxxxxxxxxx
|
org.eclipse.cosmos.me
|
Vasa is a past contributor to the TPTP build to
manage components and these will be consumed by the rm component. He will be
responsible for linking these technologies together.
|
|
David Whiteman
|
David_Whiteman@xxxxxxxxxx
|
org.eclipse.cosmos.rm
|
David is completely focused on the editing and
validation effort of SML in the rm component. He brings a strong Eclipse core
developer skill set to the project as well.
|
|
Hubert H Leung
|
hkyleung@xxxxxxxxxx
|
org.eclipse.cosmos.dc
|
Hubert will be a core developer of the dc component,
and bring several years of TPTP experience with him. This technology was
Hubert's academic focus as well.
|
|
Joel Hawkins
|
Joel.Hawkins@xxxxxxxxxxxxx
|
org.eclipse.cosmos.dc
|
Joel will add WSDM and OSGi api and impl to the dc
component. He is already a large contributor to the WSDM and OSGi community
inside and outside Eclipse.
|
|
Vsevolod Sandomirskiy
|
vss@xxxxxxxxxxxxx
|
org.eclipse.cosmos.me
org.eclipse.cosmos.dc
|
Vsevolod will develop parts of the dc component,
particularly api for exploiters. The me component is intended to enable
exploiters of the dc component and he will be responsible for the consistent
linkage between these components.
|
Regards, Toni
Program Director,
Tivoli Open
Source - COSMOS
tdrapkin@xxxxxxxxxx
(919)254-5224 / t/l 444-5224
(919)815-9894 - cell phone
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
