On 3/3/07, Ewout ter Haar <[EMAIL PROTECTED]> wrote: > I read this as saying that that the multi-db will never be incorporated > in trunk, because even if all the bugs would be worked out, even if there > would be documation, etc, etc, there is no commiter that wants to maintain > it. If it will never be in trunk, I don't want to use it.
You need to read what Jacob said. The condition for multi-db being accepted into trunk is for someone to take control of it - not just for the immediate term (finishing docs, etc), but for the medium to long term (maintenance of the code). Multi-db is a neat enough feature, but it's not an important enough feature for any of the existing core developers to take control. Therefore, someone else has to step up for the task, and the core developers have to be convinced that this person is capable of the task. That person isn't just someone that puts their hand up and says "I'll do it" - that approach is what has left us with half a dozen unmerged branches. Enthusiasm is great, but persistence is what gets the job done. Case in point - the test framework that was recently committed took about a week of actual development time, but it took 8 months to get it all accepted in trunk. And that was a relatively simple feature. What we will be looking for is a person with a track record of fixing nasty bugs, and contributing in a meaningful way to the community. In short, if the core developers don't recognize your name as a result of your previous contributions, you probably won't get the job. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
