From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: RFC: Joint, monthly, and online forum for developer discussion
Date: Tue, 10 Jan 2012 14:16:00 -0800 [thread overview]
Message-ID: <4F0CB8A0.9030107@linux.intel.com> (raw)
In-Reply-To: <289CD940EE567444BB43E62E0C3028F328F52A19@NA-MBX-02.mgc.mentorg.com>
Hi Sean,
On 09/01/12 17:49, 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.
I really like the intent here, a lot of people don't like IRC/mailing
lists and I'd like to enable as many people as possible to participate
in the project.
Two things worry me about a telephone/web conference:
1) Our projects have participants spread across many time-zones and it
will be difficult to accommodate more than one or two of those in any
such real-time discussion.
2) In my experience as the number of participants in a call increases
the ability for individuals to comment decreases. Generally I find calls
with more than half a dozen or so participants difficult to participate
in. I suspect I'm not alone.
Additionally, with respect to 1), I worry about how we might enable
folks unable to attend to, if not participate in the discussion, at
least be aware of what was discussed.
I'm not sure that minutes would be sufficient for more technical topics.
With that said I do think such conversations are important and would be
happy to join in. I simply want to raise my concerns early and see if
anyone has ideas which might help here.
> 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. ?
I think this is a great set of topics, and very worthy of discussion.
I'd certainly like to be involved in 2,3&4.
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-01-10 22:16 UTC|newest]
Thread overview: 5+ 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-10 22:16 ` Joshua Lock [this message]
2012-01-11 9:41 ` Jack Mitchell
2012-01-12 20:58 ` Andrei Gherzan
-- 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=4F0CB8A0.9030107@linux.intel.com \
--to=josh@linux.intel.com \
--cc=yocto@yoctoproject.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 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.