Interested in an Updated Progit2 Re-Edited?
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Documentación
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Stack tecnológico
- git
- Área
- documentation
Línea de trabajo
Start by reviewing the proposed changes in the linked nobozo/progit2-re repository and comparing them with the current ProGit 2nd Edition. Done means determining whether the re-edited version's copy-editing changes should be accepted and integrated, or whether the proposal should be declined.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
General overview of your idea.
About 6 or 7 years ago I offered you a large number of changes to
ProGit 2nd Edition. These were the kind of changes that a professional
copy editor would make, and weren't technical at all.
At the time, you weren't interested in these changes, so I published what I called
ProGit 2nd Edition Re-Edited on GitHub so that readers could judge for themselves.
I have no idea how many people downloaded my version. However, due to work pressure,
I stopped paying attention to either your version or my version, which is where
things stayed until about 2 weeks ago. Then, I decided then to re-insert my changes
into the latest version of ProGit 2nd Edition, which I've done. It's available at
https://github.com:nobozo/progit2-re.git
Please take a look at the changes. Frankly, I'd rather not continue to maintain my re-edited version
so I hope you're interested. If not, then please let me know so I can, again, publish my re-edited
version.
Cordially,
Jon Forrest
What problem will this solve?
The current version is often excessively wordy, and sometimes unclear. My edits go a long way to improving things.
Have you thought about other solutions?
No response
Do you want to help with this enhancement idea?
Yes
- Lenguaje dominante
- CSS
- Estrellas
- 6.6k
- Forks
- 2.1k
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de progit/progit2
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Semi-stale link for GitHosting Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
-
enhancement
Dificultad 1/5 1-3 horas Aptitud para principiantes 65/100
Todos los issues de progit/progit2
Issues similares
-
Link Checker Report Abiertoautomated issue report
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
components-web-app/docs#99 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
TheOdinProject/curriculum#31423 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
-
hcocena Abiertopolicies-accepted pre-review precheck-passed
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Bioconductor/BiocContributions#214 · 5 comentarios ·