Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 51806 invoked from network); 16 Mar 2006 07:49:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Mar 2006 07:49:48 -0000 Received: (qmail 25280 invoked by uid 500); 16 Mar 2006 07:49:32 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 24560 invoked by uid 500); 16 Mar 2006 07:49:30 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 24538 invoked by uid 99); 16 Mar 2006 07:49:30 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Mar 2006 23:49:30 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of flamefew@gmail.com designates 64.233.162.196 as permitted sender) Received: from [64.233.162.196] (HELO zproxy.gmail.com) (64.233.162.196) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Mar 2006 23:49:27 -0800 Received: by zproxy.gmail.com with SMTP id 9so306795nzo for ; Wed, 15 Mar 2006 23:49:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=DOHpNyzvPTpBKerfoEqGPUuiWaCcWAutSAP2kxma04NQJiroYNxJcCQlBPPl4uKwTdX9Fds0sgd7bpD3UP/91JiB2v77YcRl3nylcla9YalbEKdN3dcCeenHZ3II8XJCMMSEyCJSKCw3OSYzCcYe76kJo0RlmfFurb8e9CHIKwc= Received: by 10.36.105.9 with SMTP id d9mr1713564nzc; Wed, 15 Mar 2006 23:49:06 -0800 (PST) Received: by 10.36.113.8 with HTTP; Wed, 15 Mar 2006 23:49:06 -0800 (PST) Message-ID: <31cc37360603152349r329e6951l88aa7e03b0f3935b@mail.gmail.com> Date: Wed, 15 Mar 2006 23:49:06 -0800 From: "Henri Yandell" To: "Jakarta Commons Developers List" , "Jakarta Commons Users List" Subject: Blatant self promotion of blog MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Wanted to mention something I've been doing this week on my blog: http://blog.generationjava.com/roller/page/bayard?catname=3D%2FCommons Each morning at work I sit down and go over the new and modified issues in a collection of open source projects - mostly looking for security issues, but also just generally following what's going on, especially in legacy releases which tend to be the ones we're supporting. So I thought that it might be interesting to do the same kind of thing each evening for all of Commons. It's not a full summary of what's going on (I'd need to be summarising the mailing list too for that), but it does seem like a useful thing (to me). Value it adds * Way for -users of Commons components to follow -dev without having to keep up with the email. * Definitely helps me as a -dev get a good feel for what's going on. I tend not to read the bugzilla emails as they come in. * Minor things like making sure the [foo] is at the front can be dealt with for new issues. Very interested in knowing whether people think it's of worth. Especially in the long term - say we had a project blog at apache.org that committers could post things like this to. Also interested in whether it looks to be more useful for users or developers. Sorry for the blog advertising; hopefully it was enough on-topic :) Hen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org