September 2011 - Project-planning

RE: Workshop - more details
by Itamar Heim 22 Sep '11

22 Sep '11

> From: Itamar Heim [mailto:iheim@redhat.com] ... > (URL REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) > > ... > > -- enough time for investment areas from founders? > > > > I am missing a lot of deep dive time per module > - engine > - api > - ui > - vdsm > - history & reports Also: - node - sdk/cli Obviously, these could be parallel, but we need to allow people to go to more than one or two of these somehow. Maybe we'll poll the RSVP list on which of these are more relevant or do we concentrate only or 2-3 of them.

2 1

3550 visitors to oVirt yesterday
by Carl Trieloff 22 Sep '11

22 Sep '11

coming up on 2000 already visited today. regards Carl.

1 0

wiki is now live
by Carl Trieloff 21 Sep '11

21 Sep '11

Details here. http://www.ovirt.org/project/community/ Carl.

1 0

oVirt Sync Call Agenda :: 2011-09-21
by Robyn Bergeron 21 Sep '11

21 Sep '11

oVirt Sync Call Meeting Agenda Wednesday, September 21, 2011 - 14:00 UTC (10:00am US Eastern, 07:00am US Pacific) == Invitees/Attendees == project-planning(a)ovirt.org list subscribers If you do not currently have this call on your calendar and would like it to be, please send rbergero(a)redhat.com an email. == Intercall Conference == Toll Free Dial-In Number (US & Canada): (800) 451-8679 International Dial-In Number: (212) 729-5016 Other International Local and Toll-Free Dial-In Numbers: Listed in meeting invite and bottom of meeting agenda. Conference code: 9197544554 If you are not actively participating in the conversation please put your line on mute to make it easier for all participants to hear. *6 -- Mute your line #6 -- Unmute your line == Project Schedule == * Ongoing oVirt workshop promotion * oVirt Workshop - November 1, 2, 3 * USA - CA - hosted by Cisco * Press release post workshop * Community startup at workshop * Schedule first community release * Community Infrastructure * Launch at workshop * First release - January/February. == Agenda == 1) Board invites, status * New confirmations / Follow-up on confirmations in progress: * (COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) (Mike, Ryan) * (COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) (Mike Day) * (COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) (Jan W.) * (COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) - (COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) - updating * Waiting on (COMPANY NAME REDACTED - INFO: HTTP://LISTS.OVIRT.ORG/MAILMAN/PROJECT-PLANNING/2011-SEPTEMBER/000283.HTML) * (COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) - Waiting to hear back 2) Project launch status / Progress review * Website is live * Project announcement, invites have been sent * rsvp(a)ovirt.org * Do we need to have folks on the Google docs attendee list re-sign up? * OVA press release * Workshop is next major milestone 3) oVirt Workshop / Summit * Nov. 1, 2, 3, Cisco Main Campus, San Jose. * Details: * Attendee count, registration * Evening events/activities * Food 4) Infrastructure (ongoing agenda item) * Project naming status * BZ, mailing lists. 5) Other updates / Agenda topics == Previous Action Items == * Mike Day - Follow up with (COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) advise that they have less than 3 days to commit * Carl Trieloff - Update google doc to reflect correct workshop date in all areas * Andy Cathrow - Follow up with (COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) (has meeting scheduled), (COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html) ((COMPANY NAME REDACTED - INFO: http://lists.ovirt.org/mailman/project-planning/2011-September/000283.html)) * Karsten Wade - set up rsvp list at rsvp(a)ovirt.org for attendees to indicate attendance * Robyn Bergeron / Karsten to subscribe everyone on-list to board list - board list will be public, planning list will still be private. * Robyn/Carl/Karsten to send out a final version of all docs, locations, etc. * Carl following up on workspace availability. * ALL: Please review slides, invite, webpage. * ALL: We need a relevant logo or picture on the website for launch - taking suggestions. Details/size of image are posted. * ALL: Looking around for people proficient in CSS markup - if you can, or know of a potential volunteer, please follow up for website items. == International Dial-in Information == Global Access Numbers Local: Australia, Sydney Dial-In #: 0289852326 Austria, Vienna Dial-In #: 012534978196 Belgium, Brussels Dial-In #: 027920405 China Dial-In #: 4006205013 Denmark, Copenhagen Dial-In #: 32729215 Finland, Helsinki Dial-In #: 0923194436 France, Paris Dial-In #: 0170377140 Germany, Berlin Dial-In #: 030300190579 Ireland, Dublin Dial-In #: 014367793 Italy, Milan Dial-In #: 0236269529 Netherlands, Amsterdam Dial-In #: 0207975872 Norway, Oslo Dial-In #: 21033188 Singapore Dial-In #: 64840858 Spain, Barcelona Dial-In #: 935452328 Sweden, Stockholm Dial-In #: 0850513770 Switzerland, Geneva Dial-In #: 0225927881 United Kingdom Dial-In #: 02078970515 United Kingdom Dial-In #: 08445790676 United Kingdom, LocalCall Dial-In #: 08445790678 United States Dial-In #: 2127295016 Global Access Numbers Tollfree: Argentina Dial-In #: 8004441016 Australia Dial-In #: 1800337169 Austria Dial-In #: 0800005898 Bahamas Dial-In #: 18002054776 Bahrain Dial-In #: 80004377 Belgium Dial-In #: 080048325 Brazil Dial-In #: 08008921002 Bulgaria Dial-In #: 008001100236 Chile Dial-In #: 800370228 Colombia Dial-In #: 018009134033 Costa Rica Dial-In #: 08000131048 Cyprus Dial-In #: 80095297 Czech Republic Dial-In #: 800700318 Denmark Dial-In #: 80887114 Dominican Republic Dial-In #: 18887512313 Estonia Dial-In #: 8000100232 Finland Dial-In #: 0800117116 France Dial-In #: 0805632867 Germany Dial-In #: 8006647541 Greece Dial-In #: 00800127562 Hong Kong Dial-In #: 800930349 Hungary Dial-In #: 0680016796 Iceland Dial-In #: 8008967 India Dial-In #: 0008006501533 Indonesia Dial-In #: 0018030179162 Ireland Dial-In #: 1800932401 Israel Dial-In #: 1809462557 Italy Dial-In #: 800985897 Jamaica Dial-In #: 18002050328 Japan Dial-In #: 0120934453 Korea (South) Dial-In #: 007986517393 Latvia Dial-In #: 80003339 Lithuania Dial-In #: 880030479 Luxembourg Dial-In #: 80026595 Malaysia Dial-In #: 1800814451 Mexico Dial-In #: 0018664590915 New Zealand Dial-In #: 0800888167 Norway Dial-In #: 80012994 Panama Dial-In #: 008002269184 Philippines Dial-In #: 180011100991 Poland Dial-In #: 008001210187 Portugal Dial-In #: 800814625 Russian Federation Dial-In #: 81080028341012 Saint Kitts and Nevis Dial-In #: 18002059252 Singapore Dial-In #: 8006162235 Slovak Republic Dial-In #: 0800001441 South Africa Dial-In #: 0800981148 Spain Dial-In #: 800300524 Sweden Dial-In #: 200896860 Switzerland Dial-In #: 800650077 Taiwan Dial-In #: 00801127141 Thailand Dial-In #: 001800656966 Trinidad and Tobago Dial-In #: 18002024615 United Arab Emirates Dial-In #: 8000650591 United Kingdom Dial-In #: 08006948057 United States Dial-In #: 8004518679 Uruguay Dial-In #: 00040190315 Venezuela Dial-In #: 08001627182

1 0

2817 people found the launch of oVirt today
by Carl Trieloff 20 Sep '11

20 Sep '11

that resulted in a few rsvps. Let's keep getting the word out. regards Carl.

1 0

Workshop details, questions
by Robyn Bergeron 20 Sep '11

20 Sep '11

So thanks to Kyle and Michael at Cisco, we have space for our workshop on Nov. 1-3. Right now, it looks like the biggest room that we can get is capable of handling 75 people. Wireless will be available. A few questions: * Do we want to advertise that we can only handle 75 people, and have a cutoff/waiting list? * Nighttime activities: Are we interested in doing anything in the evening(s)? * Food, dinners, etc: Are we doing anything along the lines of having a company sponsor food, an event, etc.? I'm not sure that we've gotten into those details. Kyle, am I missing anything here? :) -Robyn

4 4

We are LIVE !!!
by Carl Trieloff 20 Sep '11

20 Sep '11

We are public... Please subscribe to at least the user and announce list for now. More information here http://www.ovirt.org/project/community/ Feel free to speak about it, plug it, twitter it with the oVirt tag etc. The PDF and e-mail invitation to the workshop are here http://www.ovirt.org/project/resources/ We are onto phase 2, marketing the workshop and working the agenda. Carl.

1 0

Re: Ovirt Community - Becoming a maintainer
by Doron Fediuck 20 Sep '11

20 Sep '11

(re-sending since I didn't get a reply for it) On Monday 12 September 2011 21:29:12 Carl Trieloff wrote: > On 09/11/2011 05:16 AM, Doron Fediuck wrote: > > On Sunday 11 September 2011 12:11:27 Itamar Heim wrote: > >> Cc'ing some existing leads for comments <SNIP> > > 0. Title is missing. I'm guessing it's the same as document name? > > > > 1. There's a combined usage of 'project' and 'sub-project'. I suggest using 'project' to simplify it. > > If you take Apache for example, they host projects, and even real sub-projects (http://db.apache.org/derby/derby_proposal.html) > > they end up being listed as projects (http://projects.apache.org/indexes/alpha.html#D) > > done > > > 2. The following needs some re-phrasing: > > > > IT is expected however that if you have contributed doc, and are not an expect on code that you > > don’t ack patches for example. You can also be voted into one sub-project and not another based > > on your area of influence, or you could get into them all. > > > > * IT => It > > * doc => a document? > > * and are not an expect => and are not an expert? > > - Generally this paragraph begins with one thing, and ends with something completely different. > > I'd think of adding each sentence to a relevant paragraph carrying the same theme / subject. > > re-worked, see what you think. (go ahead and edit it directly if needed.) > > > > > 3. There are terms that need clarification, or typos. For example: wsdm. Is it VDSM? Something else? > > fixed > > > > > 4. And probably the most important. This document is _also_ about being a maintainer. But it's > > _also_ about being a (sub-)project contributer (and maybe some more also's); > > > > - Contributing to a sub-project > > - Adding to the discussions and contributing code > > and there's more contents about giving to the community. This is all relevant > > to project / community membership. > > > > => This document should be spitted into community membership document and > > (sub-)project maintenance. Currently it's a mix of both. > > > > > Don't we want it mixed? why would we draw a line between the two roles? > having people thinking of community and code together is healthy. > > Carl. > OK, looks much better now. Some final (I hope) remarks; 1. We now have 2 "Becoming a maintainer" headers. I'd change the 2nd one to something like "Applying for a project maintainer role" or anything alike. 2. WRT contribution and maintenance mixture, it takes the focus off the document's topic, for no visible reason. I'll try to explain with 2 examples; a. The car You just bought a new car, and you look into the owner manual, looking for a quick & simple way to adjust your radio pre-set stations. You get the information in one chapter which includes the complete wiring scheme, board design and explanation on connector types to use when connecting to amplifiers or phone car-kit. Will you think it's very helpful and easy to understand how you should set your radio buttons? Now think of the mechanic guy in the garage, getting the same manual, which he's supposed to use in order to verify what is short-circuiting the car embedded media controller. What will he think when he needs to read the connector description along with setting radio buttons? Is mixing all the information a good idea? Does it help both guys? Any of them? b. Git Book http://book.git-scm.com/ As you can see there are separate chapters for each type of user; Basic, Intermediate and Advanced. I'm sure someone who looks for a way to recover corrupted objects, won't find git clone syntax very helpful while he looks for the relevant information. 3. Now back to us... I think the following should be used in a different document; - Contributing to a project - Adding to the discussions and contributing code - Large projects These (and maybe some more) should be located in a document focused on general community contribution and oVirt project specific contribution rules / policy / code / coding-conventions, etc. Apache,for instance, asks every contributer to sign something making the code contribution owned by / used by the relevant project, so there are no license / rights issues. This could be a good place for explaining such a signature, should we require one. Current document should be lean and mean; Containing the relevant information on becoming a maintainer, responsibilities, ethics, policies, etc. The document should start by referring to the project contribution document. In this way you give more background if needed. -- /d "All computers wait at the same speed."

2 2

Location (for Cisco, IBM, Intel)
by Carl Trieloff 20 Sep '11

20 Sep '11

If it is at all possible, could Cisco, IBM, Intel see if we can get a tentative confirm for one of the facilities for the launch on the 1-3rd November before the Wednesday call. If we can settle this by/on Wednesday we can complete the materials and go public with invitations / briefings next week. Carl.

6 17

we are partially live....
by Carl Trieloff 20 Sep '11

20 Sep '11

www.ovirt.org is up, however the DNS has not yet cut across which is causing the css not to load. hopefully DNS cuts across tonight or tomorrow morning. If you want to view the site between now and then add 173.255.252.138 ovirt.org www.ovirt.org <http://www.ovirt.org> to your etc/hosts file. I will mail out when we are cut across correctly. Carl.

2 17