summaryrefslogtreecommitdiff
path: root/Becoming-a-QMK-Collaborator.md
diff options
context:
space:
mode:
authorJack Humbert2017-04-04 21:21:27 -0400
committerJack Humbert2017-04-04 21:21:27 -0400
commitb096b57b0bddc6a127e1ffca03ba6e3ba3a563b4 (patch)
tree16474fb453a170aca0d31253aeaed5def0ec6f99 /Becoming-a-QMK-Collaborator.md
parent54f69d02d57a98b08a1a8a5ab6ca6b8ab02f5800 (diff)
Created Becoming a QMK Collaborator (markdown)
Diffstat (limited to 'Becoming-a-QMK-Collaborator.md')
-rw-r--r--Becoming-a-QMK-Collaborator.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/Becoming-a-QMK-Collaborator.md b/Becoming-a-QMK-Collaborator.md
new file mode 100644
index 000000000..3ee3ef4c2
--- /dev/null
+++ b/Becoming-a-QMK-Collaborator.md
@@ -0,0 +1,7 @@
+A QMK collaborator is a keyboard maker/designer that is interested in helping QMK grow and fully support their keyboard(s), and encouraging their users/customers to submit features, ideas, and keymaps. We're always looking to add more keyboards and collaborators, but we ask that they fulfill these requirements:
+
+* **Have a PCB available for sale** - unfortunately there's just too much variation and complications with handwired keyboards.
+* **Maintain the your keyboard's directory** - this may just require an initial setup to get your keyboard working, but it could also include accommodating changes made to QMK's core.
+* **Approve and merge their keyboard's keymap pull requests** - we like to encourage users to contribute their keymaps for others to see and work from when creating their own.
+
+If you feel you meet these requirements, shoot us an email at hello@qmk.fm with an introduction and some links to your keyboard! \ No newline at end of file