Interested in an Updated Progit2 Re-Edited?

Open
#2,030 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
git
Domain
documentation

Research direction

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.

Written by the indexing model from the issue text.

Description

enhancement
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

Dominant language
CSS
Stars
6.6k
Forks
2.1k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from progit/progit2

All issues in progit/progit2

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.