On Mon, Apr 7, 2008 at 1:45 AM, thauber <thau
...@gmail.com> wrote:
> I am going to apply for the GSoC for the Django organization. I have
> had a couple ideas and have narrowed them down to two.
> First I have talked to James Tauber and he said that he would like to
> see some hot club apps worked on for GSoC. This means I would be
> working on django-friends, django-mailer, and django-notification.
> Also he wanted to see a django based opensocial container. This would
> be my first choice, as hotclub has always been something I thought was
> important to django.
Keep in mind that the GSOC guidelines specifically exclude projects
other than coding. Feel free to correct me, but a lot of the work
required by Hotclub involves documenting interfaces and building a
community website on which to share application resources.
I agree that the Hotclub idea is an important one - but unless you can
frame it in terms of a specific coding goal, you will probably find
your application rejected.
If your project is to work on django-friends, django-mailer et al,
then your project isn't really "Hotclub" - it's to build/extend some
useful Django applications. Hotclub compliance (whatever that means at
the moment) is a feature on your to-do list, not the goal of the
project itself.
> Second I would like to work on a couchdb backend. I have been working
> on couchdb on another project and I think that it is a really cool
> database. While it may not exactly fit with couchdb document based
> database to have a relational mapping, I still think that there would
> be benefits. It would require some sort of checking to see if what
> goes in and what comes out fits the model because there is not tables
> or rows in couchdb.
I haven't played with couchdb myself, but from what I hear on the
grapevine its an interesting resource - but a completely non-SQL
resource. This would certainly be an interesting contribution.
However, keep in mind the time available for a GSOC project. Malcolm
is an extremely talented developer, yet it has taken him the better
part of 18 months to get the QuerySet refactor code to the point where
it is nearing merge quality. Integrating CouchDB has the potential to
be just as significant a change to Django. I submit to you that unless
you have a specific plan for constraining the complexity of this task,
rewriting the Django query engine to support a non-SQL query language
is perhaps a little outside the scope of a 4 month student project.
Yours,
Russ Magee %-)