Technical Cabal

Hugh Brock hbrock at redhat.com
Mon Nov 12 17:23:27 UTC 2012


On Mon, Nov 12, 2012 at 12:08:36PM -0500, Joseph VLcek wrote:
> 
> On Nov 12, 2012, at 8:37 AM, Hugh Brock wrote:
> 
> > On Mon, Nov 12, 2012 at 08:09:10AM -0500, Scott Seago wrote:
> >> On 11/12/2012 05:45 AM, Jiří Stránský wrote:
> >>> Hi all,
> >>> 
> >>> *proposed members of the cabal are in CC, please ACK or NACK your
> >>> membership by Nov 13*.
> >>> 
> >>> Technical Cabal info (mostly what Hugh wrote[1] earlier):
> >>> 
> >>> * Mission for Technical Cabal: Make technical and architectural
> >>> decisions across the Aeolus project. Settle disputes.
> >>> 
> >>> * One of the aims of the Technical Cabal is to have people from
> >>> various Aeolus subprojects present on the cabal, so that decisions
> >>> can be made effectively across all of the subprojects. On the
> >>> other hand, we try to keep the member count reasonably low
> >>> to make efficient communication possible.
> >>> 
> >>> * We have four cabals: Technical, Website, Publicity, Release.
> >>> 
> >>> * Cabals should have short weekly meetings.
> >>> 
> >>> * Membership on the cabal should be for the period of one upstream
> >>> release (roughly 6 months, next two releases have a shorter cycle
> >>> though). Repeated membership is possible.
> >>> 
> >>> * Each cabal has an Awesome, a person who should make sure that regular
> >>> meetings of the cabal really happen. Initial Awesomes are appointed,
> >>> a proper election of a permanent Awesome should take place on the
> >>> first meeting of each cabal.
> >>> 
> >>> * Notes about meeting results should be published to aeolus-devel.
> >>> 
> >>> Proposed members, as nominated at Aeolus Developer Conference:
> >>> 
> >>> * Tomas Sedovic
> >>> * Martyn Taylor
> >>> * Jason Guiditta
> >>> * Scott Seago
> >> ACK
> >> 
> >>> * Eric Helms
> >>> * Michal Fojtik
> >>> * Greg Blomquist
> >>> * Jaromir Coufal (user experience advocate)
> >>> 
> >>> *Please ACK or NACK your membership by Nov 13.* Also if anyone else
> >>> feels that the list of cabal members should be different, speak up
> >>> please.
> >>> 
> >>> Initial Awesome for the Technical Cabal is Hugh Brock.
> >>> 
> >>> [1] https://lists.fedorahosted.org/pipermail/aeolus-devel/2012-November/013191.html
> > 
> > BTW, in case I didn't make this clear before: all these membership lists
> > are proposals we came up with in the group last week. If you weren't
> > able to make it to the conference, this doesn't mean you're ineligible
> > to be in any of the Cabals -- feel free to nominate yourself or others.
> > 
> > --Hugh
> 
> I'd like to nominate myself to the Technical Cabal.
> 
> Joe VLcek

Hello Joe. Michal has already volunteered to represent Deltacloud, so
unless you guys want to swap now I'd suggest you wait until the next
go-round which will be roughly the end of March.

This makes me realize that I left out one important bit -- on the tech
cabal, we tried to pull one person to represent each upstream Aeolus
project, and we tried to keep the number to 7 or less. This doesn't mean
you can't listen in on meetings, it just means you can't vote unless
you're actually on the cabal. We intend the membership to be elected
anew each release.

--Hugh

-- 
== Hugh Brock, hbrock at redhat.com                                   ==
== Engineering Manager, Cloud BU                                   ==
== Aeolus Project: Manage virtual infrastructure across clouds.    ==
== http://aeolusproject.org                                        ==

"I know that you believe you understand what you think I said, but I’m
not sure you realize that what you heard is not what I meant."
--Robert McCloskey



More information about the aeolus-devel mailing list