Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal to move Velisarios to Coq-community #59

Open
palmskog opened this issue Mar 23, 2019 · 6 comments
Open

Proposal to move Velisarios to Coq-community #59

palmskog opened this issue Mar 23, 2019 · 6 comments
Labels
coq-extraction coq-library move-project Move a project to coq-community.

Comments

@palmskog
Copy link
Member

Move a project to coq-community

Project name: Velisarios

Initial author(s): Vincent Rahli, Ivana Vukotic, Marcus Völp, and Paulo Esteves-Verissimo

Current URL: https://github.com/vrahli/Velisarios

Kind: Coq library and extractable program

License: GPL-3.0-or-later

Description: Velisarios is a framework for verification of Byzantine fault-tolerant distributed systems, which contains an executable implementation of the PBFT algorithm.

Status: maintained (but current version on GitHub needs update for Coq 8.9)

New maintainers: Vincent Rahli (@vrahli) and Karl Palmskog (@palmskog)

PBFT is an important Coq case study. The main purpose of moving Velisarios to Coq-community (while keeping initial authors as maintainers) is to ease long-term maintenance via CI and other automation. In particular, Dune will be helpful for the executable PBFT implementation. I also suggest that Velisarios should join Coq's CI.

@palmskog palmskog added the move-project Move a project to coq-community. label Mar 23, 2019
@palmskog
Copy link
Member Author

palmskog commented Mar 23, 2019

@vrahli can you confirm here that everything looks good with the above, and that you're OK with moving the original repository to the Coq-community organization? Feel free to propose more maintainers from your team.

@Zimmi48 can you invite @vrahli to the organization so he gets full access?

Note that my main motivation as co-maintainer would be to ensure working builds for Coq 8.9 and beyond to enable proof engineering research on the project. I'm fine with any other further evolution of the project.

@spitters
Copy link

Interesting. Perhaps you can expand the readme a bit. Is there a connected paper?
The coq-tools directory seems like material that perhaps should be moved to a more central place.

@Zimmi48
Copy link
Member

Zimmi48 commented Mar 24, 2019

@spitters It seems like this is the corresponding paper: https://link.springer.com/chapter/10.1007/978-3-319-89884-1_22

@palmskog Sure I've invited @vrahli to the organization.

@vrahli
Copy link

vrahli commented Mar 24, 2019 via email

@Zimmi48
Copy link
Member

Zimmi48 commented Apr 9, 2019

@vrahli Since you have joined the organization, you should now be able to transfer your two repositories. Let me know if that's not the case or if you need help.

@Zimmi48
Copy link
Member

Zimmi48 commented Jun 26, 2019

@vrahli Do you still intend to transfer this project and NuprlInCoq to coq-community? If yes, let me know if you need help with the transfer operation. If not, we should close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coq-extraction coq-library move-project Move a project to coq-community.
Projects
None yet
Development

No branches or pull requests

5 participants