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.
RedHat, ENG-Virtualization R&D
This vote is to accept into oVirt the memory overcommit manager (mom)
project either to be used as a dependency in VDSM or as a daemon
alongside VDSM. This detail will be worked during integration.
If the project is accepted and given it is our first community submitted
project to be voted we will create an infrastructure setup list which I
will record. This can then be used to make it easier for the next
Please vote -1, 0, +1 whether you would like to include this project
into oVirt. I'll leave the vote open at least 72 hours.
Vizuri has been working on a Mobile application that interfaces with the
RHEVM API and allows Administrators to manage RHEV via their tablet or
Smartphone. The application is targeted to run on iPhone, iPad and
Android devices, but our current Proof of concept has only been tested
on Android devices. Our next iteration is focused on iOS compatibility
and is progressing well.
Our intention has always been to open source this project and it seems
like an oVirt subproject would be the perfect place for this.
Would this be a good sub-project candidate and what steps would we need
Isaac Christoffersen, Sr. Software Engineer
Vizuri, a division of AEM Corporation
"Tell me and I forget. Teach me and I remember. Involve me and I learn." - Benjamin Franklin
I believe we are ready to start our first board vote. In this regard I
have posted the initial board list on the site, so anyone can reference
it. At the bottom of http://www.ovirt.org/governance/board/
Generally before a vote is proposed it is good to have discussed the
topic and it should seem like agreement has been reached on the thread.
Once this has happened a 'VOTE' thread is started.
Anyone on the list can vote (-1,0,+1) as described on the site. I.e.
anyone in the community can voice an opinion by voting, however only the
official board seat votes are counted. If you -1 then you need to
substantiate and be willing to have your -1 debated. It is good practice
to leave the vote open long enough so that those in different timezone
can see the vote and comment. After a reasonable time (48-72 hours
generally, we close the vote).
I will shortly post a vote thread to accept the Memory overcommit
manager project into oVirt and for the Mobile client for the engine.
I think we should to add a BOF section to discuss projects, or devote
some time in our upcoming weekly meetings around bringing in / managing
My main though is that we should maybe create a set of questions for new
subprojects to fill out as I expect we are going to want to have any new
subproject answer, or think through the following basic things
- Basic summary of the project
- How / where does this sub-project integrate into the oVirt stack?
- Are there any impact or features that need to be exposed via the UI?
- What existing API's does the project use
- Does the project expose or create new APIs.
We can maybe work a doc as we do this a few times.
The idea is not to make it complicated, just to get us thinking about
the right things when we work through the process.
Is oVirt Foundation (or will it be) an independent corporation with a 501(c)3
If so, will the foundation accept sub-project targeted donations? Will the
foundation provide legal services for projects?
I'm trying to understands the pros and cons of being a member project to help
make a case for joining. Even if this isn't in place today or in the near
future, if that's where things are heading, it would be useful to know.