You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Allan Swanepoel <al...@gmail.com> on 2017/11/06 01:46:57 UTC
Re: [Proposal] How to get out of this situation?
Hey guys and gals, just kicking up the dust again on this.
Has anything been set regarding bloodhound's future?
On Wed, Oct 25, 2017 at 2:20 PM, Gary <al...@fastmail.co.uk> wrote:
> Daniel,
>
> Sorry for the delay in the message appearing - it went via moderation.
>
> My reply to the content is at the end.
>
> On Wed, 25 Oct 2017, at 11:39 AM, Daniel Brownridge wrote:
>> I used Bloodhound as our production issue management in a small
>> organisation a few years back.
>>
>> In many respects it worked very well but there where a few glitches that
>> became frustrating over time.
>>
>> I gravitated towards Bloodhound as at the time it appeared to be the
>> best thing open source could offer as an alternative to Jira which is
>> what I have encountered most frequently in use in businesses.
>>
>> I would support a move to python 3. In terms of changing the base I
>> think this is potentially a sensible idea. In terms of attracting
>> developers to the project Django would seem to be a very sensible
>> choice. This is partly coming from the fact it's what I have most
>> experience with but pragmatically the number of people familiar with
>> working on a Django project will vastly outweigh the number of people
>> who are familiar with the Trac code base.
>>
>> I'm sure there are a myriad of other potential options too, but, if it's
>> not Django then whatever does become the base of the project should
>> ideally have a lot of common ground to provide people an easy way into
>> to understanding the code.
>>
>> My assumption in making this point is that Bloodhound's ultimate goal is
>> to be the best open source bug/issue/task management tool it can be, not
>> to reinvent the wheel in other areas.
>>
>> To put it another way, and appreciate I might be a lone voice here, I
>> personally don't have much appetite to become skilled in trac, because
>> that doesn't take me much further, but as an opportunity to keep working
>> with a code base (i.e. Django etc) I know is transferable I'd be much
>> keener to contribute.
>>
>> Does this make sense to anyone?
>>
>> Thanks,
>>
>> Daniel
>>
>> ;On 25/10/17 08:13, Allan Swanepoel wrote:
>> > Gary, i completely agree with you
>> > wouldnt we end up recreating the wheel here then?
>> > https://github.com/Djacket/djacket ; gitLab; https://gitea.io/en-US/
>> > just to name a few?
>> >
>> >
>> > On Wed, Oct 25, 2017 at 4:18 AM, Gary <ga...@physics.org> 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
>> >
>> >
>>
>>
>
> So, I probably should not jump on this to reply too quickly when it
> happens to be a message that agrees with my suspicions! There may be
> other points of view but it seemed likely that knowledge of Trac itself
> was a disincentive as something extra to learn.
>
> From my point of view, the two obvious choices for web framework would
> be either Django or Flask. I believe they would have the advantage of
> being relatively easy to pick up, and would represent a much more
> transferable skill. As I think Daniel says, being based on either Django
> or Flask could attract those who are interested in gaining experience in
> these so that they get a transferable skill out of this. It may also be
> attractive to those who already have skills in these areas.
>
> We do need to consider the size of the task we are looking at though.
> Starting from scratch might be possible. We could look to adapt as much
> of the existing work as we can as well.
>
> Cheers,
> Gary
--
We live in an age when pizza gets to your home before the police.
- Jeff Marder
------------------------------------------
Allan Swanepoel
allanice001@gmail.com
allanice.001@unix.net
dragonmaster@linaccess.com
+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.
Re: [Proposal] How to get out of this situation?
Posted by John Chambers <ch...@apache.org>.
Hi Allan,
I am dedicating some time to getting the official Bloodhound instance back
up and running so at least people can see the work that has been done so
far.
Once that is available we (the community) need to document any design
ideas and raise issues for the work needed going forward.
I will be reporting my progress on the 'Public Bloodhound is down again'
thread.
Cheers
John.
On 6 November 2017 at 01:46, Allan Swanepoel <al...@gmail.com> wrote:
> Hey guys and gals, just kicking up the dust again on this.
>
> Has anything been set regarding bloodhound's future?
>
>
> On Wed, Oct 25, 2017 at 2:20 PM, Gary <al...@fastmail.co.uk> wrote:
> > Daniel,
> >
> > Sorry for the delay in the message appearing - it went via moderation.
> >
> > My reply to the content is at the end.
> >
> > On Wed, 25 Oct 2017, at 11:39 AM, Daniel Brownridge wrote:
> >> I used Bloodhound as our production issue management in a small
> >> organisation a few years back.
> >>
> >> In many respects it worked very well but there where a few glitches that
> >> became frustrating over time.
> >>
> >> I gravitated towards Bloodhound as at the time it appeared to be the
> >> best thing open source could offer as an alternative to Jira which is
> >> what I have encountered most frequently in use in businesses.
> >>
> >> I would support a move to python 3. In terms of changing the base I
> >> think this is potentially a sensible idea. In terms of attracting
> >> developers to the project Django would seem to be a very sensible
> >> choice. This is partly coming from the fact it's what I have most
> >> experience with but pragmatically the number of people familiar with
> >> working on a Django project will vastly outweigh the number of people
> >> who are familiar with the Trac code base.
> >>
> >> I'm sure there are a myriad of other potential options too, but, if it's
> >> not Django then whatever does become the base of the project should
> >> ideally have a lot of common ground to provide people an easy way into
> >> to understanding the code.
> >>
> >> My assumption in making this point is that Bloodhound's ultimate goal is
> >> to be the best open source bug/issue/task management tool it can be, not
> >> to reinvent the wheel in other areas.
> >>
> >> To put it another way, and appreciate I might be a lone voice here, I
> >> personally don't have much appetite to become skilled in trac, because
> >> that doesn't take me much further, but as an opportunity to keep working
> >> with a code base (i.e. Django etc) I know is transferable I'd be much
> >> keener to contribute.
> >>
> >> Does this make sense to anyone?
> >>
> >> Thanks,
> >>
> >> Daniel
> >>
> >> ;On 25/10/17 08:13, Allan Swanepoel wrote:
> >> > Gary, i completely agree with you
> >> > wouldnt we end up recreating the wheel here then?
> >> > https://github.com/Djacket/djacket ; gitLab; https://gitea.io/en-US/
> >> > just to name a few?
> >> >
> >> >
> >> > On Wed, Oct 25, 2017 at 4:18 AM, Gary <ga...@physics.org>
> 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
> >> >
> >> >
> >>
> >>
> >
> > So, I probably should not jump on this to reply too quickly when it
> > happens to be a message that agrees with my suspicions! There may be
> > other points of view but it seemed likely that knowledge of Trac itself
> > was a disincentive as something extra to learn.
> >
> > From my point of view, the two obvious choices for web framework would
> > be either Django or Flask. I believe they would have the advantage of
> > being relatively easy to pick up, and would represent a much more
> > transferable skill. As I think Daniel says, being based on either Django
> > or Flask could attract those who are interested in gaining experience in
> > these so that they get a transferable skill out of this. It may also be
> > attractive to those who already have skills in these areas.
> >
> > We do need to consider the size of the task we are looking at though.
> > Starting from scratch might be possible. We could look to adapt as much
> > of the existing work as we can as well.
> >
> > Cheers,
> > Gary
>
>
>
> --
> We live in an age when pizza gets to your home before the police.
> - Jeff Marder
> ------------------------------------------
> Allan Swanepoel
> allanice001@gmail.com
> allanice.001@unix.net
> dragonmaster@linaccess.com
> +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.
>