Gunicorn: mailing list for support & new features discussions

[benoitc]

I am able to setup a new mailing-list for gunicorn and would like to make it the only way to get help and advices on Gunicorn. Any tickets would be then closed in favour of a discussion to it. Thoughts?

[berkerpeksag]

+1 from me.

[tuukkamustonen]

There are some ancient messages at https://gitter.im/benoitc/gunicorn already - why not resurrect that instead?

Of course, mailing list vs. gitter serve different purpose, but I would say chat is more approachable and way more convenient when it comes to asking for help.

[benoitc]

cc @berkerpeksag @tilgovi thoughts? What's your preference?

I mean we can either setup a mailing list or using gitter or mail + irc as it used to be. I'm thinking using a mailing list is a way easier but let me know as it seems a lot of people are now using something like discourse instead.

[benoitc]

@tuukkamustonen sorry i missed that message :(

[berkerpeksag]

I'd prefer a mailing list (or anything other than GitHub) for support tickets. I think Gitter is also fine, but it's hard to archive or find quality responses for commonly asked questions (so we usually need to repeat the same response manually)

At Python, we've started to experiment with using Discourse. I don't know how hard to set up an instance (IIRC it's a Rails application) though.

[benoitc]

setting up a discourse is quite easy. I've done it myself a couple of time. And we can have mail replies too.

[benoitc]

It seems rust went to full forum but curious what @tilgovi think about it :)

[tilgovi]

I also prefer e-mail to GitHub for support tickets. I sometimes have users find my e-mail and send me mail directly anyway. I would like to be able to reply on a list, and have a searchable archive. Discourse is great forum software, and I'm happy to use that.

[benoitc]

@tilgovi it's unclear for me sorry :) I understand you're OK with discourse but prefer a mailing list?

[tilgovi]

I prefer email, not GitHub issues, for support. Discourse is great, because I can subscribe by email.

[jamadden]

FWIW (probably not much! 😄 ), I prefer GitHub issues...which I have subscribed to in email. I'm incredibly unlikely to subscribe to another mailing list.

[tilgovi]

I think that's the point for me :-). I would prefer users can have a support community and that GitHub is just for bug reports and development. But maybe that's wishful thinking and we'll still get support requests here no matter what we do.

I am fine to use GitHub for everything if others think it is best.

[jamadden]

gevent has a mailing list, and maybe 1/10 of the support requests go there. The vast majority wind up in github. Of course, I haven't particularly done anything to discourage that.

[benoitc]

@jamadden @tilgovi Long time ago I setup some project management rules.

But just checked it I failed to update the contributing doc and we never enforced them. I think I'm all for having on github somehow since it doesn't require much to maintain (nothing to install) and the moderation is easy. I propose to resurrect that and enforce it . To these Boards, it may be interresting to add running sprints/features in progress like flutter does

We can also be improved using templates:

I would also direct user either to irc or gitter. One advantage of using gitter is to setup the hooks to notify people about the activity on github.

plan

If we are all OK I propose the following plan:

• [ ] modify the contributing doc to reflect the project management as described in the wiki

• [ ] tag issues to have them correctly assigned to projects.

• [ ] update readme with gitter link

• [ ] update website and doc

• [ ] prune old issues or retag/sort issues

Thoughts?

[tilgovi]

That sounds good.

[benoitc]

@tilgovi cool :) are the current project topics OK? Should we have different column?

[tilgovi]

👍 from me

[benoitc]

closing the issue , i will open a new one asap corresponding.