From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2/next 2/4] DEVELOPERS: add initial list of Buildroot developers
Date: Tue, 23 Aug 2016 22:30:42 +0200 [thread overview]
Message-ID: <20160823223042.775ce73e@free-electrons.com> (raw)
In-Reply-To: <fb83b7f7-40e5-62ab-5d9e-ea04cd8d8df6@gmail.com>
Hello,
On Tue, 23 Aug 2016 21:51:44 +0200, Romain Naour wrote:
> > +N: Julien Boibessot <julien.boibessot@armadeus.com>
> > +F: configs/armadeus*
> > +F: package/libcddb/
>
> I guess Julien want to take care of opentyrian :)
Added.
> > +N: Nicolas Menegale <nicolas.menegale@openwide.fr>
> > +F: package/cppcms/
> > +F: package/glibmm/
> > +F: package/libxmlpp/
>
> Nicolas no longer works for Open Wide, so these packages are orphan I guess.
> Also, I'm not sure he still on the mailing list.
OK. I've moved glibmm to James Knight, since he is already taking care
of the other *mm packages (cairomm, libgtk3mm, etc.), so it makes sense
to have him look at glibmm as well.
> > +N: Romain Naour <romain.naour@openwide.fr>
>
> Please update my address with romain.naour at gmail.com
Done.
> Here are some missing packages:
> +F: package/elementary/
> +F: package/expedite/
> +F: package/xenomai/
Added.
> > +N: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> [snip]
> > +F: package/enlightenment/
> > +F: package/libevas-generic-loaders/
>
> Thomas, I'd like to take these two packages on my list ;-)
I've moved them to you. Note that as I said to Carlos, things are not
mutually exclusive: several developers can list the same packages. This
is note a file listing ownership of packages, but interest in packages.
> Also some packages are not listed yet, like busybox.
> I could be interesting to list all orphan packages.
Run:
./support/scripts/get-developer -c
It looks at all files under version control, and lists the ones that
are not associated to any developer. With all the latest updates, there
are still 2945 files that are not referenced by anyone. But I'm not
trying to make it 0 before putting this mechanism in place, it's going
to be a gradual effort, like it has been for hashes, license
information, etc.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-23 20:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 12:47 [Buildroot] [PATCHv2/next 0/4] DEVELOPERS file and get-developer tool Thomas Petazzoni
2016-08-23 12:47 ` [Buildroot] [PATCHv2/next 1/4] support/scripts/get-developers: add new script Thomas Petazzoni
2016-08-23 12:47 ` [Buildroot] [PATCHv2/next 2/4] DEVELOPERS: add initial list of Buildroot developers Thomas Petazzoni
2016-08-23 14:26 ` Gary Bisson
2016-08-23 20:15 ` Thomas Petazzoni
2016-08-23 17:38 ` Bernd Kuhls
2016-08-23 20:16 ` Thomas Petazzoni
2016-08-23 19:50 ` Carlos Santos
2016-08-23 20:25 ` Thomas Petazzoni
2016-08-23 19:51 ` Romain Naour
2016-08-23 20:30 ` Thomas Petazzoni [this message]
2016-08-23 21:01 ` Peter Korsgaard
2016-08-23 21:40 ` Thomas Petazzoni
2016-08-23 21:54 ` Peter Korsgaard
2016-08-23 21:59 ` Thomas Petazzoni
2016-08-24 0:17 ` Arnout Vandecappelle
2016-08-24 9:58 ` Peter Korsgaard
2016-08-24 14:04 ` Thomas Petazzoni
2016-08-24 14:04 ` Thomas Petazzoni
2016-08-24 6:38 ` Rahul Bedarkar
2016-08-24 14:06 ` Thomas Petazzoni
2016-08-24 13:35 ` Alistair Francis
2016-08-24 14:09 ` Thomas Petazzoni
2016-08-24 20:26 ` Alistair Francis
2016-08-29 10:19 ` Julien Boibessot
2016-08-29 11:22 ` Thomas Petazzoni
2016-08-23 12:47 ` [Buildroot] [PATCHv2/next 3/4] docs/manual: update contribute.txt to cover get-developers Thomas Petazzoni
2016-08-23 12:47 ` [Buildroot] [PATCHv2/next 4/4] docs/manual: add new section about the DEVELOPERS file and get-developer Thomas Petazzoni
2016-08-24 0:21 ` Arnout Vandecappelle
2016-08-24 14:22 ` Thomas Petazzoni
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=20160823223042.775ce73e@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