Return-Path: X-Original-To: apmail-bloodhound-user-archive@www.apache.org Delivered-To: apmail-bloodhound-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F6BA18FE3 for ; Fri, 11 Sep 2015 07:22:14 +0000 (UTC) Received: (qmail 60870 invoked by uid 500); 11 Sep 2015 07:22:14 -0000 Delivered-To: apmail-bloodhound-user-archive@bloodhound.apache.org Received: (qmail 60842 invoked by uid 500); 11 Sep 2015 07:22:14 -0000 Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@bloodhound.apache.org Delivered-To: mailing list user@bloodhound.apache.org Received: (qmail 60832 invoked by uid 99); 11 Sep 2015 07:22:14 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Sep 2015 07:22:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id ADD1918034F for ; Fri, 11 Sep 2015 07:22:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.751 X-Spam-Level: **** X-Spam-Status: No, score=4.751 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_INFOUSMEBIZ=0.75, KAM_LIVE=1, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id FBngo7k95KFv for ; Fri, 11 Sep 2015 07:21:58 +0000 (UTC) Received: from wsp-02.crystone.se (wsp02.crystone.se [83.168.209.232]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 1AC8220107 for ; Fri, 11 Sep 2015 07:21:57 +0000 (UTC) X-Halon-ID: c2c6e50e-5855-11e5-96d0-000c29afa458 Received: from mail.crystone.net (unknown [83.168.226.206]) by wsp-02.crystone.se (Halon Mail Gateway) with ESMTPS for ; Fri, 11 Sep 2015 09:21:46 +0200 (CEST) Received: (qmail 27097 invoked from network); 11 Sep 2015 07:21:44 -0000 Received: from unknown (HELO ?192.168.1.3?) (oscar@monivent.se@[217.28.199.194]) by 83.168.226.42 with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 11 Sep 2015 07:21:44 -0000 From: Oscar Edvardsson Content-Type: multipart/alternative; boundary="Apple-Mail=_C98F14EE-7BE9-4886-9C5F-2DC355CE1249" Message-Id: <1473F8CD-456A-4308-98AC-DAABA412061A@monivent.se> Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: Is it alive? Date: Fri, 11 Sep 2015 09:21:46 +0200 References: <221A2AAD0DA6E04EBA5C3C0BB0C5855958CC36@SRVUNIMBX05.uni.au.dk> <221A2AAD0DA6E04EBA5C3C0BB0C5855958CC75@SRVUNIMBX05.uni.au.dk> <55F274A2.9060900@josephdwagner.info> To: user@bloodhound.apache.org In-Reply-To: <55F274A2.9060900@josephdwagner.info> X-Mailer: Apple Mail (2.2104) --Apple-Mail=_C98F14EE-7BE9-4886-9C5F-2DC355CE1249 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 And we went with Redmine (multi product support was a requirement). If you don=E2=80=99t need multi product support, I think Trac has the = advantage that if/when Bloodhound becomes under active development, it = is easy to make the switch. We never experienced any bugs with = Bloodhound (v0.7 and v0.8) during the 6-12 months of using it, but we = needed something that was regularly maintained so any bugs would = eventually be resolved. That aside, I think we as users are sometimes more demanding than fair. = It is an open source project, and as far as I have understood it, all = development (now) occurs on the developers' free time and without = compensation. The nature of open source allows anyone to fix bugs, to = their best of their abilities, which in turn allows you to patch issues = that are important to you, but not prioritised by the core development = team. (But for us who do not have the ability or time to do it - regular = maintenance is a big thing) Sorry for the short rant, keep up the good work! Regards, > On 11 Sep 2015, at 08:28, Joseph D. Wagner = wrote: >=20 > I went with Request Tracker. It has a different set of problems -- = every ticket system does -- but it seems more manageable and definitely = has active support. >=20 > https://www.bestpractical.com/rt/ >=20 > In fairness to the BH team, this is a symptom of a systemic problem = with Apache projects that aren't considered "hip." > * James http://james.apache.org/ . Email = server with no active development since 2012. It died right in the = middle of beta-testing it's next major release. > * SpamAssassin http://spamassassin.apache.org/ = . No active development between 2011 = and 2014, but might be picking up again. > * Geronimo http://geronimo.apache.org/ . = Java EE 6 application server with no development since 2013. However, = in Apache's defense, it could be said that Oracle killed Java. >=20 > Joseph D. Wagner >=20 > On 09/10/2015 10:50 PM, Hoiniji Rosonye wrote: >> I think going to Trac is a good decision. With all due respect to = the BH team, I think it still has a long way to go. I first gave BH a = try, but it had too many bugs or configuration limits. I then decided = to try Trac, and I found that it was very rock solid. >>=20 >> On Sep 10, 2015 9:42 PM, "Torben Lauritzen" > wrote: >> Hi. >>=20 >> Thank you for your replies - I will go with the standard Trac for the = moment then. But I will be following Bloodhound. >>=20 >> /Torben >>=20 >> > -----Original Message----- >> > From: Olemis Lang [mailto:olemis@gmail.com = ] >> > Sent: 11. september 2015 05:57 >> > To: user@bloodhound.apache.org >> > Subject: Re: Is it alive? >> > >> > JFTR , I am working on a private fork of Bloodhound that I use for = my >> > deployments . Nonetheless I've had to slow down my dev speed = because I'm >> > contributing with code to the Brython project , and I've not had = all the time >> > I'd like these days for BH dev . >> > >> > >> > On 9/10/15, Ryan J Ollos > wrote: >> > > On Thu, Sep 10, 2015 at 6:38 AM, Torben Lauritzen > wrote: >> > > >> > >> Hi. >> > >> >> > >> I was just about to install Trac, when I found Bloodhound. I = have >> > >> tried installing it, and it seems ok. But at the same time it = also >> > >> looks like the project is more or less dead - last release was >> > >> 2014-12-11, the documentation has unfinished things, e.g. the >> > >> section about git here: >> > >> https://issues.apache.org/bloodhound/wiki/BloodhoundInstall = (the page >> > >> was last edited 7 months ago), there is a warning >> > >> (SubversionException) at the top of the Wiki pages etc. >> > >> >> > >> So, I just wanted to know if the project is still alive? Are = anybody >> > >> working actively on the project? >> > >> >> > > >> > > Yeah there hasn't been much activity lately. I don't have any >> > > immediate plans or time to work on Bloodhound in the near future, = but >> > > I'd be interested to hear if any other developers will be working = on it. >> > > >> > > - Ryan >> > > >> > >> > >> > -- >> > Regards, >> > >> > Olemis - @olemislc >> > >> > Apache=E2=84=A2 Bloodhound contributor >> > http://issues.apache.org/bloodhound = >> > http://blood-hound.net >> > >> > Brython committer >> > http://brython.info >> > http://github.com/brython-dev/brython = >> > >> > Blog ES: http://simelo-es.blogspot.com/ = >> > Blog EN: http://simelo-en.blogspot.com/ = >> > >> > Featured article: >=20 --Apple-Mail=_C98F14EE-7BE9-4886-9C5F-2DC355CE1249 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 And we went with Redmine (multi product support was a = requirement).
If you don=E2=80=99t need multi product = support, I think Trac has the advantage that if/when Bloodhound becomes = under active development, it is easy to make the switch. We never = experienced any bugs with Bloodhound (v0.7 and v0.8) during the 6-12 = months of using it, but we needed something that was regularly = maintained so any bugs would eventually be resolved.

That aside, I think we = as users are sometimes more demanding than fair. It is an open source = project, and as far as I have understood it, all development (now) = occurs on the developers' free time and without compensation. The nature = of open source allows anyone to fix bugs, to their best of their = abilities, which in turn allows you to patch issues that are important = to you, but not prioritised by the core development team. (But for us = who do not have the ability or time to do it - regular maintenance is a = big thing)

Sorry= for the short rant, keep up the good work!

Regards,

On = 11 Sep 2015, at 08:28, Joseph D. Wagner <joe@josephdwagner.info> wrote:

=20 =20
I went with Request Tracker.  It has a different set of = problems -- every ticket system does -- but it seems more manageable and definitely has active support.

https://www.bestpractical.com/r= t/

In fairness to the BH team, this is a symptom of a systemic problem with Apache projects that aren't considered "hip."
* James http://james.apache.org/.  = Email server with no active development since 2012.  It died right in the middle of = beta-testing it's next major release.
* SpamAssassin http://spamassassin.apache.org/.  No active development between 2011 and 2014, but might be picking up again.
* Geronimo http://geronimo.apache.org/. = Java EE 6 application server with no development since 2013.  However, in Apache's defense, = it could be said that Oracle killed Java.

Joseph D. Wagner

On 09/10/2015 10:50 PM, Hoiniji = Rosonye wrote:

I think going = to Trac is a good decision.  With all due respect to the BH team, I think it still has a long way to go.  I first gave BH a try, but it had too many bugs or configuration limits.  I then decided to try Trac, and I = found that it was very rock solid.

On Sep 10, 2015 9:42 PM, "Torben Lauritzen" <tol@bios.au.dk> = wrote:
Hi.

Thank you for your replies - I will go with the standard Trac for the moment then. But I will be following Bloodhound.

/Torben

> -----Original Message-----
> From: Olemis Lang [mailto:olemis@gmail.com]
> Sent: 11. september 2015 05:57
> To: user@bloodhound.apache.org
> Subject: Re: Is it alive?
>
> JFTR , I am working on a private fork of Bloodhound that I use for my
> deployments . Nonetheless I've had to slow down my dev speed because I'm
> contributing with code to the Brython project , and I've not had all the time
> I'd like these days for BH dev .
>
>
> On 9/10/15, Ryan J Ollos <rjollos@apache.org> wrote:
> > On Thu, Sep 10, 2015 at 6:38 AM, Torben Lauritzen <tol@bios.au.dk> wrote:
> >
> >> Hi.
> >>
> >> I was just about to install Trac, when I found Bloodhound. I have
> >> tried installing it, and it seems ok. But at the same time it also
> >> looks like the project is more or less dead - last release was
> >> 2014-12-11, the documentation has unfinished things, e.g.  the
> >> section about git here:
> >> https://issues.apache.org/bloodhound/wiki/BloodhoundInstall= (the page
> >> was last edited 7 months ago), there is a warning
> >> (SubversionException) at the top of the Wiki pages etc.
> >>
> >> So, I just wanted to know if the project is still alive? Are anybody
> >> working actively on the project?
> >>
> >
> > Yeah there hasn't been much activity lately. I don't have any
> > immediate plans or time to work on Bloodhound in the near future, but
> > I'd be interested to hear if any other developers will be working on it.
> >
> > - Ryan
> >
>
>
> --
> Regards,
>
> Olemis - @olemislc
>
> Apache=E2=84=A2 Bloodhound contributor
> http://issues.apache.org/bloodhound
> http://blood-hound.net
>
> Brython committer
> http://brython.info > http://github.com/brython-dev/brython
>
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>
> Featured article:


= --Apple-Mail=_C98F14EE-7BE9-4886-9C5F-2DC355CE1249--