Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 31569 invoked from network); 25 Jul 2006 19:13:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Jul 2006 19:13:11 -0000 Received: (qmail 98635 invoked by uid 500); 25 Jul 2006 19:13:10 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 97990 invoked by uid 500); 25 Jul 2006 19:13:08 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 97979 invoked by uid 99); 25 Jul 2006 19:13:08 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 12:13:08 -0700 X-ASF-Spam-Status: No, hits=1.7 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,RCVD_IN_SORBS_WEB,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of sppatel@gmail.com designates 64.233.184.232 as permitted sender) Received: from [64.233.184.232] (HELO wr-out-0506.google.com) (64.233.184.232) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jul 2006 12:13:07 -0700 Received: by wr-out-0506.google.com with SMTP id i20so857220wra for ; Tue, 25 Jul 2006 12:12:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:from:subject:date:to:x-mailer:sender; b=PLbIQM7hchAb3cTB0qTFsyXIm9kjwNOCs9zYyrV7rnjQ8pLAxmjoq/6OkLzC1PYgPkSla31VTWTkujfp1tTsO5bOdGCtyObW4hZ4bhPBMzLhmhrjaetCUXMnmEujlF80lV571rkgXmKgs1baXqzAbKkypbaWqU4vwQms69m/2Ok= Received: by 10.54.157.2 with SMTP id f2mr5528600wre; Tue, 25 Jul 2006 12:12:46 -0700 (PDT) Received: from ?9.37.214.144? ( [129.33.49.251]) by mx.gmail.com with ESMTP id 8sm5694752wra.2006.07.25.12.12.44; Tue, 25 Jul 2006 12:12:44 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: Content-Type: multipart/alternative; boundary=Apple-Mail-5--546094622 Message-Id: <86993EB8-21AF-4A6C-B59C-FA7897726DED@gmail.com> From: Sachin Patel Subject: Re: JIRAs adopter query/policy? Date: Tue, 25 Jul 2006 15:12:44 -0400 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.752.2) Sender: Sachin Patel X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --Apple-Mail-5--546094622 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed There are other open source projects that do this. I'm not trying to push this, but just wanted to get some input to see if this is something that could be useful to track and differentiate between what developers in the community contributing to geronimo are seeing and what only "users" are seeing. On Jul 25, 2006, at 3:03 PM, ian.d.stewart@jpmchase.com wrote: > Maybe it's just me, but this seems to smack of favoritism. Just > because I > use Geronimo as the platform for my web applications running on my > home > network, or to host my open source project, why are my bugs less > important > than those of the engineers from IBM (or JPMorgan)? > > It seems to me that the existing voting mechanism provides both a more > generic and more finely tuned approach for identifying the number > of users > that are impacted by a specific issue. > > > Ian > > It's better to be hated for who you are > than loved for who you are not > > Ian D. Stewart > Appl Dev Analyst-Advisory, DCS Automation > JPMorganChase Global Technology Infrastructure > Phone: (614) 244-2564 > Pager: (888) 260-0078 > > > > Sachin Patel > > om> To > Sent by: Sachin dev@geronimo.apache.org > > Patel cc > m> > Subject > JIRAs adopter query/policy? > > 07/25/2006 02:26 > PM > > > Please respond to > dev@geronimo.apac > he.org > > > > > > > As the Geronimo user base grows, it is important that we be able to > distinguish between JIRAs open during a development cycle to those > that are > being hit in the field or requested by companies who either use > Geronimo or > build products and or plugins on top of it. So I suggest we provide a > restricted "adopter required" field in JIRA. This adopter field > would be > exposed to JIRA users who request and identify themselves as > adopters. So > just like our query for available patches, we can easily query > these and > help ensure that these issues that companies face get the necessary > attention and help resolve them faster then they would be otherwise. > > Thoughts? > > -sachin > > > > > ----------------------------------------- > This transmission may contain information that is privileged, > confidential, legally privileged, and/or exempt from disclosure > under applicable law. If you are not the intended recipient, you > are hereby notified that any disclosure, copying, distribution, or > use of the information contained herein (including any reliance > thereon) is STRICTLY PROHIBITED. Although this transmission and > any attachments are believed to be free of any virus or other > defect that might affect any computer system into which it is > received and opened, it is the responsibility of the recipient to > ensure that it is virus free and no responsibility is accepted by > JPMorgan Chase & Co., its subsidiaries and affiliates, as > applicable, for any loss or damage arising in any way from its use. > If you received this transmission in error, please immediately > contact the sender and destroy the material in its entirety, > whether in electronic or hard copy format. Thank you. > -sachin --Apple-Mail-5--546094622 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
There are other open source = projects that do this.=A0 I'm not trying to push this, but just wanted = to get some input to see if this is something that could be useful to = track and differentiate between what developers in the community = contributing to geronimo are seeing and what only "users" are = seeing.

On Jul 25, 2006, at 3:03 PM, ian.d.stewart@jpmchase.com = wrote:

Maybe it's just me, but this = seems to smack of favoritism.=A0 = Just because I
use Geronimo as the = platform for my web applications running on my home
network, or to host my open source project, why are = my bugs less important
than those of the engineers = from IBM (or JPMorgan)?

It seems to me that the existing = voting mechanism provides both a more
generic = and more finely tuned approach for identifying the number of = users
that are impacted by a specific = issue.



It's better to be hated for who you are
than loved for who you are not

Ian D. = Stewart
Appl Dev Analyst-Advisory, DCS = Automation
JPMorganChase Global Technology = Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078



=A0=A0 =A0 =A0 = =A0 =A0 =A0 Sachin Patel =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0
=A0=A0 =A0 =A0 =A0 =A0 =A0 <sppatel2@gmail.c=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0=A0 =A0 =A0 = =A0 =A0 =A0 om>=A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 To=A0
=A0=A0 =A0 =A0 =A0 =A0 =A0 Sent = by: Sachin =A0 =A0 =A0 =A0 =A0 = dev@geronimo.apache.org=A0 =A0 =A0 =A0 =A0 =A0 = =A0
=A0=A0 =A0 =A0 =A0 =A0 =A0 = Patel=A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 cc=A0
=A0=A0 =A0 =A0 =A0 =A0 =A0 <sppatel@gmail.co=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0=A0 =A0 =A0 = =A0 =A0 =A0 m>=A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 Subject=A0
=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 JIRAs adopter = query/policy?=A0 =A0 =A0 =A0 = =A0

=A0=A0 =A0 =A0 = =A0 =A0 =A0 07/25/2006 02:26 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0=A0 =A0 =A0 = =A0 =A0 =A0 PM =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0


=A0=A0 =A0 =A0 =A0 =A0 =A0 Please = respond to=A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0
=A0=A0 =A0 =A0 =A0 =A0 =A0 dev@geronimo.apac=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0
=A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 he.org=A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0






As the Geronimo user base grows, it is important = that we be able to
distinguish between JIRAs = open during a development cycle to those that are
being hit in the field or requested by companies who = either use Geronimo or
build products and or = plugins on top of it.=A0 So I suggest we provide a
restricted "adopter required" field in JIRA.=A0 This = adopter field would be
exposed to JIRA users who = request and identify themselves as adopters.=A0 So
just like our query for available patches,=A0we can = easily query these and
help ensure that these = issues that companies face get the necessary
attention and help resolve them faster then they = would be otherwise.
Thoughts?





This = transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from = disclosure
under applicable law.=A0 If you are not the intended = recipient, you
are hereby notified that any = disclosure, copying, distribution, or
use of = the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED.=A0 Although this transmission = and
any attachments are believed to = be free of any virus or other
defect that = might affect any computer system into which it is
received and opened, it is the responsibility of the = recipient to
ensure that it is virus free and = no responsibility is accepted by
JPMorgan = Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any = way from its use.
If you received this = transmission in error, please immediately
contact = the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank = you.

=


-sachin
 =

= --Apple-Mail-5--546094622--