review example
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 164
- Forks
- 69
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 5
Description
Comment by Yani
Llegar al comentario correspondiente no me funciona muy bien; se me va de la pantalla (pero capaz que sea un problema de mi interfaz). El otro problema es que está en inglés. Como no puedo leerlo, no sé muy bien si el adjetivo "duro" es adecuado en este caso, ni qué podríamos reemplazarlo por un ejemplo en castellano.
- Ejemplo duro pero constructivo: la parte de esta revisión que sugiere una reescritura de la viñeta: [ropensci/software-review#191 (comentario)](https://github.com/ropensci/software-review/issues/191#issuecomment-368254623).
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
Start with the quoted Markdown example and follow the linked rOpenSci software-review comment to understand the referenced feedback. Review the wording around “Ejemplo duro pero constructivo” and replace it with a suitable Spanish example or phrasing, preserving the link and Markdown format. Done means the example is understandable in Spanish and accurately reflects the linked review comment.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100