Hi,

So with mato's package autobuilds churning and flagging problems that someone needs to fix, I've been thinking it would be nice if every package had a maintainer (or maintainers), who at least pretended to be interested in keeping the package working. That maintainer would have push access to repo.rumpkernel.org/rumprun-packages so that 1) issues can be assigned to them 2) they can fix the problems quickly. Submitting a package would require becoming a maintainer or finding one. Of course, open source being open source, some maintainers would fade away over time, but at least we'd know who to turn for ones which are active maintained.

There's both good and bad in a maintainer model, but at least I wouldn't have to remember who's capable of fixing problems in package X, or designating the last person who touched the package as maintainer du jour.

I sort of attempted a "maintainer" template in the mpg123 package, but I'm not quite happy with how it looks. What would be the sensible content?

thoughts?

Reply via email to