You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not saying I'm in a rush to hand over admin rights to the repo, but I am saying that I realize I'm not particularly doing this project justice as one who (1) is extremely time constrained and has been for well over a year now (2) is, on the whole, more interested in some other nights-and-weekends projects than those relating to keyboard firmwares, and (3) pretty much wrote his KMK config in late 2018 and, for most intents and purposes, hasn't touched it in any meaningful way since, other than to track KMK updates.
Thus, if there are folks here (and I know there's folks here who've been stalking the room for going on three years now!) who may be interested in stepping up into some form of a maintainer role in KMK either now or in the future, consider the door open. I don't feel I'm the best fit for that role at this time, and after numerous IRL chats with @kdb424, I don't think handing the reins (and burden, if you will) over to him is in his or the project's best interests, either.
Meanwhile, at some point, I need to figure out this damn topic-merge-keyboard-and-state-rebased debacle.........
To be clear: I'll be around for as much guidance, leadership, and tales from the pit as any future maintainer may desire. I'm not noping out of the KMK ecosystem completely. I'm just realizing that what I built serves the rest of y'all far more than it serves me, and this project deserves to be led by someone who is more deeply in the trenches than I am or plan to be any time soon.
The text was updated successfully, but these errors were encountered:
Cross-posting the following from the Matrix room:
The text was updated successfully, but these errors were encountered: