Richard Wackerbarth writes: > Stephen, > > "social_auth" is a django "app" (Think library) that handles > OpenID, BrowserID, Google, Twitter, etc. authentication.
Yeah, I think all the mentors and most of the other subscribers here can figure that out. The questions are "which one?" (just an URL will do) and "why this one?" (ie, what are the design requirements and how does this app compare to the alternatives in meeting them?) Requirements and design are important, and the GSoC developers (== students) should be doing this work and reporting on it IMO. > It is with the DRY principal in mind that I think we should "wrap" > it to make a common login manager app that will be used by both HK > and postorius. Again, I think we all agree on that. My question is, that implies a set of requirements sufficient for both HyperKitty and Postorius. Why do we believe that such a set of requirements is known, and satisfied by the design? And how about Alex's NNTP access? If access to the archives is to be authenticated, then we would want the NNTP access to be authenticated, and consistent with HyperKitty. Can a Django authentication system do that? Can social_auth? Aamir is explicitly working on HyperKitty. While it makes a whole lot of sense for him to generalize the authorization module to Postorius (and one would hope beyond), this does require communication with the people doing Postorius. If he's talked to them and believes there's agreement on requirements, all I want to see is "I've talked to Florian on IRC about Postorius requirements for authorization, and we agree that they have the same requirements (see my blog)." Of course he's welcome to post as much detail as he likes! By the way, I think we should let the developers speak for themselves. I don't have any objection to developers getting a lot of help from mentors, but they should be able to present and to some extent defend their own work. If there's a language issue -- AFAIK none of our students are native English speakers -- they should feel free to say so, too, and we'll work that out. _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
