bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Chambers <>
Subject Re: [Proposal] How to get out of this situation?
Date Wed, 25 Oct 2017 10:45:44 GMT
In my opinion and from personal experience, what has hindered contributions
has been the need to have a fairly good understanding of Trac.
Even when it comes to setup and configuration of Bloodhound it is mostly
Trac related.
I understand the reasons why the project was setup like this, but I think
it may be time to look at alternatives as Gary has said.
Especially as Olemis raises the concern that Trac might look towards
supporting multi product/project in the future.

So is it time to think about a reboot of Bloodhound using more modern
architectures and approaches?

I would be happy to take part in any discussions on this approach.



On 25 October 2017 at 08:13, Allan Swanepoel <> wrote:

> Gary, i completely agree with you
> wouldnt we end up recreating the wheel here then?
> ; gitLab;
> just to name a few?
> On Wed, Oct 25, 2017 at 4:18 AM, Gary <> wrote:
> > On Mon, 23 Oct 2017, at 08:33 PM, Allan Swanepoel wrote:
> >> As a massive outsider to this project, I joined the ML in the hope to
> >> learn more about the bloodhound project, only to be met with the
> >> possible archiving of it.
> >>
> >> Please don't get the wrong impression, I enjoy python and open source
> >> as much as i enjoy contributing to OSS.
> >>
> >> I would like to raise a few troublesome concerns I would have with
> >> this project (again, this is one person):
> >> 1) Trac - the foundation of BH is still on Py2 - with basically 2 yrs
> >> until py2 is declared EOL (2020) .
> >> 2) Trac Version - Trac is on version 1.2(stable), afaik, BH has only
> >> been tested on Trac 0.11 - 0.13
> >>
> >> So, i guess my day 1 question would be how would you get Bloodhound to
> >> py3 in ~2yrs, especially if the platform its based on isnt there yet?
> >
> > I think you make some very good points here. I would prefer to see
> > Bloodhound running on Python 3 and I am far from convinced that being
> > based on Trac will help us.
> >
> > Although it might point to a much larger effort, I would be interested
> > in opinions on whether the community (i.e. any part of the community
> > that wants to move forward with Bloodhound) would consider moving away
> > from Trac as the base for the project.
> >
> > Cheers,
> >     Gary
> --
> We live in an age when pizza gets to your home before the police.
>   - Jeff Marder
> ------------------------------------------
> Allan Swanepoel
> +27 71 850 5554
> Linux User #452990
> Linux Machine #360914
> -----------------------------------------------
> IMPORTANT: This email is intended for the use of  the  individual
> addressee(s)  named  above  and  may  contain information that is
> confidential,  privileged  or  unsuitable  for  overly  sensitive
> persons  with  low  self-esteem, no sense of humour or irrational
> religious beliefs. If you are not  the  intended  recipient,  any
> dissemination,  distribution  or copying  of  this  email is not
> authorised (either explicitly or implicitly) and  constitutes  an
> irritating  social  faux  pas. Unless the word absquatulation has been
> used in its correct context somewhere  other  than  in  this warning,
> it does not have any legal or grammatical use and may be ignored. No
> animals were  harmed  in  the  transmission  of  this email,  although
>  the  yorkshire  terrier  next door is living on borrowed time, let me
> tell you. Those of you with an overwhelming fear  of  the unknown will
> be gratified to learn that there is no hidden message revealed by
> reading  this  warning  backwards,  so just ignore that Alert Notice
> from Microsoft: However, by pouring a complete circle of salt around
> yourself and your  computer  you can  ensure  that  no harm befalls
> you and your pets.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message