From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 4BEFFE008D6 for ; Tue, 11 Mar 2014 05:35:52 -0700 (PDT) Received: by mail-ie0-f174.google.com with SMTP id rp18so8747736iec.19 for ; Tue, 11 Mar 2014 05:35:50 -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 :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=TK6gbmgdCYHwlj6oNjclhPQXkYyfxn1m82AdmZK15qQ=; b=arCZnRM8PY+AYi7k/I6ej525NA9Fa8zsTJcPNbiG+VndpLKCVyc4yPRIhC1FhZqHXe pN/mr+hg7sbKfdhHhHgezIdSeoStWKTuireqDVSU0P80aiu8ZBv7WIYKanI8W8/A51j/ kt+lyp4L97OFWP/iVZxFJgVHSdMX317oAsuU6MUcYnoh3OPbLbGSX2mTfqU8oJVZ4vM7 x1t/v2MtZV+NHkky2UuHlDA5nmGRVv/FgK96UbDLaiYim9hSATUF5+LmnWhcLuOD89zZ lTmEdomqPQLMnXAKt9awz3YtehieaYpnFoomoUPlVL7LJCuP2m8XtR/fcusRM35pcvG+ aSvg== X-Gm-Message-State: ALoCoQkWMIH9rpeh0+YO4/k8JX7G5uIw4UTtqML3Nl2xMQrMRHYZ9mcFylOu991+baHytZsAtguZ X-Received: by 10.42.119.134 with SMTP id b6mr32168638icr.31.1394541350842; Tue, 11 Mar 2014 05:35:50 -0700 (PDT) Received: from [192.168.141.83] (69-165-220-158.dsl.teksavvy.com. [69.165.220.158]) by mx.google.com with ESMTPSA id ji9sm48401288igb.1.2014.03.11.05.35.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Mar 2014 05:35:50 -0700 (PDT) Message-ID: <531F0325.5030609@linaro.org> Date: Tue, 11 Mar 2014 08:35:49 -0400 From: Trevor Woerner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: "Daiane.Angolini@freescale.com" , "meta-freescale@yoctoproject.org" References: In-Reply-To: Subject: Re: maintainer for imx53qsb 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: Tue, 11 Mar 2014 12:35:58 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, Are there any published maintainer procedures/responsibilities? I realize it might be best to not be too stringent on these requirements, but on the other hand it seems as though maintainers are free to define whatever they feel is enough, which might be "nothing" ;-) More seriously, a maintainer could decide booting core-image-minimal and seeing a login prompt is enough. This would be setting the bar quite low. Maybe for each board a matrix could be maintained whereby the maintainer is free to do as few or as many things from the list of potential items? At the very least, we'd have a better definition of what "maintained" would mean for each board. Even better: if instructions were available describing how to build and test each line item, then everyone could benefit! Best regards, Trevor