aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorskullY <skullydazed@gmail.com>2017-07-03 01:37:05 -0700
committerskullY <skullydazed@gmail.com>2017-07-03 01:37:05 -0700
commit6b0503b20d1918f4eed1975cf2104a61fd51abef (patch)
tree808262ffceeb7c0c110b491878195721e1213bc3
parent80cc23e9128ca89340cabc3517afc440489013fe (diff)
downloadqmk_firmware-6b0503b20d1918f4eed1975cf2104a61fd51abef.tar.gz
qmk_firmware-6b0503b20d1918f4eed1975cf2104a61fd51abef.zip
update the faq
-rw-r--r--docs/faq.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/faq.md b/docs/faq.md
index c46861030..d7f2a6f4f 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -10,7 +10,9 @@ TMK was originally designed and implemented by [Jun Wako](https://github.com/tmk
10 10
11From a technical standpoint QMK builds upon TMK by adding several new features. Most notably QMK has expanded the number of available keycodes and uses these to implement advanced features like `S()`, `LCTL()`, and `MO()`. You can see a complete list of these keycodes in [Quantum Keycodes](quantum_keycodes.html). 11From a technical standpoint QMK builds upon TMK by adding several new features. Most notably QMK has expanded the number of available keycodes and uses these to implement advanced features like `S()`, `LCTL()`, and `MO()`. You can see a complete list of these keycodes in [Quantum Keycodes](quantum_keycodes.html).
12 12
13From a project and community management standpoint TMK prefers to have keyboards maintained in separate forks while QMK prefers to have keyboards maintained in one central repository. 13From a project and community management standpoint TMK maintains all the officially supported keyboards by himself, with a bit of community support. Separate community maintained forks exist or can be created for other keyboards. Only a few keymaps are provided by default, so users typically don't share keymaps with each other. QMK encourages sharing of both keyboards and keymaps through a centrally managed repository, accepting all pull requests that follows the quality standards. These are mostly community maintained, but the QMK team also helps when necessary.
14
15Both approaches have their merits and their drawbacks, and code flows freely between TMK and QMK when it makes sense.
14 16
15# Debug Console 17# Debug Console
16## hid_listen can't recognize device 18## hid_listen can't recognize device