On Wed, Nov 24, 2010 at 10:06 AM, Ian Caldwell <inchosting@...360...400...> wrote:
As for the django. I like the idea, of it, However it needs to have a few things in mind if we go ahead and deploy the site in Django.
 
#1. It needs to be easy to update as needed,
Django can tie in with MySQL quite happily.
 
#2. code needs to be well commented so Joe blow of the street ten years from now should be able to understand the code or at least read the comments.
That shouldn't be an issue.  Django code tends to just make sense.

also it needs to be able to be expandable, have built in comments, admin, localization, news, pages etc all of that.
The work's been done for that sort of thing.

As for easy updating of content, a web interface is possible, integration with a bzr repository is possible (this would be my favourite way of doing it and would be very simple, actually, as it can then be file-based rather than database-based, which also makes it infinitely easier for searching without depending on the website, and makes things like batch changes trivial), really anything you feel like is possible with a bit of effort.  Some things are easier than others, naturally.  And when it gets to things like an extensions repository, as discussed earlier - doing it well with Drupal would be difficult but fairly easy with Django, including very good integration with the rest of the site.

Also osuosl currently manages sqlite and mysql servers specifically for high load sites, ARe you able to work the database into that?
Django can use MySQL quite happily.  And concerning load, as we checked last time, OSUOSL are happy with using Django, they just want to be cautious about load.  I don't think load will be much of an issue at all; provided the apps used in the project are not written too badly, Django/Python scales better than Drupal/PHP.

I like the idea of drupal because of how easy it is to add accounts and collaborate on adding pages news etc....
No one would use Django if things like that couldn't be done easily.

We could even tie in OSQA - http://www.osqa.net/ - and get a Stack Overflow-like system.  (That would really be a very suitable medium for Inkscape questions, I think.  Better than the traditional forum model.)  And the beauty of Django is that you can connect that to the rest - it doesn't need to be separate applications that you try to integrate, you dump the apps it uses into the project and it all Works.  (Disclaimer: I haven't actually tried deploying OSQA yet.)


Regards,

Chris Morgan