bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <gst...@gmail.com>
Subject Re: Moving things along
Date Wed, 31 Jan 2018 23:03:28 GMT
Ah. Thanks, John. I had missed the request to re-open that ticket. Just did
that. We'll get the VM going.

On Sat, Jan 27, 2018 at 5:16 PM, John Chambers <chambej@apache.org> wrote:

> Hi Greg,
>
> Sorry for the delay in replying. Been a little busy with work :)
> The current status from my part is that I am still waiting on the VM being
> made available for me to setup the live instance of Bloodhound on v0.8. I
> have not had time recently to chance INFRA but the ticket number is
> INFRA-13255.
>
> As for the move away from Trac there has not been much discussion on that
> since the original post.
>
> Cheers
>
> John.
>
> On 21 January 2018 at 01:47, Greg Stein <gstein@gmail.com> wrote:
>
> > Hey all ... what's the current status?
> >
> > On Tue, Dec 12, 2017 at 6:54 PM, Gary <gary.martin@physics.org> wrote:
> >
> > > Hi everyone,
> > >
> > > My apologies that I have been so quiet for a while. I want to get us
> > > moving on in our discussions about how to progress which have stalled
> > > again somewhat. There has been some work going on a little bit behind
> > > the scenes around reinstating the project bloodhound instance at the
> > > latest version. I'll nudge the person who has been doing most of that
> to
> > > keep us a bit more up to date!
> > >
> > > I feel that I should mention that I do have to write a report for the
> > > Apache board in which I will have to address decisions around whether
> to
> > > move this project to the Attic. As I am still talking about progress
> > > here, clearly my intention is to argue for further time for
> discussions.
> > > Regardless, more discussion, actual decisions and potentially action
> > > will make it easier to justify more time.
> > >
> > > So, given that I will shortly send a further message that focuses on
> > > proposing that we formally move towards replacing Trac with Django. The
> > > proposal may be relatively open in terms of the possible results but we
> > > may end up tying down more of the details in the course of the
> > > discussion. It should not arrive too long after this so please watch
> out
> > > for it.
> > >
> > > Cheers,
> > >     Gary
> > >
> >
>

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