[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[eclipse.org-architecture-council] Nick Boldt for ArchitectureCouncil
- From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
- Date: Thu, 8 Oct 2009 22:10:55 +0200
- Delivered-to: firstname.lastname@example.org
- Thread-index: AcpIOnYlA3kUtvYxSbSrTmqu0+pRuQAF84FQ
- Thread-topic: Nick Boldt for ArchitectureCouncil
Wayne Beaton has nominated you to join the Eclipse
Architecture Council in recognition of your achievements for the Eclipse
Community. In it's phone meeting today, the Council unanimously accepted this
nomination with an unprecedented amount of support (30 +1 votes from 40
members!). As per the Eclipse Development Process , your nomination is a highly visible confirmation of the Eclipse
community's respect for your technical vision, good judgement, software
development skills, but most of all your passion and support for the Eclipse
community. It is a role that should be neither given nor taken lightly.
I'm sending this E-Mail to you in order to actually confirm
that you're ready to take on that new role. Being on the Architecture Council
does not come for free: we do expect our members to be actively involved in the
Council's work. We'd appreciate if you can join the monthly 1-hour phone
meetings, but being responsive to the council's business in terms of E-Mail
discussions is just as important. Given that only AC members can serve as
official Mentors for projects, we also expect you to be ready to serve as a
Mentor, be open-eyed to interesting things going on in your domain and bring
them to the Council's attention. Only pro-active members bring real value to our
Over all, an investment of 3 hours each month for AC
business should be the minimum expectation (1 hour for the phone call, plus 2
hours for E-Mail business). What you get in return, is getting in touch with
some of the most prominent leaders in our Community, first-hand information and
a good chance to actually change things that bother you.
See the Architecture Council Wiki pages  for
more information. If you have any questions, or find those pages unclear, just
drop me an E-Mail or file a bug  against
the AC component. As a new member, you have the unique opportunity to see things
like a newcomer, and thus point out things on the website that need improvement;
Existing bug 250348  already mentions some
items that should help newcomers get started.
I'd appreciate getting you on board. Let me know what you
Thursday, October 08, 2009 7:12 PM
To: Oberhuber, Martin
Subject: Re: Nick
Boldt for ArchitectureCouncil
In this case, I don't think it matters
much which is first: I approve!
From: "Oberhuber, Martin"
Date: Thu, 8 Oct 2009 18:43:31
Subject: Nick Boldt for
may I recommend you appoint Nick
Boldt to the Architecture Council.
He's got an incredible 30 +1 votes out of
40 active AC members --
I've never seen such amount of support!
haven't talked to Nick yet whether he would be willing to accept
appointment and join us. I cannot quite remember what should be
appointment or asking him whether he would
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project Lead, DSDP PMC Member
Of Wayne Beaton
Sent: Tuesday, October 06, 2009 3:32 AM
Nick Boldt for
Greetings noble Architecture
I would like to nominate Nick Boldt for membership in the
Council. Nick's is a well-known name in the Eclipse community.
He is a
prolific contributor of code, and knowledge. He is active in
newsgroups/forums, mailing lists, IRC, Twitter, and his blog. He is
vocal proponent of Eclipse Technology, frequent challenger of
and advocate for making lives easier for committers and adopters.
Foundation database lists Nick as being a committer on no less than
different projects. His most recent efforts have resulted a
Build" infrastructure that he is tirelessly working to
innumerable projects to adopt.
I hereby request that we
undertake a vote to invite Nick into our
Membership in this list is generated by processes internal to
Foundation. To be permanently removed from this list, you
emo@xxxxxxxxxxx to request removal.