django-rest or Reviving django-rest-interface

December 23rd, 2009
I have taken it upon myself (which is probably more than I can handle!) to revive the django-rest-interface project. The new project is called simply django-rest and you can find it on Google code here: http://code.google.com/p/django-rest/ Currently the project is a shameful clone of django-rest-interface, which unfortunately seems to have been inactive for some time. I even ripped the Wiki pages! If you never heard what django-rest-interface is, than I recommend you check it out. It provides an easy way of creating RESTful layer on top of your models, treating them as resource, but also allows you to define a non-model resources. Why clone? There are a few reasons why I chose to copy the project instead of contributing to existing one:
  1. can't contribute :-) author is non-responsive
  2. django-rest-interface project was inactive for the last year
  3. it was hosted on subversion, whereas I am using Mercurial, which allows for much easier cloning and contributions
  4. It's fun! I like REST architecture style and I think this project is worthwile working on.
How to contribute
It would be great to know if anyone else if interested in contributing. Currently you can do it in a few ways:
  1. Try it out! Just by trying it you can probably find a few bugs and suggest a few improvements.
  2. Port some of the issues found in the original issue tracker to the new project's issue tracker, if they are still relevant.
  3. Clone the project and contribute improvements.
  4. Clone the Wiki (yes you can checkout the wiki too!) and contribute documentation.
  5. Make sure the licensing is correct.
In the end I hope django-rest will be very useful to people. I am sure there are a lot of users of django-rest-interface who would be willing to give back to this new project, improving it for everybody.
blog comments powered by Disqus