Le 07/05/15 13:36, Hal Lockhart a écrit : > I am sorry if I have offended anyone. We are trying to follow the Apache Way > and have an project that is open to all. We have discovered that many of the > "rules" do not seem to be written down anywhere, which makes the Mentors a > vital resource. > > Yes, Emmanuel I carefully read your message. I also received a message from > Hadrian around the same time in which he said in part: > > "It is ok to communicate any way you want via any channel you want (voice or > not). What is not ok is to make decisions that way. So if you use a more > interactive channel to speed up the exchange of ideas (many projects use irc > for instance) you need to bring that decision back to the non-interactive > mailing list where the ASF community build consensus. The reason, mentioned > by Emmanuel, is that communities are strong when people feel included.
We may slightly disagree here, Hadrian and me... I do think that such conferences are excluding potential memebrs of the community, and The Apache Software foundation stated it in http://apache.org/foundation/how-it-works.html#management : "Communication Communication is done via mailing lists. These identify "virtual meeting rooms" where conversations happen asynchronously, which is a general requirement for groups that are so geographically distributed to cover all time zones (like it's normally the case for the various Apache communities). Some projects additionally use more synchronous messaging (for example, IRC or instant messaging). Voice communication is extremely rare, normally because of costs and the language barrier (speech is harder to understand than written text). In general, asynchronous communication is much more important because it allows archives to be created and it's more tolerant on the volunteer nature of the various communities." This is pretty clear : "Voice communication is extremely rare", which is not the case if you set a weekly or monthly, meeting where people are supposed to be on teh same TZ, be native english speakers, and be available, despite the fact that they may have a day job or other activity at the same time. This is why I think it's not good to have such meetings. And it's not my personal opinion here. Note that IRC is also to be used with caution, for teh same reasons (TZ, avaibalbility) but somehow, it's sometime very convenient to solve quick issues, like technical pb with this or that which would be solved way more easily through a synchronous communication. I'm not talking about projects decisions that have to be discussed publicly, here. Hope it helps...
