We are still interested in providing the adaptor. Look forward to the 'Getting Started'. Regarding the 'Maintaining problem', this is not a problem as evidenced by the IBM Rails adaptor project as Rails has progressed from 1.x to 2.x
On Apr 14, 2:26 pm, Robert <[EMAIL PROTECTED]> wrote: > If have I understood problem well: > - ibm guys are developers > - community guys are supporters > - developers may NOT look existing code > - developers may look at technical specification > - since django hasn't got specification for writing backend - > developers can't do anything > - supporters may look at code and write specification based on this, > and provide it to developers (so. supporters are eyes for > developers ;) ) > - developers can start job based on this - implement api based on > specification > - developers can test backend running django backend/all unittests > - supporters can help when developers hit problem that can't be > solved without reading the code or asking django developers directly > - supporters can do tests too > - after all tests are passed - we have "beta" - django developers > review this and decide if to integrate in trunk - or some adjustments > should be done before integration > - if this is going to be part of django trunk - there is license > issue which should be solved - django license and ibm license are not > the same > > I neededdb2personally and I wrote onedb2driver myself (http:// > code.google.com/p/ibm-db/issues/detail?id=10,http://code.djangoproject.com/ticket/6995), > and later I found that someone have done this before me (http:// > code.djangoproject.com/ticket/5052). Maybe this could be of use. > > = Maintaining problem = > On the other hand, IMHO this ibm license problem is pretty "strange" > for Open source project, you develop something open/free for project > having "source open" for reading ... That could be the problem in > future, each backend api improvement/change needs writing > specification - just for ibm guys. > > I see two things that can be done: > - (easiest) if someone from ibm can do something to remove license > obstacle > - if django team can integrate specification which will is to be done > (if I have understood correctly Jacob suggestion, putting it in > backends\__init__.py as pydoc ...) and someone should maintain this > > = Getting started = > For the start we could provide ibm team some backend api specification > to get things started, e.g. > generating pydoc for: > -http://code.djangoproject.com/browser/django/trunk/django/db/backends... > -http://code.djangoproject.com/browser/django/trunk/django/db/backends... > -http://code.djangoproject.com/browser/django/trunk/django/db/backends... > -http://code.djangoproject.com/browser/django/trunk/django/db/backends... > - ... > and explain shortly what is to be done. > > If this suites ibm team and django team doesn't have complains, then > we could start (jeffself, Alex P from ibm, I'm willing to help > too, ...). > > On 26 ožu, 14:45, jeffself <[EMAIL PROTECTED]> wrote: > > > Since I'm the originator of this thread, (thank me or curse me), I'll > > be glad to help out in whatever ways possible. I know Jacob said he > > was going to write the documentation for this. What kind of > > assistance can I provide? > > > I'll be glad to test the driver that eventually gets written as well. > > Especially since I'm the one who needs it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
