aeolus-comm-mgmt

aeolus-comm-mgmt@lists.fedorahosted.org

89 discussions

Publicity Cabal Minutes - November 27th, 2012
by Tzu-Mainn Chen 28 Nov '12

28 Nov '12

Agenda: https://redmine.aeolusproject.org/redmine/projects/aeolus/wiki/Publicity_Ca… Attendees: Andy Fitzsimon, Angus Thomas, Jarda Coufal, Jiri Tomasek, Justin Clift, Tzu-Mainn Chen, Francesco Vollero, Matt Wagner Minutes: https://redmine.aeolusproject.org/redmine/projects/aeolus/wiki/Publicity_Ca… *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

2 1

Fwd: GCI 2013 - Mentors required (8 days left)
by Mo Morsi 27 Nov '12

27 Nov '12

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. -Mo -------- 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> To: summer-coding(a)lists.fedoraproject.org, summer-coding-mentors(a)lists.fedoraproject.org CC: Mo Morsi <mo(a)morsi.org> Hello All, Google Code in 2012 will be starting on 26th November, that means only days left. 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 ! -- Regards, Buddhike Chandradeepa Kurera (bckurera) _______________________________________________ summer-coding mailing list summer-coding(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/summer-coding

1 1

Call for Participation: FOSDEM
by Tzu-Mainn Chen 27 Nov '12

27 Nov '12

Hi all, We're looking for participants for FOSDEM (https://fosdem.org/2013/) Of particular interest may be the Virtualization DevRoom (http://osvc.v2.cs.unibo.it/index.php/Main_Page) which is being co-organized with Dave Neary. Francesco will be submitting a proposal; is there anyone else interested? Thanks, Tzu-Mainn Chen

2 1

Aeolus Tech Cabal proposed agenda format
by Hugh O. Brock 26 Nov '12

26 Nov '12

Hi all. 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 taken, etc. * 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 address that. * 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 discussed. * Adjournment Voting procedure ================ 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 topic. 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. Have fun, --Hugh -- == 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." --Robert McCloskey

1 0

Aeolus Tech Cabal: 20/11/2012 - Minutes
by Martyn Taylor 26 Nov '12

26 Nov '12

Please find Aeolus Tech Cabal initial meeting minutes below. Next weeks Agenda can be found here: http://openetherpad.org/AeolusTechnicalCabal You must add items to the etherpad if they are to be discussed in next Cabal meeting. Anyone wanting to add items to the Agenda then please do so by 26/11/2012. This will give people a chance to do some preparation. Next meeting 27/11/2012 Regards Martyn Aeolus Tech Cabal: 20/11/2012 Attendees * Tomas Sedovic * Martyn Taylor * Jason Guiditta * Scott Seago * Eric Healms * Michal Fojtik * Greg Blomquist * Jaramori Coufal Agenda Procedural Items *Meeting Format: Hugh will send format to the list before next Cabal Meeting* * Meeting Time: o 2pm Tuesday Recurring. o 1 hour max. o Items not covered will be raised in next meeting * Awesome o 1st Post: Martyn Taylor o Respoibilities + Ensure agenda is adequate + Ensure meetings move forward. * Secretary: o Weekly rotation: Next: Greg Blomquist o Responsibilites + Take Minutes + Distribute Minutes Technical API Resource Representation. 1. When shall we use full resource and minimal (link) resource representation in the API? 2. How should we allow client to access these resources? Martyn Proposed we represent full resources in all top level collections. Sub resources will be represented as a collection (with url) when one to many relationship is present. Sub resource collections will include minimal resources. Scott agreed this could solve many of the issues we are currently facing with the API and would be useful in the API. Greg mentioned that this could cause some issues with configure. But will seek advice from Eck Cabal voted in favour of proposal. Actions: * *Greg* will Confirm with Eck * *Martyn* will send mail to list further explaining the proposal. * *Martyn* will inform API contributers of changes. Instance State Machine 1. How do we represent state changes in the API? Particularly for instances, deployments and deployables. Michal spoke about using actions and links that represent state changes. It was agreed that this is not strictly RESTful. Discussion around pure REST v usability started, but the Cabal came to no conclusion on the matter. Michal advised us to take a look at the CIMI documentation (http://dmtf.org/sites/default/files/standards/documents/DSP0263_1.0.1.pdf) Since the API resembles ours in many ways. Actions: * CIMI investigation * Further discussion on the list. * Initial topic next meeting. (If unresolvable on list) Outstanding Agenda Items 1. API versioning - Supporting for versioning the API (Not for supporting multiple version) 1. URL v HTTP Header (Server HTTP header?) 2. e.g. http://docs.openstack.org/api/openstack-identity-service/2.0/content/Versio… 2. API Paging/Filtering/Sorting? 1. http://blog.apigee.com/detail/restful_api_design_can_your_api_give_develope… 3. API Race Conditions 4. Handling Deltacloud exceptions in Deltacloud - What need to be done to improve it.. 5. Callbacks in Deltacloud - When, how and who :-)

8 16

Anyone located near Brussels? (Accomodations for FOSDEM)
by Tzu-Mainn Chen 26 Nov '12

26 Nov '12

Hey all, I guess the subject really says it all, but we're looking to see if anyone is located near Brussels and is willing to accommodate a person for FOSDEM (https://fosdem.org/2013/) Thanks, Tzu-Mainn Chen

1 0

[RELEASE cabal] Weekly meeting repeats at Wed 1530 CET
by steve linabery 26 Nov '12

26 Nov '12

SSIA, but: Agreed at our meeting today that our weekly meeting time will be: Wednesday at 1530 CET Thanks all for attending. s|e

5 13

Publicity Cabal minutes
by Angus Thomas 22 Nov '12

22 Nov '12

Minutes are here: https://redmine.aeolusproject.org/redmine/projects/aeolus/wiki/Publicity_Ca… Amateur psephologists will be dismayed to hear that there was a last-minute outbreak of consensus; Tzu-Mainn and Justin have agreed to divide the role of Awesome for this cabal between them. Tzu-Mainn has already sent out a notification for the next meeting, which is scheduled for 13:30 UTC on Novenber 27th. // <http://www.thefreedictionary.com/psephologist>

1 0

Website Cabal Minutes, Nov. 20th 2012
by Tzu-Mainn Chen 20 Nov '12

20 Nov '12

November 20 Attendees: Matt Wagner (Awesome) Tzu-Mainn Chen Jiri Stransky Mo Morsi Francesco Vollero https://www.youtube.com/watch?v=zWayFPCv0ro&feature=plcp ------------ - Quick review of github issues - broken Google links need to be investigated further (https://github.com/aeolusproject/aeolusproject.github.com/issues/13) - others will be discussed through github issues - Label issues in github (Bug, Enhancement, etc) - Presentations - wiki vs website? - presentations uploaded to static site because of potential wiki moves - wiki organization - will discuss over email - focus on website content before worrying about SEO - enhance about page - mission statement, high-level picture, link to projects - change developer's link to updating contributor's page - website cabal responsibilities vs publicity cabal responsibilities - publicity about content, website about infrastructure - overlap exists, but some people are on both cabals, can help coordinate - new documents directory structure in github for cabal minutes, presentations, etc - new website section for featured items? - actually, tag blog posts, aggregate ------------- - new issues: - update about page (https://github.com/aeolusproject/aeolusproject.github.com/issues/28) - change developer's link to contribute (https://github.com/aeolusproject/aeolusproject.github.com/issues/27) - "featured" page (https://github.com/aeolusproject/aeolusproject.github.com/issues/29)

1 0

Aeolus Mission voting. VOTE REQUIRED BY NOVEMBER 19 PLEASE.
by Hugh O. Brock 20 Nov '12

20 Nov '12

Mission Statement Voting OK... I promised to schedule a vote for today and naturally I am behind. The good news is this means you guys have the weekend to think about this. A bit about process. Having been through a substantial mission statement exercise already, I'm not inclined to lengthen the process much further by accepting further tweaks. I am therefore going to exercise the mighty ><}}}*> one final time and reduce the nominees for Aeolus Mission Statement to three. I hope you all will view this less as an act of oppression and more as an act of getting the hell on with it :). In voting, I would urge you all to remember that a mission statement can and probably should be aspirational -- our software may not fill our mission today, but we intend that it will someday, and that new additions to Aeolus will be included or not based on how well they will help us fill the mission. The choices, then, are: 1. Aeolus mission: To provide superior tools and workflows for flexible construction, management, and monitoring of multi-instance systems across clouds. (This is the original version we concocted at the dev conf.) 2. Aeolus mission: To provide superior tools and workflows for flexible construction, management, and monitoring of multi-instance deployments across clouds. (Modifications by Giulio Fidente and Justin Clift, received at least one endorsement on list.) 3. Aeolus mission: "To provide open source tools for the management and monitoring of cloud based systems." (Alternative from Mo Morsi. Mo says: "Are we just focusing on 'multi-instance systems'? Isn't providing simple tools to build images and launch a single instance against any generic cloud provider part of Aeolus?") Vote for one by end of Monday, please. Thanks, --Hugh -- == 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." --Robert McCloskey

19 21

← Newer
1
2
3
4
5
6
7
8
9
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

aeolus-comm-mgmt