I share the same sentiment with Chris. While more documentation would be amazing, that documentation can come not only from Miquel and the team but from any user that decides to experiment with this. You might find several threads regarding this subject, where folks share their modules (that might end up in the main branch). I’ve been adding some features to our mGear-based rig using Python modules on top of an already built rig rather than extending the Shifter modules. At some point I would like to look into it.
Regarding the Discord server, and please note that this is just an opinion, I’m strongly opposed to it as a way of managing data. Mainly to avoid fragmentation of information. The beauty of the forum is that is a gold mine, the information is very well organized and it’s relatively easy finding if someone had the same issues/questions you have. Finding information in a place like Slack/Discord is, compared to a forum, a nightmare in my opinion.
In addition to that, I found the team and the community to be very responsive and in a very timely manner here in the forum. A chat format enables a sense of ‘urgency’, both from the person that asks the question and those who might jump to answer it. I assume everyone here is more or less busy with their day to day job, so to me it is far from an ideal format. Someone explains it really well here:
I am aware this is a bit of confirmation bias self-exercise, and while I’m not an active part of the mGear development team nor the forum, I’ve seen several communities ‘die’ because moving to other platforms where the real time interaction is favored. Good for solving individual problems, bad for letting users be aware of those, hence the same basic questions being repeated over and over and over. Facebook Groups, I’m looking at you
Sorry for the rant!