All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <list@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developer Day, Friday 3rd February, Brussels
Date: Sun, 29 Jan 2012 16:46:25 +0100	[thread overview]
Message-ID: <4F2569D1.1020707@lucaceresoli.net> (raw)
In-Reply-To: <CAAXf6LW6aCs-G_FD=pXNGsBrV3133donzNxsuNV_7O=9JMCs4Q@mail.gmail.com>

Thomas De Schampheleire wrote:

> On Tue, Jan 24, 2012 at 12:08 AM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com>  wrote:
>> Hello,
>>
>> This is a reminder about the upcoming Buildroot Developer Day, which
>> wlil take place on Friday 3rd February in Brussels, just before the
>> FOSDEM conference (http://fosdem.org).
>>
>> As of today, I have received confirmations from the following
>> participants:
>>
>>   * Peter Korsgaard
>>   * Arnout Vandecapelle
>>   * Thomas De Schampheleire
>>   * Luca Ceresoli
>>   * Yann E. Morin
>>   * myself
>>
>> The meeting will take place from 9:30 to 18:00 in a location in
>> Brussels center that will be communicated to the participants. After
>> the Buildroot Developer Day, the participants are invited to continue
>> the discussions at the Beer Event organized by the FOSDEM team.
>>
>> Are there other people interested in participating to this Buildroot
>> Developer Day?
>>
>> So far, no agenda has been defined for this meeting. It would be great
>> to discuss a list of topics to be discussed at this developer day.
>>
> 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, ...)
I've just posted an RFC patchset with a draft implementation of this
feature, with the hope this can be a good starting point for the discussion
during the BDD.

Luca

      parent reply	other threads:[~2012-01-29 15:46 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
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 [this message]

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=4F2569D1.1020707@lucaceresoli.net \
    --to=list@lucaceresoli.net \
    --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 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.