The Coq mailing list

[Anton Trunov <anton.a.trunov AT gmail.com>]

Hi Jim,

I guess both of them deserve an upvote :)
But upvoting Zimmi48’s comment should help us get that logo!
Taking the opportunity, I’d like to thank the Coq Clubbers, Twitter users, 
Redditors, and the Telegram Dependent Types community for all the upvotes.

Best,
Anton

> On 1 Jul 2018, at 22:13, Jim Fehrle 
> <jfehrle AT sbcglobal.net>
>  wrote:
> 
> Ah, upvote on your comment or on the first comment from arasatasygin?  I 
> suppose the former?
> 
> From: Théo Zimmermann 
> <theo.zimmi AT gmail.com>
> To: Coq Club 
> <coq-club AT inria.fr>
>  
> Sent: Sunday, July 1, 2018 6:43 AM
> Subject: [Coq-Club] Call for participation: coq-community, collaborative 
> long-term maintenance and advertisement of Coq packages
> 
> Hello Coq-Club,
> 
> We are launching coq-community (https://github.com/coq-community), a new 
> organization of volunteer Coq users for the long-term, collaborative 
> maintenance of Coq packages, the collaborative writing of documentation, 
> and the advertisement of valuable packages.
> 
> If you don't have time to read this e-mail in full, you can still help us 
> get a nice logo by up-voting the comment presenting coq-community here 
> https://github.com/arasatasaygin/openlogos/issues/1#issuecomment-401606081 
> (provided that you have a GitHub account).
> 
> We would like to thank the Coq workshop organizers for having proposed a 
> 15-minute slot for presentation and discussion of coq-community (out of the 
> 30 minutes normally devoted to the Coq development team, next Sunday at 3pm 
> in Oxford).
> 
> coq-community will be a community-driven effort with the following 
> objectives:
> 
> - Providing a place for the collaborative, long-term maintenance of Coq 
> packages.
> - Collaborative writing of documentation.
> - Advertisement of interesting Coq packages.
> 
> In a first phase of this effort, we will focus on the first objective 
> (maintenance). We are looking for volunteer Coq users to become official 
> maintainers. You don't need to be a very experienced Coq user to become a 
> maintainer. You can also propose packages to move to coq-community even if 
> you don't wish to become their maintainer.
> 
> In a second phase of this effort, the collaborative writing of 
> documentation and the advertisement of selected packages will be overseen 
> by an editorial board which will be composed of prominent and experienced 
> members of the Coq user community. If you are already interested to be part 
> of such a board, please let us know by writing to Pierre Castéran 
> (pierre.casteran AT labri.fr)
>  and myself 
> (theo AT irif.fr).
> 
> I'll let you discover everything there is to read about coq-community at: 
> https://github.com/coq-community/manifesto
> 
> Sincerely,
> Théo Zimmermann
> 
>