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

knausj: rebrand, honor original creator #1231

Merged
merged 18 commits into from
Jul 15, 2023
Merged

knausj: rebrand, honor original creator #1231

merged 18 commits into from
Jul 15, 2023

Conversation

phillco
Copy link
Collaborator

@phillco phillco commented Jul 13, 2023

#935. We're not in Kansas knausj anymore...

This updates:

  • The main title of the README (as well as most references therein) and adds a note about our origins. View here
    • The cloning instructions in the README.
      • (This might be up for debate; do we want people to git clone https://github.com/talonhub/community community? Some users might end up with two copies. I think @lunixbochs had a plan to check for if people have both knausj and community cloned duplicative side by side by mistake.)
      • GitHub's web UI recommends https://github.com/talonhub/community.git as the HTTPS URL, but our old instructions did not include the .git suffix. What do we want to do?
  • All GitHub links in the form of https://github.com/knausj85/knausj_talon/, such as to issues.
  • A few manual references in text files, such as in the deprecation process.

Copy link
Collaborator

@pokey pokey left a comment

Choose a reason for hiding this comment

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

Looks good with minor comments

README.md Show resolved Hide resolved
@@ -1,6 +1,11 @@
# knausj_talon
# community
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
# community
# Talon community grammar

Copy link
Collaborator Author

@phillco phillco Jul 15, 2023

Choose a reason for hiding this comment

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

I'm kind of used to the GitHub convention of the first line being the name of the repository, with a description both underneath and in the repository description field, unless there's a strong reason otherwise. Is this out of date?

I don't feel strongly but I think it looks cleaner this way

Copy link
Member

Choose a reason for hiding this comment

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

This seems to be the general convention still, I think it's fine as is.

@phillco phillco requested a review from pokey July 13, 2023 13:58
README.md Outdated Show resolved Hide resolved
@phillco phillco requested a review from auscompgeek July 15, 2023 14:42
@phillco phillco changed the title readme: rebrand, honor original creator rebrand, honor original creator Jul 15, 2023
@phillco phillco changed the title rebrand, honor original creator knausj: rebrand, honor original creator Jul 15, 2023
@knausj85
Copy link
Member

This looks good to me, thanks.

@knausj85 knausj85 merged commit 7525147 into main Jul 15, 2023
1 check passed
@knausj85 knausj85 deleted the rebrand branch July 15, 2023 18:23
MartinRykfors pushed a commit to MartinRykfors/knausj_talon that referenced this pull request Jul 27, 2023
talonhub#935. We're not in ~Kansas~
knausj anymore...

This updates:

- The main title of the README (as well as most references therein) and
adds a note about our origins. [View here](
https://github.com/talonhub/community/tree/rebrand)
    - The cloning instructions in the README.
- (This might be up for debate; do we want people to `git clone
https://github.com/talonhub/community community`? Some users might end
up with two copies. I think @lunixbochs had a plan to check for if
people have both knausj and community cloned duplicative side by side by
mistake.)
- GitHub's web UI recommends `https://github.com/talonhub/community.git`
as the HTTPS URL, but our old instructions did not include the `.git`
suffix. What do we want to do?
- All GitHub links in the form of
`https://github.com/knausj85/knausj_talon/`, such as to issues.
- A few manual references in text files, such as in the deprecation
process.

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Jeff Knaus <[email protected]>
blyons333 pushed a commit to blyons333/knausj_talon that referenced this pull request Aug 11, 2023
talonhub#935. We're not in ~Kansas~
knausj anymore...

This updates:

- The main title of the README (as well as most references therein) and
adds a note about our origins. [View here](
https://github.com/talonhub/community/tree/rebrand)
    - The cloning instructions in the README.
- (This might be up for debate; do we want people to `git clone
https://github.com/talonhub/community community`? Some users might end
up with two copies. I think @lunixbochs had a plan to check for if
people have both knausj and community cloned duplicative side by side by
mistake.)
- GitHub's web UI recommends `https://github.com/talonhub/community.git`
as the HTTPS URL, but our old instructions did not include the `.git`
suffix. What do we want to do?
- All GitHub links in the form of
`https://github.com/knausj85/knausj_talon/`, such as to issues.
- A few manual references in text files, such as in the deprecation
process.

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Jeff Knaus <[email protected]>
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

Successfully merging this pull request may close these issues.

4 participants