Adding a project to oVirt

[Anthony Liguori]

On 09/13/2011 10:42 AM, Carl Trieloff wrote:
> On 09/12/2011 03:45 PM, Anthony Liguori wrote:
>> "In order to release a cohesive stack, everything needs to work
>> together. The core of this is the engine. If a new project is started
>> it needs to integrate with a published API, or an additional API needs
>> to be created into the engine project to support the new project.
>> Finally additional API’s can come into scope to provide
>> facilities/capabilities that the engine consumes. The board signs off
>> on which project provide API’s to make sure there is coordination
>> between the projects. The board is not responsible for the technical
>> aspects of the API’s, just the facilitation when named API projects
>> are added or removed."
>>
>> It feels a bit out of place.  Perhaps it's because I don't have a good
>> grip on what the "engine project" is since it still doesn't exist as
>> an open source project.
>>
>> Maybe we can just drop this paragraph or remove the bits about the
>> engine?  The rest looks great.
>
>
> The engine is the core framework for us, as I posted in the piece on how
> eclipse works. I would like to add it and we can discuss in more detail
> in the governance tracks at the workshop and edit as required.

Okay, it makes sense re: eclipse but I think we need to come up with a 
firm mission statement of the engine project.

The way it's positioned, if RHEV-M Server is oVirt Engine, then you're 
excluding the possibility of having an stand alone VDSM with tools that 
build directly on top of VDSM.  If that's the case, then it dramatically 
affects the type of ecosystem being built here.

Regards,

Anthony Liguori

>
> However to the point on related projects, I'm going to add a para on that
>
> Carl.
>