From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
"Daiane.Angolini@freescale.com" <Daiane.Angolini@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Call for maintainers (was [RFC PATCH] fsl-commity-bsp: Add meta-qt5)
Date: Tue, 25 Mar 2014 07:12:45 -0700 [thread overview]
Message-ID: <53318EDD.1020605@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKretK0SKadvGdXJxT+0LpdvK-ne3ufiNaZEVb07_ORCKw@mail.gmail.com>
On 03/25/2014 06:24 AM, Otavio Salvador wrote:
> Hello Daiane,
>
> On Tue, Mar 25, 2014 at 9:35 AM, Daiane.Angolini@freescale.com
> <Daiane.Angolini@freescale.com> wrote:
>>> On 03/24/14 12:55, Otavio Salvador wrote:
>>>> Yes; I think a Google Hangout would fit perfectly fine here. Some
>>>> people has suggested it privately in past but our community was still
>>>> too small for it to make sense. I think we are big enough for it to be
>>>> worth it and I am supportive to the idea. What others think?
>>>
>>> I would be in favour of having a google hang-out, or a meeting on IRC.
>>> Perhaps even on a quasi-regular basis?
>>
>> 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".
>
> Ok.
>
> I have started a Google Driver document[1] which can be commented by
> anyone. I have added you (Daiane) as editor as well.
>
> 1. http://bit.ly/OVtbmd
>
> So let's start work in a draft and then we can keep adding and
> reworking it until we get it 'good enough'.
>
Thanks Otavio.
next prev parent reply other threads:[~2014-03-25 14:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 20:35 [RFC PATCH] fsl-commity-bsp: Add meta-qt5 Eric Nelson
2014-03-21 20:37 ` Otavio Salvador
2014-03-24 13:08 ` Daiane.Angolini
2014-03-24 14:26 ` Otavio Salvador
2014-03-24 15:58 ` Call for maintainers (was [RFC PATCH] fsl-commity-bsp: Add meta-qt5) Eric Nelson
2014-03-24 16:55 ` Otavio Salvador
2014-03-24 16:57 ` Daiane.Angolini
2014-03-24 20:45 ` Eric Nelson
2014-03-25 2:56 ` Trevor Woerner
2014-03-25 11:55 ` Otavio Salvador
2014-03-25 13:59 ` Eric Nelson
2014-03-25 16:17 ` Trevor Woerner
2014-03-26 14:50 ` Tony Felice
2014-03-25 12:35 ` Daiane.Angolini
2014-03-25 13:24 ` Otavio Salvador
2014-03-25 14:12 ` Eric Nelson [this message]
2014-03-25 16:26 ` Trevor Woerner
2014-03-25 16:32 ` Otavio Salvador
2014-03-24 15:42 ` [RFC PATCH] fsl-commity-bsp: Add meta-qt5 Eric Nelson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53318EDD.1020605@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=Daiane.Angolini@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.