Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 82338 invoked from network); 13 Feb 2006 19:29:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Feb 2006 19:29:20 -0000 Received: (qmail 13476 invoked by uid 500); 13 Feb 2006 19:29:19 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 13241 invoked by uid 500); 13 Feb 2006 19:29:18 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 13232 invoked by uid 99); 13 Feb 2006 19:29:18 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2006 11:29:18 -0800 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.182.145] (HELO e5.ny.us.ibm.com) (32.97.182.145) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Feb 2006 11:29:18 -0800 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e5.ny.us.ibm.com (8.12.11/8.12.11) with ESMTP id k1DJSvfZ032707 for ; Mon, 13 Feb 2006 14:28:57 -0500 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.12.10/NCO/VERS6.8) with ESMTP id k1DJSvcg211680 for ; Mon, 13 Feb 2006 14:28:57 -0500 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11/8.13.3) with ESMTP id k1DJSvcO019561 for ; Mon, 13 Feb 2006 14:28:57 -0500 Received: from [127.0.0.1] (sig-9-48-107-158.mts.ibm.com [9.48.107.158]) by d01av03.pok.ibm.com (8.12.11/8.12.11) with ESMTP id k1DJSsEE019361 for ; Mon, 13 Feb 2006 14:28:56 -0500 Message-ID: <43F0DDF1.4060708@sbcglobal.net> Date: Mon, 13 Feb 2006 11:28:49 -0800 From: Mike Matrigali Reply-To: mikem_app@sbcglobal.net User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: Naming individuals in the subject line of posts References: <43ECF16D.3030902@bristowhill.com> <43ED2CBC.8020104@sun.com> <43ED36FA.8050609@bristowhill.com> In-Reply-To: <43ED36FA.8050609@bristowhill.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I just wanted to apologize for my 2 recent posts with names in the subject line. I didn't realize it was a problem. I actually didn't even mean to direct the posts to those people alone. I had 2 goals with those posts. 1) Enlist discussion from the entire list about those 2 issues. They are continuing regression test failures which could be causing problems for all developers. 2) I admit I did want to draw attention to those who had assigned themselves to the JIRA issues. I figured that was a sort of accepted ownership of an issue. I also didn't want to procede without their advice as it seemed likely since they had assigned themselves to the issue that they were in fact likely experts on those issues. Can I ask advice on how best to achieve #2? o send direct private email asking about status? Now the discussion is off the list. o post comments to JIRA entry asking for status? Now o subject it with just JIRA entry and assume owner will read? For me personally I have no problem with people directing a public query to me about an issue I have assigned myself in JIRA. I try to only assign issues to myself that I am actively working on. For the last couple of weeks my particular itch has been to try to get the nightly test regressions under control. But it has been quite frustrating as I believe we are actually in worst shape now than when I started (more new issues came in than were resolved). I have to believe it is frustrating for new developers to be told to run as set of tests and then spend time figuring out what are the "acceptable" failures -- which have been around for weeks. Jean T. Anderson wrote: > Rick Hillegas wrote: > >>Hi Jean, >> >>I think that sometimes there's is no substitute for a response from a >>particular individual, perhaps because of their expertise or keenness >>for some issue. Somehow you have to cut through the blizzard of Derby >>mail which buries all of our mailboxes. I don't see the point in being >>coy about whose feedback you're seeking. To my way of thinking, naming >>someone in the subject line is preferable to back-channel communication >>and also to losing your query through the cracks. I have seen this >>technique work on other large mailing lists. Sometimes you get a >>response from a colleague telling you that the person you're trying to >>reach is on vacation or otherwise unreachable. That's useful to know. > > > Hi, Rick, > > By focusing on a single individual are you likely to miss other > potential contributors who might be lurking? > > I don't think the subject line needs to be coy -- if it's carefully > worded to convey what the post is about people with that interest will > naturally be drawn to it -- and you might find some contributors emerge > that you didn't expect. Currently there are 238 subscribers to derby-dev > (see http://people.apache.org/~coar/mlists.html#db.apache.org). > Carefully worded subject lines also make searching topics in archives > easier. > > And if somebody isn't available, that's all the reason more for the > subject line to not be exclusionary. > > >>I understand your concern about people feeling cornered, but I think >>that's part of the price you pay for being an expert. Personally, I >>don't feel put off by these direct pages and I don't feel excluded from >>responding if I have something to say. Also, I am not a big fan of >>addressing people in the third person or through other indirection. > > > We directly address each other a lot in the body of our posts -- and I > think that's fine. It's the direct address in the subject line that I > find jarring. > > -jean > > > >>Both approaches (direct paging and indirect fishing) can be off-putting >>in their own ways. I don't know how to fine-tune this, particularly >>given all the warmth and emotional cues we lose by communicating through >>email. >> >>Regards, >>-Rick > > >