Open tmk opened 9 years ago
I'm about to release my own controller based on tmk - it's for the VEB Robotron K7637 keyboard in case you wonder. I'm unsure how to proceed. The best way would certainly be to add tmk_core as a submodule to a repository containing only my new controller firmware. But the tmk_core repository seems to be hopelessly outdated. So I will fork tmk_keyboard and do my work on a dedicated branch that I can rebase if necessary. This seems to be what most people do.
@tmk Why don't you use a tmk_core submodule in the development of tmk_keyboard? I would suggest to
I still have a plan and will do that in the end. But it won't happen some time soon. I don't have enough time to do properly and another reason is my laziness.
tmk_core was updated using git-subtree merge and this makes process a bit complex. I'll base on submodule instead next time.
The tmk_core repo was updated with change sets from this repo now. https://github.com/tmk/tmk_core/commit/8bfaa6ce5380323c77427cf2a01ae2092db5ff49
This repo will be changed later once my topic branches in progress are settled.
I have published my project using a tmk_core submodule as was suggested. Could you add a link to my project, please?
Interesting project! Done.
I have plan to remove some of projects which I can't mainatain from repository, or move projects to another(each own) repository.
1) Most of converter projects will continue to be updated by hasu/tmk(me) because I still own keyboards needed to test firmware. Meanwhile most of keyboard projects can't be tested. hasu/tmk owns keyboard pojejcts; gh60, hbkb, hhkb, infinity, onekey and onekey_mbed. But they may be separated from core library.
2) If contributor of the project has a repository it should be center of the project.
README of tmk_keyboard just has a link to the repository and tmk_keyboard has no code for the project.Place your repository link on this wiki page: https://github.com/tmk/tmk_keyboard/wiki/TMK-Based-ProjectsUpdate: 2016/01 Moved some projects to orphan directory now. 649151c