[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] Migration to SourceForge tracker?
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] Migration to SourceForge tracker?
- From: "Stewart L" <stewartl42 (at) gmail.com>
- Date: Fri, 22 Aug 2008 10:17:36 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=AXrRAeywGu54VMIROpERMwjHMWx4oJF6X/bV1wiqIXU=; b=MwkbWMSqFeADOyd58nVocDkkhUk54tnPzDSsFDnsjLxxnd9czkIue5nvWrnP4X7VU2 01w5p2p1zxWxjadxCRhXmimMugggNQ0sxfTy8nqYYnPqMHVproQKsrgbtXFrOQJGLyjg U1dEpTXkQqLQRVKu7fBy8VnTAk5HW9hGGouWM=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=kf2LKvV49kdn2PYpOWjPrBpr9WnhYoMswMKenrViXvjL8DsqxwIf7vlP/+Efby7bHX 6d4rnWBDyEMj2ihxbuWClXMdqP1ogIof4FIxYTnA9d1UHCnjZPdhGDUEwoUsbrkdV2vp ieoryIXMC9tCiD6uaB11PvHYxHlI+i6LTWxrg=
- References: <48a96a8c.1e35440a.7dfd.ffffc4deSMTPIN_ADDED (at) mx.google.com> <5e59d8180808211707p31e07cc7xde32d74fe13d5965 (at) mail.gmail.com> <BAY138-W32C44352A84CBA83ECD2F69F6A0 (at) phx.gbl> <997a524e0808220711u5c73f83pabd6287b67c611ea (at) mail.gmail.com>
SF provides Trac and mailing lists as a free service for using them.
Integrates with SVN as well for bug tracking, I believe.
Stewart
On Fri, Aug 22, 2008 at 10:11 AM, Ralph Mitchell <ralphmitchell (at) gmail.com>wrote:
> One advantage of using Sourceforge is that they are hosting it. Is there a
> similar site hosting Trac??
>
> Ralph Mitchell
>
>
>
> On Fri, Aug 22, 2008 at 9:01 AM, T.J. Yang <tj_yang (at) hotmail.com> wrote:
>
>> If given voting right, I would vote for using trac to coordinate the
>> hobbit community. sourcefoge looks like has a bigger supersets of features
>> than trac. I like the Statistics (R1) especially. Too bad we (hobbit
>> community) is not totally embraceing sourceforge.* *Ex, we still have our
>> own mailling list while sourceforge provide this feature.*
>>
>> *I can work with either sourceforge or trac solutions, but please lets
>> utilize a solution's features as much as possible.*
>>
>> *
>> R1:
>> http://sourceforge.net/project/stats/detail.php?group_id=128058&ugn=hobbitmon&type=tracker
>>
>> T.J. Yang
>>
>> ------------------------------
>> Date: Thu, 21 Aug 2008 20:07:21 -0400
>> From: paulehr (at) gmail.com
>> To: hobbit (at) hswn.dk
>> Subject: Re: [hobbit] Migration to SourceForge tracker?
>>
>>
>> Instead of sourceforge, how about something like Trac?
>>
>> http://trac.edgewall.org/
>>
>> I think it has everything your looking for in a tracker, not to mention it
>> can integrate with subversion.
>>
>> Another option would be if you don't want to host your own tracker is
>> Launchpad
>>
>> https://launchpad.net/
>>
>> Only issue with Launchpad is that it uses bazaar instead of subverison
>> for a VCS.
>>
>> -Paul
>>
>>
>> On Mon, Aug 18, 2008 at 8:22 AM, SebA <spa (at) syntec.co.uk> wrote:
>>
>> Seeing as we are now using subversion (yay!), and moving to a more
>> de-centralised development model, maybe it's time (or after the project
>> namechange anyway) to start using the SourceForge bug and feature-request
>> tracker? (Or another tracker.) This would enable all the developers and
>> users to track the outstanding bugs instead of just Henrik. I've noticed in
>> the past that Henrik is very quick at fixing the critical bugs and core
>> dumps (thanks), but other less critical ones (in trunk) seem to be
>> outstanding for many months. Having a public bug tracker would:
>> (a) enable users to contribute to bugs via confirmation of the bug,
>> narrowing down of the cause(s) / scenarios, testing of patches, etc.
>> (b) ensure bugs (and feature requests) don't get forgotten about;
>> (c) more easily allow other developers to create patches;
>> (d) facilitate the release process by being able to see what might need
>> fixing / doing / adding before the next release; (I believe 4.3.0 is about
>> a year overdue, but unfortunately trunk still isn't stable…)
>> (e) increase the acceptance of Hobbit by users / companies, as it would
>> increase the signs of life of the project (if used properly), the signs of
>> support (in terms of bug fixing), etc.
>> (f) encourage people posting bugs that someone who might fix their bug
>> might (eventually) see their bug post! ;)
>> In terms of the stability of hobbit, if new features are going to be
>> added, isn't it time we branched 4.3 off from trunk? (So we don't add new
>> bugs to the 4.3 branch and further delay the release. Or has this already
>> been done?) Personally, I would have liked this to have happened this time
>> last year after Henrik announced 4.3.0 was nearly ready, instead of adding
>> new features since then. What would have happened, I suppose, is the
>> current trunk would have developped into 4.4.0. (If someone particularly
>> wanted a specific new feature from trunk in 4.3, they could backport the
>> patch. This would be facilitated if patches were uploaded to the bug
>> tracker for these new features when, or preferably before (thereby
>> increasing the stability of trunk by allowing testing of the patch first),
>> checking in to trunk.) I expect nearly everyone knows an open-source
>> project that works like this, but Asterisk is one that works well in this
>> way, with hundreds of people submitting patches to their customised Mantis
>> bug tracker.
>> Kind regards,
>> SebA
>>
>>
>>
>>
>> ------------------------------
>> Be the filmmaker you always wanted to be—learn how to burn a DVD with
>> Windows(R). Make your smash hit<http://clk.atdmt.com/MRT/go/108588797/direct/01/>
>>
>
>
--
Stewart
--
You only lose what you cling to.