DEVELOPERS file and get-developer tool
cover DEVELOPERS file and get-developer tool
Hello,
This is the second iteration of this patch series.
Changes since v1
================
- Took into account comments received on the DEVELOPERS file, specifically:
* Baruch isn't taking care of wireshark, Gustavo is.
* Bernd isn't taking care of pjsip, Luca is.
* Luca is not taking care of ffmpeg and linphone.
* Added Chris Packham as the micropython-lib and syslog-ng developer, upon his request.
- Thanks to the comment from Chris Packham, found many more Git commits adding packages, and used that to further extend the DEVELOPERS final with a bunch of additional entries. This reduces the number of unassigned files from 3458 to 3016 (on a total of 8543). Of course, many packages have been added a long time ago, and their original submitter is no longer active. This is something we will adjust progressively, as we determine which developers are active on a given package.
- Improved the getdeveloperlib.py library to check if the patterns in the "F:" entries of the DEVELOPERS file actually match existing files/directories.
Also, today's autobuilder e-mail to the mailing list has been sent using the new Python script
(https://git.buildroot.org/buildroot-test/tree/utils/daily-mail), and individual developers have received notifications about build failures related to their architectures and packages.
Original introduction for the patch series
==========================================
This patch series implements something that has already been discussed several times during Buildroot meeting and that will hopefully help maintaining Buildroot.
It adds a DEVELOPERS text file that associates developers (and their e-mail address) with the list of files they look after in Buildroot. On top of this, a "get-developer" tool allows to:
- Get the proper list of recipients for "git send-email" when sending patches. This will make sure that developers looking after a given area in Buildroot (be it a package, package infra, documentation, defconfig, etc.) will receive the patches touching this area.
- Notify developers when there are build failures on architectures they take care of (this was already the case today) but also packages they take care of (it wasn't possible without this mechanism)
The first patch adds the get-developer tool itself and its companion Python library. We have a separate library because it is used by the autobuilder infrastructure (rather than calling the command line tool repeatedly).
The second patch adds an initial DEVELOPERS file. Of course, the aim is to progressively improve this file so that it covers as many areas of Buildroot as possible.
The last two patches update the Buildroot manual.
Let me know what you think, both in the general principles, but also the implementation details (I'm sure my Python is not very good, so comments and suggestions welcome).
It is worth mentioning that I have already adapted the autobuilder infrastructure to use this mechanism, and if everything works well:
- Tomorrow's daily autobuilder report on the list will be generated by the new Python script (no visible difference)
- All developers taking care of an architecture or a package causing a build failure will be individually notified.
Thanks,
Thomas
Thomas Petazzoni (4):
support/scripts/get-developers: add new script
DEVELOPERS: add initial list of Buildroot developers docs/manual: update contribute.txt to cover get-developers docs/manual: add new section about the DEVELOPERS file and
get-developer
DEVELOPERS | 1542 ++++++++++++++++++++++++++++++++++++ docs/manual/contribute.txt | 12 +- docs/manual/developers.txt | 45 ++ docs/manual/manual.txt | 2 + support/scripts/get-developers | 83 ++ support/scripts/getdeveloperlib.py | 201 +++++ 6 files changed, 1883 insertions(+), 2 deletions(-) create mode 100644 DEVELOPERS create mode 100644 docs/manual/developers.txt create mode 100755 support/scripts/get-developers create mode 100644 support/scripts/getdeveloperlib.py
Signature · 1 line
2.7.4
PATCH 1/4 support/scripts/get-developers: add new script
This script, and its companion library, is more-or-less Buildroot's equivalent to the kernel get_maintainer.pl script: it allows to get the list of developers to whom a set of patches should be sent to.
To do so, it first relies on a text file, named DEVELOPERS, at the root of the Buildroot source tree (added in a followup commit) to list the developers and the files they are interested in. The DEVELOPERS file's format is simple:
N: Firstname Lastname <email> F: path/to/file F: path/to/another/file
This allows to associate developers with the files they are looking after, be they related to a package, a defconfig, a filesystem image, a package infrastructure, the documentation, or anything else.
When a directory is given, the tool assumes that the developer handles all files and subdirectories in this directory. For example "package/qt5/" can be used for the developers looking after all the Qt5 packages.
Conventional shell patterns can be used, so "package/python-*" can be used for the developers who want to look after all packages matching "python-*".
A few files are recognized specially:
- .mk files are parsed, and if they contain $(eval $(<something>-package)), the developer is assumed to be looking after the corresponding package. This way, autobuilder failures for this package can be reported directly to this developer.
- arch/Config.in.<arch> files are recognized as "the developer is looking after the <arch> architecture". In this case, get-developer parses the arch/Config.in.<arch> to get the list of possible BR2_ARCH values. This way, autobuilder failures for this package can be reported directly to this developer.
- pkg/pkg-<infra>.mk are recognized as "the developer is looking after the <infra> package infrastructure. In this case, any patch that adds or touches a .mk file that uses this infrastructure will be sent to this developer.
Examples of usage:
$ ./support/scripts/get-developers 0001-ffmpeg-fix-bfin-build.patch git send-email--to buildroot at buildroot.org --to "Luca Ceresoli <[email protected]>" --to "Bernd Kuhls <[email protected]>"
$ ./support/scripts/get-developers -p imx-lib Arnout Vandecappelle <[email protected]> Gary Bisson <[email protected]>
$ ./support/scripts/get-developers -a bfin Waldemar Brodkorb <[email protected]>
--- support/scripts/get-developers | 83 +++++++++++++++ support/scripts/getdeveloperlib.py | 201 +++++++++++++++++++++++++++++++++++++ 2 files changed, 284 insertions(+) create mode 100755 support/scripts/get-developers create mode 100644 support/scripts/getdeveloperlib.py
support/scripts/get-developers new file +83 -0
@@ -0,0 +1,83 @@ +#!/usr/bin/env python + +import argparse +import getdeveloperlib + +def parse_args(): + parser = argparse.ArgumentParser() + parser.add_argument('patches', metavar='P', type=str, nargs='*', + help='list of patches') + parser.add_argument('-a', dest='architecture', action='store', + help='find developers in charge of this architecture') + parser.add_argument('-p', dest='package', action='store', + help='find developers in charge of this package') + parser.add_argument('-c', dest='check', action='store_const', + const=True, help='list files not handled by any developer') + return parser.parse_args() + +def __main__(): + devs = getdeveloperlib.parse_developers() + if devs is None: + sys.exit(1) + args = parse_args() + + # Check that only one action is given + action = 0 + if args.architecture is not None: + action += 1 + if args.package is not None: + action += 1 + if args.check: + action += 1 + if len(args.patches) != 0: + action += 1 + if action > 1: + print("Cannot do more than one action") + return + if action == 0: + print("No action specified") + return + + # Handle the check action + if args.check: + files = getdeveloperlib.check_developers(devs) + for f in files: + print f + + # Handle the architecture action + if args.architecture is not None: + for dev in devs: + if args.architecture in dev.architectures: + print(dev.name) + return + + # Handle the package action + if args.package is not None: + for dev in devs: + if args.package in dev.packages: + print(dev.name) + return + + # Handle the patches action + if len(args.patches) != 0: + (files, infras) = getdeveloperlib.analyze_patches(args.patches) + matching_devs = set() + for dev in devs: + # See if we have developers matching by package name + for f in files: + if dev.hasfile(f): + matching_devs.add(dev.name) + # See if we have developers matching by package infra + for i in infras: + if i in dev.infras: + matching_devs.add(dev.name) + + result = "--to buildroot at buildroot.org" + for dev in matching_devs: + result += " --to \"%s\"" % dev + + if result != "": + print("git send-email %s" % result) + +__main__() +
support/scripts/getdeveloperlib.py new file +201 -0
201 lines not on this page · raw message
Signature · 1 line
2.7.4
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Thomas PetazzoniThis is an initial list of Buildroot developers. It has been created semi-automatically by parsing the Git history, and finding the authors of commits with a title like "<foo>: new package". Some additional manual tweaking has been done (merging multiple entries corresponding to the same person, adding some more entries, etc.).
--- DEVELOPERS | 1542 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1542 insertions(+) create mode 100644 DEVELOPERS
DEVELOPERS new file +1542 -0
@@ -0,0 +1,1542 @@ +# Syntax: +# +# N: Firstname Lastname <email> +# F: file pattern or directory +# F: file pattern or directory +# +# The "F" entries can be: +# +# - A directory, in which case all patches touching any file in this +# directory or its subdirectories will be CC'ed to the developer. +# - A pattern, in which case the pattern will be expanded, and then +# all files/directories (and their subdirectories) will be +# considered when matching against a patch +# +# Notes: +# +# - When a developer adds an "arch/Config.in.<arch>" file to its list +# of files, he is considered a developer of this architecture. He +# will receive e-mail notifications about build failures occuring on +# this architecture. Not more than one e-mail per day is sent. +# - When a developer adds a directory that contains one or several +# packages, this developer will be notified when build failures +# occur. Not more than one e-mail per day is sent. +# - When a developer adds an "package/pkg-<infra>.mk" file to its list +# of files, he is considered interested by this package +# infrastructure, and will be CC'ed on all patches that add or +# modify packages that use this infrastructure. + +N: Abhishek Singh <[email protected]> +F: package/cxxtest/ + +N: Adam Duskett <[email protected]> +F: package/nginx-naxsi/ + +N: Alex Suykov <[email protected]> +F: package/vboot-utils/ + +N: Alexander Clouter <[email protected]> +F: package/odhcp6c/ + +N: Alexander Dahl <[email protected]> +F: package/fastd/ +F: package/libuecc/ +F: package/putty/ + +N: Alexander Lukichev <[email protected]> +F: package/openpgm/ + +N: Alexander Varnin <[email protected]> +F: package/liblog4c-localtime/ + +N: Alexandre Belloni <[email protected]> +F: package/tz/ + +N: Alistair Francis <[email protected]> +F: package/xen/ + +N: Alvaro G. M <[email protected]> +F: package/dcron/ +F: package/libxmlrpc/ +F: package/python-docopt/ + +N: Anders Darander <[email protected]> +F: package/ktap/ + +N: Andr? Hentschel <[email protected]> +F: package/openal/ +F: package/p7zip/ +F: package/wine/ + +N: Andrew Ruder <[email protected]> +F: package/expect/ + +N: Andy Kennedy <[email protected]> +F: package/libunwind/ + +N: Angelo Compagnucci <[email protected]> +F: package/mono/ +F: package/mono-gtksharp3/ +F: package/monolite/ +F: package/python-can/ +F: package/python-pillow/ +F: package/python-pydal/ +F: package/python-web2py/ +F: package/sysdig/ + +N: Anthony Viallard <[email protected]> +F: package/gnuplot/ + +N: Antoine T?nart <[email protected]> +F: package/wf111/ + +N: ARC Maintainers <[email protected]> +F: arch/Config.in.arc + +N: Ariel D'Alessandro <[email protected]> +F: package/axfsutils/ +F: package/mali-t76x/ + +N: Arnaud Aujon <[email protected]> +F: package/espeak/ + +N: Arnaud R?billout <[email protected]> +F: package/dbus-triggerd/ +F: package/lftp/ +F: package/tcping/ + +N: Arnout Vandecappelle <[email protected]> +F: package/freescale-imx/firmware-imx/ +F: package/freescale-imx/imx-lib/ +F: package/gstreamer/gst-fsl-plugins/ +F: package/moarvm/ +F: package/owfs/ +F: package/python-bottle/ +F: package/sqlcipher/ +F: package/stress/ + +N: Assaf Inbal <[email protected]> +F: package/lbase64/ +F: package/luabitop/ +F: package/luacrypto/ +F: package/luaexpatutils/ +F: package/luaposix/ +F: package/luasec/ +F: package/lua-ev/ +F: package/orbit/ + +N: Bartosz Golaszewski <[email protected]> +F: package/autoconf-archive/ +F: package/doxygen/ +F: package/libserialport/ +F: package/libsigrok/ +F: package/libsigrokdecode/ +F: package/libzip/ +F: package/pulseview/ +F: package/sigrok-cli/ + +N: Baruch Siach <[email protected]> +F: package/ebtables/ +F: package/openipmi/ + +N: Ben Boeckel <[email protected]> +F: package/taskd/ + +N: Benjamin Kamath <[email protected]> +F: package/lapack/ + +N: Bernd Kuhls <[email protected]> +F: package/apache/ +F: package/clamav/ +F: package/dovecot/ +F: package/dovecot-pigeonhole/ +F: package/fetchmail/ +F: package/freeswitch/ +F: package/ffmpeg/ +F: package/giflib/ +F: package/jsoncpp/ +F: package/kodi* +F: package/leafnode2/ +F: package/libaacs/ +F: package/libasplib/ +F: package/libbdplus/ +F: package/libbroadvoice/ +F: package/libcodec2/ +F: package/libcrossguid/ +F: package/libdcadec/ +F: package/libdvbcsa/ +F: package/libdvdcss/ +F: package/libebur128/ +F: package/libfreeglut/ +F: package/libg7221/ +F: package/libglew/ +F: package/libglfw/ +F: package/libglu/ +F: package/libhdhomerun/ +F: package/libilbc/ +F: package/libldns/ +F: package/libminiupnpc/ +F: package/libnatpmp/ +F: package/libopenh264/ +F: package/libplatform/ +F: package/libsidplay2/ +F: package/libsilk/ +F: package/libsoil/ +F: package/libsoundtouch/ +F: package/libsquish/ +F: package/liburiparser/ +F: package/libva/ +F: package/libva-intel-driver/ +F: package/libyuv/ +F: package/mjpg-streamer/ +F: package/perl-crypt-openssl-random/ +F: package/perl-crypt-openssl-rsa/ +F: package/perl-db-file/ +F: package/perl-digest-sha1/ +F: package/perl-encode-detect/ +F: package/perl-encode-locale/ +F: package/perl-file-listing/ +F: package/perl-html-parser/ +F: package/perl-html-tagset/ +F: package/perl-http-cookies/ +F: package/perl-http-daemon/ +F: package/perl-http-date/ +F: package/perl-http-message/ +F: package/perl-http-negotiate/ +F: package/perl-io-html/ +F: package/perl-lwp-mediatypes/ +F: package/perl-mail-dkim/ +F: package/perl-mailtools/ +F: package/perl-mime-base64/ +F: package/perl-net-dns/ +F: package/perl-net-http/ +F: package/perl-netaddr-ip/ +F: package/perl-time-hires/ +F: package/perl-timedate/ +F: package/perl-uri/ +F: package/perl-www-robotrules/ +F: package/pound/ +F: package/pure-ftpd/ +F: package/python-mako/ +F: package/tinyxml2/ +F: package/tor/ +F: package/softether/ +F: package/unixodbc/ +F: package/vnstat/ +F: package/x11r7/ + +N: Bimal Jacob <[email protected]> +F: package/nginx-upload/ + +N: Bogdan Radulescu <[email protected]> +F: package/iftop/ +F: package/ncdu/ + +N: Bryan Brinsko <[email protected]> +F: package/pps-tools/ + +N: Carlo Caione <[email protected]> +F: package/sunxi-boards/ + +N: Carlos Santos <[email protected]> +F: package/gmock/ +F: package/perl-file-util/ + +N: Carsten Schoenert <[email protected]> +F: package/dvbsnoop/ +F: package/libdvbsi/ +F: package/libsvg/ +F: package/libsvg-cairo/ + +N: Chris Packham <[email protected]> +F: package/eventlog/ +F: package/micropython/ +F: package/micropython-lib/ +F: package/syslog-ng/ + +N: Christian Stewart <[email protected]> +F: package/batman-adv/ +F: package/docker-containerd/ +F: package/docker-engine/ +F: package/mosh/ +F: package/rtl8821au/ +F: package/runc/ + +N: Christophe Vu-Brugier <[email protected]> +F: package/drbd-utils/ +F: package/iotop/ +F: package/python-configshell-fb/ +F: package/python-rtslib-fb/ +F: package/python-urwid/ +F: package/targetcli-fb/ + +N: Clayton Shotwell <[email protected]> +F: package/audit/ +F: package/cpio/ + +N: Clayton Shotwell <[email protected]> +F: package/checkpolicy/ +F: package/libcgroup/ +F: package/libee/ +F: package/libestr/ +F: package/liblogging/ +F: package/libselinux/ +F: package/libsemanage/ +F: package/libsepol/ +F: package/sepolgen/ +F: package/ustr/ + +N: C?dric Ch?pied <[email protected]> +F: package/znc/ + +N: Dagg Stompler <[email protected]> +F: package/libamcodec/ +F: package/odroid-mali/ +F: package/odroid-scripts/ + +N: Damien Lanson <[email protected]> +F: package/libvdpau/ +F: package/log4cpp/ + +N: Daniel Nystr?m <[email protected]> +F: package/e2tools/ +F: package/fbgrab/ + +N: Daniel Price <[email protected]> +F: package/nodejs/ +F: package/redis/ + +N: Daniel Sangue <[email protected]> +F: package/libftdi1/ + +N: Danomi Manchego <[email protected]> +F: package/cjson/ +F: package/jq/ +F: package/ljsyscall/ +F: package/lua-cjson/ +F: package/luaexpat/ +F: package/xinetd/ + +N: Dave Skok <[email protected]> +F: package/ola/ + +N: David Bachelart <[email protected]> +F: package/ccrypt/ +F: package/dos2unix/ +F: package/ipmiutil/ +F: package/python-daemon/ + +N: David Bender <[email protected]> +F: package/benejson/ +F: package/cgic/ +F: package/freeradius-client/ +F: package/openldap/ + +N: David du Colombier <[email protected]> +F: package/x264/ + +N: Davide Viti <[email protected]> +F: package/flann/ +F: package/python-paho-mqtt/ +F: package/qhull/ +F: package/tcllib/ + +N: Denis Bodor <[email protected]> +F: package/libstrophe/ + +N: Dimitrios Siganos <[email protected]> +F: package/wireless-regdb/ + +N: Dominik Faessler <[email protected]> +F: package/logsurfer/ +F: package/python-id3/ + +N: Doug Kehn <[email protected]> +F: package/nss-pam-ldapd/ +F: package/sp-oops-extract/ +F: package/unscd/ + +N: Ed Swierk <[email protected]> +F: package/xxhash/ + +N: Eric Le Bihan <[email protected]> +F: package/adwaita-icon-theme/ +F: package/eudev/ +F: package/hicolor-icon-theme/ +F: package/jemalloc/ +F: package/ninja/ +F: package/smack/ + +N: Eric Limpens <[email protected]> +F: package/pifmrds/ +F: package/ympd/ + +N: Erico Nunes <[email protected]> +F: package/acpica/ +F: package/acpitool/ +F: package/efibootmgr/ +F: package/efivar/ +F: package/spi-tools/ +F: package/xdotool/ + +N: Erik Stromdahl <[email protected]> +F: package/mxsldr/ + +N: Ernesto L. Williams Jr <[email protected]> +F: package/szip/ + +N: Evan Zelkowitz <[email protected]> +F: package/sdl_gfx/ + +N: Ezequiel Garcia <[email protected]> +F: arch/Config.in.nios2 +F: package/fio/ +F: package/iptraf-ng/ +F: package/jimtcl/ +F: package/nodm/ +F: package/openbox/ +F: package/supertuxkart/ + +N: Fabio Estevam <[email protected]> +F: configs/freescale_imx* + +N: Fabio Porcedda <[email protected]> +F: package/netsurf-buildsystem/ + +N: Fabrice Fontaine <[email protected]> +F: package/domoticz/ +F: package/openzwave/ + +N: Fabrice Fontaine <[email protected]> +F: package/alljoyn/ +F: package/alljoyn-base/ +F: package/alljoyn-tcl/ +F: package/alljoyn-tcl-base/ +F: package/gtksourceview/ +F: package/gupnp-dlna/ +F: package/gupnp-tools/ +F: package/igd2-for-linux/ +F: package/minissdpd/ +F: package/tinycbor/ +F: package/tinydtls/ + +N: Floris Bos <[email protected]> +F: package/ipmitool/ +F: package/odhcploc/ + +N: Francisco Gonzalez <[email protected]> +F: package/ser2net/ + +N: Francois Perrad <[email protected]> +F: package/4th/ +F: package/botan/ +F: package/cosmo/ +F: package/dado/ +F: package/ficl/ +F: package/gdbm/ +F: package/libtomcrypt/ +F: package/libtommath/ +F: package/libump/ +F: package/linenoise/ +F: package/ljlinenoise/ +F: package/lpeg/ +F: package/lpty/ +F: package/lrandom/ +F: package/lsqlite3/ +F: package/lua* +F: package/lunit/ +F: package/lzlib/ +F: package/perl* +F: package/qemu/ +F: package/tekui/ +F: support/scripts/scancpan + +N: Frank Hunleth <[email protected]> +F: package/am335x-pru-package/ +F: package/libdmtx/ +F: package/libsodium/ +F: package/python-cherrypy/ +F: package/sane-backends/ +F: package/ucl/ +F: package/upx/ +F: package/zxing-cpp/ + +N: Gary Bisson <[email protected]> +F: configs/nitrogen* +F: package/freescale-imx/ +F: package/libimxvpuapi/ +F: package/sshpass/ + +N: Geoff Levand <[email protected]> +F: package/flannel/ + +N: Geoffrey Ragot <[email protected]> +F: package/python-pycli/ +F: package/python-pyyaml/ + +N: Gilles Talis <[email protected]> +F: package/fdk-aac/ +F: package/httping/ +F: package/iozone/ +F: package/ocrad/ +F: package/webp/ + +N: Giovanni Zantedeschi <[email protected]> +F: package/libpam-radius-auth/ +F: package/libpam-tacplus/ + +N: Gregory Dymarek <[email protected]> +F: package/ding-libs/ +F: package/gengetopt/ +F: package/janus-gateway/ +F: package/libnice/ +F: package/libsrtp/ +F: package/libwebsock/ +F: package/sofia-sip/ + +N: Gregory Hermant <[email protected]> +F: package/bcusdk/ +F: package/dfu-util/ +F: package/libpthsem/ +F: package/linknx/ +F: package/snowball-hdmiservice/ +F: package/ux500-firmware/ + +N: Guillaume Gardet <[email protected]> +F: package/c-icap/ +F: package/c-icap-modules/ +F: package/sdl2/ + +N: Guillaume William Brs <[email protected]> +F: package/liquid-dsp/ + +N: Gustavo Zacarias <[email protected]> +F: arch/Config.in.powerpc +F: board/qemu/ +F: configs/qemu_* +F: package/argp-standalone/ +F: package/arptables/ +F: package/audiofile/ +F: package/autossh/ +F: package/bitstream-vera/ +F: package/blktrace/ +F: package/bmon/ +F: package/btrfs-progs/ +F: package/c-ares/ +F: package/cantarell/ +F: package/check/ +F: package/collectd/ +F: package/comix-cursors/ +F: package/connman-gtk/ +F: package/conntrack-tools/ +F: package/cppdb/ +F: package/crda/ +F: package/cryptodev-linux/ +F: package/dbus-cpp/ +F: package/debianutils/ +F: package/dt/ +F: package/exfat/ +F: package/exfat-utils/ +F: package/f2fs-tools/ +F: package/faad2/ +F: package/fping/ +F: package/ftop/ +F: package/gcr/ +F: package/geoip/ +F: package/gpsd/ +F: package/granite/ +F: package/graphite2/ +F: package/gsettings-desktop-schemas/ +F: package/hans/ +F: package/haveged/ +F: package/heimdal/ +F: package/hostapd/ +F: package/ifupdown/ +F: package/inconsolata/ +F: package/iodine/ +F: package/iperf3/ +F: package/ipset/ +F: package/iw/ +F: package/jhead/ +F: package/jquery-keyboard/ +F: package/kompexsqlite/ +F: package/kvmtool/ +F: package/lame/ +F: package/lft/ +F: package/libao/ +F: package/libcroco/ +F: package/libcue/ +F: package/libcuefile/ +F: package/libepoxy/ +F: package/libgee/ +F: package/libglib2/ +F: package/libgtk2/ +F: package/libgtk3/ +F: package/libmcrypt/ +F: package/libmemcached/ +F: package/libmhash/ +F: package/libmnl/ +F: package/libmng/ +F: package/libmpdclient/ +F: package/libnetfilter_acct/ +F: package/libnetfilter_conntrack/ +F: package/libnetfilter_cthelper/ +F: package/libnetfilter_cttimeout/ +F: package/libnetfilter_log/ +F: package/libnetfilter_queue/ +F: package/libnfnetlink/ +F: package/libnl/ +F: package/liboping/ +F: package/libreplaygain/ +F: package/libsamplerate/ +F: package/libtorrent/ +F: package/libuv/ +F: package/lksctp-tools/ +F: package/lshw/ +F: package/lz4/ +F: package/lzip/ +F: package/mbedtls/ +F: package/mcrypt/ +F: package/memcached/ +F: package/minizip/ +F: package/mpd/ +F: package/mpv/ +F: package/mtr/ +F: package/musepack/ +F: package/ncmpc/ +F: package/net-tools/ +F: package/netstat-nat/ +F: package/nettle/ +F: package/nfacct/ +F: package/nftables/ +F: package/nload/ +F: package/nmap/ +F: package/noip/ +F: package/norm/ +F: package/obsidian-cursors/ +F: package/ocf-linux/ +F: package/opencore-amr/ +F: package/openswan/ +F: package/opusfile/ +F: package/p11-kit/ +F: package/p910nd/ +F: package/pax-utils/ +F: package/procrank_linux/ +F: package/php-* +F: package/pkgconf/ +F: package/privoxy/ +F: package/protobuf-c/ +F: package/ptpd/ +F: package/ptpd2/ +F: package/pwgen/ +F: package/ramspeed/ +F: package/rng-tools/ +F: package/rtorrent/ +F: package/samba4/ +F: package/sbc/ +F: package/snmppp/ +F: package/sox/ +F: package/spidev_test/ +F: package/squid/ +F: package/start-stop-daemon/ +F: package/swig/ +F: package/thrift/ +F: package/twolame/ +F: package/ulogd/ +F: package/unionfs/ +F: package/unrar/ +F: package/ushare/ +F: package/vala/ +F: package/vorbis-tools/ +F: package/wavpack/ +F: package/wayland-protocols/ +F: package/webkitgtk/ +F: package/webkitgtk24/ +F: package/whois/ +F: package/wireshark/ +F: package/wpan-tools/ +F: package/x11r7/xdriver_xf86-video-qxl/ +F: package/xtables-addons/ +F: package/zd1211-firmware/ + +N: Gwenhael Goavec-Merou <[email protected]> +F: package/gnuradio/ +F: package/gr-osmosdr/ +F: package/libusbgx/ +F: package/python-cheetah/ +F: package/python-markdown/ +F: package/python-pyqt/ +F: package/python-sip/ + +N: Henrique Camargo <[email protected]> +F: package/json-glib/ + +N: Hiroshi Kawashima <[email protected]> +F: package/gauche/ +F: package/gmrender-resurrect/ +F: package/squeezelite/ + +N: Ian Haylock <[email protected]> +F: package/python-rpi-gpio/ + +N: Ignacy Gaw?dzki <[email protected]> +F: package/angularjs/ + +N: James Knight <[email protected]> +F: package/atkmm/ +F: package/cairomm/ +F: package/google-material-design-icons/ +F: package/gtkmm3/ +F: package/libpqxx/ +F: package/pangomm/ +F: package/yad/ + +N: Jan Pedersen <[email protected]> +F: package/zip/ + +N: Jan Viktorin <[email protected]> +F: package/python-pexpect/ +F: package/python-ptyprocess/ +F: package/zynq-boot-bin/ + +N: Jarkko Sakkinen <[email protected]> +F: package/quota/ + +N: Jason Pruitt <[email protected]> +F: package/librtlsdr/ + +N: Jens Rosenboom <[email protected]> +F: package/sl/ + +N: Jens Zettelmeyer <[email protected]> +F: package/batctl/ + +N: Jeremy Rosen <[email protected]> +F: package/fxload/ + +N: Joel Stanley <[email protected]> +F: package/pdbg/ + +N: Johan Derycke <[email protected]> +F: package/python-libconfig/ + +N: Johan Oudinet <[email protected]> +F: package/ejabberd/ +F: package/erlang-goldrush/ +F: package/erlang-lager/ +F: package/erlang-p1-cache-tab/ +F: package/erlang-p1-iconv/ +F: package/erlang-p1-sip/ +F: package/erlang-p1-stringprep/ +F: package/erlang-p1-stun/ +F: package/erlang-p1-tls/ +F: package/erlang-p1-utils/ +F: package/erlang-p1-xml/ +F: package/erlang-p1-yaml/ +F: package/erlang-p1-zlib/ + +N: John Stile <[email protected]> +F: package/dhcpcd/ + +N: Jonathan Ben Avraham <[email protected]> +F: arch/Config.in.xtensa +F: package/autofs/ +F: package/dawgdic/ +F: package/libphidget/ +F: package/phidgetwebservice/ +F: package/rapidxml/ +F: package/sphinxbase/ + +N: Jonathan Liu <[email protected]> +F: package/python-meld3/ +F: package/supervisor/ + +N: Joris Lijssens <[email protected]> +F: package/emlog/ +F: package/libcoap/ +F: package/libnet/ +F: package/libuio/ +F: package/netsniff-ng/ +F: package/rabbitmq-c/ + +N: Juha Rantanen <[email protected]> +F: package/acsccid/ + +N: Julian Lunz <[email protected]> +F: package/freerdp/ + +N: Julian Scheel <[email protected]> +F: package/bitstream/ +F: package/cbootimage/ +F: package/cryptopp/ +F: package/dvblast/ +F: package/tegrarcm/ + +N: Julien Boibessot <[email protected]> +F: configs/armadeus* +F: package/libcddb/ + +N: Julien Corjon <[email protected]> +F: package/qt5/ + +N: Julien Floret <[email protected]> +F: package/lldpd/ + +N: Justin Maggard <[email protected]> +F: package/dtach/ + +N: J?r?me Oufella <[email protected]> +F: package/libdri2/ +F: package/qt-webkit-kiosk/ + +N: J?r?me Pouiller <[email protected]> +F: package/apitrace/ +F: package/freescale-imx/gpu-amd-bin-mx51/ +F: package/freescale-imx/libz160/ +F: package/lxc/ +F: package/strongswan/ +F: package/wmctrl/ +F: package/x11r7/xdriver_xf86-video-imx/ +F: package/x11r7/xdriver_xf86-video-imx-viv/ + +N: J?rg Krause <[email protected]> +F: package/libshout/ +F: package/libupnpp/ +F: package/luv/ +F: package/luvi/ +F: package/mp4v2/ +F: package/shairport-sync/ +F: package/swupdate/ +F: package/upmpdcli/ +F: package/wavemon/ + +N: Karoly Kasza <[email protected]> +F: package/irqbalance/ +F: package/openvmtools/ + +N: Kelvin Cheung <[email protected]> +F: package/cpuload/ +F: package/bwm-ng/ +F: package/ramsmp/ + +N: Laurent Cans <[email protected]> +F: package/aircrack-ng/ + +N: Lee Jones <[email protected]> +F: boot/afboot-stm32/ + +N: Lionel Orry <[email protected]> +F: package/mongrel2/ + +N: Lothar Felten <[email protected]> +F: package/ti-sgx-demos/ +F: package/ti-sgx-km/ +F: package/ti-sgx-um/ + +N: Luca Ceresoli <[email protected]> +F: package/agentpp/ +F: package/exim/ +F: package/libpjsip/ +F: package/qpid-proton/ +F: package/rtl8188eu/ +F: package/stm32flash/ +F: package/unzip/ +F: support/legal-info/ + +N: Lucas De Marchi <[email protected]> +F: package/fswebcam/ + +N: Ludovic Desroches <[email protected]> +F: board/atmel/ +F: configs/at91* +F: configs/atmel_* +F: package/fb-test-app/ +F: package/python-json-schema-validator/ +F: package/python-keyring/ +F: package/python-simplejson/ +F: package/python-versiontools/ +F: package/wilc1000-firmware/ + +N: Mamatha Inamdar <[email protected]> +F: package/nvme/ + +N: Manuel V?gele <[email protected]> +F: package/python-requests-toolbelt/ + +N: Marcin Bis <[email protected]> +F: package/bluez5_utils/ +F: package/cc-tool/ +F: package/ecryptfs-utils/ + +N: Marcin Niestroj <[email protected]> +F: package/argparse/ +F: package/rs485conf/ +F: package/turbolua/ + +N: Marek Belisko <[email protected]> +F: package/libatasmart/ +F: package/polkit/ +F: package/sg3_utils/ +F: package/udisks/ + +N: Markos Chandras <[email protected]> +F: package/harfbuzz/ +F: package/libsecret/ + +N: Martin Bark <[email protected]> +F: package/ca-certificates/ + +N: Martin Hicks <[email protected]> +F: package/cryptsetup/ + +N: Matt Weber <[email protected]> +F: package/bc/ +F: package/eigen/ +F: package/fmc/ +F: package/fmlib/ +F: package/igmpproxy/ +F: package/iputils/ +F: package/omniorb/ +F: package/python-ipy/ +F: package/python-posix-ipc/ +F: package/python-pypcap/ +F: package/python-pyrex/ +F: package/raptor/ +F: package/setools/ +F: package/simicsfs/ +F: package/smcroute/ +F: package/tclap/ + +N: Mauro Condarelli <[email protected]> +F: package/mc/ +F: package/python-autobahn/ +F: package/python-cbor/ +F: package/python-characteristic/ +F: package/python-click/ +F: package/python-crossbar/ +F: package/python-lmdb/ +F: package/python-mistune/ +F: package/python-netaddr/ +F: package/python-pyasn-modules/ +F: package/python-pygments/ +F: package/python-pynacl/ +F: package/python-pytrie/ +F: package/python-service-identity/ +F: package/python-setproctitle/ +F: package/python-shutilwhich/ +F: package/python-treq/ +F: package/python-txaio/ +F: package/python-ujson/ +F: package/python-wsaccel/ + +N: Max Filippov <[email protected]> +F: arch/Config.in.xtensa + +N: Maxime Hadjinlian <[email protected]> +F: package/babeld/ +F: package/dante/ +F: package/faifa/ +F: package/initscripts/ +F: package/intel-microcode/ +F: package/iucode-tool/ +F: package/jasper/ +F: package/kodi/ +F: package/libass/ +F: package/libbluray/ +F: package/libcdio/ +F: package/libcofi/ +F: package/libenca/ +F: package/libmodplug/ +F: package/libnfs/ +F: package/libplist/ +F: package/libshairplay/ +F: package/linux-zigbee/ +F: package/netcat-openbsd/ +F: package/open-plc-utils/ +F: package/rpi-firmware/ +F: package/rpi-userland/ +F: package/rtmpdump/ +F: package/skeleton/ +F: package/systemd/ +F: package/systemd-bootchart/ +F: package/tinyalsa/ +F: package/tinyxml/ + +N: Maxime Ripard <[email protected]> +F: package/kmsxx/ + +N: Michael Rommel <[email protected]> +F: package/aiccu/ +F: package/knock/ +F: package/python-crc16/ +F: package/python-pyzmq/ + +N: Michael Trimarchi <[email protected]> +F: package/python-spidev/ + +N: Mikhail Boiko <[email protected]> +F: package/libfribidi/ + +N: Morgan Delestre <[email protected]> +F: package/monkey/ + +N: Murat Demirten <[email protected]> +F: package/jpeg-turbo/ +F: package/libgeotiff/ + +N: Nathan Lynch <[email protected]> +F: package/chrony/ + +N: Nathaniel Roach <[email protected]> +F: package/bandwidthd/ +F: package/libgudev/ + +N: Naumann Andreas <[email protected]> +F: package/evemu/ +F: package/libevdev/ + +N: Nicolas Menegale <[email protected]> +F: package/cppcms/ +F: package/glibmm/ +F: package/libxmlpp/ + +N: Nicolas Serafini <[email protected]> +F: package/exiv2/ +F: package/nvidia-tegra23/nvidia-tegra23-binaries/ +F: package/nvidia-tegra23/nvidia-tegra23-codecs/ + +N: Nimai Mahajan <[email protected]> +F: package/libucl/ + +N: Niranjan Reddy <[email protected]> +F: package/cgroupfs-mount/ + +N: No? Rubinstein <[email protected]> +F: package/tpm-tools/ +F: package/trousers/ + +N: Olaf Rempel <[email protected]> +F: package/ctorrent/ + +N: Oli Vogt <[email protected]> +F: package/python-django/ +F: package/python-flup/ + +N: Olivier Schonken <[email protected]> +F: package/ijs/ +F: package/poppler/ +F: package/qpdf/ +F: package/openjpeg/ + +N: Olivier Singla <[email protected]> +F: package/shellinabox/ + +N: Parnell Springmeyer <[email protected]> +F: package/scrypt/ + +N: Pascal Huerst <[email protected]> +F: package/google-breakpad/ + +N: Patrick Gerber <[email protected]> +F: package/yavta/ + +N: Patrick Ziegler <[email protected]> +F: package/aespipe/ +F: package/libqmi/ + +N: Paul Cercueil <[email protected]> +F: package/libiio/ + +N: Paul Cercueil <[email protected]> +F: package/lightning/ + +N: Pedro Aguilar <[email protected]> +F: package/libunistring/ + +N: Peter Korsgaard <[email protected]> +F: package/flickcurl/ +F: package/libfastjson/ +F: package/lzop/ +F: package/python-alsaaudio/ +F: package/python-enum/ +F: package/python-enum34/ +F: package/python-ipaddr/ +F: package/python-pam/ +F: package/python-psutil/ +F: package/triggerhappy/ +F: package/wpa_supplicant/ + +N: Peter Seiderer <[email protected]> +F: package/assimp/ +F: package/bcm2835/ +F: package/dejavu/ +F: package/dillo/ +F: package/edid-decode/ +F: package/ghostscript-fonts/ +F: package/gstreamer1/gst1-validate/ +F: package/log4cplus/ +F: package/postgresql/ +F: package/qt5/qt53d/ +F: package/qt5/qt5quickcontrols2/ +F: package/qt5/qt5tools/ +F: package/racehound/ +F: package/wiringpi/ + +N: Peter Thompson <[email protected]> +F: package/sdl2_gfx/ +F: package/sdl2_image/ +F: package/sdl2_ttf/ + +N: Petr Vorel <[email protected]> +F: package/linux-backports/ + +N: Phil Eichinger <[email protected]> +F: package/libqrencode/ +F: package/psplash/ +F: package/sispmctl/ +F: package/zsh/ + +N: Philipp Claves <[email protected]> +F: package/libassuan/ +F: package/libgpgme/ + +N: Philippe Proulx <[email protected]> +F: package/python-ipython/ + +N: Pierre Floury <[email protected]> +F: package/trace-cmd/ + +N: Pieter De Gendt <[email protected]> +F: package/libvips/ + +N: Pieterjan Camerlynck <[email protected]> +F: package/libdvbpsi/ +F: package/mraa/ + +N: Qais Yousef <[email protected]> +F: package/bellagio/ + +N: Rahul Bedarkar <[email protected]> +F: package/gflags/ +F: package/glog/ +F: package/gssdp/ +F: package/gupnp/ +F: package/gupnp-av/ + +N: Renaud Aubin <[email protected]> +F: package/libhttpparser/ + +N: Rhys Williams <[email protected]> +F: package/lirc-tools/ + +N: Richard Braun <rbraun@> +F: package/curlftpfs/ + +N: Richard Braun <[email protected]> +F: package/tzdata/ + +N: Rico Bachmann <[email protected]> +F: package/apr-util/ +F: package/subversion/ + +N: Rodrigo Rebello <[email protected]> +F: package/chocolate-doom/ +F: package/irssi/ + +N: Romain Naour <[email protected]> +F: package/bullet/ +F: package/efl/ +F: package/iqvlinux/ +F: package/liblinear/ +F: package/mcelog/ +F: package/openpowerlink/ +F: package/stress-ng/ +F: package/terminology/ + +N: Ryan Barnett <[email protected]> +F: package/atftp/ +F: package/miraclecast/ +F: package/python-pyasn/ +F: package/python-pycrypto/ +F: package/python-pysnmp/ +F: package/python-pysnmp-apps/ +F: package/python-pysnmp-mibs/ +F: package/python-tornado/ + +N: Ryan Wilkins <[email protected]> +F: package/biosdevname/ + +N: R?mi R?rolle <[email protected]> +F: package/libfreeimage/ + +N: Sagaert Johan <[email protected]> +F: package/git/ +F: package/gsl/ +F: package/jquery-mobile/ +F: package/libgsasl/ +F: package/qdecoder/ +F: package/qlibc/ + +N: Sam Bobroff <[email protected]> +F: package/librtas/ + +N: Samuel Martin <[email protected]> +F: package/armadillo/ +F: package/canfestival/ +F: package/clapack/ +F: package/cwiid/ +F: package/flite/ +F: package/nginx/ +F: package/openobex/ +F: package/python-numpy/ +F: package/scrub/ +F: package/urg/ +F: package/ussp-push/ + +N: Santosh Multhalli <[email protected]> +F: package/valijson/ + +N: Scott Fan <[email protected]> +F: package/libssh/ +F: package/x11r7/xdriver_xf86-video-fbturbo/ + +N: Sebastien Bourdelin <[email protected]> +F: package/atf/ +F: package/cppunit/ +F: package/kyua/ +F: package/lutok/ +F: package/yaml-cpp/ + +N: Sergio Prado <[email protected]> +F: package/libgdiplus/ +F: package/mongodb/ +F: package/stella/ +F: package/tunctl/ +F: package/ubus/ + +N: Simon Dawson <[email protected]> +F: boot/at91bootstrap3/ +F: package/cppzmq/ +F: package/czmq/ +F: package/filemq/ +F: package/googlefontdirectory/ +F: package/jansson/ +F: package/jquery-ui/ +F: package/jquery-ui-themes/ +F: package/json-javascript/ +F: package/lcdapi/ +F: package/libfreefare/ +F: package/libjson/ +F: package/libnfc/ +F: package/libnfc/ +F: package/libserial/ +F: package/libsigsegv/ +F: package/macchanger/ +F: package/minicom/ +F: package/minidlna/ +F: package/msgpack/ +F: package/nanocom/ +F: package/neard/ +F: package/neardal/ +F: package/owl-linux/ +F: package/python-nfc/ +F: package/rapidjson/ +F: package/sconeserver/ +F: package/sound-theme-borealis/ +F: package/sound-theme-freedesktop/ +F: package/vlc/ +F: package/wvdial/ +F: package/wvstreams/ +F: package/xscreensaver/ +F: package/zmqpp/ +F: package/zyre/ + +N: Spenser Gilliland <[email protected]> +F: arch/Config.in.microblaze +F: package/a10disp/ +F: package/glmark2/ +F: package/libvpx/ +F: package/mesa3d-demos/ +F: package/sunxi-mali/ +F: package/ti-gfx/ + +N: Stefan Fr?berg <[email protected]> +F: package/elfutils/ +F: package/libtasn1/ +F: package/proxychains-ng/ +F: package/yasm/ + +N: Stephan Hoffmann <[email protected]> +F: package/cache-calibrator/ +F: package/gtest/ +F: package/mtdev/ +F: package/mtdev2tuio/ +F: package/qtuio/ + +N: Steve Calfee <[email protected]> +F: package/python-pymysql/ +F: package/python-pyratemp/ + +N: Steve James <[email protected]> +F: package/leveldb/ +F: package/libcli/ + +N: Steve Kenton <[email protected]> +F: package/dvdauthor/ +F: package/dvdrw-tools/ +F: package/memtest86/ +F: package/mjpegtools/ +F: package/tovid/ +F: package/xorriso/ + +N: Steve Thomas <[email protected]> +F: package/cloog/ +F: package/isl/ + +N: Steven Noonan <[email protected]> +F: package/hwloc/ +F: package/powertop/ + +N: Sven Neumann <[email protected]> +F: package/gstreamer1/gst1-libav/ + +N: Sven Neumann <[email protected]> +F: package/glib-networking/ +F: package/libmms/ +F: package/orc/ + +N: S?bastien Szymanski <[email protected]> +F: package/mmc-utils/ +F: package/python-flask-jsonrpc/ +F: package/python-flask-login/ + +N: Thierry Bultel <[email protected]> +F: package/mpd-mpc/ + +N: Thijs Vermeir <[email protected]> +F: package/ranger/ +F: package/x265/ + +N: Thomas Claveirole <[email protected]> +F: package/fcgiwrap/ + +N: Thomas Davis <[email protected]> +F: package/civetweb/ + +N: Thomas De Schampheleire <[email protected]> +F: package/libpfm4/ +F: package/mkpasswd/ +F: package/zeromq/ + +N: Thomas Petazzoni <[email protected]> +F: arch/Config.in.arm +F: boot/boot-wrapper-aarch64/ +F: boot/grub2/ +F: boot/gummiboot/ +F: package/android-tools/ +F: package/b43-firmware/ +F: package/b43-fwcutter/ +F: package/c-periphery/ +F: package/cdrkit/ +F: package/cifs-utils/ +F: package/cloop/ +F: package/cmake/ +F: package/cramfs/ +F: package/dmidecode/ +F: package/enlightenment/ +F: package/flashrom/ +F: package/gcc/gcc-final/ +F: package/gcc/gcc-initial/ +F: package/genext2fs/ +F: package/genromfs/ +F: package/getent/ +F: package/gnu-efi/ +F: package/heirloom-mailx/ +F: package/hiawatha/ +F: package/igh-ethercat/ +F: package/intltool/ +F: package/libcap/ +F: package/libevas-generic-loaders/ +F: package/libffi/ +F: package/libsha1/ +F: package/libtirpc/ +F: package/liburcu/ +F: package/libxkbcommon/ +F: package/libxml-parser-perl/ +F: package/localedef/ +F: package/log4cxx/ +F: package/lttng-babeltrace/ +F: package/lttng-libust/ +F: package/lttng-modules/ +F: package/lttng-tools/ +F: package/monit/ +F: package/mpdecimal/ +F: package/msmtp/ +F: package/musl/ +F: package/ne10/ +F: package/pkg-python.mk +F: package/pkg-autotools.mk +F: package/pkg-generic.mk +F: package/polarssl/ +F: package/python/ +F: package/python3/ +F: package/python-mad/ +F: package/python-serial/ +F: package/qextserialport/ +F: package/rpcbind/ +F: package/rt-tests/ +F: package/sam-ba/ +F: package/scons/ +F: package/squashfs/ +F: package/wayland/ +F: package/weston/ +F: toolchain/ + +N: Tiago Brusamarello <[email protected]> +F: package/aer-inject/ + +N: Tom Sparks <[email protected]> +F: package/ibrcommon/ +F: package/ibrdtn/ +F: package/ibrdtn-tools/ +F: package/ibrdtnd/ + +N: Tzu-Jung Lee <[email protected]> +F: package/dropwatch/ +F: package/tstools/ + +N: Vanya Sergeev <[email protected]> +F: package/lua-periphery/ + +N: Vicente Olivert Riera <[email protected]> +F: arch/Config.in.mips +F: package/gnupg2/ +F: package/hidapi/ +F: package/libfm/ +F: package/libfm-extra/ +F: package/libksba/ +F: package/menu-cache/ +F: package/openblas/ +F: package/openmpi/ +F: package/pinentry/ +F: package/trinity/ + +N: Vincent Stehl? <[email protected]> +F: package/i7z/ +F: package/msr-tools/ + +N: Vinicius Tinti <[email protected]> +F: package/python-thrift/ + +N: Volkov Viacheslav <[email protected]> +F: package/rfkill/ +F: package/v4l2grab/ +F: package/zbar/ + +N: Wade Berrier <[email protected]> +F: package/ngrep/ + +N: Waldemar Brodkorb <[email protected]> +F: arch/Config.in.bfin +F: arch/Config.in.sparc +F: arch/Config.in.m68k + +N: Waldemar Rymarkiewicz <[email protected]> +F: package/ccid/ +F: package/pcsc-lite/ + +N: Will Newton <[email protected]> +F: package/enchant/ +F: package/erlang/ +F: package/libmicrohttpd/ +F: package/sysprof/ +F: package/time/ + +N: Will Newton <[email protected]> +F: package/numactl/ + +N: Will Wagner <[email protected]> +F: package/yaffs2utils/ + +N: Wojciech M. Zabolotny <[email protected]> +F: package/avrdude/ +F: package/jack2/ +F: package/python-msgpack/ +F: package/python-pyusb/ + +N: Wojciech Nizi?ski <[email protected]> +F: package/fwup/ + +N: Yann E. MORIN <[email protected]> +F: package/cegui06/ +F: package/celt051/ +F: package/dtc/ +F: package/dtv-scan-tables/ +F: package/dvb-apps/ +F: package/keyutils/ +F: package/libbsd/ +F: package/libedit/ +F: package/libinput/ +F: package/libiscsi/ +F: package/libseccomp/ +F: package/mesa3d-headers/ +F: package/mke2img/ +F: package/nut/ +F: package/omxplayer/ +F: package/python-pyparsing/ +F: package/pkg-download.mk +F: package/slirp/ +F: package/snappy/ +F: package/spice/ +F: package/spice-protocol/ +F: package/tmux/ +F: package/tvheadend/ +F: package/usbredir/ +F: package/vde2/ +F: package/w_scan/ +F: support/download/ + +N: Yegor Yefremov <[email protected]> +F: package/acl/ +F: package/attr/ +F: package/bluez_utils/ +F: package/boost/ +F: package/bootstrap/ +F: package/cannelloni/ +F: package/circus/ +F: package/feh/ +F: package/giblib/ +F: package/imlib2/ +F: package/jquery-datetimepicker/ +F: package/jquery-sidebar/ +F: package/kmod/ +F: package/libical/ +F: package/libmbim/ +F: package/libndp/ +F: package/libnftnl/ +F: package/libsoc/ +F: package/libsocketcan/ +F: package/libubox/ +F: package/libuci/ +F: package/linux-firmware/ +F: package/modem-manager/ +F: package/nuttcp/ +F: package/parted/ +F: package/python* +F: package/socketcand/ +F: package/qt5/qt5serialbus/ +F: package/sdparm/ +F: package/ti-utils/ +F: package/x11r7/xapp_xconsole/ +F: package/x11r7/xapp_xinput-calibrator/ +F: package/zlog/ +F: support/scripts/scanpypi + +N: Zoltan Gyarmati <[email protected]> +F: package/crudini/ +F: package/grantlee/ +F: package/python-configobj/ +F: package/python-iniparse/ +F: package/qjson/ +F: package/quazip/ +F: package/tinc/
Signature · 1 line
2.7.4
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Thomas, All,
2016-08-23 14:47 GMT+02:00 Thomas Petazzoni
<[email protected]>:
DEVELOPERS line 468
Quoted 6 lines
<snip>
DEVELOPERS new file +5
-0+N: Gary Bisson <[email protected]> +F: configs/nitrogen* +F: package/freescale-imx/ +F: package/libimxvpuapi/ +F: package/sshpass/
Maybe you can add:
board/boundarydevices/
package/gstreamer1/gst1-imx/
Regards,
Gary
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 12 lines · Gary Bisson
2016-08-23 14:47 GMT+02:00 Thomas Petazzoni
<[email protected]>:DEVELOPERS line 468
Quoted 6 lines
<snip>
DEVELOPERS new file +5
-0+N: Gary Bisson <[email protected]> +F: configs/nitrogen* +F: package/freescale-imx/ +F: package/libimxvpuapi/ +F: package/sshpass/Maybe you can add:
board/boundarydevices/
package/gstreamer1/gst1-imx/
Thanks for the suggestion, I've added those.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Thomas PetazzoniAm Tue, 23 Aug 2016 14:47:44 +0200 schrieb Thomas Petazzoni:
Quoted 69 lines
DEVELOPERS new file +69
-0+N: Bernd Kuhls <[email protected]> +F: package/apache/ +F: package/clamav/ +F: package/dovecot/ +F: package/dovecot-pigeonhole/ +F: package/fetchmail/ +F: package/freeswitch/ +F: package/ffmpeg/ +F: package/giflib/ +F: package/jsoncpp/ +F: package/kodi* +F: package/leafnode2/ +F: package/libaacs/ +F: package/libasplib/ +F: package/libbdplus/ +F: package/libbroadvoice/ +F: package/libcodec2/ +F: package/libcrossguid/ +F: package/libdcadec/ +F: package/libdvbcsa/ +F: package/libdvdcss/ +F: package/libebur128/ +F: package/libfreeglut/ +F: package/libg7221/ +F: package/libglew/ +F: package/libglfw/ +F: package/libglu/ +F: package/libhdhomerun/ +F: package/libilbc/ +F: package/libldns/ +F: package/libminiupnpc/ +F: package/libnatpmp/ +F: package/libopenh264/ +F: package/libplatform/ +F: package/libsidplay2/ +F: package/libsilk/ +F: package/libsoil/ +F: package/libsoundtouch/ +F: package/libsquish/ +F: package/liburiparser/ +F: package/libva/ +F: package/libva-intel-driver/ +F: package/libyuv/ +F: package/mjpg-streamer/ +F: package/perl-crypt-openssl-random/ +F: package/perl-crypt-openssl-rsa/ +F: package/perl-db-file/ +F: package/perl-digest-sha1/ +F: package/perl-encode-detect/ +F: package/perl-encode-locale/ +F: package/perl-file-listing/ +F: package/perl-html-parser/ +F: package/perl-html-tagset/ +F: package/perl-http-cookies/ +F: package/perl-http-daemon/ +F: package/perl-http-date/ +F: package/perl-http-message/ +F: package/perl-http-negotiate/ +F: package/perl-io-html/ +F: package/perl-lwp-mediatypes/ +F: package/perl-mail-dkim/ +F: package/perl-mailtools/ +F: package/perl-mime-base64/ +F: package/perl-net-dns/ +F: package/perl-net-http/ +F: package/perl-netaddr-ip/ +F: package/perl-time-hires/ +F: package/perl-timedate/ +F: package/perl-uri/
DEVELOPERS line 226
Quoted 10 lines
DEVELOPERS new file +10
-0+F: package/perl-www-robotrules/ +F: package/pound/ +F: package/pure-ftpd/ +F: package/python-mako/ +F: package/tinyxml2/ +F: package/tor/ +F: package/softether/ +F: package/unixodbc/ +F: package/vnstat/ +F: package/x11r7/
Hi,
you can add the following packages to my list:
F: package/exim/
F: package/transmission/
F: package/libvpx/
F: package/libdrm/
F: package/mesa3d/
F: package/libsndfile/
F: package/mplayer/
F: package/libdvdread/
F: package/libdvdnav/
F: package/tvheadend/
F: package/libmicrohttpd/
F: package/vlc/
F: package/eudev/
F: package/glmark2/
F: package/dtv-scan-tables/
F: package/taglib/
F: package/libbluray/
F: package/x264/
F: package/x265/
F: package/minidlna/
F: package/znc/
F: package/libcec/
F: package/libass/
F: package/libpciaccess/
F: package/rtmpdump/
F: package/lame/
F: package/apr-util/
F: package/apr/
F: package/pixman/
F: package/libogg/
F: package/libvorbis/
F: package/libcdio/
Or in other words:
F: package/_everything_needed_for_kodi_freeswitch_mail/
;)
Regards, Bernd
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 1 line · Bernd Kuhls
you can add the following packages to my list:
[...]
Quoted 2 lines
Or in other words:
F: package/_everything_needed_for_kodi_freeswitch_mail/
Thanks for the suggestions, I've added those, they will be part of v3.
Of course, we will still be able to patch the DEVELOPERS file afterwards, what I'm proposing in my patch series is just an initial state.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Thomas PetazzoniQuoted 1 line
From: "Thomas Petazzoni" <[email protected]>
---8<---
Quoted 5 lines
This is an initial list of Buildroot developers. It has been created semi-automatically by parsing the Git history, and finding the authors of commits with a title like "<foo>: new package". Some additional manual tweaking has been done (merging multiple entries corresponding to the same person, adding some more entries, etc.).
---8<---
DEVELOPERS line 243
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Carlos Santos <[email protected]> +F: package/gmock/ +F: package/perl-file-util/
I can take care of util-linux, too.
---8<---
DEVELOPERS line 486
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Giovanni Zantedeschi <[email protected]> +F: package/libpam-radius-auth/ +F: package/libpam-tacplus/
Giovanni does not work at DATACOM anymore. Please replace by casantos at ...
---8<---
DEVELOPERS line 1271
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Stephan Hoffmann <[email protected]> +F: package/cache-calibrator/ +F: package/gtest/
I'm planing to replace gmock and gtest by "googletest" in the near future, so I could take care of gtest if Stefan does not mind. ---8<---
Carlos Santos (Casantos)
DATACOM, P&D
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 11 lines · Carlos Santos
Quoted 5 lines
This is an initial list of Buildroot developers. It has been created semi-automatically by parsing the Git history, and finding the authors of commits with a title like "<foo>: new package". Some additional manual tweaking has been done (merging multiple entries corresponding to the same person, adding some more entries, etc.).
---8<---
DEVELOPERS line 243
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Carlos Santos <[email protected]> +F: package/gmock/ +F: package/perl-file-util/I can take care of util-linux, too.
Added, even though you haven't made any commits to util-linux yet (I remember we have 3 patches from you in patchwork on util-linux).
Quoted 5 lines
DEVELOPERS line 486
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Giovanni Zantedeschi <[email protected]> +F: package/libpam-radius-auth/ +F: package/libpam-tacplus/Giovanni does not work at DATACOM anymore. Please replace by casantos at ...
Done, thanks for letting me know!
Quoted 6 lines
---8<---
DEVELOPERS line 1271
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Stephan Hoffmann <[email protected]> +F: package/cache-calibrator/ +F: package/gtest/I'm planing to replace gmock and gtest by "googletest" in the near future, so I could take care of gtest if Stefan does not mind.
I've added package/gtest/ for you as well. Package assignments are not
exclusive: two developers can express their interest for the same package. That's why I've chosen the term "developer" and not "maintainer": it's not a file that really describes "ownership" of packages, but rather "interest".
Thanks for your feedback!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Thomas PetazzoniHi Thomas,
Le 23/08/2016 ? 14:47, Thomas Petazzoni a ?crit :
DEVELOPERS line 777
Quoted 13 lines
This is an initial list of Buildroot developers. It has been created semi-automatically by parsing the Git history, and finding the authors of commits with a title like "<foo>: new package". Some additional manual tweaking has been done (merging multiple entries corresponding to the same person, adding some more entries, etc.).
Signed-off-by Thomas Petazzoni <[email protected]>---
DEVELOPERS new file +4
-0+ +N: Julien Boibessot <[email protected]> +F: configs/armadeus* +F: package/libcddb/
I guess Julien want to take care of opentyrian :)
DEVELOPERS line 1001
Quoted 5 lines
DEVELOPERS new file +5
-0+ +N: Nicolas Menegale <[email protected]> +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.
Quoted 1 line
+N: Romain Naour <[email protected]>
Please update my address with romain.naour at gmail.com
DEVELOPERS line 1154
Quoted 8 lines
DEVELOPERS new file +8
-0+F: package/bullet/ +F: package/efl/ +F: package/iqvlinux/ +F: package/liblinear/ +F: package/mcelog/ +F: package/openpowerlink/ +F: package/stress-ng/ +F: package/terminology/
Here are some missing packages:
+F: package/elementary/
+F: package/expedite/
+F: package/xenomai/
Quoted 1 line
+N: Thomas Petazzoni <[email protected]>
[snip]
DEVELOPERS line 1359
Quoted 2 lines
DEVELOPERS new file +2
-0+F: package/enlightenment/ +F: package/libevas-generic-loaders/
Thomas, I'd like to take these two packages on my list ;-)
Also some packages are not listed yet, like busybox. I could be interesting to list all orphan packages.
Best regards,
Romain
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 5 lines · Romain Naour
DEVELOPERS line 777
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Julien Boibessot <[email protected]> +F: configs/armadeus* +F: package/libcddb/I guess Julien want to take care of opentyrian :)
Added.
Quoted 7 lines
DEVELOPERS line 1001
Quoted 4 lines
DEVELOPERS new file +4
-0+N: Nicolas Menegale <[email protected]> +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.
Quoted 3 lines
Quoted 1 line
+N: Romain Naour <[email protected]>
Please update my address with romain.naour at gmail.com
Done.
Review
Quoted 4 lines
Here are some missing packages:
(quoted diff) +3
-0+F: package/elementary/ +F: package/expedite/ +F: package/xenomai/
Added.
Quoted 6 lines
Quoted 1 line
+N: Thomas Petazzoni <[email protected]>
[snip]
DEVELOPERS line 1359
Quoted 2 lines
DEVELOPERS new file +2
-0+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.
Quoted 2 lines
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
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Thomas PetazzoniQuoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Hi,
Quoted 10 lines
This is an initial list of Buildroot developers. It has been created semi-automatically by parsing the Git history, and finding the authors of commits with a title like "<foo>: new package". Some additional manual tweaking has been done (merging multiple entries corresponding to the same person, adding some more entries, etc.).
Signed-off-by Thomas Petazzoni <[email protected]>DEVELOPERS new file +2
-0+N: Peter Korsgaard <[email protected]> +F: package/flickcurl/
DEVELOPERS line 1067
Quoted 10 lines
DEVELOPERS new file +10
-0+F: package/libfastjson/ +F: package/lzop/ +F: package/python-alsaaudio/ +F: package/python-enum/ +F: package/python-enum34/ +F: package/python-ipaddr/ +F: package/python-pam/ +F: package/python-psutil/ +F: package/triggerhappy/ +F: package/wpa_supplicant/
I know this is just a first try (and I don't mind), but interesting that your script flagged me for wpa_supplicant (and nobody else), considering I have never used it in buildroot, a number of other people have added new features and fixes, and my last real fix to it was in 2010.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 4 lines · Peter Korsgaard
I know this is just a first try (and I don't mind), but interesting that your script flagged me for
wpa_supplicant(and nobody else), considering I have never used it in buildroot, a number of other people have added new features and fixes, and my last real fix to it was in 2010.
It's because of commit 6828f982b89c4f85101fb8cfd5987ae4b1992de8:
commit 6828f982b89c4f85101fb8cfd5987ae4b1992de8
Author: Peter Korsgaard <[email protected]> Date: Mon Mar 9 20:28:40 2009 +0000
wpa_supplicant: new package
Patch by Gustavo Zacarias <[email protected]>
Closes #81.
The patch was indeed provided by Gustavo, but you are the author of the patch, and that's what my script was looking at.
I'll change that and put Gustavo as the referee for the wpa_supplicant package.
Thanks for the feedback!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Quoted 16 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Thomas" == Thomas Petazzoni <[email protected]> writes:
Hello,
Quoted 4 lines · Peter Korsgaard
I know this is just a first try (and I don't mind), but interesting that your script flagged me for
wpa_supplicant(and nobody else), considering I have never used it in buildroot, a number of other people have added new features and fixes, and my last real fix to it was in 2010.It's because of commit
6828f982b89c4f85101fb8cfd5987ae4b1992de8:commit
6828f982b89c4f85101fb8cfd5987ae4b1992de8Author: Peter Korsgaard <[email protected]> Date: Mon Mar 9 20:28:40 2009 +0000
Quoted 8 lines
wpa_supplicant: new packagePatch by Gustavo Zacarias <[email protected]>
Closes #81.
The patch was indeed provided by Gustavo, but you are the author of the patch, and that's what my script was looking at.
Ahh, ok. And your script really looks for something like
'<foo>: new package' and not just the first commit for for E.G. every .mk file?
E.G. it didn't flag me as developer for package/opus:
commit c226de26ec1379a88f7fe0e278ceb5888b92a054
Author: Peter Korsgaard <[email protected]> Date: Tue Sep 11 22:45:08 2012 +0200
package: add opus audio codec library
or package/pulseaudio:
commit d96e977e372a9b7b7c681fc7bc6902211273ea1e
Author: Peter Korsgaard <[email protected]> Date: Wed Oct 19 15:25:11 2011 +0200
package: add pulseaudio
or package/jquery:
commit 4e20e8fe00b7125e2fe4538c69c6560f5bb75121
Author: Peter Korsgaard <[email protected]> Date: Sun Dec 18 23:11:14 2011 +0100
package: add Javascript menu and jQuery package
A lot of open source Javascript libraries can be interesting to use on embedded systems, so add a specific Javascript menu and the probably most well known library of them all, jQuery.
Quoted 2 lines
I'll change that and put Gustavo as the referee for the
wpa_supplicantpackage.
great!
Quoted 1 line
Thanks for the feedback!
You're welcome, the series looks OK to me.
Signature · 2 lines
Venlig hilsen, Peter Korsgaard
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 4 lines · Peter Korsgaard
Ahh, ok. And your script really looks for something like
'<foo>: new package' and not just the first commit for for E.G. every .mk file?
Yes, I've looked at "<foo>: new package" commits. Looking at the first commit if each .mk file would have been a better approach indeed. I can try to have a look at this alternative approach, and see if it brings some additional/better details.
Quoted 3 lines
Quoted 1 line
Thanks for the feedback!
You're welcome, the series looks OK to me.
Thanks. I believe the Python code could definitely get some review, but follow-up patches are also possible to improve the implementation.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Thomas PetazzoniHi Thomas,
DEVELOPERS line 112
Quoted 5 lines · Thomas Petazzoni
DEVELOPERS new file +5
-0+N: Arnout Vandecappelle <[email protected]> +F: package/freescale-imx/firmware-imx/ +F: package/freescale-imx/imx-lib/ +F: package/gstreamer/gst-fsl-plugins/ +F: package/moarvm/
This one was an accident: I took over the patch from Francois and slightly
amended it, but then I committed with --reset-author (I have an alias for git commit --amend --reset-author -C HEAD). I actually have no idea what moarvm does :-)
DEVELOPERS line 116
Quoted 4 lines
DEVELOPERS new file +4
-0+F: package/owfs/ +F: package/python-bottle/ +F: package/sqlcipher/ +F: package/stress/
All of these were really drive-by patches, I don't use any of them regularly.
And in fact, I think that that will be the case for the majority of the packages that are listed now.
I'm afraid that maintaining the DEVELOPERS file (pruning dead e-mail addresses,
removing people that are no longer interested in a particular package) is going to take more effort (i.e. more commits) than we actually gain by putting the developers in Cc.
So for this initial version, I'd suggest keeping just the people that we know
are active. Basically the people who have responded to this patch :-) And then in the contributing documentation, invite people to also update the DEVELOPERS file with their entry.
Regards,
Arnout
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Arnout" == Arnout Vandecappelle <[email protected]> writes:
Hi,
Quoted 14 lines
DEVELOPERS line 116
Quoted 4 lines
DEVELOPERS new file +4
-0+F: package/owfs/ +F: package/python-bottle/ +F: package/sqlcipher/ +F: package/stress/All of these were really drive-by patches, I don't use any of them regularly.
And in fact, I think that that will be the case for the majority of the packages that are listed now.I'm afraid that maintaining the DEVELOPERS file (pruning dead e-mail addresses,
removing people that are no longer interested in a particular package) is going to take more effort (i.e. more commits) than we actually gain by putting the developers in Cc.
Quoted 4 lines
So for this initial version, I'd suggest keeping just the people that we know
are active. Basically the people who have responded to this patch :-) And then in the contributing documentation, invite people to also update the DEVELOPERS file with their entry.
Yes, I also think we should start small and see how it goes.
Signature · 1 line
Bye, Peter Korsgaard
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 9 lines · Peter Korsgaard
Quoted 8 lines
All of these were really drive-by patches, I don't use any of them regularly.
And in fact, I think that that will be the case for the majority of the packages that are listed now.I'm afraid that maintaining the DEVELOPERS file (pruning dead e-mail addresses,
removing people that are no longer interested in a particular package) is going to take more effort (i.e. more commits) than we actually gain by putting the developers in Cc.
Quoted 6 lines
Quoted 4 lines
So for this initial version, I'd suggest keeping just the people that we know
are active. Basically the people who have responded to this patch :-) And then in the contributing documentation, invite people to also update the DEVELOPERS file with their entry.Yes, I also think we should start small and see how it goes.
I disagree, see my reply to Arnout for the reasons why.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Arnout VandecappelleHello,
Quoted 10 lines · Arnout Vandecappelle
DEVELOPERS line 112
Quoted 5 lines · Thomas Petazzoni
DEVELOPERS new file +5
-0+N: Arnout Vandecappelle <[email protected]> +F: package/freescale-imx/firmware-imx/ +F: package/freescale-imx/imx-lib/ +F: package/gstreamer/gst-fsl-plugins/ +F: package/moarvm/This one was an accident: I took over the patch from Francois and slightly
amended it, but then I committed with --reset-author (I have an alias for git commit --amend --reset-author -C HEAD). I actually have no idea what moarvm does :-)
ACK, I'm moving this package to Fran?ois.
Quoted 8 lines
DEVELOPERS line 116
Quoted 4 lines
DEVELOPERS new file +4
-0+F: package/owfs/ +F: package/python-bottle/ +F: package/sqlcipher/ +F: package/stress/All of these were really drive-by patches, I don't use any of them regularly.
And in fact, I think that that will be the case for the majority of the packages that are listed now.
Shall I remove those packages from your name?
Quoted 4 lines
I'm afraid that maintaining the DEVELOPERS file (pruning dead e-mail addresses,
removing people that are no longer interested in a particular package) is going to take more effort (i.e. more commits) than we actually gain by putting the developers in Cc.
Then I don't think you've been doing this "Analysis of autobuilder results" enough times. It's a very long and boring work to look at those autobuilder issues, analyze them quickly, and try to remember by head which developer is the most appropriate for the different packages/issues in order to Cc the relevant people.
So I completely disagree that maintaining this file will be more work than putting the developers in Cc. Or at least, I can say that the work will be spread on the shoulders of everyone (every developer submitting a new package) instead of just being on my shoulders, when doing the analysis of autobuilder results.
Or maybe you just volunteered to do the analysis of the autobuilder results ? :-)
Quoted 4 lines
So for this initial version, I'd suggest keeping just the people that we know
are active. Basically the people who have responded to this patch :-) And then in the contributing documentation, invite people to also update the DEVELOPERS file with their entry.
I also completely disagree with this. Keeping only the people that we know are active would be _entirely_ useless. The people that we know are active... well they are already active, so there's little point Cc'ing them some additional e-mails: they already look at the autobuilder issues regularly, they fix their own packages, and even packages submitted by others, etc.
The whole point of this DEVELOPERS file is to increase the set of developers who help in fixing the autobuilder issues, and in reviewing new patches coming in that touch packages they know about.
By adding a large initial set of developers, even people who are rarely active, we let those people know that we need their help to continue maintain the packages they contributed. In the best case, since they will receive a direct e-mail, they will notice, and help us. In the worst case, they will ignore the e-mail or maybe better let us know they are no longer interested in Buildroot (in which case we can decide what to do with the problematic package).
So having a minimal DEVELOPERS file would be pretty much entirely against the point of having it.
Best regards,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Thomas PetazzoniHi Thomas,
DEVELOPERS line 31
Quoted 4 lines · Thomas Petazzoni
DEVELOPERS new file +4
-0+ +N: Abhishek Singh <[email protected]> +F: package/cxxtest/ +
Abhishek is no longer with IMG, I can volunteer for this package.
Thanks,
Rahul
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 8 lines · Rahul Bedarkar
DEVELOPERS line 31
Quoted 4 lines · Thomas Petazzoni
DEVELOPERS new file +4
-0+ +N: Abhishek Singh <[email protected]> +F: package/cxxtest/ +Abhishek is no longer with IMG, I can volunteer for this package.
Thanks for the notification, I've updated the DEVELOPERS file accordingly, it will be in my v3.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Thomas Petazzoni2016-08-23 8:47 GMT-04:00 Thomas Petazzoni
<[email protected]>:
Quoted 65 lines
This is an initial list of Buildroot developers. It has been created semi-automatically by parsing the Git history, and finding the authors of commits with a title like "<foo>: new package". Some additional manual tweaking has been done (merging multiple entries corresponding to the same person, adding some more entries, etc.).
Signed-off-by Thomas Petazzoni <[email protected]>--- DEVELOPERS | 1542 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1542 insertions(+) create mode 100644 DEVELOPERSDEVELOPERS new file +47
-0@@ -0,0 +1,1542 @@ +# Syntax: +# +# N: Firstname Lastname <email> +# F: file pattern or directory +# F: file pattern or directory +# +# The "F" entries can be: +# +# - A directory, in which case all patches touching any file in this +# directory or its subdirectories will be CC'ed to the developer. +# - A pattern, in which case the pattern will be expanded, and then +# all files/directories (and their subdirectories) will be +# considered when matching against a patch +# +# Notes: +# +# - When a developer adds an "arch/Config.in.<arch>" file to its list +# of files, he is considered a developer of this architecture. He +# will receive e-mail notifications about build failures occuring on +# this architecture. Not more than one e-mail per day is sent. +# - When a developer adds a directory that contains one or several +# packages, this developer will be notified when build failures +# occur. Not more than one e-mail per day is sent. +# - When a developer adds an "package/pkg-<infra>.mk" file to its list +# of files, he is considered interested by this package +# infrastructure, and will be CC'ed on all patches that add or +# modify packages that use this infrastructure. + +N: Abhishek Singh <[email protected]> +F: package/cxxtest/ + +N: Adam Duskett <[email protected]> +F: package/nginx-naxsi/ + +N: Alex Suykov <[email protected]> +F: package/vboot-utils/ + +N: Alexander Clouter <[email protected]> +F: package/odhcp6c/ + +N: Alexander Dahl <[email protected]> +F: package/fastd/ +F: package/libuecc/ +F: package/putty/ + +N: Alexander Lukichev <[email protected]> +F: package/openpgm/
DEVELOPERS line 57
Quoted 10 lines
DEVELOPERS new file +10
-0+ +N: Alexander Varnin <[email protected]> +F: package/liblog4c-localtime/ + +N: Alexandre Belloni <[email protected]> +F: package/tz/ + +N: Alistair Francis <[email protected]> +F: package/xen/ +
Can I please have a second email added?
Alistair Francis <[email protected]>
I need to keep my company email here, but it is much easier to do list work from my gmail. If not what's here now is fine.
Thanks,
Alistair
[...]
Quoted 8 lines
--
2.7.4_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 10 lines · Alistair Francis
DEVELOPERS line 57
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Alistair Francis <[email protected]> +F: package/xen/ +Can I please have a second email added?
Alistair Francis <[email protected]>
I need to keep my company email here, but it is much easier to do list work from my gmail. If not what's here now is fine.
Having two e-mail addresses is currently not supported, but it can probably be added without too much efforts, though I'm not sure to do it for this version of the patch series (and rather handle that as a possible future improvement). Would this be OK?
In fact, thinking about this, using simply a comma to separate both e-mail addresses might even work as-is, but I would have to test first.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Quoted 15 lines · Thomas Petazzoni
Hello,
Quoted 10 lines · Alistair Francis
DEVELOPERS line 57
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Alistair Francis <[email protected]> +F: package/xen/ +Can I please have a second email added?
Alistair Francis <[email protected]>
I need to keep my company email here, but it is much easier to do list work from my gmail. If not what's here now is fine.
Quoted 7 lines
Having two e-mail addresses is currently not supported, but it can probably be added without too much efforts, though I'm not sure to do it for this version of the patch series (and rather handle that as a possible future improvement). Would this be OK?
In fact, thinking about this, using simply a comma to separate both e-mail addresses might even work as-is, but I would have to test first.
No worries. Can you just change my email to just use my gmail one instead? That should be fine and should make communication easier.
Thanks,
Alistair
Quoted 6 lines
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
In reply to Thomas PetazzoniHello Thomas,
Quoted 5 lines · Thomas Petazzoni
This is an initial list of Buildroot developers. It has been created semi-automatically by parsing the Git history, and finding the authors of commits with a title like "<foo>: new package". Some additional manual tweaking has been done (merging multiple entries corresponding to the same person, adding some more entries, etc.).
Nice initiative !
Quoted 37 lines
Signed-off-by Thomas Petazzoni <[email protected]>--- DEVELOPERS | 1542 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 1542 insertions(+) create mode 100644 DEVELOPERSDEVELOPERS new file +24
-0@@ -0,0 +1,1542 @@ +# Syntax: +# +# N: Firstname Lastname <email> +# F: file pattern or directory +# F: file pattern or directory +# +# The "F" entries can be: +# +# - A directory, in which case all patches touching any file in this +# directory or its subdirectories will be CC'ed to the developer. +# - A pattern, in which case the pattern will be expanded, and then +# all files/directories (and their subdirectories) will be +# considered when matching against a patch +# +# Notes: +# +# - When a developer adds an "arch/Config.in.<arch>" file to its list +# of files, he is considered a developer of this architecture. He +# will receive e-mail notifications about build failures occuring on +# this architecture. Not more than one e-mail per day is sent. +# - When a developer adds a directory that contains one or several +# packages, this developer will be notified when build failures +# occur. Not more than one e-mail per day is sent. +# - When a developer adds an "package/pkg-<infra>.mk" file to its list
DEVELOPERS
Quoted 10 lines
DEVELOPERS new file +8
-0+# of files, he is considered interested by this package +# infrastructure, and will be CC'ed on all patches that add or +# modify packages that use this infrastructure. + + +N: Julien Boibessot <[email protected]> +F: configs/armadeus* +F: package/libcddb/
+ board/armadeus/*
+ package/gpm
+ package/lbreakout2
+ package/libmodbus
+ package/ltris
+ package/opentyrian
+ package/pygame
+ package/smstools3
[...]
Thanks !
Regards,
Julien
PATCH 2/4 DEVELOPERS: add initial list of Buildroot developers
Hello,
Quoted 5 lines · Julien Boibessot
DEVELOPERS line 777
Quoted 3 lines
DEVELOPERS new file +3
-0+N: Julien Boibessot <[email protected]> +F: configs/armadeus* +F: package/libcddb/+ board/armadeus/*
This last "*" is not needed. Directories are by default handled recursively. Patterns are only needed if you want to match several directories, like package/python-* for example.
Quoted 7 lines
+ package/gpm
+ package/lbreakout2
+ package/libmodbus
+ package/ltris
+ package/opentyrian
+ package/pygame
+ package/smstools3
All added, thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
PATCH 3/4 docs/manual: update contribute.txt to cover get-developers
In reply to Thomas PetazzoniThis commit updates the contribute.txt part of the manual to tell people to use get-developers to get the appropriate "git send-email" command when sending patches.
--- docs/manual/contribute.txt | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
docs/manual/contribute.txt +10 -2
@@ -283,10 +283,18 @@ automatically adding the +Signed-off-by+ line. Once patch files are generated, you can review/edit the commit message before submitting them, using your favorite text editor. -Lastly, send/submit your patch set to the Buildroot mailing list: +Buildroot provides a handy tool to know to whom your patches should be +sent, called +get-developers+. This tool reads your patches and +outputs the appropriate +git send-email+ command to use: --------------------- -$ git send-email --to buildroot at buildroot.org outgoing/* +$ ./support/scripts/get-developers outgoing/* +--------------------- + +Use the output of +get-developers+ to send your patches: + +--------------------- +$ git send-email --to buildroot at buildroot.org --to bob --to alice outgoing/* --------------------- Note that +git+ should be configured to use your mail account.
Signature · 1 line
2.7.4
PATCH 4/4 docs/manual: add new section about the DEVELOPERS file and get-developer
In reply to Thomas Petazzoni--- docs/manual/developers.txt | 45 +++++++++++++++++++++++++++++++++++++++++++++ docs/manual/manual.txt | 2 ++ 2 files changed, 47 insertions(+) create mode 100644 docs/manual/developers.txt
docs/manual/developers.txt new file +45 -0
@@ -0,0 +1,45 @@ +// -*- mode:doc; -*- +// vim: set syntax=asciidoc: + +== DEVELOPERS file and get-developers + +The main Buildroot directory contains a file named +DEVELOPERS+ that +list the developers in charge of various areas of Buildroot. Thanks to +this file, the +get-developer+ tool allows to: + +- Calculate the list of developers to whom patches should be sent, by + parsing the patches and matching the modified files with the + relevant developers. See xref:submitting-patches[] for details. + +- Find which developers are in charge of a given architecture or + package, so that they can be notified when a build failure occurs on + this architecture or package. This is done in interaction with + Buildroot's autobuild infrastructure. + +We ask developers adding new packages, new boards, or generally new +functionality in Buildroot, to register themselves in the +DEVELOPERS+ +file. As an example, we expect a developer contributing a new package +to include in his patch the appropriate modification to the ++DEVELOPERS+ file. + +The +DEVELOPERS+ file format is documented in detail inside the file +itself. + +The +get-developer+ tool, located in +support/scripts+ allows to use +the +DEVELOPERS+ file for various tasks: + +- When passing one or several patches as command line argument, + +get-developer+ will return the appropriate +git send-email+ + command. + +- When using the +-a <arch>+ command line option, +get-developer+ will + return the list of developers in charge of the given architecture. + +- When using the +-p <package>+ command line option, +get-developer+ + will return the list of developers in charge of the given package. + +- When using the +-c+ command line option, +get-developer+ will look + at all files under version control in the Buildroot repository, and + list the ones that are not handled by any developer. The purpose of + this option is to help completing the +DEVELOPERS+ file. +
docs/manual/manual.txt +2 -0
@@ -64,6 +64,8 @@ include::debugging-buildroot.txt[] include::contribute.txt[] +include::developers.txt[] + = Appendix include::appendix.txt[]
Signature · 1 line
2.7.4
PATCH 4/4 docs/manual: add new section about the DEVELOPERS file and get-developer
Quoted 26 lines · Thomas Petazzoni
Signed-off-by Thomas Petazzoni <[email protected]>--- docs/manual/developers.txt | 45 +++++++++++++++++++++++++++++++++++++++++++++ docs/manual/manual.txt | 2 ++ 2 files changed, 47 insertions(+) create mode 100644 docs/manual/developers.txtdocs/manual/developers.txt new file +13
-0@@ -0,0 +1,45 @@ +// -*- mode:doc; -*- +// vim: set syntax=asciidoc: + +== DEVELOPERS file and get-developers + +The main Buildroot directory contains a file named +DEVELOPERS+ that +list the developers in charge of various areas of Buildroot. Thanks to +this file, the +get-developer+ tool allows to: + +- Calculate the list of developers to whom patches should be sent, by + parsing the patches and matching the modified files with the + relevant developers. See xref:submitting-patches[] for details. +
docs/manual/developers.txt line 23
Quoted 10 lines
docs/manual/developers.txt new file +10
-0+- Find which developers are in charge of a given architecture or + package, so that they can be notified when a build failure occurs on + this architecture or package. This is done in interaction with + Buildroot's autobuild infrastructure. + +We ask developers adding new packages, new boards, or generally new +functionality in Buildroot, to register themselves in the +DEVELOPERS+ +file. As an example, we expect a developer contributing a new package +to include in his patch the appropriate modification to the ++DEVELOPERS+ file.
As I hinted in my reply to patch 2, I would also add this message to the end of
the "The formatting of a patch" section in contribute.txt. Something like:
If you are interested in getting notified of build failures and of further changes in the packages you modified, please add yourself to the DEVELOPERS file. This should be done in a separate patch of the series. See xref:DEVELOPERS[the DEVELOPERS file] for more information.
(and add [[DEVELOPERS]] to the developers section).
Regards,
Arnout
Quoted 36 lines
docs/manual/developers.txt new file +22
-0+ +The +DEVELOPERS+ file format is documented in detail inside the file +itself. + +The +get-developer+ tool, located in +support/scripts+ allows to use +the +DEVELOPERS+ file for various tasks: + +- When passing one or several patches as command line argument, + +get-developer+ will return the appropriate +git send-email+ + command. + +- When using the +-a <arch>+ command line option, +get-developer+ will + return the list of developers in charge of the given architecture. + +- When using the +-p <package>+ command line option, +get-developer+ + will return the list of developers in charge of the given package. + +- When using the +-c+ command line option, +get-developer+ will look + at all files under version control in the Buildroot repository, and + list the ones that are not handled by any developer. The purpose of + this option is to help completing the +DEVELOPERS+ file. +docs/manual/manual.txt +2
-0@@ -64,6 +64,8 @@ include::debugging-buildroot.txt[] include::contribute.txt[] +include::developers.txt[] + = Appendix include::appendix.txt[]
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
PATCH 4/4 docs/manual: add new section about the DEVELOPERS file and get-developer
Hello,
Quoted 9 lines · Arnout Vandecappelle
As I hinted in my reply to patch 2, I would also add this message to the end of
the "The formatting of a patch" section in contribute.txt. Something like:If you are interested in getting notified of build failures and of further changes in the packages you modified, please add yourself to the DEVELOPERS file. This should be done in a separate patch of the series. See xref:DEVELOPERS[the DEVELOPERS file] for more information.
(and add [[DEVELOPERS]] to the developers section).
Thanks for the suggestion, added.
While adding this, I noted that the references like:
xref:label[some description]
are not rendered just has "some description" in the HTML, but as:
"some description <the title of the section pointed to>"
For example, for:
Before reporting any issue, please check in xref:community-resources[the mailing list archive] whether someone has
you get:
Before reporting any issue, please check in the mailing list archive Chapter 5, Community resources whether someone has
which is not very pretty.
Maybe someone with AsciiDoc knowledge can look into this?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com