From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 52306E00AC5 for ; Mon, 24 Mar 2014 08:58:53 -0700 (PDT) Received: by mail-pd0-f170.google.com with SMTP id v10so5564554pde.1 for ; Mon, 24 Mar 2014 08:58:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=HQTK3nmNtW/qGgOtZnMRJzF88m3PHN9wdz8gsYCKFK8=; b=iAXTSDeTfm4qxTrZsLbT98DeNbq2szelfCXbvQee5208Z6APrk0RArvqgsQD/1EApu pVpGQCtlOB/rEC4A6uGkpp5I0Dmn36XcWhFtifIMiaP574pE7phMoyTebJD7ZrpEf4DE 35G/A/2SgbsVNG0tDhFwurGFZLvM5M0A0Khpo9Bsb6scQxpI7cTKPs8+QL1zZeaiExwG i+bHS2bS1/+hBafw8m4iF2aRuxZolrdeVCg+T28clxZShNjR59Ta50EOv63cTK8SDyQp suNgsjp7DUpJEwf16EobDZ63psAJbt1rFEMrK0GXyD5vV9Sy8E+Lppm/Dceq1X+w/dax Mgug== X-Gm-Message-State: ALoCoQkWmH+t+34kHTW5EUq+1xqg4vKT0QyQrKP00h3Vtg30YBBBHm6D/TCEqiquCDKxU9MVUiBk X-Received: by 10.66.5.135 with SMTP id s7mr4007898pas.154.1395676733257; Mon, 24 Mar 2014 08:58:53 -0700 (PDT) Received: from [192.168.0.53] ([63.226.49.26]) by mx.google.com with ESMTPSA id ps1sm61639674pac.26.2014.03.24.08.58.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Mar 2014 08:58:52 -0700 (PDT) Message-ID: <5330563A.9070404@boundarydevices.com> Date: Mon, 24 Mar 2014 08:58:50 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Otavio Salvador , "Daiane.Angolini@freescale.com" References: <1395261322-14905-1-git-send-email-eric.nelson@boundarydevices.com> <73259f17c01648dbb65e768113c90f58@BY2PR03MB379.namprd03.prod.outlook.com> In-Reply-To: Cc: "meta-freescale@yoctoproject.org" Subject: Re: Call for maintainers (was [RFC PATCH] fsl-commity-bsp: Add meta-qt5) X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Mar 2014 15:58:59 -0000 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Otavio, Since we have diverged off the topic again, I changed the subject line to invite more folks to chime in. On 03/24/2014 07:26 AM, Otavio Salvador wrote: > On Mon, Mar 24, 2014 at 10:08 AM, Daiane.Angolini@freescale.com > wrote: >>> I am not sure we ought to include it or not. I see valid points for both >>> and I will focus my answer in the cons: >>> >>> * Documentation: our Release Notes, User Guide and FAQ are still >>> uncomplete. Add new stuff will only make it worse as those will also need >>> to be documented. >>> >>> * Tests: We see limited tests using the images we have and people does not >>> provide much feedback when we open the test form. More things will only >>> complicate it more. >> >> Until here I understand. And I agree. >> >>> * Size: more metadata means more updates and maintenance. We need more >>> people helping the metadata maintenance before extend it. >> >> We already have almost 100% of the boards with maintainers. What do you mean, when you >> say we need more maintenance before extend the metadata? >> >> I still don´t have a clear idea if I like or dislike the idea of downloading more meta layers by default. >> >> I´m still deciding ;) > > We need to split the maintainership areas: > > * boards: Yes, most of board has someone committed nowadays and this > is awesome. This help us to get tests and feedback from those boards > and more people to help to address board specific things. However this > does not address the rest of meta-fsl-arm ... > > * core BSP support: here we have some people working. You and me has > been doing most of work until now and Lauren has been started to > contribute more to this since Freescale started to work in the > 3.10.17-1.0.0 BSP. Here we need a lot of help and it does affect > /every/ board we use/add/maintain ... > These are areas where both carrots and sticks might help. It seems very reasonable to ask each board maintainer to update and test against some set of target images within a certain time period. > * technology specific support: here is where we are beginning. This > involves a lot of commitment and time. Here is where Qt5 and Chromium > are going to be covered. Currently we have no one really committed to > either and we cannot supply something in FSL Community BSP which is > not /maintained/ and for maintained I mean someone watching it and > doing the rework/improvements/commitments need for it to keep working > when Qt5 5.3 or Chromium 40 is released. > I think you're under-stating the issue here, since there are many more bits than just Qt5 and Chromium. Just off the top of my head: - Is anybody testing DirectFB on a regular basis? (seems a question on the ML today), - Up until the recent addition of , there weren't any easy-buttons for testing the gstreamer plugins in a non-X environment, and - There's Wayland activity, but AFAIK, no image available to take advantage of it. > So it is a extensive topic; I hope it is clear now why I see we need > more people involved to grow. > I feel like I've thrown a couple of bricks in the last week (Chromium and Qt5), but I hope they can be constructive. I do think that the questions you raise are worthy of a separate set of discussions (or at least a separate e-mail chain). Since there are a lot of different, interested parties with different agendas, I wonder whether a different (more interactive) forum might be a better match. Conference call? Google Hangout meeting? I'm sure it's too late to schedule anything at FTF, but perhaps not. I'm also sure that there will be those interested in the topic who won't be attending. Regards, Eric