Posting my humble $.02 on this interesting subject: Given the existance of a django.db.backends.dummy module that probably contains, in *some* form, all of the required information to produce a document with "API signatures and entry/exit conditions", i would say the easiest to go is to hire (or lend) a developer and have the module code translated into Dutch, Spanish, English or whatever lingo IBM lawyers be happy with and IBM devs can read and code to.
I think (but i do not speak for them) at least one core django developer will be happy to look at the resulting document and comment on it. IBM is a very big contributor of Open Source but the business is "commercial" software. Lines between commercial software and open source do get blurry from time to time as is the case with DB2 Express- C for example. So, "Let's all shut up ... and write some documentation :) "... is a message that can be acted up on by open source developers in IBM offices as well. It will broaden the business opportunities for the DB2 product so some investment for the lift off seems easily justified. Best regards Niels (wow, i'm Dutch :) On Mar 25, 10:59 am, Ned Batchelder <[EMAIL PROTECTED]> wrote: > I thought I would end this standoff by simply going where James pointed, > and turning it into the minimal "spec" Alex describes. I know next to > nothing about db backends, but it sounded like this was a job for a > scribe, not a developer. > > Unfortunately, django.db.backends.dummy falls below the bar for minimal > API documentation. While it may have the names of the entry points, > they are all defined as complain(*args, **kwargs), and they have no > docstrings or comments, so there is no guidance about what they expect, > do, or produce. > > Perhaps James mis-spoke: django.db.backends contains base classes, and > has much more useful information. > > --Ned.http://nedbatchelder.com/blog > > > > > > James Bennett wrote: > > On Mon, Mar 24, 2008 at 11:15 PM, Alex P <[EMAIL PROTECTED]> wrote: > > >> 1. The original message was in brief: there is a growing interest in > >> the Python community for DB2 support, and we (developers behind IBM_DB > >> driver, DB-API wrapper and SQLAlchemy adapter) are interested to help > >> in the Django context if some _minimal_ documentation is provided in > >> an unrestricted form, even under a Open Source license like BSD (even > >> with sample/example API usage code, for that matter). > > > The thing is, though, that there *is* a minimal API documented: > > django.db.backends.dummy. If this were Java, you could take that as > > laying out the interface to be implemented. The confusion came from > > the apparent refusal to deal with this because it's in the form of > > open-source code. > > -- > Ned Batchelder,http://nedbatchelder.com- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
