Patches for pjproject missing upstream submission
Issue generated from Tuleap's migration script. Originally submitted by: Andrey Gursky (agur)
Hi,
I'd like to ask you to open a ticket on pjproject's trac for every patch or add a comment like "doesn't need forwarding because ..." This will make it easier to manage them.
Ideally, you could add the following fields on the top of each patch (similar to Debian policy):
Description: why it is needed and what it does
Author:
Bug: https://tuleap.ring.cx/...
Forwarded: https:// (or not needed because ...)
Last-Update:
BTW, feel free to apply this not only for pjproject but all patches used by Ring.
Thanks,
Andrey
P.S. While it is, you know, possible to patch every open source project in use, it is not a common practice (for upstream). And you could imagine, what would happen if this would be widely practiced - distribution packaging would become useless, security audit become harder, more disk space / RAM consumption and so on.