we had some discussion about MD at another place and me and others had been asked to copy, my interpretation (being kind of lazy), parts to this new discussion to get your thoughts, rants or even praise.
The team has become way to silent for me, the main reason i became addicted to MD had been Andrews (Lekashman) behaviour and the way he interacted with us, the customers.
He gave me the feeling that MD as a company is a lot more involved with the community like Amazon as an example, nowadays the mk community regarding MD staff is empty most of the time.
It would be nice, even more for newcomers, to know which person to talk to or ask something at all.
MK community, chief in charge and to talk with is xxxx. Customers may not care, community members do, they want the feeling to be taken serious and to be involved.
I understand staff and manpower is limited, but this is essential for me to keep and grow a healthy community!"
This seems to be a good moment to ask why drop descriptions are so bad sometimes missing parts that should be natural given due to the nature of the product.
Is there a limitation of templates possibilities or to alter, change them at all.
I wish a certain standard, exceptions may happen, would be given.
How this should look like might be arguable, but sometimes i'm just astonished to put it gentle.
@makami just coming out a of a meeting, apologies for the late response. Would you mind sending me a few examples or whenever you see them and I can investigate / forward to the team (this goes for everyone else as well). Realistically, what we've seen is that sub-par drop descriptions are a result of one of 2 things (1) incomplete information being passed to the writers/creative team (2) rush requests for a drop resulting in less time to complete the description. There are limitations to what we can do with the template but I don't want to use that as an excuse. I'll take a look at the examples and it'll be easier to figure out how to improve and what may need to change with the process."
... A general example, the KC60 had a couple of thousand comments, we had gathered a lot of use full information the first drop happened.
Due to the unpleasing discussion format this information is stored at git hub. Two re-drops it hasn't been possible to add this information itself or the according link to the description. We post that link in the beginning for the always same questions answered in the beginning of a re-drop and then its getting lost again and again. This behavior makes me think, what the fuck, why do i even care.
Andy/Livingspeedbump made a nice write up about keycapsizes and layouts for folks to better understand what they need to get. Standard and/or non standard keycaps they have to look for buying sets.
We told the staff this should be linked in any upcoming keycap drop for better understanding and less over and over again questions.
Guess what, nothing, why did he spend a lot of time doing this, lost in Nirvana, scrolling down endlessly in the talk section you may find it. This ain't good and discouraging!
Subpar, that's what the community is thinking, mk drops are presented in the tech community, no keycaps flipped shown as example. One thing people ask for over and over again, this seems to be gotten standard by now in the mk community, we begged for that a long time.
If i find a bad example in the future i'll come back to you to let you know. I don't want to blame anyone to be "bad", but running a business, no matter which one, I've to talk and settle with my staff for certain information standards to be given to my customers, what goal we want to achieve and so on.
OK, enough of being an older grumpy guy ranting, i love you all for having a nice community and nice folks here at MD! :slightly_smiling_face:
@makami I think one of the best parts of working at MD is that people here are generally very receptive to feedback internally and when we hear negative feedback it's never viewed as "bad" but more just an opportunity to improve. That said, we are definitely guilty of having things slip through the cracks, and missing out on the opportunity to link to prior helpful posts is on us.
I am going to block some time off next week to see what we can do to start a process to summarize the key questions for upcoming drops specifically those that are extremely popular with hundreds of comments (and historical questions). It's already something we are talking about with some of our top community collaboration products (i.e. k7xx) but should be extended more broadly.
Another thing, you mentioned was that there are a lot of great write ups that already exist. A project I want to get kicked off in the next few weeks is to start summarizing and gathering that information together to have the best list of on-site/off-site posts/resources for any given community. Call it a great beginners guide, to address the most common questions or most important things to know. Thinking of starting with Mech Keys."
Feel free to discuss and don't hold back!