Hi Nick, On Thu, 2006-10-19 at 18:48 -0700, [EMAIL PROTECTED] wrote: > Malcolm , > Thanks for you for your contributions, your presence on this project > really makes a positive difference. > > > It's already "ready" and able to be used. Chris keeps his branch in sync > > with trunk regularly and is extremely responsive to fixing bugs. It will > > be merged when we have had a chance to review it thoroughly. > > Here is a small offer that I would like you to consider: > I would be willing to pay you a couple hundred dollars $US to get this > done by next Friday(10/27/06). I wish it could be more, I'm just on a > very tight budget.
Whilst the idea isn't a bad one, I don't think I can accept this for a few reasons. Firstly, I don't think I have time in the next seven days to give it the concentration it deserves, since I already have commitments to paying clients and a couple of other things due. Secondly, I don't get ultimate say in these things -- apparently my ideas are listened to by Adrian and Jacob, but they still get final say and they are as busy as I am, by the looks of things. So any guarantees I could make would not be sufficient. Finally, I don't think it would be right for me to accept money for this type of job, getting something into the repository. If somebody wanted to pay me to do a particular piece of development on Django core and the price was right, I would certainly accept it (I've taken professional Django jobs previously and working on the main code or a project is all pretty much the same). However, that would not come with a cast-iron guarantee it would make it into core; just that it would go through the normal channels (the usual way commerical contributions to Open Source projects work). It's this last step -- actually getting the code into core, if it's a big change -- that cannot be for hire. I don't have the authority and I also don't believe it contributes positively to a project (this is the same principle that the Linux kernel, GNOME, KDE and many other projects all operate under for the same reason). To help you out, I can only repeat what I said before: all the indications are that this branch is of a high quality and Chris is working actively on fixing any problems as they arise. So if I was personally in a position where I really need row-level permissions, I would develop code against that branch on the grounds that it is reasonably up-to-date and likely to be merged back to the trunk in the near future. It makes sense to me from a technical risk perspective. If, however, you only want to work against the trunk, then you have the alternative you mentioned in your initial post: manage the permissions yourself outside of the core. A little more work, but not impossible to pull together an application-specific solution, I'm sure. Best wishes, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
