On Wed, Feb 17, 2016 at 8:23 PM, Mattmann, Chris A (3980)
<chris.a.mattm...@jpl.nasa.gov> wrote:
> My rationale is that the chair also makes sense to be someone
> heavily vested in the project’s success which of course you are
> Sam. We don’t have to worry about BDFL here. You’re the opposite
> and someone we trust.
>
> Beyond that, if someone else really comes up in Whimsy (like Sebb
> is doing), maybe at some point he steps in as chair..

OK, the board meeting is coming up in a little over a week.  I guess I
should submit a chair change resolution?

- Sam Ruby

> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>
>
> -----Original Message-----
> From: <sa3r...@gmail.com> on behalf of Sam Ruby <ru...@intertwingly.net>
> Reply-To: "dev@whimsical.apache.org" <dev@whimsical.apache.org>
> Date: Wednesday, February 17, 2016 at 12:08 PM
> To: "dev@whimsical.apache.org" <dev@whimsical.apache.org>
> Subject: Re: Perhaps I ought to step down as PMC Chair after-all
>
>>On Wed, Feb 17, 2016 at 1:51 PM, Mattmann, Chris A (3980)
>><chris.a.mattm...@jpl.nasa.gov> wrote:
>>> +1 thank you for your service Ross.
>>>
>>> Sam prepared the report this month - any objections to him
>>> being the chair?
>>
>>I'm not opposed to the workload, but if there is anybody else
>>willing/able to take this role, I think it would help ensure that
>>there were multiple eyes on the project.  I think that was part of the
>>thinking behind Ross's original volunteering for this role; but (quite
>>understandably given his workload), it didn't quite work out as hoped.
>>
>>- Sam Ruby
>

Reply via email to