linkedin / linkedin/dr-elephant
Development instructions
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 839
- PR merge metrics
- No merged PRs in 30d
Description
The current version of development instructions suggests to dist/deploy after each change. Clearly this approach doesn't scale. Is there a way to work on Dr. E omitting these steps? A step-by-step guide for people unfamiliar with Play or a list of useful references would be very helpful.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the current development instructions and the Play-based development workflow. Document a way to work without running dist/deploy after every change, then add a step-by-step guide and useful references for newcomers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100