From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC agenda items for the next meeting
Date: Sun, 13 Feb 2011 16:38:08 -0500 [thread overview]
Message-ID: <4D584F40.80009@balister.org> (raw)
In-Reply-To: <ij8d1t$cd9$1@dough.gmane.org>
On 02/13/2011 05:50 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> The new TSC is holding a meeting next week and we wanted to see if
> anyone wants to suggest items we put in the agenda for the meeting.
>
> If you have such items, please let us know by replying to this mail.
I'd like to see definitive guidelines for creating board support
packages. This should address:
1) Where to define toolchains and versions.
2) How to create kernel bb files. (Per board, or per kernel version)
3) Same for u-boot, how to pin u-boot versions for BSP's.
Basically, we should identify all the BSP's issues that create
discussions on the list and work out a best practices document so we can
have more consistency.
A similar set of guidelines defining what a a distro's responsibility
would also be good.
Philip
next prev parent reply other threads:[~2011-02-13 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 10:50 TSC agenda items for the next meeting Koen Kooi
2011-02-13 21:38 ` Philip Balister [this message]
2011-02-13 22:36 ` Graeme Gregory
2011-02-14 8:08 ` Frans Meulenbroeks
2011-02-14 6:58 ` Frans Meulenbroeks
2011-02-14 9:16 ` Yury Bushmelev
2011-02-14 9:48 ` Stefan Schmidt
2011-02-14 10:55 ` Graeme Gregory
2011-02-14 13:33 ` Frans Meulenbroeks
2011-02-14 14:18 ` Stefan Schmidt
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=4D584F40.80009@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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 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.