[os-infrastructure] Bug/issue tracking (was commit messages)

Fri May 2 05:05:23 PDT 2008

Perforce and Jira are TOTALLY different animals.

Jira is definitely the leader in this space with customers like  
Apache, rPath, Jboss. Check out http://www.atlassian.com/software/jira/customers.jsp 
  if you really believe it is not an OSS leader.

Re: Subversion -- On the PM side, we've looked at Collabnet Enterprise  
and spoken to partners that do use it (e.g. JasperSoft) and it remains  
an option. It lacks functionality and flexibility as a complete  
solution, but even having enterprise hosting of subversion (one of  
their services) MAY be an option. The ticketing/bug system is unable  
to get mildly close to meeting the requirements I've seen coming  
across this list.

At this stage, the point is to flesh out the right technology that can  
meet the business requirements of BOTH supporting development of a  
highly complex products set, and making that experience friendly and  
as seamless as possible to the community (including our paying  
customers and dealing with security bugs and data privacy laws).

The issue here is less cost at this scale (how much do you think we've  
spent in going as far as we have with subversion?) and more about how  
we make it that seamless and user friendly experience for the partner  
and development community. I don't think perforce is totally out of  
the picture IMHO, but it is definitely NOT as user friendly or  
community development friendly as svn or mercurial. In this case, the  
scale of the economy (Perforce costs) are shifted to the potential  
customer/partner/community developer with client-based pricing. This  
just doesn't scale out to encourage adding more contributors, in fact,  
it does exactly the opposite. This and other reasons are why Perforce  
is likely one of the less the optimal solutions. With that said, I  
would like to throw out there that we SHOULD look at Perforce in this  
process and that someone should step up to the plate like Andrew has  
done with svn, or like Jay has done with mercurial to champion it (not  
me, I'm a mercurial fan).

Regards,

Mike Sale

On May 2, 2008, at 5:42 AM, Bodo Bergmann wrote:

>
> There is a price tag for JIRA as well ($4,800 upfront + $2,400/year).
> They have an option for free use for pure Open Source projects,
> but Perforce has this too,
> and our sources are not all Open Source either (Gateways, OpenROAD,
> Ingres2.6).
>
> If we plan to spend some money anyway,
> then we should rather have a look at some integrated solutions
> e.g. CollabNet Enterprise Edition (which includes Subversion)
> http://www.collab.net/products/cee/
> This would free us from spending a lot of time with integrating
> solutions from different vendors.
>
> -----Original Message-----
> From: opensource-infrastructure-bounces at lists.ingres.com
> [mailto:opensource-infrastructure-bounces at lists.ingres.com] On  
> Behalf Of
> Grant Croker
> Sent: Friday, May 02, 2008 1:19 PM
> To: opensource-infrastructure at lists.ingres.com
> Subject: Re: [os-infrastructure] Bug/issue tracking (was commit
> messages)
>
> Bodo,
>
> In principle I agree but what it should come down to is the best tool
> for the job, open-source solutions should be considered/evaluated  
> along
> side their closed source counterparts.
>
> If the SCM is Perforce then so be it, however the $200 price tag for
> every user might count against it. If you are aware of any open source
> bug/issue tracking software that be setup to support a paying/non- 
> paying
>
> customer base then let the list know.
>
> regards
>
> grant
>
> On 02/05/08 12:30, Bodo Bergmann wrote:
>> JIRA is not Open Source.
>>
>> I thought Subversion was selected because of it's the most common  
>> Open
>
>> Source SCM,
>> otherwise we could also have selected Perforce - which is much more
>> Piccolo-like - due to its history/developers,
>> so changing our processes using Perforce would a much easier task to
> do.
>>
>> One of the arguments for Subversion was: It shows our commitment to
>> Open Source.
>> If that is the case, we should continue this way when planning  
>> systems
>
>> for issue & bug tracking.
>>
>> Bodo.
>>
>>
> ------------------------------------------------------------------------
>> *From:* opensource-infrastructure-bounces at lists.ingres.com
>> [mailto:opensource-infrastructure-bounces at lists.ingres.com] *On  
>> Behalf
>
>> Of *Alex Hanshaw
>> *Sent:* Friday, May 02, 2008 11:20 AM
>> *To:* opensource-infrastructure at lists.ingres.com
>> *Subject:* Re: [os-infrastructure] Bug/issue tracking (was commit
>> messages)
>>
>> I can see that it would be nice to be able to say we had JIRA running
>> on Ingres, but I do not see this as important.
>> Outlook does not use Ingres as a repository but we use Outlook. RPM
>> does not use Ingres as a repository but
>> that doesn't stop us  using RPM based distributions of Linux.
>>
>> Alex
>>
>> On Fri, 2008-05-02 at 11:03 +0200, Grant Croker wrote:
>>> On 01/05/08 10:18, Andrew Ross wrote:
>>>> The only issue I see is that Jira does not run on Ingres currently.
> I personally feel this is important. I don't think they would do a  
> port
> just because. If we engage and show value/share some of the work, they
> may be interested in talking.
>>> I never thought I would say this but I do not believe that not  
>>> having
>
>>> Jira or whatever running on Ingres from day 1 is a problem. However
> the
>>> rollout of any system should include the plans/steps to port said
> system
>>> to Ingres. I guess this would be dependant on how willing Altassian
> (or
>>> whoever) would be to work with us to do a port and how much work
> would
>>> be involved. If there is functionality missing in Ingres that is
>>> required, how long would we be prepared to wait?
>>>
>>> g
>>>
>>>
>>
>>
>> Alex Hanshaw
>> Manager, Sustaining Engineering
>>
>> *Ingres Corporation*
>>
>> _Alex.Hanshaw at ingres.com <mailto:first.last at ingres.com>_
>> *PHONE*+44 1753 559515
>> *FAX*+44 1753 559550
>>
>> *_www.ingres.com <http://www.ingres.com/>_*
>>
>> This transmission is confidential and intended solely for the use of
>> the recipient named above. It may contain confidential, proprietary,
>> or legally privileged information. If you are not the intended
>> recipient, you are hereby notified that any unauthorized review, use,
>> disclosure or distribution is strictly prohibited. If you have
>> received this transmission in error, please contact the sender by
>> reply e-mail and delete the original transmission and all copies from
>> your system.
>>
>>
> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> opensource-infrastructure mailing list
>> opensource-infrastructure at lists.ingres.com
>> http://lists.ingres.com/mailman/listinfo/opensource-infrastructure
>>
>
>
> -- 
> Grant Croker - Ingres PHP, Ruby and Python maintainer
> Here the man in blue crimplene accosted us once more but we patiently
> explained to him that he could **** off.
>
> _______________________________________________
> opensource-infrastructure mailing list
> opensource-infrastructure at lists.ingres.com
> http://lists.ingres.com/mailman/listinfo/opensource-infrastructure
> _______________________________________________
> opensource-infrastructure mailing list
> opensource-infrastructure at lists.ingres.com
> http://lists.ingres.com/mailman/listinfo/opensource-infrastructure