oasisprotocol / oasisprotocol/oasis-core
Cleanup/unify terminology
Open
Nobody has claimed this yet.
c:docs
p:3
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Currently we have a bunch of things called backend, module etc. We should probably go through everything and make sure things are named consistently and clearly.
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 no files, tests, or entry points, and asks for a project-wide terminology review. Start by inventorying the terms mentioned in the repository, then establish consistent replacements and a complete list of affected locations; done means the naming is clear and consistent throughout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100