On Tue, Feb 11, 2014 at 2:56 PM, Saint Germain <[email protected]> wrote:
> On Tue, 11 Feb 2014 18:55:59 +0000, Gary Martin > <[email protected]> wrote : > > > Hi everyone, > > > > We may be starting to look at this a little on the late side now but > > I would very much like to see Bloodhound being a part of GSoC again > > this year. We now have three committers with some level of experience > > with mentoring projects and so I expect we will all want to give what > > help we can to any other Bloodhound committers who are also > > interested in mentoring. > > > > Once again we need to generate ideas that are appropriate for > > students without a deep knowledge of the internals of Bloodhound/Trac > > that should fit into a 6-8 week project. > > > > Projects from last year are listed here (tagged with 'gsoc'): > > < > https://issues.apache.org/bloodhound/query?status=!closed&keywords=~gsoc> > > > > We may be able to make use of some of the ideas on this list but I > > would like to see more ideas generated that might catch the attention > > of students. Also, obviously, the earlier potential mentors become > > involved the better. > > > > Hello Gary, > > I am currently trying to embed Bloodhound in a Django website. > Indeed it seems a good idea to have an issue tracking system for > customer request (or issues). > > There is surpringly few solutions on the market, especially in Python. > Most issue tracking I've seen embedded in websites are either very > simple or ugly (i.e. no real integration but a simple redirection). > > Django website itself is using Trac (yeah !) but no real integration > either. > What features might the integration provide? > So far my experiment works without problem through WSGI. But having > worked with Django and Trac/Bloodhound/Genshi, I was quite strucked by > how similar they can be on many points. > > It's a long long shot, but we can try to make Trac/Bloodhound easier to > integrate with Django and other frameworks ? > (I'm not talking about replacing Genshi templating system or other > components by Django, as I don't know enough about the subject) > I'd be interested to see your experiment. Do you plan to make it public? I've considered as an experiment to try and make Trac run on Django or Flask (i.e. replace the Trac framework). I mainly interested in the idea though as a way to learn and compare frameworks, and see if there is anything useful that we can adopt in the Trac framework. In order to evaluate your idea of Trac-Django integration as a project we'll need more details of what you have in mind. > Olemis created a ticket related to this topic: > https://labs.blood-hound.net/ticket/287 > > I don't know what is the "market share" for issue tracking system, but > it seems that a lot of e-commerce website could benefit from that. > > Just throwing some ideas... >
