Hello, Sorry for the delay.
On Wed, 12 Feb 2014 16:01:56 -0800, Ryan Ollos <[email protected]> wrote : > 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? > Potentially a lot of things: - authentication - some preferences (languages) - URL redirect - notifications by email - security (CSRF ?) - caching - database (use of Django ORM) - database migration (South) - search - logging - analytics > > 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? > Yes as soon as I got time to finish it ;-) However it is not revolutionary or anything. It is just: - shared authentication by calling Bloodhound directly through WSGI. - all url with bloodhound/* are sent to Bloodhound. - customization Bloodhound theme to integrate it to the website (with Bootstrap, I directly modifed the HTML, I haven't touched the CSS). But it is quite nice to have Bloodhound integrated in a website, instead to have it completely appart (especially for authentication). > 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. > > I just began with Django a few months ago and this is the first web dev framework I am learning, so I am not in a good position to give all the benefits of Django. However it seems that it has the same benefits of Python: it has a huge repo of available apps which cover a lot of needs. The problems with Django are pretty well advertised: it is an integrated framework with its own ORM so it may not be flexible/powerful enough for some needs. So basically what I have in mind is: the biggest problem to install Bloodhound is not Bloodhound itself, it's the whole infrastructure behind (have a secured server, apache/nginx, uwsgi/gunicorn, PostgreSQL/MySQL, etc...). If you have a running Django website, you already have all this. So if the Django admins can just install Bloodhound as an app, we may see adoption increased quickly. In addition, as you said, it may be possible for Bloodhound to rely on Django components (templating system, database, internationalization, URL management, etc.). However I don't know yet how goods are the current Bloodhound/Trac internal components compared to Django. If you have other questions, don't hesitate. I'll try to be more available ! Regards,
