Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: openembedded-core@lists.openembedded.org
Subject: Re: RFC: Joint, monthly, and online forum for developer discussion
Date: Thu, 12 Jan 2012 22:58:09 +0200	[thread overview]
Message-ID: <4F0F4961.2060702@gherzan.ro> (raw)
In-Reply-To: <289CD940EE567444BB43E62E0C3028F328F52A19@NA-MBX-02.mgc.mentorg.com>

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

On 01/10/2012 03:49 AM, Hudson, Sean wrote:
> I propose having a monthly, online developer forum that promotes 
> discussion on longer term technical issues that impact both Yocto and 
> OpenEmbedded.  This would supplement the already existing mailing list 
> and irc communication channels.  In order to facilitate this, I'd like 
> to propose a telephone/web conference, which my employer has agreed to 
> host.
> This forum would help provide an additional way for the community to 
> discuss technical issues and share information about planned work and 
> works in progress.
> Initial Topics for Discussion might include:
>
>  1. layering definitions -- discussion on what exists today and how to
>     make it better
>  2. discussions on techniques to make working with oe/yocto better
>  3. oe/yocto disconnects (opportunities for better alignment)
>  4. common new user issues
>  5. documentation (standards, lacks, etc)
>  6. ?
>
> Regards,
>      Sean
> Sean Hudson | Embedded Linux Architect for Mentor Embedded Linux
> Mentor Graphics -- Embedded Software Division^(TM)
>
This was something i i wanted to propose as well. It would be a easier 
way of communication.

@g

[-- Attachment #2: Type: text/html, Size: 2619 bytes --]

  reply	other threads:[~2012-01-12 21:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10  1:49 RFC: Joint, monthly, and online forum for developer discussion Hudson, Sean
2012-01-12 20:58 ` Andrei Gherzan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-01-10 17:24 Hudson, Sean

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=4F0F4961.2060702@gherzan.ro \
    --to=andrei@gherzan.ro \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox