Hello Viktor,
thanks for the pointers. Please note that upstream development of
courier and the Debian packaging for courier are somewhat different
projects.
You're mostly mentioning upstream work and issues. I guess upstream
needs to decide how they want to work.
For the Debian packaging, it's certainly going to be the Debian BTS for
bug reporting, as it's tightly integrated with all of the existing
Debian infrastructure. But I'm subscribed to the relevant courier-*
mailing lists [0] and I'll have a look at the bugs and patches you
mentioned. Don't expect me to do feature development for courier, though.
Kind Regards
Markus Wanner
[0]: Please note that I'm subscribed to lots of mailing lists, but I'm
certainly not reading all of it. Therefore, please CC me for a heads-up.
On 03/23/2017 09:59 PM, SZÉPE Viktor wrote:
Would it be possible to enable very easy bug reporting?
I have two here: https://github.com/szepeviktor/courier/issues
I think discussion in a Debian bug report is quiet hard.
On GitHub it is very easy to contribute.
Sam merged a lot of Debian patches as you may know.
https://github.com/szepeviktor/courier/commit/bca5316f40bf9335c9ec36db850916481e99cd2c
And we have final break-through with CNAMEs (Amazon SES, Mailjet etc.)
https://github.com/svarshavchik/courier-libs/commit/5e522ab14f45c6f4f43c43e32a2f72fbf6354f1c
And you can read on courier-users that many are willing to contribute.
All the best to you!
SZÉPE Viktor
https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md