Fixed #30573 -- Rephrased documentation to avoid words that minimise the involved difficulty.#11482
Conversation
|
Hey @rixx. Thanks for this. (Can't remember what I actually said, but 👍 🙂)
Perfect. 😀 @claudep, @felixxm makes a good point on the ticket about creating work for the translation teams (so not to backport). Tim often would mention the need for re-translations too. Can I ask, what's the general maxim there? And, for me, this patch seems positive and in line with what we aim for generally, so is it reasonable, without putting too much burden on our current volunteers? (I'm just not sure of the state of play. Thank you!) |
claudep
left a comment
There was a problem hiding this comment.
From a translator point of view, please avoid backporting to current docs. As for the wording, I'm not fluent enough in English to judge.
b3cbba8 to
d322d9f
Compare
I have to admit that I hadn't thought of the additional burdon for translators. If you judge this PR to have an unhelpful ratio of effort for translators as opposed to its usefulness, we can definitely decide to close it. |
|
I think the sentiment, that we eliminate the "just" and "obviously" and so on is right. And it can't be that we can't make improvements — but knowing the work it involves is helpful to judge. Obviously (🙂) there's no hard line; I was fishing for rule-of-thumb guidance... (Thanks again.) |
|
If this is really improving the docs (not simple nit-picking), you should do it. I just say that the stable docs should only be changed for real errors, because between the push and the translations going on-line, there is a gap of ~1 month where those strings appear untranslated. |
|
OK, thanks @claudep. That's a good guiding principle. |
adamchainz
left a comment
There was a problem hiding this comment.
Reviewed about 20% so far... 😱
In general a great improvement 👍
adamchainz
left a comment
There was a problem hiding this comment.
Second review, next file to review is docs/topics/db/search.txt
docs/internals/contributing/writing-code/submitting-patches.txt
Outdated
Show resolved
Hide resolved
docs/internals/contributing/writing-code/submitting-patches.txt
Outdated
Show resolved
Hide resolved
cd535e4 to
4c497a4
Compare
|
I think I addressed all your review comments by resolving them, except for two which I replied to. Thank you so much for reviewing this little monster! |
|
Nice work! |
|
Right, got the rebase conflict addressed, too, so this is looking good, pending further review :) |
adamchainz
left a comment
There was a problem hiding this comment.
I'm approving but if you want to leave for a bit to see if anyone else has the heart to read all this, fair enough :)
|
I'm completely happy with your review, I just saw that there was "1 pending reviewer" in the GitHub interface, so I wasn't sure how this was going to proceed. I don't need a second review ;) |
I want to go through this, so it's that's me. It's on the list for this week. 🙂 |
carltongibson
left a comment
There was a problem hiding this comment.
Hi @rixx.
Just before diving into the individual changes, I think, having gone to this effort, we should add a paragraph/sentence to writing-documentation.txt in the Writing style section, saying to avoid using simple etc in this way. What do you think?
Absolutely, I added a change like that. Feel free to correct the phrasing, as always. |
fafe9ae to
085156b
Compare
|
Right, roll-up sleeves... I rebased and pulled the Style suggestion into a separate commit cf9e66fe58e198faf647a07b2ab5625dba417985. (@felixxm We could pull that in already no?) I'll go through the text changes one-by-one now. (Given how many changes there are, I think I'll push an Edits commit to allow review of any suggestions... — incoming. 🙂) |
|
@carltongibson Sure, merged and backported (I fixed one typo). |
085156b to
cfa59eb
Compare
|
Thanks @felixxm! |
cfa59eb to
4fd0cf6
Compare
carltongibson
left a comment
There was a problem hiding this comment.
Right. Wowser. That took a while. 😅
I've pushed edits. @rixx — please have a look.
- I felt a bit sorry for "Just" and "Simple" — they're not always minimisers. Sometimes they have import. I've restored those I felt essential. I've let some go, thinking that leaning towards being strict is fine now, as they'll leak back in over time, and we've probably over-used in the past.
- There were a few purely cosmetic re-wraps. These were correct, AFAICS, so I left them, not having the energy to pull them out.
- I reverted the man page change as @felixxm will do that he branches for 3.0.
Thank you for your effort here! 🥇
@felixxm: This is good to go for me (with a squash). There may be one or two little regressions I've missed, but overall the patch is good — I think it should be much more approachable for folks (like me) who aren't entirely convinced that e.g. writing custom migration operations is simple 🙂. If you have bandwidth to review before we branch stable/3.0.x then super. If not I think we should take it anyway.
|
@carltongibson Thank you very much for your review! Apart from one typo, your changes look fine to me. I also sympathised with "just" and "simple", and left many of them in place, but I appreciate your reverts. I guess after some time staring at the same words, I leaned too much on the side of removal. Regarding the cosmetic rewraps: I tried to remove all of them and just rewrap paragraphs ends following my changes. If you'd like me to, I can check the PR again and see what should be reverted? |
4fd0cf6 to
c1ba079
Compare
|
Typo fixed. 👍
If you have energy... They weren't incorrect so I left them. At this point I'd be happy to see them left. (@felixxm may have an opinion, which he'll state if he does 🙂)
Yes. 😀 Much effort. Hard to do. Hard to review. You've done a great job here. |
…the involved difficulty. This patch does not remove all occurrences of the words in question. Rather, I went through all of the occurrences of the words listed below, and judged if they a) suggested the reader had some kind of knowledge/experience, and b) if they added anything of value (including tone of voice, etc). I left most of the words alone. I looked at the following words: - simply/simple - easy/easier/easiest - obvious - just - merely - straightforward - ridiculous Thanks to Carlton Gibson for guidance on how to approach this issue, and to Tim Bell for providing the idea. But the enormous lion's share of thanks go to Adam Johnson for his patient and helpful review.
c1ba079 to
4a954cf
Compare
|
Thanks y'all 🌟 |
Obviously (heh.) this patch does not remove all occurrences of the words
in question. Rather, I went through all of the occurrences of the words
listed below, and judged if they a) suggested the reader had some kind
of knowledge/experience, and b) if they added anything of value
(including tone of voice, etc). I left most of the words alone. I looked
at the following words:
Thanks to Carlton Gibson for guidance on how to approach this issue, and to Tim Bell for providing the idea.
Ticket link: https://code.djangoproject.com/ticket/30573