December 2012 - Foundation - lists.openinfra.dev

[OpenStack Foundation] Board discussing how to improve the Individual Director election process, community input wanted
by Alan Clark 05 Feb '13

05 Feb '13

Dear OpenStack Foundation Members, There has been much discussion in the Community recently, including during the breakfast with the Board sessions at the last Summit, regarding how Individual Members are elected to the Board. As a result of this feedback, the Board has begun discussing how to improve the Individual Director election process and wants to solicit additional community input on some steps for future elections. Informal conversations after the Summit led the Board, as a first step, to establish a sub-committee composed of primarily Individual Members. That sub-committee distilled the ideas received to date into a few critical issues in order that the Board can go back to the Community with proposals for review and comment, and work towards implementing reforms if necessary. In the course of these meetings and during the Board meeting of November 2, the sub-committee and the Board considered a broad range of options for improvements to the Individual Member Director election process and rules, including those that would require a change to the bylaws of the Foundation. An etherpad detailing all of the potential options explored and discussed is at https://etherpad.openstack.org/Board-2012-VotingProposals. Given the short time between the November 2 Board meeting and the commencement of the January 2013 Individual Member Director election process in late November (request for nominations), the sub-committee and Board concluded that it would not be feasible to make any changes to the process for this election cycle that would require a change to the bylaws and approval by the Foundation membership. However, a number of well thought out options were developed that would not require a change to the bylaws to be adopted for the January 2013 elections, and we would like to present these proposals to the Community and Membership for discussion and feedback, as set out below. The Board would like to emphasise to the Community that Individual Member Director election process proposals that do require bylaw changes will definitely be a priority for the Board and membership following the January 2013 election, with plenty of time for careful framing, discussion, debate and adoption prior to the January 2014 election." There were four proposed actions for improvement of election processes that the Board identified as being able to be implemented in the short term which would not require bylaw changes and the Board wishes to present these to the Community for wider discussion. Firstly, for the August 2012 election, four questions were produced from mailing list input and put to each election candidate, some of whom responded and some did not. It is the Board's recommendation that we develop this into a compulsory procedure where a nominated candidate is required to make a clear statement of the candidate's contribution to OpenStack. How this is proposed to be structured is open for the Community to discuss, be it reliant on the existing four questions or extended into further qualitative or quantitative measures. The Board feels it is very important for the nominees to present this information clearly for the Community's informed choice. Secondly, the Board would like to more clearly inform the electorate on the reasons for individual members of the Board and explain their role, the importance of diversity on the Board, be that international, cultural, technological, gender or otherwise, the role of the Individual members for who and or what they represent, and provide guidance for members to use these criteria to assess their voting choice. Thirdly, the Board asks that all organisations act honourably, be respectful and demonstrate responsibility and guide their staff to vote according to the best interests of the Community, and not their organisation. OpenStack's life blood is the Community. By implementing suitable measures in place from the first and second proposals providing detailed explanations of candidate contribution and with Foundation guidance of the functions of the Individual Members, the Board is hopeful this will inspire everyone to make an informed choice and vote for candidates who best represent the Community. Fourthly, the Board is exploring options not requiring by-law changes and that fall within the current cumulative voting structure which will help to create a balanced representation of candidates from affiliated organisations, independents and minorities. The Board are meeting on the 16th of November and seek to approve and publish the results of these Community proposals on the 19th of November, a week before the Individual nominations open on November 26th. As a supplement to the discussion on this Foundation mailing list, We have provided an etherpad for discussion of these four short term proposals at https://etherpad.openstack.org/2013-Individual-Elections, and Board members will be maintaining a presence in #openstack-community for general Q and A . Regards, OpenStack Foundation Board of Directors

14 27

[OpenStack Foundation] Thinking about the mission of the user committeee
by Narayan Desai 15 Jan '13

15 Jan '13

I originally sent this mail to Tim Bell, on the subject of a document that he (and the other members of the user committee) are preparing. Tim suggested widening the discussion to this mailing list, so I've forwarded the message here. I'm particularly interested in others' opinions about the mission of the user committee, and aspects of the openstack community culture that this mission reflects. -nld ===================== Hi Tim. Thanks for the update on the user committee. When Lauren (Sell) originally mentioned the user committee to me, I was most excited about the addition of user advocacy into the openstack community. From early on in the project (at least back to Bexar when I started paying attention), openstack has primarily been a developer-focused community. While this culture has been excellent for encouraging contribution of code, I think that this is a tendency that needs to be moderated in order for openstack to grow to its full potential. I have a few comments; these aren't so much comments about the document that you're circulating; rather, they speak specifically to the mission of the user committee, which is only discussed briefly at the end. This mission of the user committee should (IMO) flow from a few basic questions: - How do users engage in the community? - How do we incentivize these participants to help fill the current gaps that exist in the community? - How do we best integrate the perspectives of users into the design process of openstack code? - How can the user committee facilitate a more productive engagement between these two parts of the openstack community? To the first point, there is often a tone of "patches welcome" in the community, that is somewhat unwelcoming to users that can't or won't develop code. This suggests that engagement solely on the development terms is probably not a sustainable solution for the heterogenous community that is developing around openstack. I think that it is important to give these folks (ones that build systems, not so much software) a role that they can identify with as a contributor to the project. I think that there are a large range of gaps between the coding and deployments today. Openstack supports a wide enough range of functions (and IMO it is necessary, not incidental complexity) that it is difficult to boil down to simple configurations. I think this poses a serious difficulty for both documentation and testing. These issues have been discussed at length, but make me wonder if a different structure would address these gaps as well as the social split as well. As I've written this, I'm realizing that the one thing that doesn't sit well with me about the current structure you're proposing for the user committee seems to institutionalize the current split between developers and users, where I think that the committee should be trying to figure out ways to blur the divisions between the groups. I'd suggest adding in an explicit mission for the group at the top of the document, in addition to the mandate. I think that might set the tone for the rest of the document in a productive way. Considering my lack of standing on the committee, I think that it might be presumptive for me to suggest its mission, but I think that the four questions above capture many of the things that I think are important. I'm happy to help in any way you'd like. let me know if you'd like additional comments, or participation in the documents in some fashion. Happy holidays. -nld

9 17

[OpenStack Foundation] Invitation to OpenStack Incubator Process Update Committee Meeting
by messenger＠webex.com 18 Dec '12

18 Dec '12

Hello Foundation Mailing List, The OpenStack Board and Technical Committee invite you to participate as an attendee in the following online OpenStack Incubation Process Update Committee meeting. We will be using the WebEx Training Session tool to facilitate the meeting and audio conferencing. Please join the WebEx session then follow the instructions to either join the telephone conference service or to join via VOIP. Topic: OpenStack Incubator Process Update Committee Meeting Host: Alan Clark Date: Thursday, December 20, 2012 Time: 8:00 am, Pacific Standard Time (San Francisco, GMT-08:00) Session number: 927 104 935 Session password: This session does not require a password. Agenda: http://http://wiki.openstack.org/Governance/Foundation/IncubationUpdate2013 ------------------------------------------------------- To join the session ------------------------------------------------------- 1. Go to https://openstack.webex.com/openstack/k2/j.php?ED=212656082&UID=1489604037&… 2. Enter your name and email address. 3. Enter the session password: This session does not require a password. 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link https://openstack.webex.com/openstack/k2/j.php?ED=212656082&UID=1489604037&… ------------------------------------------------------- To join the session by phone only ------------------------------------------------------- To receive a call back, provide your phone number when you join the training session, or call the number below and enter the access code. Call-in toll number (US/Canada):1-650-479-3207 Call-in toll-free number (US/Canada):1-855-244-8681 Having trouble dialing in? Try these backup numbers: Call-in toll-free number (US/Canada):1-855-244-8681 Call-in toll number (US/Canada):1-650-479-3207 Global call-in numbers: https://openstack.webex.com/openstack/globalcallin.php?serviceType=TC&ED=21… Show toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 927 104 935 ------------------------------------------------------- For assistance ------------------------------------------------------- You can contact Alan Clark at: aclark(a)suse.com To add this session to your calendar program (for example Microsoft Outlook), click this link: https://openstack.webex.com/openstack/k2/j.php?AT=down&ED=212656082&EF=MA&U… http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.

1 0

[OpenStack Foundation] User Committee Update
by Tim Bell 18 Dec '12

18 Dec '12

This note provides an update on the user committee status and a request for feedback on the OpenStack user committee mandate and structure. The user committee was formed following the nomination of Tim Bell as the management board representative and Ryan Lane as the technical committee representative. As defined in the foundation bylaws (http://wiki.openstack.org/Governance/Foundation/Bylaws clause 4.14), Tim and Ryan have selected a 3rd candidate, JC Martin, to complete the initial user committee team. JC has been driving the cloud architecture at eBay and is a strong advocate of OpenStack key values, providing regular summit presentations and active participation in user related issues with the community. For communication between the user committee members, a mailing list has been established at user-committee(a)lists.openstack.org.<mailto:user-committee@lists.openstack.org> The archives are available at http://lists.openstack.org/pipermail/user-committee/ and are world readable. For discussions around the user committee mandate and structure, it is suggested to use the document below and the foundation mailing list at foundation(a)lists.openstack.org<mailto:foundation@lists.openstack.org>. An initial set of points to review is available at https://docs.google.com/document/d/1yD8TfqUik2dt5xo_jMVHMl7tw9oIJnEndLK8YqE…. If you would like to contribute to this document, please drop me a mail to be added to the editors list and make your comments there. Thanks Tim

1 0

[OpenStack Foundation] Welcome Claire & Jim
by Mark Collier 12 Dec '12

12 Dec '12

I wanted to let everyone know that we have two new Stackers joining the OpenStack Foundation staff. Claire Massey is joining us as Marketing Coordinator, and Jim Blair has joined us as an Infrastructure Engineer. Welcome Claire & Jim! We still have openings for another Infrastructure Engineer, Community Manager, Marketing Manager, and Director of Business Development: http://www.openstack.org/community/jobs/?foundation=1 Mark

3 2

Re: [OpenStack Foundation] [Openstack] Welcome Claire & Jim
by John_Igoe＠Dell.com 12 Dec '12

12 Dec '12

Welcome to Claire and Jim! Sent from my Windows Phone -----Original Message----- From: Mark Collier Sent: Wednesday, December 12, 2012 3:20 PM To: openstack(a)lists.launchpad.net; Foundation(a)lists.openstack.org Cc: jeblair(a)openstack.org Subject: [Openstack] Welcome Claire & Jim I wanted to let everyone know that we have two new Stackers joining the OpenStack Foundation staff. Claire Massey is joining us as Marketing Coordinator, and Jim Blair has joined us as an Infrastructure Engineer. Welcome Claire & Jim! We still have openings for another Infrastructure Engineer, Community Manager, Marketing Manager, and Director of Business Development: http://www.openstack.org/community/jobs/?foundation=1 Mark _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack(a)lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp

1 0

[OpenStack Foundation] AUTO: Cicman, Joseph is out of the office. (returning 12/17/2012)
by Joseph Cicman 12 Dec '12

12 Dec '12

I am out of the office until 12/17/2012. I will be out of the office on vacation from Wednesday 12/12/2012 returning Monday, 12/17/2012. If this is an urgent matter, please contact Tom Hauan at thauan(a)us.ibm.com Note: This is an automated response to your message "Foundation Digest, Vol 13, Issue 5" sent on 12/12/2012 7:00:01. This is the only notification you will receive while this person is away.

1 0

[OpenStack Foundation] Invitation to OpenStack Incubator Process Update Committee Meeting
by messenger＠webex.com 11 Dec '12

11 Dec '12

Hello Foundation Mailing List, The OpenStack Board and Technical Committee invite you to participate as an attendee in the following online OpenStack Incubation Process Update Committee meeting. We will be using the WebEx Training Session tool to facilitate the meeting and audio conferencing. Please join the WebEx session then follow the instructions to either join the telephone conference service or to join via VOIP. Topic: OpenStack Incubator Process Update Committee Meeting Host: Alan Clark Date: Thursday, December 13, 2012 Time: 8:00 am, Pacific Standard Time (San Francisco, GMT-08:00) Session number: 927 570 637 Session password: This session does not require a password. Agenda: http://http://wiki.openstack.org/Governance/Foundation/IncubationUpdate2013 ------------------------------------------------------- To join the session ------------------------------------------------------- 1. Go to https://openstack.webex.com/openstack/k2/j.php?ED=211992037&UID=1485984087&… 2. Enter your name and email address. 3. Enter the session password: This session does not require a password. 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link https://openstack.webex.com/openstack/k2/j.php?ED=211992037&UID=1485984087&… ------------------------------------------------------- To join the session by phone only ------------------------------------------------------- To receive a call back, provide your phone number when you join the training session, or call the number below and enter the access code. Call-in toll number (US/Canada):1-650-479-3207 Call-in toll-free number (US/Canada):1-855-244-8681 Having trouble dialing in? Try these backup numbers: Call-in toll-free number (US/Canada):1-855-244-8681 Call-in toll number (US/Canada):1-650-479-3207 Global call-in numbers: https://openstack.webex.com/openstack/globalcallin.php?serviceType=TC&ED=21… Show toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 927 570 637 ------------------------------------------------------- For assistance ------------------------------------------------------- You can contact Alan Clark at: aclark(a)suse.com To add this session to your calendar program (for example Microsoft Outlook), click this link: https://openstack.webex.com/openstack/k2/j.php?AT=down&ED=211992037&EF=MA&U… http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.

1 0

[OpenStack Foundation] Invitation to OpenStack Incubator Process Update Committee Meeting
by messenger＠webex.com 03 Dec '12

03 Dec '12

Hello Foundation Mailing List, The OpenStack Board and Technical Committee invite you to participate as an attendee in the following online OpenStack Incubation Process Update Committee meeting. We will be using the WebEx Training Session tool to facilitate the meeting and audio conferencing. Please join the WebEx session then follow the instructions to either join the telephone conference service or to join via VOIP. Topic: OpenStack Incubator Process Update Committee Meeting Host: Alan Clark Date: Thursday, December 6, 2012 Time: 8:00 am, Pacific Standard Time (San Francisco, GMT-08:00) Session number: 926 730 175 Session password: This session does not require a password. Agenda: http://http://wiki.openstack.org/Governance/Foundation/IncubationUpdate2013 ------------------------------------------------------- To join the session ------------------------------------------------------- 1. Go to https://openstack.webex.com/openstack/k2/j.php?ED=211224212&UID=1481733797&… 2. Enter your name and email address. 3. Enter the session password: This session does not require a password. 4. Click "Join Now". 5. Follow the instructions that appear on your screen. To view in other time zones or languages, please click the link https://openstack.webex.com/openstack/k2/j.php?ED=211224212&UID=1481733797&… ------------------------------------------------------- To join the session by phone only ------------------------------------------------------- To receive a call back, provide your phone number when you join the training session, or call the number below and enter the access code. Call-in toll number (US/Canada):1-650-479-3207 Call-in toll-free number (US/Canada):1-855-244-8681 Having trouble dialing in? Try these backup numbers: Call-in toll-free number (US/Canada):1-855-244-8681 Call-in toll number (US/Canada):1-650-479-3207 Global call-in numbers: https://openstack.webex.com/openstack/globalcallin.php?serviceType=TC&ED=21… Show toll-free dialing restrictions: http://www.webex.com/pdf/tollfree_restrictions.pdf Access code: 926 730 175 ------------------------------------------------------- For assistance ------------------------------------------------------- You can contact Alan Clark at: aclark(a)suse.com To add this session to your calendar program (for example Microsoft Outlook), click this link: https://openstack.webex.com/openstack/k2/j.php?AT=down&ED=211224212&EF=MA&U… http://www.webex.com IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.

1 0

[OpenStack Foundation] [General Survey] Asking for help from OpenStack Korea User Group.
by Jaesuk Ahn 03 Dec '12

03 Dec '12

Hi Everyone This is Jaesuk Ahn, a leading person in OpenStack Korea User Group. OpenStack Korea User Group is sincerely asking for help. :) We are having a openstack conference in Korea this week. As a one of conference problem, we would like to get openstack member's opinion on following questions. We will publiclly present answers we gets here during the conference, as well as some panel discussion on same questions I put here. It would be very nice of you if anyone can spare little bit of his/her time to give us your thought on the following questions. Thank you!!! ----- Questions ----------- 1. What would be the biggest missing point, things need to be improved most, in Openstack? In other word, If you need to point one thing for openstack to have in order to be successful, what would it be? 2. What would be openstack's unique strengh comapring to other open source solutions? 3. If you choose OpenStack for building cloud service, what would be your first reason? 4. What is the best experience on openstack? 5. What is the worst experience on openstack? 6. What would be the most common problem you gets when you are operating openstack-based commercial cloud service? 7 (IMPORTANT). Cloud you please make one sentence to explain how awesome openstack is?

2 1