[oe] Do we need a patch queue (Patchwork)?

[Paul Menzel]

Dear OE folks,


(This is the last organizational message I will write today.)

We currently have a patch queue/tracker called Patchwork [1][2] which
should be used according to the documentation in the Wiki.

The current situation though is that nobody seems to use it anymore, i.
e. does not update the patch state. (Also because of some problems with
registration.)

Before the move to oe-core and meta-oe there were some people caring
about Patchwork and going through the uncommitted each quarter or so.
Currently this is not the case anymore.

Should the system be shut down or do we still need it?

### benefits ###

1. Patches are easy to apply from Patchwork when not having access to
the email program with the list inbox.
2. Old patches are not forgotten.
3. Patch state can be tracked and the thread representation is more
concise then the list archive.
4. Searching for patches on the Web most of the time the first hits
point to the threads in Patchwork.

### downsides ###

1. It is a lot of work to update the patch state manually.
2. A lot of people refuse to use it.


We could also say that the current installation will stay at is and that
it is only used to import patches easily and for getting the discussion
overview. I am fine with that, but the documentation needs to be
updated!


Thanks,

Paul


[1] http://patches.openembedded.org/project/oe/list/
[2] http://openembedded.org/index.php?title=Patchwork
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20110915/daed4f16/attachment-0002.sig>