Draft of call for contributors/maintainers for Stdlib
send on:
The Rocq Stdlib, the historical standard library of the Rocq Prover (formerly Coq), is at a turning point. While its development has faced challenges in the past decade, it remains a critical piece of the ecosystem, widely used and offering unique features. With a dedicated repository now separate from Rocq core, we see an opportunity to renew and modernize it. To achieve this, we are launching a call for contributors and maintainers to help shape the future of the library.
We recently gave the Rocq Stdlib a brand new repository distinct from the Rocq core repository, the later only retaining a minimal subset of files shared by most users (named Corelib). We hope that this new setting will help foster a renewal of the library.
At this point, the Rocq Stdlib offers some unique features and is massively used. However, there has been no team dedicated to its development for several years and we now want one to make it a solid, state of the art library on which Rocq projects can rely on.
The future of the Rocq Stdlib is open-ended and ready to be shaped by
those who step forward. We aim to:
We are looking for contributors and maintainers of all experience levels. Whether you’re a seasoned Rocq developer or a newcomer there is a place for you.
Given the library’s breadth, volunteers can focus on specific domains (e.g., real numbers, lists, etc. - see https://rocq-prover.org/doc/V9.0.0/stdlib/index.html).
As a part of Rocq's official projects, the Stdlib follows the Rocq Governance rules. However, there are no rigid rules yet regarding release cycles and specific governance rules can be defined collectively by those involved.
To ensure that the Stdlib development is a safe and agreeable experience, the development of Rocq Stdlib follows Rocq's code of conduct.
We hope that contributors will:
Interested? Let us know on the dedicated zulip channel. A brief note on your background and intended contribution would be helpful, but all interest statements are welcome, even with a small expected involvement or a limited prior experience.
(TODO) We aim to organize a first video call to launch development in June, in conjunction with the Rocq'n share first event.
Let’s work together to bring new life to the Rocq Stdlib!
or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Do you want to remove this version name and description?
Syncing