Return-Path: Mailing-List: contact community-help@apache.org; run by ezmlm Delivered-To: mailing list community@apache.org Received: (qmail 41091 invoked from network); 1 Dec 2002 21:37:00 -0000 Received: from unknown (HELO pulse.betaversion.org) (217.158.110.65) by daedalus.apache.org with SMTP; 1 Dec 2002 21:37:00 -0000 Received: (qmail 18066 invoked from network); 1 Dec 2002 21:37:04 -0000 Received: from unknown (HELO apache.org) (stefano@157.22.245.61) by pulse.betaversion.org with SMTP; 1 Dec 2002 21:37:04 -0000 Message-ID: <3DEA817D.5070807@apache.org> Date: Sun, 01 Dec 2002 13:39:09 -0800 From: Stefano Mazzocchi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: community@apache.org Subject: Re: [proposal] creation of communitity.apache.org References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Ben Hyde wrote: > > On Sunday, December 1, 2002, at 06:04 AM, Stefano Mazzocchi wrote: > >> Ben Hyde wrote: >> >>>> 'community.apache.org' web site. >>> >>> -1 >> >> >> Uh, thanks Ben. That helped a lot understanding the reasons behind >> your negative vote. > > > My prior post regarding this enthusiasm follows... Ok, cool. See my comments below. >> Return-Path: >> Mailing-List: contact community-help@apache.org; run by ezmlm >> Delivered-To: mailing list community@apache.org >> Received: (qmail 12720 invoked from network); 15 Nov 2002 13:13:49 -0000 >> Received: from rwcrmhc53.attbi.com (204.127.198.39) >> by daedalus.apache.org with SMTP; 15 Nov 2002 13:13:49 -0000 >> Received: from pobox.com >> (h00055da7108f.ne.client2.attbi.com[66.30.192.113]) >> by attbi.com (rwcrmhc53) with SMTP >> id <20021115131348053005tddbe>; Fri, 15 Nov 2002 13:13:48 +0000 >> Date: Fri, 15 Nov 2002 08:14:24 -0500 >> Subject: Re: @apache web pages >> Content-Type: text/plain; charset=US-ASCII; format=flowed >> Mime-Version: 1.0 (Apple Message framework v546) >> From: Ben Hyde >> To: community@apache.org >> Content-Transfer-Encoding: 7bit >> In-Reply-To: >> Message-Id: <294E76F8-F89C-11D6-83E7-003065CC5042@pobox.com> >> X-Mailer: Apple Mail (2.546) >> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N >> >> It would be fun to have an Apache community aggregate of web logs, but >> I have trouble seeing how it serves the foundation's mission. Sorry to >> be a wet blanket... >> >> I'm concerned that if we create people.apache.org we create another >> inside/outsider boundary. I've got a handful of other concerns about >> this, but that's my primary one. I hear your concerns but today there is no easy way to find out some context about the person that I'm talking to on this list. My personal experience shows that promoting personal context helps creating more friendly communities. The real-life events are a way to promote personal context, but these events will not scale with the amount of people the ASF currently has. Thus a need to find a more decentralized solution. >> >> Some other ones... >> >> I'd rather not co-mingles the Apache brand with the personal web face >> of individuals in various subparts of the community. >> >> Our mission. Creating great software. Puzzling out how to do that >> productively in cooperative volunteer teams. Releasing that widely >> under a license that is both open. Crafting an effective open license. >> One that doesn't entrap folks. This proposal is exactly about 'puzzling out how to do that productively in cooperative volunteer teams'. The ASF is currently fragmented. Allow me to say "balkanized". I see this as a problem. I want to 'puzzle out' how to solve this problem and I think that giving more personal context will help out. This is my personal experience. You might disagree. But try to remember if knowing apache group members in person helped the creation of the httpd community. Sure I'd love to organize gettogethers every week, but we don't have the resources for that. Having homepages for ASF-related stuff might not be as good as meeting people in real life, but it's much better than having just a dry name to confront to. >> I have to do a lot of A supports B supports C supports D before I get >> to the conclusion that D, building out a mess of committer web pages, >> supports A, the mission of the foundation. Hope the above explains my intentions. Bringing people closer together is for sure part of the mission of the foundation. >> I'm concerned that a few highly vocal members might generate the >> impression that the foundation is taking positions that it's not. >> Consider Sam's web log with where he's been poking at RSS - that's not >> a ASF position. Consider my web log with it's rants on the wealth >> distribution - that's not an ASF position. I *am* *NOT* proposing to turn apache web pages into weblogs. Weblogs are personal things, I totally and completely agree with you that weblogs should *NOT* be part of those homepages. I just want to be able to associate a name with a person. some bio information, his interests around the ASF and whatever else the person wants me to know about his ASF involvement. my proposal is *NOT*: - about weblogs - about moving all personal info inside the ASF web zone - about forcing people to do anything, but empowering those who want to have their personal info available in a coherent manner >> The easiest way to avoid a star stage is not to build the stage. Fair, but that is not my intention. Hope my explaination change the picture somehow. -- Stefano Mazzocchi --------------------------------------------------------------------