We have seriously hijacked the original thread:( This has not been much of an issue because the lists have been low enough traffic that everyone was able to keep track of everything.
For the first six months, everyone in the project went to every irc meeting. As a result a lot of stuff was decided at meeting. I have _decided_ not to attend to irc meetings so that I am not aware of what has happened until the meeting summary has been posted to the relevant list. That way, I end up asking the dumb questions about what is going on so the newer participants don't have to ask. The first thing we must accept is that this is not an easy issue. _Every_ project suffers from it. The successful projects figure something out. Interestingly the bigger the project, the bigger the issue. The most common, and seemingly the most effective, solution is to keep all conversation on a single list until there is a good reason to split up the list. Once the list has split, there needs to be some form of 'digest' to summarize the important threads so that participants who do not subscribe to a list can quickly review what is happening elsewhere in the project. The rational is to avoid prematurely fragmenting the community. But once a communication channel is overloaded something needs to happen to keep the separate pieces synchronized. I think the first step is to come to some sort of consensus about what the lists are for. devel - for developer issues. marketing - for marketing issues. iaep - for everything else. From there, just make an effort to post to the most appropriate list. That will result in a painful itch. We all don't know every thing anymore. The fix will be to encourage some sort of ml digest to cover the highlights rather than start cross posting again. david On Wed, Jun 17, 2009 at 7:25 AM, Bert Freudenberg<b...@freudenbergs.de> wrote: > On 17.06.2009, at 14:09, Martin Dengler wrote: > >> No, that's not the problem. It's people that don't know that they >> don't know what they're doing. My point is that I think we're >> worrying about people that a) want to be testers; and b) are so keen >> that they go copy-nanding (after getting a devkey, etc.) without >> understanding what they're doing. As I'm saying I don't think there >> are enough people like that on IAEP/sugar-devel to worry about, and >> you're saying there are (IIUC). > > I for one would *hope* that on the IAEP list many people do > participate who are not necessarily familiar with technical details, > but who care deeply about education. Care so much in fact that they > are not even detained by these awkward instructions when they try to > help. In know there were such people in the OLPC community, and > hopefully we are not driving them away by too much tech-talk that is > only remotely related to the actual educational goals of the project. > >> Well, I'm happy to leave it at that. > > Me too. > > - Bert - > > > _______________________________________________ > IAEP -- It's An Education Project (not a laptop project!) > i...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
