From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Topics to discuss at the meeting
Date: Wed, 8 Oct 2014 10:56:53 +0200 [thread overview]
Message-ID: <20141008105653.7252facd@free-electrons.com> (raw)
Hello,
The meeting is approaching, so to foster some preliminary discussion,
here is the current list of topics we have in the Wiki:
- Look-back to action points from previous developer days at Fosdem
2014: is everything that was decided done? What remains?
- Patch naming: current convention is
package-number-description.patch, but a proposal was made on the
list to simplify this to number-description.patch. Go or no-go?
- Since Luca will be present: state of legal-info infrastructure,
improvements to be made?
- Could more details be added here (by Thomas DS, who proposed the
topic)
- Discussion on atomic operations and how to handle the related
dependencies at the kconfig level
- Cleanup the patchwork; triage patches in two categories:
- things that hasn't been pushed enough but that we believe is useful
- things that haven't been pushed enough and that are too anecdotic
for us to care about
- Pending large series:
- The paranoid wrapper series from Thomas P.
- The march/mcpu conflict on ARM series from Thomas P.
- The Qemu series from Yann
- The freerdp series from Yann
- The NVidia series from Yann
- The OpenCV series from Samuel
- The apr-util/apache series from Bernd
- The gendoc series from Yann (IMPORTANT)
- The X.org/i.MX6 series from J?r?me
- The libudev series from Yann (IMPORTANT)
- Key-signing party: it would be usefull to have a web-of-trust
amongst Buildroot developpers, to submit sensitive information, such
as the hashes.
- Project maintenance:
- Peter seems to be less active now
- Thomas (who acts as deputy committer) has new responsibilities,
and risks being less available too
- How do we see the short- and long-term maintenance of the project?
- Should we move buildroot.org to its own server, and split from
busybox.net and uclibc.org?
Feel free to comment on these topics, or add new ones. For those who
have an account, do not hesitate to update the Wiki accordingly.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2014-10-08 8:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 8:56 Thomas Petazzoni [this message]
2014-10-08 9:10 ` [Buildroot] Topics to discuss at the meeting Yegor Yefremov
2014-10-08 16:13 ` Thomas Petazzoni
2014-10-10 7:41 ` Yegor Yefremov
2014-10-10 8:07 ` Thomas Petazzoni
2014-10-08 11:56 ` Thomas De Schampheleire
2014-10-08 16:12 ` Thomas Petazzoni
2014-10-10 9:50 ` Thomas De Schampheleire
2014-10-10 10:18 ` Thomas Petazzoni
2014-10-12 8:13 ` Luca Ceresoli
2014-10-12 14:41 ` Matthew Weber
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=20141008105653.7252facd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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