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

Improve title #232

Closed
lgrapenthin opened this issue Apr 1, 2022 · 2 comments
Closed

Improve title #232

lgrapenthin opened this issue Apr 1, 2022 · 2 comments

Comments

@lgrapenthin
Copy link

"The Clojure Style Guide" as a title projects much more authority than this document has or should have. By using the definitive form it leaves no space for other. It makes unsuspecting readers believe that it is some official reference to adhere to. In sharp contrast, its introduction already clarifies that it consists of personally opinionated rules somebody assembled based on his "extensive career as a software engineer". This is a source for much confusion.

Here are some brainstormed ideas to improve upon:

  • "An unofficial Clojure Style Guide"
  • "My Clojure Style Recommendations"
  • "Clojure Style for extensive career"
  • "Clojure with Style: Unoffical rules"
@bbatsov
Copy link
Owner

bbatsov commented Apr 1, 2022

I should actually remove those first-person references as they are just a remnant of the early days of the style guide (and I'll take a note to do so). I think the name is fine as it is - it has been around for a very long time and nobody was been concerned with the name being confusing so far.

@bbatsov bbatsov closed this as completed Apr 1, 2022
bbatsov added a commit that referenced this issue Apr 1, 2022
Let's adopt language that reflects better the community-driven nature of the
guide.
@lgrapenthin
Copy link
Author

lgrapenthin commented Apr 3, 2022

@bbatsov I contributed this issue not to change the introduction text, but the title. Because the title is deceiving.
Based on your input I'd suggest to call it:

  • "Unofficial Community Clojure Style Guide"

Happy to open a new issue if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants