[arch-dev-public] Looking for co-maintainers (and proposal to join cross toolchain packages)
Hi all, Over the past few weeks, perhaps months(?), I have been struggling a little bit with mental health and that has made it a bit harder to keep up-to-date with packaging. For this reason, I would like find co-maintainers for my packages, so that it eases things in times like this. Feel free to adopt any of my packages, just let me know via email or IRC that you have done so. https://archlinux.org/packages/?maintainer=FFY00 Some of the packages that give me the most work are the cross toolchains, not because they are difficult to maintain, they aren't, they just take some work. I was wondering if perhaps we could maybe join them together in one single PKGBUILD? Anatol, Eli, NicoHood and Felix maintain the rest of the cross toolchains, so if they agree maybe we could join all architectures into a single PKGBUILD for each component? Cheers, Filipe Laíns
On Wed, Jun 16, 2021 at 07:30:47PM +0100, Filipe Laíns via arch-dev-public wrote:
Hi all,
Over the past few weeks, perhaps months(?), I have been struggling a little bit with mental health and that has made it a bit harder to keep up-to-date with packaging.
Hey, I'm sorry to hear about this. Besides the maintainership, please know that I'm here if you ever want to talk about things.
For this reason, I would like find co-maintainers for my packages, so that it eases things in times like this. Feel free to adopt any of my packages, just let me know via email or IRC that you have done so.
I'm adding a list at the bottom to help people prioritize adoptions. This in theory should be the packages that have Filipe as the only maintainer. FWIW, I'll be helping with openocd as I use it often. I'm also going to take on blackmagic and python-libevdev :)
Some of the packages that give me the most work are the cross toolchains, not because they are difficult to maintain, they aren't, they just take some work. I was wondering if perhaps we could maybe join them together in one single PKGBUILD? Anatol, Eli, NicoHood and Felix maintain the rest of the cross toolchains, so if they agree maybe we could join all architectures into a single PKGBUILD for each component?
Cheers, Filipe Laíns
Cheers! -Santiago santiago at ~/.../contrib/package ✔ ./pkgsearch -m FFY00 adrdox ansible-bender at51 blackmagic bluefish budgie-extras cm256cc cockatrice code codec2 cycfx2prog dbxtool d-containers discord d-mir-core dsdcc d-stdx-allocator easy-pdk entr evolution-on fcrackzip flterm fontobene-qt5 fusesoc ghdl gifski gir-to-d glibd grub-theme-vimix hamlib hid-tools iio-sensor-proxy inspectrum libad9361 libosmosdr libratbag lightdm-webkit2-greeter lightdm-webkit-theme-litarvan limesuite liquidctl liquid-dsp lm32-elf-binutils lm32-elf-gcc lm32-elf-gdb lm32-elf-newlib log4cpp lrzip lutris mbelib monkeytype multimon-ng mustache-d nds32le-elf-binutils nds32le-elf-gcc nds32le-elf-newlib netcf openfpgaloader openocd or1k-elf-binutils or1k-elf-gcc or1k-elf-gdb or1k-elf-newlib pasystray pcbdraw peek piper podman-compose ppc64le-elf-binutils ppc64le-elf-gdb prjtrellis prjtrellis-db prjxray-db proxmark3 pulseaudio-equalizer-ladspa pyannotate python2-importlib-metadata python-aiohttp-apispec python-aiomysql python-aiopg python-aiosqlite python-asyncpg python-auditwheel python-bitcoinlib python-build python-clickclick python-colorlog python-connexion python-contextlib2 python-covdefaults python-databases python-dill python-docutils-stubs python-edalize python-euclid3 python-fastapi python-flake8-typing-imports python-flit python-httptools python-install python-installer python-intelhex python-ipyxact python-jsonmerge python-keyring python-kikit python-libcst python-libevdev python-libusb1 python-linkify-it-py python-litedram python-liteeth python-liteiclink python-litejesd204b python-litepcie python-litesata python-litescope python-litesdcard python-litevideo python-litex python-litex-boards python-markdown2 python-zc.lockfile
participants (2)
-
Filipe Laíns
-
Santiago Torres-Arias