Bugzilla Re-organization

Bugzilla Re-organization

[Michael Halstead]

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

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



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4464 bytes --]

Re: Bugzilla Re-organization

[Damian, Alexandru]

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

I like how it works :)

Alex

On Sat, May 26, 2012 at 1:38 AM, Michael Halstead
<michael@yoctoproject.org>wrote:

> 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
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>

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

Re: Bugzilla Re-organization

[Rifenbark, Scott M]

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

ScottR

-----Original Message-----
From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Michael Halstead
Sent: Friday, May 25, 2012 3:38 PM
To: yocto-infrastructure@yoctoproject.org; 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

Re: Bugzilla Re-organization

[Michael Halstead]

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

On 05/30/2012 07:51 AM, Rifenbark, Scott M wrote:
> 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
>
> ScottR
>
> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Michael Halstead
> Sent: Friday, May 25, 2012 3:38 PM
> To: yocto-infrastructure@yoctoproject.org; 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
>
>
>



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4464 bytes --]

Re: Bugzilla Re-organization

[Darren Hart]

On 05/25/2012 03:38 PM, Michael Halstead wrote:
> 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.


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

Re: Bugzilla Re-organization

[Bruce Ashfield]

On 12-05-31 2:27 PM, Darren Hart wrote:
>
>
> On 05/25/2012 03:38 PM, Michael Halstead wrote:
>> 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

+1. I completely agree with this.

>
> 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

>
> 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.
>
>

Re: Bugzilla Re-organization

[Darren Hart]

On 05/31/2012 08:37 PM, Bruce Ashfield wrote:
> On 12-05-31 2:27 PM, Darren Hart wrote:
>>
>>
>> On 05/25/2012 03:38 PM, Michael Halstead wrote:
>>> 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
> 
> +1. I completely agree with this.
> 
>>
>> 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

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


> 
> ?
> 
> Bruce
> 
>>
>> 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
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Re: Bugzilla Re-organization

[Bruce Ashfield]

On 12-06-01 01:43 PM, Darren Hart wrote:
>
>
> On 05/31/2012 08:37 PM, Bruce Ashfield wrote:
>> On 12-05-31 2:27 PM, Darren Hart wrote:
>>>
>>>
>>> On 05/25/2012 03:38 PM, Michael Halstead wrote:
>>>> 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
>>
>> +1. I completely agree with this.
>>
>>>
>>> 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
>
> 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.

Agreed. This makes sense to me.

+1

Bruce

>
> --
> Darren
>
>
>>
>> ?
>>
>> Bruce
>>
>>>
>>> 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.
>>>
>>>
>>
>

Re: Bugzilla Re-organization

[Darren Hart]

On 05/31/2012 08:37 PM, Bruce Ashfield wrote:
> On 12-05-31 2:27 PM, Darren Hart wrote:
>>
>>
>> On 05/25/2012 03:38 PM, Michael Halstead wrote:
>>> 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
> 
> +1. I completely agree with this.
> 
>>
>> 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

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


> 
> ?
> 
> Bruce
> 
>>
>> 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
Intel Open Source Technology Center
Yocto Project - Linux Kernel

Re: Bugzilla Re-organization

[Tom Zanussi]

On Fri, 2012-06-01 at 10:45 -0700, Darren Hart wrote:
> 
> On 05/31/2012 08:37 PM, Bruce Ashfield wrote:
> > On 12-05-31 2:27 PM, Darren Hart wrote:
> >>
> >>
> >> On 05/25/2012 03:38 PM, Michael Halstead wrote:
> >>> 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
> > 
> > +1. I completely agree with this.
> > 
> >>
> >> 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
> 
> I think so. I like this better.
> 
> Tom, any objections?
> 

No objections, this all looks fine to me.

> 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.
> 

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.

> 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.

> 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...

> 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.

>      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.
> 

I agree. Acked-by-me...

Tom

> --
> Darren
> 
> 
> > 
> > ?
> > 
> > Bruce
> > 
> >>
> >> 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.
> >>
> >>
> > 
> 

Re: Bugzilla Re-organization

[Darren Hart]

On 06/01/2012 02:33 PM, Tom Zanussi wrote:
> On Fri, 2012-06-01 at 10:45 -0700, Darren Hart wrote:

>> 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.

kernel-recipes ?

>> 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

> 
>>      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.
>>
> 
> I agree. Acked-by-me...

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

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

Re: Bugzilla Re-organization

[Tom Zanussi]

On Fri, 2012-06-01 at 14:42 -0700, Darren Hart wrote:
> 
> On 06/01/2012 02:33 PM, Tom Zanussi wrote:
> > On Fri, 2012-06-01 at 10:45 -0700, Darren Hart wrote:
> 
> >> 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.
> 
> kernel-recipes ?
> 

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

Tom

> >> 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
> 
> > 
> >>      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.
> >>
> > 
> > I agree. Acked-by-me...
> 
> Great. Michael, the kernel-team is now in agreement.
>