> here is what I hear you saying. > > you'd rather write your own code to do the same/similar thing to what > chris > has already done (and also what has a high chance of getting merged > in the > coming months).
What I'm trying to say, is that I was working to implement something that wouldn't impact the current functionality of Django so that I could run off of trunk without continually patching it, etc. However, after diving in, it became clear that this is a fairly complex problem that would warrant the level of work that Chis/Joseph/Others have put into solving this problem. I was hoping that someone would have a trick up there sleeve. > > and as it's your own code, you are also willing to handle all the > merges, bugfixes, > and potential incompatiblies in it by yourself, and on your own dime. > Actually, I would like to avoid this, and is why I offered to come up with some money out of my own pocket so that everyone in the community could benefit from this feature. > If you have an active interest in Chris's code, may I suggest you > petition the powers > that be for a SVN account on it, and modify it instead of writing it > the same functionality yourself. This is definitely worth considering. > > that way you can keep it current with the trunk (just like you would > have to do with your own) > and get it to a state where the trunk maintainers will feel much more > confident with merging it back > into the trunk. > Actually, I'm not sure why this isn't already in trunk. To my knowledge it doesn't dramatically affect the current auth system, it just extends it (I would like to have Chris's verify that of course). Jay Parlor and others have mentioned that they were looking at the RLP branch and have reported some of the early bugs, of which Chris promptly fixed. I played around with the branch and things generally seemed to work as prescribed. Is it possible that the core maintainers are to busy to worry about functionality that they don't really need . I have noticed that some features have been adopted to trunk rather quickly without nearly as much testing as the RLP code has already had. > That is how I would justify working on it to my boss at least ;-) I'm my own boss, that is why I have to get things done. When I worked in the Corporate world I could just say "The project will be delayed, and by the way has accounting issued our paychecks " :) Thanks for your helpful advice! --Nick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
