Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[doc] Revise the glossary documentation #5837

Merged
merged 1 commit into from
Jan 13, 2025

Conversation

tengqm
Copy link
Contributor

@tengqm tengqm commented Dec 11, 2024

What changes were proposed in this pull request?

This PR fixes the glossary docs.

Why are the changes needed?

The glossary is reordered for quick reference.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

N/A

@justinmclean
Copy link
Member

Please do not break sentences over multiple lines as this breaks some tooling.

docs/glossary.md Outdated Show resolved Hide resolved
@tengqm
Copy link
Contributor Author

tengqm commented Dec 12, 2024

Please do not break sentences over multiple lines as this breaks some tooling.

No. I don't agree with this. Long lines are hard to review, hard to maintain, hard to read even in an IDE.

@justinmclean
Copy link
Member

justinmclean commented Dec 12, 2024

IDE wrap lines, so that's not really an issue. As I explained elsewhere, if you break up lines, tools like grammar and style checkers that we use will not work. Some people who contribute to this project don't have English as their first language and rely heavily on these tools.

@tengqm
Copy link
Contributor Author

tengqm commented Dec 12, 2024

IDE wrap lines, so that's not really an issue. As I explained elsewhere, if you break up lines, tools like grammar and style checkers that we use will not work. Some people who contribute to this project don't have English as their first language and rely heavily on these tools.

No. It is an issue, and a very annoying issue. Please refer this comment.
Different people (including developers) see different things (I'm not using your IDE),
that is an additional issue. This is like the TAB usage scenario.
Grammar or style checker is not a valid reason for this change.
I was not encouraging breaking a long line in the middle.
I was suggesting to break long lines APPROPRIATELY, at statement boundary, at punctuation.

@tengqm
Copy link
Contributor Author

tengqm commented Dec 12, 2024

Check this change and tell me ... how this change is breaking your IDE syntax checker?
Can you elaborate how this "line breaks" hurts anything?

image

@justinmclean
Copy link
Member

That change is fine. The issue occurs when you break up a sentence over several lines.

@justinmclean
Copy link
Member

Changes like this cause the issue:
image

@tengqm
Copy link
Contributor Author

tengqm commented Dec 12, 2024

Okay, let me revise this further. Breaking those long sentences to simple English.

@jerryshao
Copy link
Contributor

@justinmclean would you please help to review again? Thanks.

docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
docs/glossary.md Outdated Show resolved Hide resolved
@tengqm
Copy link
Contributor Author

tengqm commented Jan 7, 2025

All comments addressed as suggested. Many thanks for the review.

@jerryshao jerryshao added the branch-0.8 Automatically cherry-pick commit to branch-0.8 label Jan 10, 2025
Copy link
Member

@justinmclean justinmclean left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update.

@justinmclean justinmclean merged commit b2b2338 into apache:main Jan 13, 2025
25 checks passed
github-actions bot pushed a commit that referenced this pull request Jan 13, 2025
### What changes were proposed in this pull request?

This PR fixes the glossary docs.

### Why are the changes needed?

The glossary is reordered for quick reference.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

N/A
Abyss-lord pushed a commit to Abyss-lord/gravitino that referenced this pull request Jan 14, 2025
### What changes were proposed in this pull request?

This PR fixes the glossary docs.

### Why are the changes needed?

The glossary is reordered for quick reference.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

N/A
@tengqm tengqm deleted the doc-glossary branch January 16, 2025 03:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-0.8 Automatically cherry-pick commit to branch-0.8
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants