Buildroot:DeveloperDaysELCE2015

Location and date
The Buildroot community is organizing a meeting on October 3rd and 4th 2015, for Buildroot developers and contributors. This meeting will be a mixture of discussion and hacking session around the Buildroot project. This meeting takes place right before the Embedded Linux Conference Europe, in order to make it easy for participants to attend both events. It is not mandatory to attend both days.

The meeting will take place in the Orange Business Services offices, located:

Garryard House Earlsfort Terrace Dublin 2

Sponsors
We are currently looking for companies willing to sponsor the event. The sponsoring will be used to pay for the Saturday dinner for the participants or Buildroot T-shirts for the participants. Contributions in the range of 250 EUR to 500 EUR are sufficient.

Participants

 * 1) Thomas Petazzoni
 * 2) Yann E. MORIN
 * 3) Arnout Vandecappelle Arriving Oct 2 21:50, staying at My Place, 89 - 90 Lower Gardiner St, leaving Oct 8 6:40
 * 4) Luca Ceresoli
 * 5) Samuel Martin
 * 6) Maxime Hadjinlian
 * 7) Peter Korsgaard
 * 8) Romain Naour

Who can attend ?
This meeting is opened to all Buildroot users and developers. The event is free. However, we make it clear that it is not a training event about Buildroot aimed at newcomers. It is a meeting for Buildroot developers to make progress about various topics in Buildroot. It is recommended to already be a Buildroot contributor to participate to the event.

For administrative reasons, participants will have to register to the event before Friday, Sep. 25th, so that access badges are printed. For this reason, people that are not registered will not be granted access to the site. Please, register by adding your name to the list, above.

Agenda

 * Google Summer of Code
 * Guidelines for defconfigs (e.g. FPU selection), demo defconfigs, and kernel configs [Arnout]
 * Packages without directly-accessible archives (e.g. wf111, Qt5 proprietary addons...) [Yann, Thomas, Peter, Arnout]
 * Multi-br2-external trees [Yann]
 * Hash files for all packages: should we have an empty/useless .hash files for github fetched packages? [Thomas]
 * Run-time testing
 * Dealing with bugs for which patches exist [Arnout]
 * It has happened a couple of times recently that a bug/problem was reported, a fix was posted, but the fix was not quite good enough and never got applied. Can we do better?
 * Reducing the mailing list traffic (reprise, because there have again been complaints about it)[Arnout]. Some statistics (not 100% accurate) taken from Arnout's mailbox over roughly the last 10 months:
 * 27632 mails (= almost 650 per month)
 * 23% commit mails
 * 100 (< 1%) replies to commit mails
 * 29% patches (mails with [Buildroot] [PATCH in the subject)
 * 34% replies to patches
 * which leaves 12% other mails