[Webhob] Events information updates

[Webhob] Events information updates

[Calin Dragomir]

[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]

Hello team,

Please find my updates on the Events information table in the following 
lines, based on our latest discussions.

*Builds table*
* "outcome" field has been added
* "bitbake_version" field had been added
* we can grab: "machine", "distro", "distro_version" from bitbake with 
the getVariable command
* layer names can be obtin by asking for the BBLAYERS variable.

*Tasks table*
* diffsigs output variable added.

*Variables*
* added "changed" field

*General*
* updated all fields with DONE and N/A values to illustrate what info 
needs to be covered.

*Qs:*

* what's the difference between a package and a recipe ? Because for the 
Tasks table, I get the recipe name from the event._package attribute, 
and if this is different from what it should be stored there maybe we 
need to change it.

* what do you think about this option to tie the dependecies: 
https://docs.djangoproject.com/en/dev/topics/db/models/#extra-fields-on-many-to-many-relationships 
?
=> if adopted, it would mean extra fields (ManyToManyFields) added to 
TASKS, RECIPE and PACKAGE tables.

* specific fields questions have been inserted in the Events information 
page.


Based on your feedback on this , I will get to putting up some Django 
models on Monday, with the elements we have defined on the Events 
Information page ( https://wiki.yoctoproject.org/wiki/Event_information) .

I will not be in office tomorrow (Friday 14th), because of a company 
event, so I'll be able to see any answers on Monday.

Thank you,
Calin

[-- Attachment #2: Type: text/html, Size: 2445 bytes --]

Re: [Webhob] Events information updates

[Damian, Alexandru]

Please find comments below,

Alex


On Thu, Jun 13, 2013 at 5:26 PM, Calin Dragomir
<calinx.l.dragomir@intel.com> wrote:
>
> Hello team,
>
> Please find my updates on the Events information table in the following lines, based on our latest discussions.
>
> Builds table
> * "outcome" field has been added
> * "bitbake_version" field had been added
> * we can grab: "machine", "distro", "distro_version" from bitbake with the getVariable command
> * layer names can be obtin by asking for the BBLAYERS variable.
>
> Tasks table
> * diffsigs output variable added.
>
> Variables
> * added "changed" field
>
> General
> * updated all fields with DONE and N/A values to illustrate what info needs to be covered.
>
> Qs:
>
> * what's the difference between a package and a recipe ? Because for the Tasks table, I get the recipe name from the event._package attribute, and if this is different from what it should be stored there maybe we need to change it.
>

Alex: A package is an archive containing a set of files and
corresponding metadata, ready to be installed on a target system.
A recipe is a set of instructions on how to build a set of packages. A
recipe can generate 0 or more packages.

> * what do you think about this option to tie the dependecies: https://docs.djangoproject.com/en/dev/topics/db/models/#extra-fields-on-many-to-many-relationships ?
> => if adopted, it would mean extra fields (ManyToManyFields) added to TASKS, RECIPE and PACKAGE tables.

Alex: I am not a fan of ManyToMany fields because they break the 4th
normal form, IMHO. I actually would prefer to have separate
_Dependencies models that would list the dependencies separately.

>
> * specific fields questions have been inserted in the Events information page.
>
>
> Based on your feedback on this , I will get to putting up some Django models on Monday, with the elements we have defined on the Events Information page ( https://wiki.yoctoproject.org/wiki/Event_information) .
>
> I will not be in office tomorrow (Friday 14th), because of a company event, so I'll be able to see any answers on Monday.
>
> Thank you,
> Calin