-
Notifications
You must be signed in to change notification settings - Fork 23
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
release FCF through coq-released and Coq Platform? #48
Comments
I'm not opposed to the idea, but I don't know if there is enough justification, as required by the inclusion criteria. I'm not even aware if anyone has used it in the last 5 years other than me. @andrew-appel are you aware of significant uses of FCF, or did you have some other justification in mind? |
It seems to be used by (1) VST testcases and (2) @andres-erbsen, two external users independent of the FCF developer and of each other. That might be enough for the Coq Platform, and it's certainly enough to justify inclusion in coq-released. |
Thanks for the info! I'm still not opposed to the idea, but I'm not willing to be the maintainer. So I think we will need a volunteer for this part. |
Since FCF is useful and seems to have at least one maintainer (for example, @andres-erbsen), I suggest that FCF should be released via opam in the coq-released archive, and then added to the Coq Platform.
Does anyone else think this is a good idea, and is anybody willing to be a "maintainer" for the purposes of this process? If so, there's at least one member of the Coq Platform board who will advocate for it.
The text was updated successfully, but these errors were encountered: