Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developer Day, Friday 3rd February, Brussels
Date: Wed, 25 Jan 2012 12:04:33 -0600	[thread overview]
Message-ID: <201201251204.35978.minimod@morethan.org> (raw)
In-Reply-To: <20120125135707.6ceb7e86@skate>

On Wed January 25 2012, Thomas Petazzoni wrote:
> Hello,
> 
> Le Wed, 25 Jan 2012 12:03:12 +0100,
> Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
> 
> > Some topics we could discuss:
> > 
> > - status of some things that were discussed on the previous BDD
> > -- send-patches
> > -- testing infrastructure
> > -- crosstool-ng integration
> > -- documentation migration
> > -- out-of-tree builds
> > -- website update
> > -- maintenance process / patchwork
> > -- relocatable toolchain
> > 
> > - things that may need further discussion:
> > -- license stuff (report generation, ...)
> > -- finalization of Acked-by / Signed-off-by / Reviewed-by discussion.
> > We talked about this before, but as far as I know there was no final
> > decision as to: we'll do it this way.
> > 

A suggestion which passed by on the OpenEmbedded M.L. recently that might
fit into that discussion:

On the 'Tested-by:' attribute (if used) then adding a classification of
what that testing covered or did not cover (whichever is most informative).
I.E:

Tested-by: J. Q. Public
Coverage: HP, PA-RISC only
or
Coverage-needed: World

Examples above are invented only to display the coverage attribute names.

Mike

> > - future directions for buildroot
> > -- deprecate customize package
> > -- ...
> > 
> > I'll let you know if I think of other things.
> 
> Sounds like a good start. However, I fear that on most topics, no much
> progress has been made since the Prague BDD. But this upcoming BDD will
> gather more developers, so probably we'll be able to spread the
> development effort a bit more, and it's good to make a status on items
> that were discussed in previous meetings.
> 
> Best regards,
> 
> Thomas

  reply	other threads:[~2012-01-25 18:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 23:08 [Buildroot] Buildroot Developer Day, Friday 3rd February, Brussels Thomas Petazzoni
2012-01-24  9:56 ` Thomas Petazzoni
2012-01-25 11:03 ` Thomas De Schampheleire
2012-01-25 12:57   ` Thomas Petazzoni
2012-01-25 18:04     ` Michael S. Zick [this message]
2012-01-25 18:07       ` Michael S. Zick
2012-01-27 10:33   ` Arnout Vandecappelle
2012-01-27 11:58     ` Thomas Petazzoni
2012-01-27 15:24       ` Peter Korsgaard
2012-01-27 15:27         ` Thomas Petazzoni
2012-01-27 15:32           ` Yegor Yefremov
2012-01-27 15:36             ` Thomas Petazzoni
2012-01-27 15:50               ` Yegor Yefremov
2012-01-27 15:52                 ` Thomas Petazzoni
2012-01-27 19:36                   ` Peter Korsgaard
2012-01-30  9:19     ` Thomas De Schampheleire
2012-01-30  9:42       ` Peter Korsgaard
2012-01-30 14:16         ` Thomas De Schampheleire
2012-01-30 15:09           ` Peter Korsgaard
2012-01-30 11:26       ` Thomas Petazzoni
2012-01-29 15:46   ` Luca Ceresoli

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=201201251204.35978.minimod@morethan.org \
    --to=minimod@morethan.org \
    --cc=buildroot@busybox.net \
    /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