On 9/30/20 6:57 AM, Ruth Ivimey-Cook wrote:
For my own purposes I have created some patches which apply to the current mailman pip package.
I'm only responding here to the issue of how to suggest patches. If you hope that they could be incorporated into the distribution, posting them to this list is not very effective. It is too easy for list posts to get lost, buried or forgotten.
The best thing to do is to create an issue or issues at https://gitlab.com/mailman/mailman/-/issues (each issue should address only one thing). Then you can either attach the suggested patch to the issue or better, create a merge request with the patch to fix the issue. Ideally, the merge request would also contain relevant additions to unit tests.
The first advantage is open issues do not get lost. They are always there in the tracker.
The second is that all of the above is work that needs to be done in order to actually get the patch into the master branch, and the more of it you do, the less of it needs to be done by someone else who may not be as motivated as you are.
Granted, this may seem like a burden for you. After all, you fixed your problem so why bother, but open source works best if we all contribute what we can to improve the product.
-- Mark Sapiro firstname.lastname@example.org The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan