On Wednesday, April 4, 2012 at 1:16 PM, Alex Ogier wrote: > To Adrian specifically: You have indicated on this list that you are eager to > have at this problem yourself, and that may make this proposal a non-starter. > I think we are very much on the same page in terms of technical direction and > end goals of the refactoring: I want to make this change as conservative as > possible from a technical standpoint, but document, test and validate it as > much as possible from the community's standpoint. I think we have strong > motivation for the specific decisions we agreed on, and they give the project > enough direction that it will rapidly become obvious if and when I am > derailing your conception of what needs to be done, so I hope you will > consider letting it be done as a GSoC project. > > >
The issue is specifically that GSoC does not allow collaboration -- all the code needs to be written by the student. There's a lot of people, including Adrian, who want to contribute; doing this as a GSoC project would actively prevent them from contributing. Auth refactoring really can't be a GSoC project, sorry. If you really want to work on auth, you'll need to do it outside of GSoC. If it's an issue of money making the difference between being able to work on the project and not, then let me know. We can perhaps look at taking the costs until the DSF's wing instead of GSoC, and thus not get into the way of Google's rules. Jacob -- 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.
