About the return on your post about community involvement in MOC development, especially about issues that you don't have the time to handle outside of the actual core moc coding.
There is some issues I've seen with the post that leads me to believe most people probable never even read it.
1. You buried it in a post called moc tenth aniversary, rather then putting it up with a clear post subject requesting more community involvement, to leave you free to code.
2. Reading the post requires clicking 'more' to see the rest of the post,
people that wheren't interested in a article about the tenth aniversary didn't click it.
3. Its buried inside a large road map about moc development, posted in in article that the tl;dr crowd (even developers can be part of it) didn't read all the way through, and so requires reading the entire rather lengthy blog post to see that part of it.
4. The need for contributors is understated a little in the post, its very well written about code organization, and how you want to just focus
on the code base and leave the plugins to thirdy parties.
5. In my experience of dealing with people in community projects (MMO clans, lol, eh, people are people), people don't step up for ambigously declared places they can step up to, you have to clearly define what they're going to be doing what their tools are where they can go to immediately take over that role, and directly define who they're going to be interacting with or what they're going to manage, so they can fit right into the role, return on involvement in a project is quicker and more productive if you make it simple (brain dead) to clearly step into a place or role.
I probable have more to see but I'm going to post this and think for a minute.
