Bugzilla Re-organization

DISCUSSION Michael Halstead 6 participants 12 messages May 25, 2012 – Jun 1, 2012

Share & tools

Michael Halstead

author

2012-05-25 22:38 UTC #0 lore raw

The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well.

Signature · 2 lines

Michael Halstead
Yocto Project / Sys Admin

Damian, Alexandru

2012-05-28 05:28 UTC #1 lore raw

I like how it works :)

Alex

Quoted 18 lines · Michael Halstead

The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well.
--
Michael Halstead
Yocto Project / Sys Admin
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Rifenbark, Scott M

2012-05-30 14:51 UTC #2 lore raw

In reply to Michael Halstead

For documentation there should be six things. We are missing the ADT Manual and the BSP manual.

ScottR

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Michael Halstead
Sent: Friday, May 25, 2012 3:38 PM
To: [email protected]; Yocto Project Discussion
Subject: [yocto] Bugzilla Re-organization

--
Michael Halstead
Yocto Project / Sys Admin

Michael Halstead

author

2012-05-30 15:12 UTC #3 lore raw

Quoted 1 line · Scott M

For documentation there should be six things. We are missing the ADT Manual and the BSP manual.

The reclassification step is incomplete. ADT didn't reclassify as expected and has remained in Build System & Metadata. BSPs is still in Yocto Project Components. I'll correct these in the script and import fresh data to test.

Thank you Scott for reporting this.

Michael Halstead

Quoted 17 lines

ScottR
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Michael Halstead
Sent: Friday, May 25, 2012 3:38 PM
To: [email protected]; Yocto Project Discussion
Subject: [yocto] Bugzilla Re-organization
The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well.
--
Michael Halstead
Yocto Project / Sys Admin

Darren Hart

2012-05-31 18:28 UTC #4 lore raw

In reply to Michael Halstead

Quoted 6 lines · Michael Halstead

The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well.

It seems to me one should be able to find the linux-yocto kernel itself under the Yocto Project Components from the basic search page. Currently there is Kernel Tooling and BSPs, but there are times when the bug is not BSP specific and is in the kernel itself, not the tooling. For this, a hierarchy like the following might be preferable:

Yocto Project Components
BSPs
bsps
Kernel
linux-yocto
configuration
kernel-tooling

I am still not sure how best to deal with BSPs here and BSPs in Build System & Metadata. I think We should pick one or the other as the distinction between the two is non-obvious (actually I have no idea what it would be).

Tom, Bruce: opinions on the above?

"Build System & Metadata" and "Yocto Metadata Layers" use different naming schemes for the components in the various layers products. Some use meta- others do not.

Signature · 3 lines

Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Bruce Ashfield

2012-06-01 03:37 UTC #5 lore raw

Quoted 16 lines · Darren Hart

Quoted 6 lines · Michael Halstead
The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well.
It seems to me one should be able to find the linux-yocto kernel itself under the Yocto Project Components from the basic search page. Currently there is Kernel Tooling and BSPs, but there are times when the bug is not BSP specific and is in the kernel itself, not the tooling. For this, a hierarchy like the following might be preferable:

Quoted 7 lines

Yocto Project Components
BSPs
bsps
Kernel
linux-yocto
configuration
kernel-tooling

+1. I completely agree with this.

Quoted 5 lines

I am still not sure how best to deal with BSPs here and BSPs in Build System& Metadata. I think We should pick one or the other as the distinction between the two is non-obvious (actually I have no idea what it would be).

Agreed .. that this is hard. If we used 'configuration' for the kernel category, could the build system + meta data fall into that as well under BSPs ?

i.e.

BSPs
bsps - runtime
bsps - configuration

Bruce

Quoted 9 lines

Tom, Bruce: opinions on the above?
"Build System& Metadata" and "Yocto Metadata Layers" use different naming schemes for the components in the various layers products. Some use meta- others do not.

Darren Hart

2012-06-01 17:44 UTC #6 lore raw

Quoted 37 lines · Bruce Ashfield

Quoted 16 lines · Darren Hart
Quoted 6 lines · Michael Halstead
The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well.
It seems to me one should be able to find the linux-yocto kernel itself under the Yocto Project Components from the basic search page. Currently there is Kernel Tooling and BSPs, but there are times when the bug is not BSP specific and is in the kernel itself, not the tooling. For this, a hierarchy like the following might be preferable:
Quoted 7 lines
Yocto Project Components
BSPs
bsps
Kernel
linux-yocto
configuration
kernel-tooling
+1. I completely agree with this.
Quoted 5 lines
I am still not sure how best to deal with BSPs here and BSPs in Build System& Metadata. I think We should pick one or the other as the distinction between the two is non-obvious (actually I have no idea what it would be).
Agreed .. that this is hard. If we used 'configuration' for the kernel category, could the build system + meta data fall into that as well under BSPs ?

Quoted 5 lines

i.e.
BSPs
bsps - runtime
bsps - configuration

I think so. I like this better.

Tom, any objections?

Yocto Project Components
BSPs
bsps-runtime
bsps-configuration
Kernel
linux-yocto
kernel-configuration
kernel-tooling

The other Kernel related path would include
Build System & Metadata
Layers - OpenEmbedded-Core
kernel

This would be for the kernel.bbclass and other recipes and classes.

I think we should just kill:
Build System & Metadata
Layers - BSPs

and move all the BSP components under Yocto Project Components->BSPs

Finally there is:

Build System & Metadata
Layers - meta-yocto
machines

Which should just go away and be replaced witha BSPs->meta-yocto component, if anything.

So, the final layout would be:

Yocto Project Components
BSPs
bsps-runtime
bsps-configuration (these top too being "generic" buckets) bsps-meta-yocto
bsps-meta-fsl-ppc
bsps-meta-intel
bsps-meta-ti
bsps-tools
bsps-xilinx (meta-xilinx?)

Kernel
linux-yocto
kernel-configuration
kernel-tooling

I believe this would make it much easier for us to manage Kernel related issues across the project.

--
Darren

Quoted 15 lines

?
Bruce
Quoted 9 lines
Tom, Bruce: opinions on the above?
"Build System& Metadata" and "Yocto Metadata Layers" use different naming schemes for the components in the various layers products. Some use meta- others do not.

Signature · 3 lines

Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Bruce Ashfield

2012-06-01 20:03 UTC #7 lore raw

Quoted 94 lines · Darren Hart

Quoted 37 lines · Bruce Ashfield
Quoted 16 lines · Darren Hart
Quoted 6 lines · Michael Halstead
The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well.
It seems to me one should be able to find the linux-yocto kernel itself under the Yocto Project Components from the basic search page. Currently there is Kernel Tooling and BSPs, but there are times when the bug is not BSP specific and is in the kernel itself, not the tooling. For this, a hierarchy like the following might be preferable:
Quoted 7 lines
Yocto Project Components
BSPs
bsps
Kernel
linux-yocto
configuration
kernel-tooling
+1. I completely agree with this.
Quoted 5 lines
I am still not sure how best to deal with BSPs here and BSPs in Build
System& Metadata. I think We should pick one or the other as the
distinction between the two is non-obvious (actually I have no idea what it would be).
Agreed .. that this is hard. If we used 'configuration' for the kernel category, could the build system + meta data fall into that as well under BSPs ?
Quoted 5 lines
i.e.
BSPs
bsps - runtime
bsps - configuration
I think so. I like this better.
Tom, any objections?
Yocto Project Components
BSPs
bsps-runtime
bsps-configuration
Kernel
linux-yocto
kernel-configuration
kernel-tooling
The other Kernel related path would include
Build System& Metadata
Layers - OpenEmbedded-Core
kernel
This would be for the kernel.bbclass and other recipes and classes.
I think we should just kill:
Build System& Metadata
Layers - BSPs
and move all the BSP components under Yocto Project Components->BSPs
Finally there is:
Build System& Metadata
Layers - meta-yocto
machines
Which should just go away and be replaced witha BSPs->meta-yocto component, if anything.
So, the final layout would be:
Yocto Project Components
BSPs
bsps-runtime
bsps-configuration (these top too being "generic" buckets) bsps-meta-yocto
bsps-meta-fsl-ppc
bsps-meta-intel
bsps-meta-ti
bsps-tools
bsps-xilinx (meta-xilinx?)

Quoted 7 lines

Kernel
linux-yocto
kernel-configuration
kernel-tooling
I believe this would make it much easier for us to manage Kernel related issues across the project.

Agreed. This makes sense to me.

Bruce

Quoted 21 lines

--
Darren
Quoted 15 lines
?
Bruce
Quoted 9 lines
Tom, Bruce: opinions on the above?
"Build System& Metadata" and "Yocto Metadata Layers" use different
naming schemes for the components in the various layers products. Some use meta- others do not.

Darren Hart

2012-06-01 17:46 UTC #8 lore raw

In reply to Bruce Ashfield

Quoted 37 lines · Bruce Ashfield

Quoted 16 lines · Darren Hart
Quoted 6 lines · Michael Halstead
The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well.
It seems to me one should be able to find the linux-yocto kernel itself under the Yocto Project Components from the basic search page. Currently there is Kernel Tooling and BSPs, but there are times when the bug is not BSP specific and is in the kernel itself, not the tooling. For this, a hierarchy like the following might be preferable:
Quoted 7 lines
Yocto Project Components
BSPs
bsps
Kernel
linux-yocto
configuration
kernel-tooling
+1. I completely agree with this.
Quoted 5 lines
I am still not sure how best to deal with BSPs here and BSPs in Build System& Metadata. I think We should pick one or the other as the distinction between the two is non-obvious (actually I have no idea what it would be).
Agreed .. that this is hard. If we used 'configuration' for the kernel category, could the build system + meta data fall into that as well under BSPs ?

Quoted 5 lines

i.e.
BSPs
bsps - runtime
bsps - configuration

I think so. I like this better.

Tom, any objections?

Yocto Project Components
BSPs
bsps-runtime
bsps-configuration
Kernel
linux-yocto
kernel-configuration
kernel-tooling

The other Kernel related path would include
Build System & Metadata
Layers - OpenEmbedded-Core
kernel

This would be for the kernel.bbclass and other recipes and classes.

I think we should just kill:
Build System & Metadata
Layers - BSPs

and move all the BSP components under Yocto Project Components->BSPs

Finally there is:

Build System & Metadata
Layers - meta-yocto
machines

Which should just go away and be replaced witha BSPs->meta-yocto component, if anything.

So, the final layout would be:

Kernel
linux-yocto
kernel-configuration
kernel-tooling

I believe this would make it much easier for us to manage Kernel related issues across the project.

--
Darren

Quoted 15 lines

?
Bruce
Quoted 9 lines
Tom, Bruce: opinions on the above?
"Build System& Metadata" and "Yocto Metadata Layers" use different naming schemes for the components in the various layers products. Some use meta- others do not.

Signature · 3 lines

Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Tom Zanussi

2012-06-01 21:33 UTC #9 lore raw

Quoted 41 lines · Darren Hart

Quoted 39 lines · Bruce Ashfield
Quoted 16 lines · Darren Hart
Quoted 6 lines · Michael Halstead
The first draft of the reorganized bugzilla is available for feedback now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently disabled on this preview copy. Please feel free to take a look and see if you spot any errors. Additional refinement of product or component descriptions will be helpful as well.
It seems to me one should be able to find the linux-yocto kernel itself under the Yocto Project Components from the basic search page. Currently there is Kernel Tooling and BSPs, but there are times when the bug is not BSP specific and is in the kernel itself, not the tooling. For this, a hierarchy like the following might be preferable:
Quoted 7 lines
Yocto Project Components
BSPs
bsps
Kernel
linux-yocto
configuration
kernel-tooling
+1. I completely agree with this.
Quoted 5 lines
I am still not sure how best to deal with BSPs here and BSPs in Build System& Metadata. I think We should pick one or the other as the distinction between the two is non-obvious (actually I have no idea what it would be).
Agreed .. that this is hard. If we used 'configuration' for the kernel category, could the build system + meta data fall into that as well under BSPs ?
i.e.

Quoted 8 lines

Quoted 3 lines
BSPs
bsps - runtime
bsps - configuration
I think so. I like this better.
Tom, any objections?

No objections, this all looks fine to me.

Quoted 9 lines

Yocto Project Components
BSPs
bsps-runtime
bsps-configuration
Kernel
linux-yocto
kernel-configuration
kernel-tooling

Quoted 7 lines

The other Kernel related path would include
Build System & Metadata
Layers - OpenEmbedded-Core
kernel
This would be for the kernel.bbclass and other recipes and classes.

It would be nice to have that fact reflected in the name somehow, to avoid confusion for users with Yocto Project Components->Kernel, but I'm not coming up with anything wieldy.

Quoted 6 lines

I think we should just kill:
Build System & Metadata
Layers - BSPs
and move all the BSP components under Yocto Project Components->BSPs

I agree, it would just add confusion to keep this.

Quoted 9 lines

Finally there is:
Build System & Metadata
Layers - meta-yocto
machines
Which should just go away and be replaced witha BSPs->meta-yocto component, if anything.

Better known as 'core BSPs', which might be more clear to some...

Quoted 7 lines

So, the final layout would be:
Yocto Project Components
BSPs
bsps-runtime
bsps-configuration (these top too being "generic" buckets) bsps-meta-yocto

On the other hand this naming is clean and consistent with the rest, so is probably better.

Quoted 6 lines

bsps-meta-fsl-ppc
bsps-meta-intel
bsps-meta-ti
bsps-tools
bsps-xilinx (meta-xilinx?)

Quoted 8 lines

Kernel
linux-yocto
kernel-configuration
kernel-tooling
I believe this would make it much easier for us to manage Kernel related issues across the project.

I agree. Acked-by-me...

Tom

Quoted 20 lines

--
Darren
Quoted 15 lines
?
Bruce
Quoted 9 lines
Tom, Bruce: opinions on the above?
"Build System& Metadata" and "Yocto Metadata Layers" use different naming schemes for the components in the various layers products. Some use meta- others do not.

Darren Hart

2012-06-01 21:43 UTC #10 lore raw

Quoted 7 lines · Tom Zanussi

Quoted 5 lines · Darren Hart
The other Kernel related path would include
Build System & Metadata
Layers - OpenEmbedded-Core
kernel

Quoted 6 lines

Quoted 2 lines
This would be for the kernel.bbclass and other recipes and classes.
It would be nice to have that fact reflected in the name somehow, to avoid confusion for users with Yocto Project Components->Kernel, but I'm not coming up with anything wieldy.

kernel-recipes ?

Quoted 10 lines

Quoted 7 lines
So, the final layout would be:
Yocto Project Components
BSPs
bsps-runtime
bsps-configuration (these top too being "generic" buckets) bsps-meta-yocto
On the other hand this naming is clean and consistent with the rest, so is probably better.

Ah, but you remind me that we probably also need:

bsps-oe-core

Quoted 12 lines

Quoted 12 lines
bsps-meta-fsl-ppc
bsps-meta-intel
bsps-meta-ti
bsps-tools
bsps-xilinx (meta-xilinx?)
Kernel
linux-yocto
kernel-configuration
kernel-tooling

Quoted 5 lines

Quoted 3 lines
I believe this would make it much easier for us to manage Kernel related issues across the project.
I agree. Acked-by-me...

Great. Michael, the kernel-team is now in agreement.

Signature · 3 lines

Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Tom Zanussi

2012-06-01 21:47 UTC #11 lore raw

Quoted 9 lines · Darren Hart

Quoted 7 lines · Tom Zanussi
Quoted 5 lines · Darren Hart
The other Kernel related path would include
Build System & Metadata
Layers - OpenEmbedded-Core
kernel

Quoted 9 lines

Quoted 6 lines
Quoted 2 lines
This would be for the kernel.bbclass and other recipes and classes.
It would be nice to have that fact reflected in the name somehow, to avoid confusion for users with Yocto Project Components->Kernel, but I'm not coming up with anything wieldy.
kernel-recipes ?

It doesn't really capture the 'classes' part, but I suppose that would be implied and close enough.

Tom

Quoted 35 lines

Quoted 10 lines
Quoted 7 lines
So, the final layout would be:
Yocto Project Components
BSPs
bsps-runtime
bsps-configuration (these top too being "generic" buckets) bsps-meta-yocto
On the other hand this naming is clean and consistent with the rest, so is probably better.
Ah, but you remind me that we probably also need:
bsps-oe-core
Quoted 12 lines
Quoted 12 lines
bsps-meta-fsl-ppc
bsps-meta-intel
bsps-meta-ti
bsps-tools
bsps-xilinx (meta-xilinx?)
Kernel
linux-yocto
kernel-configuration
kernel-tooling
Quoted 5 lines
Quoted 3 lines
I believe this would make it much easier for us to manage Kernel related issues across the project.
I agree. Acked-by-me...
Great. Michael, the kernel-team is now in agreement.