On Tue, Dec 12, 2017 at 8:13 PM, Gary <[email protected]> wrote: [...]
> > I would like to propose that Apache Bloodhound should migrate away from > Trac as a base and instead use the Django web framework. > > [...] > > My proposal as it is does not intend to go any further than settle the > question of our desire to change from Trac to Django but there are > decisions around some of the practicalities that are worth considering. > > [...] > > There are still a range of ways that we could implement such a migration > to Django, In my opinion this should be the first thing we should do if there is consensus on migrating to Django . Bloodhound v0.9 (or whatever other version number is chosen) architecture proposal plus milestones . [...] > > Regardless of other decisions, the scope of the project should remain > broadly the same, so we would be aiming to have reasonable feature > parity including, amongst other stuff: > > * Multi tracker support (multi-product) > * Integrated wiki > * Fast search plugin > * SCM integration > > We will obviously also need to ensure that we can migrate from a > bloodhound based on Trac to any new version. > > > > [...] +1 -- 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 - Ambassador Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article:
