Giulio and I had some conversation after today's Release Cabal meeting about google hangouts versus irc for our meetings.
We agreed that g+ hangouts are often effective for facilitating discussion, but there are a couple of obvious drawbacks as well:
1) requires use of the closed/proprietary google plugin
2) ease of conversation often comes at the expense of thorough meeting notes
We also agreed that sometimes irc is less efficient than face to face talk. Furthermore, having saved videos of our meetings is of limited historical interest/value if our notes are comprehensive.
None of the above is news, I presume; apologies for restating the obvious.
Since we want the best of both worlds I propose the following. Let's start each meeting on irc only, and if anyone (or preferably two) feels that day's meeting agenda item(s) would benefit from a hangout, then we'll do at least part of the meeting in a hangout.
I'd also like us to adopt the somewhat standard practice of appointing a scribe for the meeting to drive MeetBot and make sure that we document our conversations.
Good work in today's meeting, and good luck on all of our #action items.
The third Deltacloud API Community call will be held on:
Thursday, 29th November @ 1700 CET (Prague, Brno, GMT+1)
(which means 0800 PST (US West Coast, GMT-8) or 1100 EST (US East
Anyone interested in the Deltacloud project is very welcome to join us.
We are using Google+ Hangouts again for this call. If you want to join
us, all you need to do is to setup a Google+ account and send us your
email, so we can invite you.
For this call we have decided to make the duration half hour - we've had
some feedback about the length of the recorded meetings (at 1 hour)
being a little too long to sit through. This means realistically we will
only address one agenda item. Agenda is at
November 29th, 2012
Matt Wagner (Awesome)
- Follow-up on last week's issues
- Mainn labeled issues in github
- Matt created presentations wiki page
- wiki organization - will discuss over email- Mo will start email
- about page - Matt pushed a new version
- updated projects page? - Mo has updated pull request - Jiri will review
- change developer's link to updating contributor's page - Jiri will submit a pull request for this for next Sprint
- featured items section - table until we get more items
- Open Github issues
- matt will add @realjustinclift twitter account
- Clean up contact page - pattern after example that justin sent?
- figure out whether we can remove business and non-technical contacts section, remove iwhd mailing list
- Mo will submit a pull request
- let's not do calendar
- new issues
- personas page - Andy is updating, will show us when he's done, we can decide where it goes
Attendees: Andy Fitzsimon, Angus Thomas, Jarda Coufal, Jiri Tomasek, Justin Clift, Tzu-Mainn Chen, Francesco Vollero, Matt Wagner
*University talk in Brno* - Jaromir will send materials and notes to Mainn; Mainn will write up a blog post
*FOSDEM* - Francesco and Justin are preparing proposals, notes at http://etherpad.corp.redhat.com/Aeolus-FOSDEM-2013-Talks; hopefully others will hop on in
*Red Hat Brno Dev Conference* - Mainn and Justin will work on crafting an email for the community
*Linux.conf.au* - Andy/Dan are invited to speak; will send notes for a blog post to Mainn, or blog about it themselves
*Debian and Aeolus* - Justin will 'rattle a few trees'
*Presentations from Brno* - Jirka and Mainn will work to coordinate blog posts with presentations and video; Matt will write up his notes for the wiki
*Aeolus Release* - upstream release in January; will need to think about promotion cycle when date firms up
*Release (Other)* - Justin will interrogate the Release Cabal regarding upcoming release dates for other Aeolus components
*DevTools (Conductor on Ubuntu)* - Mainn will talk to Mike Orazi
*Red Hat Summit* - Matt will send a proposal
If anyone is interested in submitting a proposal.
Submitted a few smaller ideas that had been discussed for the
Fedora/Ruby sig. The GCI is geared towards high school students (whereas
the GSOC is for college level participants) so obviously the
expectations here should be slightly different.
-------- Original Message --------
Subject: GCI 2013 - Mentors required (8 days left)
Date: Sun, 18 Nov 2012 19:44:24 +0530
From: Buddhike Kurera <bckurera(a)fedoraproject.org>
CC: Mo Morsi <mo(a)morsi.org>
Google Code in 2012 will be starting on 26th November, that means only
Therefore we are looking for mentors who can assist with the students
mentoring them at least with 2 tasks. If you are interested please do
contact us asap. Please login with your Google account to
google-melange.com and create your profile, then send me your username
so that I can invite you to become a mentor with the Fedora project.
You can add you task at https://fedoraproject.org/wiki/GCI_2012/Task_Page
If you want any help please do contact me at any time, Thanks !
Buddhike Chandradeepa Kurera (bckurera)
summer-coding mailing list
Here's a typical meeting order of business/agenda for the cabal to
consider. It may seem unnecessarily stuffy, but I find that having real
process helps to keep the discussion from wandering off on tangents,
which is important if you want anything to really be done.
Finally, note that it is the responsibility of the Awesome to direct the
discussion, remind folks to stay on the current topic, etc., and the
responsibility of the rest of the cabal to be willing to be so
directed and to follow the process for getting concerns properly
addressed. Otherwise it all devolves into chaos.
Proposed Aeolus tech cabal meeting format
* Roll -- the secretary notes those present. Important in case votes are
* Discussion of and approval of the minutes of the previous
meeting. This *should* be quick and easy, but sometimes the secretary
gets a detail wrong and it's important that there be a channel to
* Sub-cabal reports. Should the cabal find it necessary to create
subgroups to work on specific issues, this is the spot to hear reports
from them and discuss issues that come up or proposed resolutions.
* Old business. Items that were tabled during the previous meeting for
research or further contemplation should be discussed here. The
Awesome should provide a list of items if there are any, and members
should be asked to bring up any that have been overlooked.
* New business. Items that were suggested for discussion on-list but
have not yet been brought up should be discussed here. Members should
be able to suggest new items for discussion during the meeting if
there is time after any items listed on the agenda have been
There will come a time when some of the cabal feels it is time to either
vote on an issue or table it until the next meeting, while others feel
it needs further discussion. In this situation a member must move to
either vote or table, and another member must second the motion; if
there is no second, the discussion should continue. I hope things don't
ever get controversial enough that we have to vote on whether to end
debate, but if they do, that's the procedure.
Throughout the process, it is the job of the Awesome to move the
discussion from item to item and to remind members to stay on
I would suggest the cabal put the above to discussion and vote early in
the next meeting, so that the procedure is established going
forward. I'd also suggest the cabal choose a secretary, it's an
important job that probably shouldn't be rotated weekly.
== Hugh Brock, hbrock(a)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."