Re: [Proposal] Core Bloodhound - basic concepts

On Mon, 19 Mar 2018, at 2:09 PM, Greg Stein wrote: > On Mon, Mar 19, 2018 at 8:43 AM, Gary Martin > wrote: > > > Hi everyone, > > > > I am going to start building out a basic core implementation to play > > around with some of the ideas we have discussed. I'll try not to

Re: [Proposal] Core Bloodhound - basic concepts

On Mon, Mar 19, 2018 at 8:43 AM, Gary Martin wrote: > Hi everyone, > > I am going to start building out a basic core implementation to play > around with some of the ideas we have discussed. I'll try not to take > things too far before getting this into source control.

Re: [Proposal] Core Bloodhound - basic concepts

een as all that problematic though. > > > j. > > > > > > -Original Message- > > From: Allan Swanepoel [mailto:allanice...@gmail.com] > > Sent: 11 March 2018 21:36 > > To: dev@bloodhound.apache.org > > Subject: Re: [Proposal] Core Bloodhound

Re: [Proposal] Core Bloodhound - basic concepts

> > -Original Message- > From: Allan Swanepoel [mailto:allanice...@gmail.com] > Sent: 11 March 2018 21:36 > To: dev@bloodhound.apache.org > Subject: Re: [Proposal] Core Bloodhound - basic concepts > > Possibly take a look at what has already been done using Django in

RE: [Proposal] Core Bloodhound - basic concepts

Subject: Re: [Proposal] Core Bloodhound - basic concepts Possibly take a look at what has already been done using Django in this arena? One project that jumps out with some Google foo is https://djacket.github.io/ Also, if you want to separate (loosely couple) the front-end and the back-end

Re: [Proposal] Core Bloodhound - basic concepts

On Sun, Mar 11, 2018 at 4:21 PM, Gary wrote: >... > How tickets are stored as a whole is also worth tackling, which is what #2 > is trying to broadly decide. Here I am suggesting that the state of a > ticket can be built up from a query that collects all the change

Re: [Proposal] Core Bloodhound - basic concepts

Hi Allan, Thank you for the suggestions. Please take my word for it that the input is definitely appreciated. I do want to delay discussion on how the front-end could work, or at least limit that discussion in this thread. The main thing I want to focus on here is getting agreement on the

Re: [Proposal] Core Bloodhound - basic concepts

Possibly take a look at what has already been done using Django in this arena? One project that jumps out with some Google foo is https://djacket.github.io/ Also, if you want to separate (loosely couple) the front-end and the back-end, possibly build the whole front-end with some js framework