+1 for the idea if it doesn't already exist. It would ease development for
those already working on the project, but it would also make it easier for
others who would like to contribute to it, but aren't comfortable with
navigating such a large code base.
On Mon, Sep 19, 2016 at 3:56 AM, Martin Sivak <msi...@redhat.com> wrote:
> I just wanted to find out if we have some documentation for the
> developers that would give hint on different aspects of the engine
> development in terms of coding.
> - code style (we have the config in sources)
> - what libraries are (not) allowed (guava..ehm..)
> - how should CDI be used (see https://gerrit.ovirt.org/#/c/63747/)
> - what files need to be touched to properly support translations
> - ...
> It would be cool to have something brief we can search easily. I know
> it can get outdated fast, but if we use it only for the important
> stuff and review it for each major release (as the major rules do not
> change much) we should be able to keep it usable.
> Martin Sivák
> SLA / oVirt
> Devel mailing list
Devel mailing list