You are not logged in.
Pages: 1
I have a question about arch-etiquette. I looked froward an answer around, but did not find it.
If one or more apps in the repos are out-of-date from a lot if time (a couple of months), have been already flagged as out-of-date, but nobody seems to care, is it wise and polite to email directly the maintainer? Or is it a rude behaviour I should avoid, since any maintainer has a well-established priorities list?
In this specific case, the apps I care about are xchat and moc (maintained by the same person), but I would like to know how I should behave in any other analogous situation.
Thanks for any tip.
Mortuus in anima, curam gero cutis
Offline
The maintainers have indeed a well-established priority list. some applications are hold back for specific reasons, though don't know if that's the case for xchat and moc. As maintainers know which packages are flagged out of date, I would not email them about that, as they know what tasks they have, and what has priority.
If you can't wait for certain apps, you can always use abs to build the newer version.
Offline
Although I would have my reasons (I hope i would at least) for not upgrading something for that long, I wouldnt have any problem with anyone emailing me about it if I had not made any announcements.
But hey, im the new dev on the block, not sure what other's preferences are.
James
Offline
moc was updated two days ago, btw.
Offline
I guess the devs are under highest pressure. Everybody wants this and that. As a non-dev, I would mark a package as outdated, and don't ask, presuming no packages are orphaned and devs have a lot more to do then answering my direct input. But maybe I am too polite.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
i do not like people emailing me, for example dbus was held back because no new functionality would be added and we need to rebuild xfce/gnome and kde... so no fun...
so not always everything will be updated instantly
if people want a reason they should talk to me on irc
Freedom is what i love
Offline
I've had several PMs, emails, forum posts and I guess also a bugreport that krusader is out of date. It's not on my top-priority todo list, so it could take a while. At this moment, priority is getting the latest gnome, kde and gstreamer releases good enough for current/extra. After this, I'm able to update many of my out-of-date packages.
Offline
Mayby we could help pkg maintainers somehow?
For example I made a PKGBUILD for the newest krusader and I could send it to JGC that he would have less work. (or mayby more? :> )
Offline
I don't mind emails. The only exception is people flagging bmp when it's a dead project. Hence the bmpx in testing.
Offline
I guess that the prevealing answer is that I should not send emails, it is enough to flag tha package outdated and to wait. I had no opinion, I only wanted to know how to behave. Thanks for your opinions and arguments.
Mortuus in anima, curam gero cutis
Offline
Would it be possible, in the future (possible) integration with AUR, to have a list of comments to each package in the official repos?
The comments should be editable only by the maintainers, if there's something to tell about that package (or users start sending out-of-date mails). The webpage is a good place to put such comments because the web interface is the only place these notifications can be sent from. Also, it might be a good place to display install comments (the ones in post_install for example).
This way communication problems as the ones described above might be avoided.
:: / my web presence
Offline
That would mean additional work for the maintainers. They do newsletters and postings enough, if you kindly read them. I'ld vote a nay.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
Pages: 1