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.

Sign up for GitHub

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

Jump to bottom

contributing: Use word addon consistently #929

Merged
merged 1 commit into from
Jul 18, 2023
Merged

contributing: Use word addon consistently #929

merged 1 commit into from
Jul 18, 2023

Conversation

wenzeslaus
Copy link
Member

  • Use addon as a word (replace all AddOn by addon).
  • Remove git (Git) from title. No need to distinguish from Subversion. Use the word code, to distinguish it from documentation or from a place where binaries or such things would be uploaded.
  • Simplify the sentences by removing repetitions of GRASS...addon... where repository is enough.
  • Name the cloned directory just like the repo is named, but still be explicit.
  • Mention the compilation with g.extension (other compilation instructions would still use some improvements).
  • Use addon as an adjective and don't say addons modules.
  • Consider scripts as modules (both C and Python can be a module, i.e., a tool).
  • Mention RFC2 first, write access only at the end.
  • Replace Track wiki links by GitHub source code where possible.

@wenzeslaus
contributing: Use word addon consistently
fafde24 
- Use addon as a word (replace all AddOn by addon).
- Remove git (Git) from title. No need to distinguish from Subversion. Use the word code, to distinguish it from documentation or from a place where binaries or such things would be uploaded.
- Simplify the sentences by removing repetitions of GRASS...addon... where repository is enough.
- Name the cloned directory just like the repo is named, but still be explicit.
- Mention the compilation with g.extension (other compilation instructions would still use some improvements).
- Use addon as an adjective and don't say addons modules.
- Consider scripts as modules (both C and Python can be a module, i.e., a tool).
- Mention RFC2 first, write access only at the end.
- Replace Track wiki links by GitHub source code where possible.
@wenzeslaus wenzeslaus added the manual Documentation related issues label Jul 18, 2023
@wenzeslaus wenzeslaus merged commit a2c75eb into OSGeo:grass8 Jul 18, 2023
6 checks passed
@wenzeslaus wenzeslaus deleted the consistent-addon-naming branch July 18, 2023 19:01
cwhite911 pushed a commit to cwhite911/grass-addons that referenced this pull request Sep 19, 2023
@wenzeslaus
contributing: Use word addon consistently (OSGeo#929)
fd320c4 
- Use addon as a word (replace all AddOn by addon).
- Remove git (Git) from title. No need to distinguish from Subversion. Use the word code, to distinguish it from documentation or from a place where binaries or such things would be uploaded.
- Simplify the sentences by removing repetitions of GRASS...addon... where repository is enough.
- Name the cloned directory just like the repo is named, but still be explicit.
- Mention the compilation with g.extension (other compilation instructions would still use some improvements).
- Use addon as an adjective and don't say addons modules.
- Consider scripts as modules (both C and Python can be a module, i.e., a tool).
- Mention RFC2 first, write access only at the end.
- Replace Track wiki links by GitHub source code where possible.
@echoix echoix mentioned this pull request Dec 22, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
manual Documentation related issues
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@wenzeslaus