From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f171.google.com (mail-vc0-f171.google.com [209.85.220.171]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9E21CE0073C for ; Tue, 25 Mar 2014 09:26:28 -0700 (PDT) Received: by mail-vc0-f171.google.com with SMTP id lg15so868604vcb.16 for ; Tue, 25 Mar 2014 09:26:27 -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=feD/AjPnsbjY8FN7SvCQxOKo1NVfZyjksPl/7c5Hyp0=; b=Xb6yNOWCUVaucd/vQoV8LVeYbybSZQDnQMmTOBHBKYKpfAM4pcolbUgkXJCecCV6K+ l3o7+CXdkdknhFkdJ38th0wfPJRB7Ccw1RXKK0nY5htA8EMCMfdfMB8YkW+n0ADNdYiK +57HYgfTbPSrTr4lAREqOWE9KMdpcoGLkVhOO/mBy+2exLoRdagZQ+1VvnMwP7sGGMjP gA1izVGqKVysoMg4ciwi/8nHJdqUPM4N7137EC1rjVhKVuU1gi6U7Is9YUihp0KZP18w lvo1l0D+glKU4sCz78YKSg5SahM8l7q9wBhKTsfnGeY3usKtYKTF6zU2V8tdROItMFud qWcg== X-Gm-Message-State: ALoCoQnZJdaIGhAHwm9i2k6oeLRuMpU4sEWt0ir6Ql6eEtfvtYZFazNqxZ0DkixzFPKJ7c2ktPnG X-Received: by 10.58.66.195 with SMTP id h3mr45293vet.57.1395764787640; Tue, 25 Mar 2014 09:26:27 -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 bk6sm19583183vec.6.2014.03.25.09.26.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Mar 2014 09:26:26 -0700 (PDT) Message-ID: <5331AE31.40202@linaro.org> Date: Tue, 25 Mar 2014 12:26:25 -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: "meta-freescale@yoctoproject.org" References: <1395261322-14905-1-git-send-email-eric.nelson@boundarydevices.com> <73259f17c01648dbb65e768113c90f58@BY2PR03MB379.namprd03.prod.outlook.com> <5330563A.9070404@boundarydevices.com> <5330F04E.1020904@linaro.org> In-Reply-To: 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: Tue, 25 Mar 2014 16:26:28 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit On 03/25/14 08:35, Daiane.Angolini@freescale.com wrote: > Before defining any period. I prefer we define the "agenda for next meeting" > > We can build the agenda and when itīs big enough, we set the "next meeting". I think these meetings would be a good opportunity for maintainers to get together and discuss any issues they're facing leading into the next release. Maybe these meetings could provide an opportunity to update status information with respect to testing efforts in order to keep all the board testing moving forward as we come into the next release? I'm not implying these meetings should only be for maintainers, I'm just pointing them out as one example of a group who might benefit from such a meeting. As such an agenda item could be: - short testing status from maintainers/testers