search

coq / coq.github.io

Source files of the coq.inria.fr website
https://coq.inria.fr/
Other
15 stars 37 forks source link

Update to Zulip. List more communication channels. #148

Closed Zimmi48 closed 4 years ago

Zimmi48 commented 4 years ago

Screenshot:

2020-06-05-163325_665x387_scrot

@anton-trunov, @JasonGross and others: am I missing some active Coq places?

Maybe we should list Codewars somewhere on the community page but I'm not sure where it fits best.

JasonGross commented 4 years ago

Should/do we mention coqdev?

am I missing some active Coq places?

Does the GitHub issue tracker count? ;-)

Zimmi48 commented 4 years ago

Should/do we mention coqdev?

IMO coqdev is deprecated in favor of the Dev category of Discourse. When I find some time to do it, I'd like to set things up so that messages to this category are automatically forwarded to Coqdev subscribers and messages sent to Coqdev are forwarded to Discourse.

Does the GitHub issue tracker count? ;-)

It is already mentioned in the "How to contribute?" box on the homepage. Should it be repeated here as well?

anton-trunov commented 4 years ago

@anton-trunov, @JasonGross and others: am I missing some active Coq places?

I concur with @JasonGross on including the GitHub issue tracker into the official communication channel. It looks like it might be a good idea to explicitly include it here. For instance, I've seen a lot of questions on SO which essentially were reporting some issues (usually with CoqIDE or PG).

anton-trunov commented 4 years ago

Maybe we should list Codewars somewhere on the community page but I'm not sure where it fits best.

That's a great idea! Perhaps it could go to the documentation page (https://coq.inria.fr/documentation)? It's kind of a set of exercises on steroids, so including it alongside with books and tutorials may seem like a nice addition.

Zimmi48 commented 4 years ago

Thanks for the feedback! I've restored the listing of the GitHub issue tracker. I'll add Codewars to the documentation page.