Re: [ovirt-devel] Best (and up-to-date) practices for developers?

I like that idea. I would prefer having the smaller, more focused files in a directory. I would probably call it documentation or something similar, though. -Phillip Bailey On Tue, Sep 20, 2016 at 9:14 AM, Roy Golan wrote: > > > On 19 September 2016 at 15:18, Martin Betak

Re: [ovirt-devel] Best (and up-to-date) practices for developers?

On 19 September 2016 at 15:18, Martin Betak wrote: > Yeah definitely +1. > > Even after being with the project for some time, I often wonder about > things > like in what order should fields in class be based on their function (as in > logger, static sonstants, @Injected

Re: [ovirt-devel] Best (and up-to-date) practices for developers?

Yeah definitely +1. Even after being with the project for some time, I often wonder about things like in what order should fields in class be based on their function (as in logger, static sonstants, @Injected dependencies, actual instance fields...) so such document could answer questions like

Re: [ovirt-devel] Best (and up-to-date) practices for developers?

+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. -Phillip Bailey On Mon, Sep 19, 2016 at

[ovirt-devel] Best (and up-to-date) practices for developers?

Hi, 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. Like: - code style (we have the config in sources) - what libraries are (not) allowed (guava..ehm..) - how should CDI be used