c4c-dev team mailing list archive

Thread
Date

Re: Blueprint approval authority

To: c4c-dev@xxxxxxxxxxxxxxxxxxx
From: Eric Bradshaw <ericbradshaw@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 20 May 2015 22:22:25 -0600
In-reply-to: <555909FE.9080709@yahoo.com>
Organization: Computers4Christians
User-agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.6.0

Guys,

This seems very appropriate to me, but do please chime in if you have a
different opinion.

Eric

On 05/17/2015 03:37 PM, KI7MT wrote:
> Hello All,
>
> This is off list as it deals with the C4C organization.
>
> I've started adding a few basic Blueprints prints to c4c-dev and
> c4c-maual projects (several more are needed). I've assigned them to
> myself for the time being, but one question remains, Blueprint approval
> authority.
>
> With Eric being the C4C President, Tim and Grant being officers, and the
> current structure does not have a named CTO (Chief Technical Officer), I
> would think the logical approving authority would be Eric in
> consultation with Tim and Grant.
>
> If this is acceptable, I will change the Blueprint approver from
> "c4c-team (which we are all a part of)" to Eric's Launchpad ID (C4C).
>
> If you don't think this is appropriate, please advise.
>
> best regards,
>
> Greg.
>
>