Requesting co-maintainers and maintainers for lots of packages

ShadowKyogre · 2019-09-05 02:30:50

It's been a while since I posted on the forums. Recently life's made it hard to attend to the AUR and other coding situations like I used to. The original post about it is on the aur-general mailing list.

https://lists.archlinux.org/pipermail/a … 35332.html

Since making that post, the following occurred to me.

I still like doing AUR work. But it's not something I can reliably provide like before. So I'm not sure how to handle being able to do it on the sidelines without making myself seem unavailable on purpose.
People might not be willing to pick up a package after it's been orphaned due to not knowing the maintenance problems I've had with some packages in the past.
Some packages might not be used enough to know when the sources are broken, thus needing updating.
Some packages required maintenance from upstream developers due to no one else being available to maintain it.

So I've compiled a list of packages that need co-maintainers, those that I've kept due to low maintenance time, and those that are potentially orphanable due to maintenance circumstances. This list can be found here.

https://write.as/l15zfw3838y89q0c.md

Is there anything else I should do to make it easier for future maintainers to help ease their workload?

Lone_Wolf · 2019-09-05 16:06:50

You could group them differently .

some examples
mse-* packages appear to be related to magicseteditor and "Magic : The Gathering"
I'd put all of them in 1 group to catch the attention of Magic:The gathering users.

many of the packages you list under" Co-Maintainers ASAP" are related to compiz & emerald.
separate those from the non-compositor related packages.

ShadowKyogre · 2019-09-06 14:58:34

Hi Lone_Wolf. Took the time today to rearrange the contents of the listing by project first, then source availability second. Does the new grouping look more accessible now? I've archived the previous revision of the listing and put a link to it on the main listing page.

Lone_Wolf · 2019-09-07 11:36:45

Yes, new grouping is an improvement.

I loooked at hypervc & ninit, but their upstream devs seems to have vanished.
Keeping old code working is not something i'm good at.

Last edited by Lone_Wolf (2019-09-07 11:39:53)

progandy · 2019-09-07 12:29:22

That list looks good. I am not good at maintaing packages I have no real interest in, though. Still, here are some possible sources you can add:

The author of wallpaperd has archived it in a git repository: https://github.com/pekdon/wallpaperd

As for magicseteditor, in my opinion the 2.0.1 version is just the SVN trunk compiled by some users. Or maybe someone chose the version bump without tag as the 2.0.1 release: https://sourceforge.net/p/magicseteditor/code/1729/
There is also a fork available with changes from 2015: https://github.com/msoucy/MagicSetEditor/

PeterBB · 2021-05-06 10:53:25

ShadowKyogre wrote:

...
I've compiled a list of packages that need co-maintainers, those that I've kept due to low maintenance time, and those that are potentially orphanable due to maintenance circumstances. This list can be found here.
https://write.as/l15zfw3838y89q0c.md
...

I would like to adopt or co-maintain qosmic. The PKGBUILD needs updating due to changes in some build dependencies, namely Lua & ICU.

This is my suggestion for the new PKGBUILD

# Contributor: Anton Bazhenov <anton.bazhenov at gmail>
# Contributor: Nick B <Shirakawasuna at gmail _dot_com>
# Contributor: mar77i <mysatyre at gmail dot com>
# Contributor: PeterB <peter at pblackman dot plus dot co.uk>
# Maintainer:  ShadowKyogre
 
pkgname=qosmic
pkgver=1.6.0
pkgrel=2
pkgdesc="An application for creating, editing, and rendering flam3 fractal images"
arch=('i686' 'x86_64')
url="https://github.com/bitsed/qosmic"
license=('GPL')
depends=('qt5-base' 'lua52' 'flam3')

source=(
	"${pkgname}-${pkgver}.tar.gz::https://github.com/bitsed/qosmic/archive/v${pkgver}.tar.gz"
	"missing-qbuttongroup-include.patch::https://aur.archlinux.org/cgit/aur.git/plain/missing-qbuttongroup-include.patch?h=qosmic"
	"lua.patch::https://patch-diff.githubusercontent.com/raw/bitsed/qosmic/pull/36.patch"
	"externc.patch::https://github.com/bitsed/qosmic/commit/bd184ab2a1d8fc11d45225018dd1ee9795da57ab.patch"
)

prepare() {
  cd "$srcdir/$pkgname-$pkgver"
  patch -Np1 -i "${srcdir}/missing-qbuttongroup-include.patch"
  patch -Np1 -i "${srcdir}/lua.patch"
  patch -Np1 -i "${srcdir}/externc.patch"

}

build() {
  cd "$srcdir/$pkgname-$pkgver"
  qmake-qt5
  # https://github.com/bitsed/qosmic/issues/28
  sed -i '/^DEFINES/ s/$/ -DLUA_COMPAT_5_2/' Makefile
  make
}

package() {
	cd "$srcdir/$pkgname-$pkgver"
	make INSTALL_ROOT="$pkgdir" install
}

sha256sums=('b61d5c6189a87701761005aa049f13e0e2f1863cba6a24397edc538f12a8a04b'
            '2b2f338dca2d35e9243baec72f2a28b2cee52ca9d90c96d7aacf8631476cab32'
            'ff44f6232f35c57a3080d76616454c7b600c7a008312e09de748f81672c97a05'
            'e3b7a2c388f96079e3bcb7234970839b6eb733c533576952c4b2a7814f355482')

Arch Linux

#1 2019-09-05 02:30:50

Requesting co-maintainers and maintainers for lots of packages

#2 2019-09-05 16:06:50

Re: Requesting co-maintainers and maintainers for lots of packages

#3 2019-09-06 14:58:34

Re: Requesting co-maintainers and maintainers for lots of packages

#4 2019-09-07 11:36:45

Re: Requesting co-maintainers and maintainers for lots of packages

#5 2019-09-07 12:29:22

Re: Requesting co-maintainers and maintainers for lots of packages

#6 2021-05-06 10:53:25

Re: Requesting co-maintainers and maintainers for lots of packages

Board footer