[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[dsdp-tm-dev] Welcome Radoslav Gerganov as a new dsdp.tm Committer !
- From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
- Date: Tue, 22 Apr 2008 16:15:16 +0200
- Delivered-to: firstname.lastname@example.org
- Importance: high
- Priority: Urgent
- Thread-index: AcikgaipVxbBMMRMRXWRFc52fawNKgAACDpA
- Thread-topic: Welcome Radoslav Gerganov as a new dsdp.tm Committer !
I'm very glad to have you on the team, and
An overwhelming +10 / -0 vote shows that
All the others are impressed with your work
As I have done with all other committers so far,
I'd like to have a personal talk with wou on the
phone before you actually starty any work as
committer. We can meet on Skype or on fixed phone
for that, please let me know when you are available.
As a project lead, I'm responsible for educating
you on the Eclipse IP/Legal process, as well as
your duties as a committer. Through your work as a
contributor for DSDP/TM I think you learned much
of this already. Still, please take some look at
the document links I have provided here.
This may seem a little process-heavy, but it's
designed to minimize conflict between companies
and individuals working on shared open source code.
If you have ANY questions, never hesitate to ask me,
or the DSDP PMC at mailto:dsdp-pmc@xxxxxxxxxxx --
we are here to help you!
So, here are the documents:
(1) The DSDP Charter
The DSDP charter at
governs how our project operates. For most of the
stuff, it merely references the Eclipse standard
toplevel charter at
Please read at least the section about Committers
there: voting, taking part on the mailing list
and the newsgroup.
(2) Committer Guidelines
You are now a committer, so just like the process that
we put on your own contributions, you may now accept
contributions from others. Most of the process is
documented for our project on
-- this is the essence in a short form of what the
original documents are about. For your reference, you
should have seen the origininal documents at least once:
the committer guidelines at
tell us about the IP due diligence process. This must be
followed BEFORE any checkins to CVS. We - as committers -
are responsible for keeping the code base clean. This is
very important. See also the Eclipse IP Legal poster for
a graphical description of the process, at
(3) Eclipse Development Process
The Eclipse Development Process is more important to
know for me as a project lead, it specifies the phases
of our project and deliverables such as a project plan,
release review and others. It's a long read but also
interesting to look at once. Also note that several parts
Of the Process are currently being discussed and about
To be changed -- such as the possibility to have arbitrarily
Deep subproject nexting. Anywyas, what's probably more
helpful is the FAQs here:
For final reference,
give all the background information for how we work.
Note especially the Legal and Trademark sections. You
don't need to understand everything right away, but be
aware that regulations exist and you can ask me in case
anything is unclear.
I guess you'll mostly work on your own WinCE code to start
With, but I've granted you full access to all of the TM
Repository since we've already seen that you work very
Diligently. I'd appreciate if you also take part on the
mailto:dsdp-tm-dev@xxxxxxxxxxx mailing list and the
Once that is done, I guess that your first
Action will be committing your own outstanding
Pathes. Note that you'll need to create
Tm-log.csv entries for those, just to be safe.
Thanks for joining, and I'm very much
Looking forward to working with you!
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member