On 11/6/17, John Chambers <[email protected]> wrote: > [...] > > >> 3. Do any design docs live anywhere at all? I've also got Python / >> Django development experience. Most recently building APIs with Django >> Rest Framework. So can help on that front. Guess we need to do a bit of >> a review of where things stand to get a plan in place for what to do >> next. >> > > Once the official Bloodhound wiki and issue tracker are back online we can > then start to discuss and bring together our plans for the future of > Bloodhound. But there is no reason why we can't start those discussions on > this list in the meantime. Nothing has been decided as of yet. >
That's correct . All previous decisions have been specified and documented in Bloodhound Enhancement Proposal (a.k.a. BEP) documents available. Once the project wiki will be back you'll be able to see the multi-product architecture (BEP-0003), etc ... It's all quite Trac-specific, so you might want to spend some time reading the Trac docs [1]_ first. [...] .. [1] http://trac.edgewall.org -- Regards, Olemis - @olemislc Apache™ Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Brython committer http://brython.info http://github.com/brython-dev/brython SciPy Latin America - Cuban Ambassador Chairman of SciPy LA 2017 - http://scipyla.org/conf/2017 Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article:
