[GH-ISSUE #170] No Good Way to Share Information with the Team #143

New issue

Open

opened 2026-05-05 05:00:26 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:00:26 -06:00

Owner

Originally created by @sdeken on GitHub (Jun 3, 2020).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/170

I was just sent the following PDF from a fan of KeyCastr, and I thought I'd share it with the team. But it turns out that the best way we currently have is filing a ticket!

So this ticket has two purposes. The first purpose is to share the coverage KeyCastr got in the German magazine "Mac&i" in their March 2020 issue, on page 59:

KeyCastr in Mac&i - March 2020.pdf

The second purpose is to recommend we find a way to communicate with each other without filing tickets 😄

Originally created by @sdeken on GitHub (Jun 3, 2020). Original GitHub issue: https://github.com/keycastr/keycastr/issues/170 I was just sent the following PDF from a fan of KeyCastr, and I thought I'd share it with the team. But it turns out that the best way we currently have is filing a ticket! So this ticket has two purposes. The first purpose is to share the coverage KeyCastr got in the German magazine "Mac&i" in their March 2020 issue, on page 59: * [KeyCastr in Mac&i - March 2020.pdf](https://github.com/keycastr/keycastr/files/4725930/KeyCastr.in.Mac.i.-.March.2020.pdf) The second purpose is to recommend we find a way to communicate with each other without filing tickets 😄

gitea-mirror commented

2026-05-05 05:00:31 -06:00

Author

Owner

@akitchen commented on GitHub (Jun 7, 2020):

This is pretty neat! thanks for sharing @sdeken

A while ago @elia set up https://gitter.im/keycastr/Lobby , but I'm not sure how much usage it gets and whether it would meet requirements for private communication. Other options might include setting up a slack instance (I've already registered keycastr.slack.com) or converting our github org to a paid org and using a private repository's ticket list, wiki, & project management tools. I'm open to other ideas too!

Cheers

@akitchen commented on GitHub (Jun 7, 2020): This is pretty neat! thanks for sharing @sdeken A while ago @elia set up https://gitter.im/keycastr/Lobby , but I'm not sure how much usage it gets and whether it would meet requirements for private communication. Other options might include setting up a slack instance (I've already registered keycastr.slack.com) or converting our github org to a paid org and using a private repository's ticket list, wiki, & project management tools. I'm open to other ideas too! Cheers

gitea-mirror commented

2026-05-05 05:00:34 -06:00

Author

Owner

@elia commented on GitHub (Jun 8, 2020):

TBH I'm fine with using issues for most "internal" discussions… although for this specific instance it might even work as a new "Press" (or "Praise") section in the readme, wdyt @sdeken / @akitchen ?

We also have wikis, that might turn useful for other types of content.

Gitter is seldom used and from my point of view I would consider slack overkill, but I'd be fine with it, I recently did the same change for @opalrb, and it's much better than gitter.

@elia commented on GitHub (Jun 8, 2020): TBH I'm fine with using issues for most "internal" discussions… **although for this specific instance it might even work as a new "Press" (or "Praise") section in the readme, wdyt @sdeken / @akitchen ?** We also have wikis, that might turn useful for other types of content. Gitter is seldom used and from my point of view I would consider slack overkill, but I'd be fine with it, I recently did the same change for @opalrb, and it's much better than gitter.

gitea-mirror commented

2026-05-05 05:00:37 -06:00

Author

Owner

@MacMog commented on GitHub (Apr 5, 2022):

Did anything come of this? I would like to work with this project, to either write a new visualizer or possibly add features to one of the existing two, and maybe implement a few of the wishlist items. I guess I could ask questions via issues, but using that system as chat that feels clunky to me.

I also hoped to get help from the active developers with some build problems. I fixed a few of them and now can build the KCVisualizer target in Debug, though you may have a better solution than the changes I made; we should discuss before I create a PR. I also cannot get KeyCastr to build due to a problem with the ShortcutRecorder headers. I figured you might have a simple solution, before I make a mess fiddling with the XCode project settings.

@MacMog commented on GitHub (Apr 5, 2022): Did anything come of this? I would like to work with this project, to either write a new visualizer or possibly add features to one of the existing two, and maybe implement a few of the wishlist items. I guess I could ask questions via issues, but using that system as chat that feels clunky to me. I also hoped to get help from the active developers with some build problems. I fixed a few of them and now can build the KCVisualizer target in Debug, though you may have a better solution than the changes I made; we should discuss before I create a PR. I also cannot get KeyCastr to build due to a problem with the ShortcutRecorder headers. I figured you might have a simple solution, before I make a mess fiddling with the XCode project settings.

gitea-mirror commented

2026-05-05 05:00:40 -06:00

Author

Owner

@akitchen commented on GitHub (Apr 5, 2022):

@MacMog glad to hear you're interested in contributing! No, nothing really came of this discussion topic.

I'd say let's start with issues and see where it goes. I'd be happy to reopen this idea if you're finding the friction to be too high.

The project should build fine out of the box -- in fact I just verified this in a fresh checkout in order to be sure before replying. After you clone the repo, be sure to run git submodule update --init --recursive to pull down the submodule dependencies. No customization of the dependencies or build configuration should be needed. If you're seeing anything different (maybe specific to developing on an M1 mac?) then we'd definitely want to hear about those.

Thanks for getting in touch!

@akitchen commented on GitHub (Apr 5, 2022): @MacMog glad to hear you're interested in contributing! No, nothing really came of this discussion topic. I'd say let's start with issues and see where it goes. I'd be happy to reopen this idea if you're finding the friction to be too high. The project should build fine out of the box -- in fact I just verified this in a fresh checkout in order to be sure before replying. After you clone the repo, be sure to run `git submodule update --init --recursive` to pull down the submodule dependencies. No customization of the dependencies or build configuration should be needed. If you're seeing anything different (maybe specific to developing on an M1 mac?) then we'd definitely want to hear about those. Thanks for getting in touch!