2 Comments


  1. There is definitely a tricky balance to achieve between openness and also having the ability to have a meaningful conversation.

    I was in that MP6 Skype conversation since the beginning (I committed the very first version of MP6), and while there is nothing there that couldn’t be fully “open”, the question of whether it should be or not isn’t really the important thing. The important thing is the type of interaction involved.

    See, you can’t work with a thousand people at once. You just can’t. The dangers of design-by-committee are well known, but there’s also the issue of the number of voices in the room. If you have everybody talking at once, the conversation leads nowhere. Ultimately, somebody has to be in charge and making the decisions in such a large group and leadership becomes important, along with organization and everything else. But in a smaller group, say, 10-15 people, everybody can work together and at once without necessarily having well-defined structure or leadership roles. Smaller groups that are all on the same page can get things done quicker and faster.

    I think that’s the benefit of “private” conversations, they can be a smaller group of people, working towards a common goal. You get much more rapid iteration and active feedback. If everything had to be presented to a large group, then it would slow things down. Large group conversations take more time to gather and give feedback. Because of this, people in large group situations tend to work alone and only present final results to the larger group conversation, to avoid these time delays. It’s a natural response, when you share with the world, you tend to polish the work more. But when you’re sharing and working with just a few people, you can show half-baked ideas, thoughts, and concepts much more easily. Smaller groups tend to make progress faster because of this.

    I guess what I’m saying is that group dynamics is a fascinating subject, really. :)

    Reply
  2. Bryan Petty

    Most of your points here revolve around supporting arguments for adequately splitting up communication into sub-channels that aren’t flooded with thousands of people giving input, but that still doesn’t mean it’s a case for hosting those conversations behind closed doors, by invite only, and without any logs.

    We don’t send every reply to every ticket in the issue tracker to one single mailing list where everyone is required to sift through it to find the discussions relevant to them (and I don’t mean the firehose notifications here, that’s just a secondary feature for convenience). When you adequately split up discussion boards and mailing lists into sub-topics that evenly split the community up by interest (and the P2s already are), you can host very useful and controlled discussions completely in the public eye, where absolutely anyone that wants to be involved can speak their mind even if they aren’t writing the code themselves. Trac is actually the perfect example of that.

    Sometimes conversations become heated, and trail off-topic, as they do all the time on Trac and the forums, but proper moderation is the key, and you can still do that on mailing lists, and even P2s. When you look at the infamous LKML, completely public, with over 500 messages per day on a single mailing list, but consider that this is exactly where and how the Linux kernel is designed and developed (and even where you submit patches too), it’s actually pathetic to see WordPress denying the public access to spark new conversations or give feedback on one simple and small core feature plugin. In order for me to make one comment on something related to one feature I’m concerned about, WordPress now expects me to dive entirely in and become a full-time contributor to that feature or I’m not allowed to even join those meetings. I have to be a member of a team now. WordPress really has forgotten what it means to be an open source project.

    I wholeheartedly agree with Marko’s views on open communication:
    http://markoheijnen.com/open-source-and-my-opinion-on-it/

    As for “design-by-committee”, you’re right, you can’t, but just because everyone can comment on some new feature doesn’t mean you don’t still have leadership. a democracy, or some kind of equal representation involved in making timely final decisions. It just means that the project has a chance to get a well rounded idea about where the *entire* community stands on something even if you can’t address everything and everyone. The most important part is that everyone is given the chance to speak and be heard.

    You can’t do any of that on Skype.

    Reply

Leave a Reply