@Columbus I invited you on GitHub to be a member of the coq-community organization. When you accept, I can make you admin of topology and zorns-lemma. We usually recommend people to do proposed changes via pull requests for branches in the repo rather than a fork (making it easier for others to add to a topic branch)
please take a look at our templates for the general workflow on how to update boilerplate like CI configuration: https://github.com/coq-community/templates
we also have a recommended project structure that you could consider for your projects: https://github.com/coq-community/manifesto/wiki/Recommended-Project-Structure
Thanks for the links. I haven’t noticed the wiki yet.
Is there a "style guide" or something about the formatting of the code/proofs?
there is nothing general for Coq style/formatting, but here are some examples of project-specific styles:
Ok, thanks. I also know of the HoTT Style guide.
with some colleagues, I'm working on a machine learning based tool that can suggest formatting/style (short abstract with examples https://arxiv.org/abs/2006.16743), but we are quite far from being generally usable yet
another example: https://github.com/uwplse/verdi-raft/blob/master/STYLE.md
:D that’d be nice
this is a good guide for best practices which are not style related: https://www.ssi.gouv.fr/uploads/2014/11/anssi-requirements-on-the-use-of-coq-in-the-context-of-common-criteria-evaluations-v1.0-en.pdf
I remember reading that one.
there are also tools/plugins that can help with maintenance, e.g., https://github.com/Karmaki/coq-dpdgraph
we try to maintain a list of useful stuff (resources/tools) at https://github.com/coq-community/awesome-coq
Last updated: Feb 05 2023 at 15:03 UTC