Request clarifiactions about social/PCLinuxOS packager conventions

[sling-shot]

We have an unknown number of existing packager's at present.
We also do not know who is working on what and who has worked on what and who is currently on vacation/busy/left the distro.
We have some dedicated packagers who do a lot of heavy lifting and we have some packagers who package whenever time permits.

I am very apprehensive about stepping on the toes of existing packagers by becoming overzealous and doing something that they are already doing. It will also be a waste of man hours doing the same thing over and over.

Things like KDE / VLC / Firefox etc are probably well known and our pillars of packaging must be working on them. And they will know if someone who regularly does that has stopped or not.
However things become murky about the fringe packages.

Eg. rekonq. I have seen the package request for 2.0 release sitting for sometime unattended. I have done a job on it (hopefully good). But was it sitting because the packager who routinely does it was busy or because no one was doing it?

How about a wiki page listing packages, version, last updated by, date of last packaging, next version available, scheduled to be packaged by

Code: [Select]

dukto    R5   sling-shot   22-12-2012  not-released   not-scheduled

Also will there be a time period after which the package can be deemed to be allowed to be touched by another free packager?

[gseaman]

I've wondered about this a few times, myself. But, I decided to work on any package request that had no responses, as time permits. Hopefully, I haven't interfered with anyone else's work, but I trust that they will tell me if I do. Also, I have packaged a couple of simpler ones, that got submitted by someone else first. I don't worry about it. The packages that take a lot of work are usually the ones that noone is  working on!

Galen

[kjpetrie]

I would think the main thing is to post that you're working on it so someone else doesn't start duplicating your effort. Also, I've sometimes forgotten to check it's not in testing already before starting work!

It's annoying (for both the packager and Neal) to submit something only to be told it's already in testing, or to have someone reply to your request for help in packagers by saying they've just dropped it into dropbox!

[sling-shot]

I have been confused by some of our regular packagers using differing names / identities at different places / times.

I have consistently been using sling-shot as my identity everywhere including my signature.

I suppose I could just ask by PM of whom I need to know