- 1 Buildroot Developers Meeting, 25-27 October 2019, Lyon
- 2 Notes of the meeting
- 3 Agenda
- 3.1 How to organise "demo" defconfigs
- 3.2 How to deal with long-term-supported packages
- 3.3 Python 2 deprecation plans
- 3.4 check-uniq-files
- 3.5 Buildroot logo / trademark
- 3.6 Next steps for security Common Platform Enumeration (CPE) manifests and automation
- 3.7 Board Meeting of the Buildroot Association
Buildroot Developers Meeting, 25-27 October 2019, Lyon
The Buildroot Developers meeting is a 3-day event for Buildroot developers and contributors. It allows Buildroot developers and contributors to discuss the hot topics in the Buildroot development, work on patches, and generally meet each other, facilitating further online discussions. Attending the event is free, after registration.
Location and date
The next Buildroot Developers meeting will take place between October 25 to October 27, right before the Embedded Linux Conference Europe 2019.
The meeting will take place in the offices of Smile, located 107 Boulevard de Stalingrad, 69100 Villeurbanne. The location is not far way from the Embedded Linux Conference Europe venue location, which will allow participants to both events to find convenient nearby accommodation.
The meeting will start each day at 9:00 AM.
- Smile is sponsoring this event, by providing the location of the 3 days of the meeting, within their offices in Lyon, France.
We are looking for sponsors for this event, for example to cover the social event for the participants of the meeting.
- Thomas Petazzoni, on all 3 days
- Titouan Christophe from Saturday 26/10
- Matt Weber, all 3 days
- Mark Corbin
- Arnout Vandecappelle from Saturday 26/10
- Yann E. MORIN, from Friday around 11am.
- Peter Korsgaard from Friday 25/10 around 16-17h
- Romain Naour
- Jeremy Rosen
- Nicolas Carrier, all 3 days
- Shyam Saini, from Friday 25/10 around 13h-14h.
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 the first day of the meeting. 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.
Notes of the meeting
The notes of the meeting are being collected at https://bimestriel.framapad.org/p/buildroot-elce-2019-meeting while the meeting is on-going.
How to organise "demo" defconfigs
We currently have almost 200 minimal board defconfigs. Intermingled with those are a few "demo" defconfigs that show additional features. Some of these are somewhat board-specific (e.g. beaglebone_qt5), but others are pretty much independent (e.g. at91sam9x5ek_dev). There is some resistance against adding additional "demo" defconfigs (e.g. for mender). Can we find a way to add "demo" configurations without exploding the configs directory?
How to deal with long-term-supported packages
Some packages (e.g. Qt) have a long-term support lifecycle that is different from ours. If we bump to the latest version, we are likely to sometimes "miss" the LTS branch in our LTS branch. Conversely, if we stick to only LTS, nobody is able to benefit from the features in the latest.
Examples of packages with this (or a similar) issue: qt5, python3, lxc
NIT: python3 is afaik NOT a good example, as each version is supported for ~5 years, so >> than our LTS: https://devguide.python.org/#status-of-python-branches
Python 2 deprecation plans
This was briefly discussed during the hackaton in August, but needs to be fleshed out a bit. Python 2 goes EOL soon. How will we approach it deprecation and eventual removal in Buildroot?
We start with a listing of the Python 2 packages currently in use, and see how we can address them (bump / adapt / drop ?)
Buildroot logo / trademark
Recently, a new logo was proposed and during the discussion the issue about trademarks was brought up. What to do?
Next steps for security Common Platform Enumeration (CPE) manifests and automation
Discuss where we're at and consider what has chanced with the completion of the summer intern's effort that added release-monitoring.org support.
Board Meeting of the Buildroot Association
- Misc topics