Coq Call 2021 10 20 - rocq-prover/rocq GitHub Wiki
Topics
Notes
- meaning of issue assignment
- Everyone should go through their assigned issues and remove those they are not actively working on / do not plan to actively work on soon
- We could get coqbot to remind people about stale assignments to issues (but let's wait to see if we actually need it before implementing it)
- Intention of issue assignment is "I intend to work on this"
- https://github.com/coq/coq/pull/14616 (delayed building of app terms)
- applying to the Open Science Free Software Award (Théo)
- Théo suggests that Coq would be a good fit for this award
- We discussed the subprizes and how relevant they are for Coq. How to best present the Strengths of Coq?
- Community is where we excel most:
We have a large (and scientific) user base + package ecosystem
Coq is a scientific tool used commonly in many places
- We should apply for the prize if it only brings benefits
- Publicity? But then do we need to finalize the name change first?
- Highlights work on community building / software engineering / documentation
- Do comments come before or after statements in .mli? (Ali)
- Take a look at https://github.com/coq/coq/pull/14718#pullrequestreview-784325464 (Ali)
- Some unicode normalization issues still remain
- Discuss factoring directory code between coqdep and coqtop (Ali)
- when to update the website with respect to a new release (need to wait for a platform release / announcement)? (Théo, follow-up of discussion at https://coq.zulipchat.com/#narrow/stream/237656-Coq-devs.20.26.20plugin.20devs/topic/Coq.20Website).
-> delayed to next week