From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 042F1E00747; Fri, 1 Jun 2012 13:03:55 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail1.windriver.com (8.14.3/8.14.3) with ESMTP id q51K3shU026284 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 1 Jun 2012 13:03:54 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Fri, 1 Jun 2012 13:03:54 -0700 Message-ID: <4FC92022.4080402@windriver.com> Date: Fri, 1 Jun 2012 16:03:46 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Darren Hart References: <4FC009CD.9030201@yoctoproject.org> <4FC7B80E.1020802@linux.intel.com> <4FC83910.9050302@windriver.com> <4FC8FF2E.3060701@linux.intel.com> In-Reply-To: <4FC8FF2E.3060701@linux.intel.com> Cc: Yocto Project Discussion , yocto-infrastructure@yoctoproject.org Subject: Re: Bugzilla Re-organization X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jun 2012 20:03:56 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit 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. >>> >>> >> >