Refactoring / Code Improvements discussion
Open
Nobody has claimed this yet.
discussion
- Dominant language
- Java
- Stars
- 4.1k
- Forks
- 673
- PR merge metrics
- No merged PRs in 30d
Description
Wednesday May 24, 2017 at 18:34 GMT
Originally opened as https://github.com/4pr0n/ripme/issues/557
@Gaboso Let's talk about which changes need to be done, style guidelines, etc. If we're going to make a push to improve code quality, let's also strive for consistency.
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. Read the existing discussion and repository-wide contribution or style guidance first, then identify a specific agreed refactoring scope. Work is complete only when the discussion defines a concrete change and its acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100