Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 73002 invoked from network); 13 Jan 2004 18:04:05 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 13 Jan 2004 18:04:05 -0000 Received: (qmail 63904 invoked by uid 500); 13 Jan 2004 18:03:49 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 63794 invoked by uid 500); 13 Jan 2004 18:03:49 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 63726 invoked from network); 13 Jan 2004 18:03:48 -0000 Received: from unknown (HELO mail.lokitech.com) (209.92.53.4) by daedalus.apache.org with SMTP; 13 Jan 2004 18:03:48 -0000 Received: from 209.92.53.102 ([209.92.53.102]) by mail.lokitech.com (JAMES SMTP Server 2.1.3) with SMTP ID 365 for ; Tue, 13 Jan 2004 13:03:49 -0500 (EST) Message-ID: <4004342F.1000203@lokitech.com> Date: Tue, 13 Jan 2004 13:08:47 -0500 From: Serge Knystautas User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: [PROPOSAL] Jakarta Commons moving to JIRA References: In-Reply-To: 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 X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N rleland@apache.org wrote: > I am -1 for moving Jakarta Commons as a --whole-- to JIRA, I am also -1 to that proposal. I think Noel was just seeing if there was interest as normally these moves are done on a project basis, and Commons is a bit different. > If each sub-project of commons wants to move then thats ok. Yup. > Does infrastructure really want to support 2 bug tracking systems ? JIRA is #3. We have had bugzilla and scarab for some time. > I believe that the question of a BugTracking system to use is really > an Apache wide decision, since if all projects don't move to JIRA, > then there is 2 systems to maintain and learn. ASF is volunteer driven, soif people are willing to give their time to support some tool for the ASF community, then it appears. That's why JIRA is now available. > Are the JIRA people willing to provide admin type maintance for free ? Yes. Have, will continue. Jeff is a committer and works for the small company that makes JIRA. > The biggest improvement would be to treat each commons sub-project, > as a project in bugzilla. I also think that each committer should > automatically be made a buzilla admin. I'll let however is maintaining bugzilla answer this. You may want to bring it up to infrastructure. > As echoed by others I believe we should use OSS software where there > is a viable alternative, with similar functionality. Everyone is free to not use commercial tools that are available to the ASF, like JIRA or Clover. -- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. sergek@lokitech.com --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org