rocq-prover / rocq-prover/stdlib
Maintaining NaryFunctions
Open
Nobody has claimed this yet.
- Dominant language
- Rocq Prover
- Stars
- 42
- Forks
- 38
- Avg merge
- 14h 6m
- Merged PRs (30d)
- 3
Description
Saw the deprecation notice for NaryFunctions.v. I do not use that module but would be happy to step up to maintain it in the name of backwards compatibility.
What are the expectations of a maintainer in this role?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names NaryFunctions.v and its deprecation notice but no file, test, or entry point. First review that module and the notice, then clarify the expectations and scope of the maintainer role; done is an agreed maintenance scope rather than a specified code change.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100