James Carlson wrote: >[EMAIL PROTECTED] writes: > > >>Just to throw my $0.02 in on this, I'd suggest thinking about: >>* kernel networking (protocols, frameworks, etc) >>* network project discussion >>* network administration (routing protocols, tools, configuration, etc) >>* networking APIs (sockets, RPC, etc) >>* general networking discussion/questions (for people who want to ask >> questions but don't know where to go) >> >> > >That doesn't look like a good breakdown to me. We were talking about >communities, not just mailing lists. > >What projects would a "general networking discussion/questions" >community endorse? > >
Some of the above make good community boundaries, some do not. What's important to recognise here is that the communities serve as the means to support discussion forums wherein information is exchanged. If we make networking any more fine grained then we must have a catch-all bucket for those that find our community model too troublesome or are just confused and want to ask an opensolaris networking question. >I suggest thinking about the community organization first, and *then* >worrying about what mailing lists make sense. > > The problem I read is "how to keep up with everything that is going on". I usually relate this to there being too much information (ie email) to keep up with - and possibly the manner in which information is being disbursed is not well organised either. I raised the topic as mailing lists because they're bound to communities. At present we're a single community and we can't keep our networking community web page in shape. One community, one page and that's not maintained well. I think we need to demonstrate that we can better manage just a single community and its single web page before we consider being multiple communities (with thus fewer to maintain it.) Erstwhile it seems like a fraught decision to divide it up... The current opensolaris model for mailing lists is centered around either projects or communities and as you've highlighted above, this doesn't cover "everything" - or to put it differently, even if networking is divided up, people will think "I have a networking question, where do I ask it?", and not along community boundaries (sometimes possibly along project boundaries.) Another suggestion is to completely decouple the idea of mailing lists from that of communities, or if there must be some sort of relationship, create a mailing list for the discussion *about* the community rather than the topics a community is meant to be about AND continue to pursue discussion forums that model generally related topics of discussion. i.e. seperate the technical discussion from the organisational discussion completely. To summarise, I'd rather see us get a better handle on understanding what the OpenSolaris networking is on about and try managing that in different ways before we try to carve it up. Darren p.s. I'd be more in favour of there being a single OpenSolaris community than one for each of networking, SMF, ZFS, etc. _______________________________________________ networking-discuss mailing list [email protected]
