splitting cli/sdk project
by Michael Pasternak
Hi folks,
I would like to propose splitting cli/sdk projects as each of them should become a master-project for different implementations
and i guess we wouldn't want mixing different SDKs and CLIs under same project.
--
Michael Pasternak
RedHat, ENG-Virtualization R&D
13 years, 2 months
oVirt Sync Call Meeting Minutes :: 2011-09-28
by Robyn Bergeron
oVirt Sync Call Meeting Minutes
Wednesday, September 28, 2011 - 14:00 UTC (10:00am US Eastern, 07:00am
US Pacific)
== Invitees/Attendees ==
project-planning(a)ovirt.org list subscribers
Robyn Bergeron (Red Hat)
Carl Trieloff (Red Hat)
Kyle Mestery (Cisco)
Ayal Baron (Red Hat)
Alex Graf (SUSE)
Kerri Catallozzi (Red Hat)
Anthony Liguori (IBM)
Andy Cathrow (Red Hat)
Perry Myers (Red Hat)
Jim Jagielski (Red Hat)
Jon Benedict (NetApp)
Frank Novak (IBM)
Karsten Wade (Red Hat)
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.
== Action Items ==
* Kerri to put together draft press release for review next week
* Robyn to update meeting time to one hour
* List discussion items: Two-tier project acceptance/graduation
proposal, Webex discussion
* Kyle to look into the option of getting a UCS on site rather than
Andy shipping a rack
== 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.
== Call Agenda ==
0) General Updates
* Andy has RHEV entitlements to help out those who want to get a bit
more context
* If anyone needs an entitlement to download RHEL + RHEV in order to
get some experience with RHEV then please email acathrow(a)redhat.com
* Agree to an hour going forward, at least in the short term, for
phone call time.
Voting on new project
1) Board news
* Board members are now confirmed from each strategic company. (Carl)
* Board members voting on first few proposed projects
* We have had 3 projects approach us. Right now - really working on
getting through the process, going through framework of
process/acceptance, framing discussion.
* What are requirements for oVirt project?
* To get a project in / join ecosystem, the bar should be reasonably
low, so we can build community, build interaction. Not a lot of detail
around this right now.
* It's important for us to get traction, but not necessarily
creating precedent that we can't ever undo. Maybe a two-stage process
akin to Apache Incubator - as a project/code/development grows, they can
graduate onto higher level. Lets us have low barriers, allows us to be
more nimble as far as changing things without creating long-term precedence.
* Take back to list.
2) Project launch status / Progress review
* Statistics review (Carl)
3) oVirt Workshop / Summit - Nov. 1 - 3, Cisco Main Campus, San Jose, CA.
* http://www.ovirt.org/news-and-events/workshop/
* Attendance updates (Robyn)
* 54 RSVPs so far for the kick off workshop
* Attendees not from initial group are numbering around 12 currently
* We are still waiting for RSVPs from NetApp, IBM and more from
Red Hat
* Plan to leave the RSVP's open for another couple of weeks.
* Bringing in 4-5 additional signups per day
* Logistics planning:
* Capacity is 45 people
* Planning for breakout rooms
* Evening events/activities planning
* Food
* Hotel arrangements
* Press release discussion (Kerri from Red Hat joining call)
* Next steps: Kerri to take a stab at drafting press release, get
contacts at companies for PR; asking that folks help Kerri get in touch
with appropriate people.
* Target a launch for after the workshop - most likely the week
following to make sure we get maximum pickup
* One option is a joint release with all companies on the board ,
which Kerri would coordinate. This option is more effective in terms of
press pickup but harder to coordinate given corporate press approval cycles
* Another option is a Red Hat press release with supporting quotes
from board members
* Joint press release:
* All tickers would be included, would lead to more
coverage/awareness level
* Cons - intensive scrutiny, hard to wrangle agreement sometimes.
* Red Hat only press release
* Easier to just get supporting quotes from member companies
* Would lose a bit of awareness from not having tickers, etc. - not
hitting as wide an audience
* Thoughts:
* Joint press release makes it a true joint effort, and not just a
Red Hat Thing.
* Time delay might be a problem on join press release, but think it
is crucial to success of oVirt to get it out as a Joint Press Release.
* To-Do's: Agreed, Kerri to put together draft joint release. Basic
content is that we've launched the community at a F2F in California,
examples of what we're agreeing to work on, companies + other folks.
Very focused on workshop and results.
* Kerri: Feel free to ask JimJag for help.
4) Infrastructure (Karsten)
* Wiki update, movement from shared google document
* Project-planning list archival plans
* Project naming status
5) Other updates / Agenda topics
* Andy is working with Corporate Comms folks to utilize our corporate
webex account. Schedule some webex sessions/archived recordings, do some
quick introductions to RHEV, use that going forward to have larger
sessions as part of training/collaboration. Could be useful for
overviews of projects, etc.
* Should we post a schedule of topics to be done and when, and put
it on the website?
* Seeking volunteers for wanting to discuss things on webex.
* Good background for folks coming to conference.
* Hardware for workshop - Demo rack that we can ship out. If we want
to do hands-on work, we can use it. Do we need any other hardware
on-site for workshop?
* Kyle will look into the option of getting a UCS on site rather
than Andy shipping a rack
13 years, 3 months
archives cleaned, ready to open list
by Karsten Wade
Folks:
As per the original design for this list, we are planning to open the
archives and subscription to the community.
Prior to doing that, I manually redacted specific company names, names
of individuals, and the Google Docs URLs with similar information in
them. These redacted details are related to individuals and
organizations that did not elect to join oVirt to start. We want their
relationship with oVirt to be revealed in a manner and time of their
choosing, not by accident from our archives.
For any Google Docs we are using, we need to create a new document and
copy/paste the clean information in to it to avoid the revision
history.
I'd like to open the list and archives following the next meeting. If
you want to check for any particular detail in the archives, please
take the opportunity to look and let me know if you have any
questions, something that needs changing, and so forth.
If there is no protest, I'll be opening the archives 24 hours from
now.
Thanks - Karsten
--
name: Karsten 'quaid' Wade, Sr. Community Gardener
team: Red Hat Community Architecture & Leadership
uri: http://communityleadershipteam.org
http://TheOpenSourceWay.org
gpg: AD0E0C41
13 years, 3 months
Additional govenance guideline doc
by Carl Trieloff
Based on suggestions and comments on the threads around sub-project, I
suggest we add the following guide for new projects.
Most of the content from Anthony.
fire away with comments... when we are happy with it, I'll post it.
Carl.
------------------------------------------------------------------------------------------------
A Project that wants to join oVirt should follow the following basic
guidelines:
1) Project posts an overview page on ovirt.org/wiki, including scope and
short term roadmap to ovirt.org wiki. That page is then copied as a mail
to board@ovirt
2) There is an official comment period that lasts for a period of time
up to 3 weeks. This time period allows for questions to be enhanced, and
the wiki to be improved. Projects can complete this stage faster,
however the key is provide enough time for discussion.
3) At any point in this time period, the proposal can be officially
withdrawn.
4) At the end of the period or once there seems to be consensus, there
is a final call for comments before a vote takes place. If the thread's
comments die down, then a VOTE thread can be used to move the process along.
Include the following information on the overview wiki page
Project name:
Project description:
Initial scope:
Description of how the project meets the oVirt requirements
http://www.ovirt.org/governance/adding-a-subproject/
a.) Each project must agree to support the oVirt complete stack (CS)
release schedule
b.) Each project must agree to provide or integrate with one of the
published API’s
Create dev list:
Create bugzilla:
GIT location if already open source:
13 years, 3 months
hotel for workshop
by Itamar Heim
Can we arrange with a hotel adjacent to the workshop for group pricing
(or maybe cisco already has one)?
would be nice if most would stay in same hotel, and reduce costs
Thanks,
Itamar
13 years, 3 months
oVirt Sync Call Meeting Agenda :: 2011-09-28
by Robyn Bergeron
oVirt Sync Call Meeting Agenda
Wednesday, September 28, 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 mail rbergero(a)redhat.com.
== 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.
== Call Agenda ==
1) Board news
* Board members are now confirmed from each strategic company. (Carl)
* Board members voting on first few proposed projects
2) Project launch status / Progress review
* Statistics review (Carl)
3) oVirt Workshop / Summit - Nov. 1 - 3, Cisco Main Campus, San Jose, CA.
* http://www.ovirt.org/news-and-events/workshop/
* Attendance updates (Robyn)
* Logistics planning:
* Capacity is 45 people
* Planning for breakout rooms
* Evening events/activities planning
* Food
* Hotel arrangements
* Press release discussion (Kerri from Red Hat joining call)
4) Infrastructure (Karsten)
* Wiki update, movement from shared google document
* Project-planning list archival plans
* Project naming status
5) Other updates / Agenda topics
== 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
13 years, 3 months
Confirming RSVPs
by Robyn Bergeron
I've seen a number of comments in various places touching on the fact
that people aren't quite sure what they should be getting when they send
an email to rsvp(a)ovirt.org.
Do we want to add some sort of confirmation mail, stating that we've
received your RSVP and added you to our list, and more details will be
forthcoming by $specificdate?
-Robyn
13 years, 3 months
Board member
by Carl Trieloff
If it is possible, could we get the named board members for each
strategic member. If we are going to action decisions on the 3
subprojects requests we will need these for voting.
I suggest we try get them named this week, I'll spend some time on the
call around it, and the next week we spend some time on the sub project
topic.
kind regards,
Carl.
13 years, 3 months
6998 page views Friday
by Carl Trieloff
Top referrers.
1.) reddit
2.) register
3.) lpeer's blog
...
8) twitter
13 years, 3 months
