[Mailman-Developers] HyperKitty login

[Richard Wackerbarth]

Stephen,

"social_auth" is a django "app" (Think library) that handles OpenID, BrowserID, Google, Twitter, etc. authentication.
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.

This is important because "Sally", as a website designer, will want to have Postorius, HK, and her own (for example project status or e-commerce) material delivered as a single website. The end-user, "Bob", will think of this as a single website and not as three websites cobbled together. He perceives that he logs into the site, not the mailing list or archives. He certainly wants to log in only once to be able to access all of the functions of any of the components. Since the login access and (at least some of) the user tools would likely appear in the header of (almost) every page on the website, each component needs to make these items available to the site designer for her inclusion in the sites "base_site.html" template and ALL of the submodules, including django.contrib.admin, need to extend a single (remember DRY) common template. This infers that, where possible, each of these should use the same css classes in a consistent way.

As for George posting to both his blog and this list, I think that the purpose in his doing so is to make additional members of the developer community aware of his activity. Since he is still in the design phase for the interfaces to both the web side and the MM core side, it is important for him to get early feedback. In keeping with the DRY principal, it might be more appropriate for him (and Aamir, etc.) to post simple paragraphs

"Work progressing on .... See my latest update on <a href="http://...">my Blog</a> for additional details.

to this list when they have made a significant posting. 


Richard


On May 29, 2012, at 11:37 PM, Stephen J. Turnbull wrote:

> Aamir Khan writes:
>> Hi everybody!
>> 
>> First task I am going to do for my GSoC project is to have login
>> authentication mechanism for HyperKitty users. I have had discussion with
>> few mailman developers about it. I am planning to wrap up social_auth into
>> mm_ui_auth django application. Both postorius and HyperKitty can use this
>> app for authenticating users.
> 
> Please explain in somewhat more detail.  Not all of us know what
> "social_auth" is, and since Postorius and HyperKitty are independent
> apps, presumably there will need to be some design and coordination
> effort to get everybody on the same page.
> 
> In the spirit of "DRY" (don't repeat yourself), rather than make long
> posts here, I suggest that you start a blog or a Wiki page on the
> Mailman site where you can log (1) your design decisions and (2) any
> agreements on APIs etc you make with other Mailman developers (or
> third parties such as maintainers of libraries you use).  Then you can
> simply have a shortcut key and say
> 
> "I've designed an authentication mechanism for HyperKitty users, which
> I expect to be extensible for use by Postorius and other Django apps
> for Mailman.  See my blog: http://blogs.example.com/~aamir/gsoc/."
> 
> George is doing this quite well IMO.  Kudos to George!
> 
> N.B. George is generally copying his blog post to this list.  That's
> OK if you want to do it, but IMO not necessary.  (But that's something
> we will evolve over time, and I defer to Terri's opinion on this kind
> of thing.  This is all just a suggestion.)