[Chicago] Site accounts

[Brian Ray]

I like the openID, as long as it returns the correct full name as it is
required for RSVP for security at front desk reasons. I also have used
emails to do things like invite to social networking sites and poke
speakers who decide to disappear.


On Tue, Jan 8, 2013 at 2:47 PM, Adam "Cezar" Jenkins <emperorcezar at gmail.com
> wrote:

> You'll notice it's doesn't have usernames and passwords, just OpenID
> accounts (with nice buttons to click). I assume almost everyone has a
> google, github, bitbucket, stack overflow, yahoo, etc account. I have
> Google, Github, and generic OpenID already turned on and can easily
> add others.
>
> I did this, because honestly, it's likely to sit around with very
> little maintainace for a long time and I didn't want to take the
> security burden of storing passwords for a site that's not going to be
> watched over that much. Especially when the only things we need an
> account for are talk submissions and rsvps
>
> As much as I wish they didn't, people use the same passwords for other
> sites and I don't want to find out that we got compromised and peoples
> passwords got out there because we forgot to update Django or
> something else.
>
> That said. If there is a big outcry we can turn on password based
> accounts and registration. I have been known to be wrong.
>
> I will port old meeting information over, the models are very similar,
> and I'll just have to write some minor glue code.
>
> On Tue, Jan 8, 2013 at 2:35 PM, Brian Ray <brianhray at gmail.com> wrote:
> > Carl:
> >
> > I will do my best to add the talks to the Flourish test install.
> >
> >
> > Adam:
> >
> > Good work. Can we port all existing accounts over, as well?
> >
> >
> >
> > On Tue, Jan 8, 2013 at 2:22 PM, Adam "Cezar" Jenkins
> > <emperorcezar at gmail.com> wrote:
> >>
> >> Yea, this is for flourish and just to help them out. The new Chipy
> >> site talk submission is really simple. chipy.herokuapp.com
> >>
> >> Note that I still don't have it connecting different types of accounts
> >> yet. If you use your google, then your github you'll have two seperate
> >> accounts.
> >>
> >> On Tue, Jan 8, 2013 at 2:17 PM, Brian Ray <brianhray at gmail.com> wrote:
> >> > I do not mind entering the talks; however, I do mind it if it is a big
> >> > hassle. Are you saying it is not clear on how to enter talks?
> >> >
> >> >
> >> > On Tue, Jan 8, 2013 at 2:14 PM, Carl Karsten <carl at personnelware.com>
> >> > wrote:
> >> >>
> >> >> I want this weeks ChiPy presenters  to enter their talk data into
> >> >> http://beta.flourishconf.com but it isn't obvious how.
> >> >> Will someone figure out how to enter a talk, and give feedback on how
> >> >> to make it clear?
> >> >>
> >> >> This is the codebase that PyCon uses for
> >> >> https://us.pycon.org/2013/
> >> >>
> >> >> Which now that I look at it I don't see a clear path either.
> >> >>
> >> >> --
> >> >> Carl K
> >> >> _______________________________________________
> >> >> Chicago mailing list
> >> >> Chicago at python.org
> >> >> http://mail.python.org/mailman/listinfo/chicago
> >> >
> >> >
> >> >
> >> >
> >> > --
> >> > Brian Ray
> >> > @brianray
> >> > (773) 669-7717
> >> >
> >> > _______________________________________________
> >> > Chicago mailing list
> >> > Chicago at python.org
> >> > http://mail.python.org/mailman/listinfo/chicago
> >> >
> >> _______________________________________________
> >> Chicago mailing list
> >> Chicago at python.org
> >> http://mail.python.org/mailman/listinfo/chicago
> >
> >
> >
> >
> > --
> > Brian Ray
> > @brianray
> > (773) 669-7717
> >
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > http://mail.python.org/mailman/listinfo/chicago
> >
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> http://mail.python.org/mailman/listinfo/chicago
>



-- 
Brian Ray
@brianray
(773) 669-7717
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20130108/a83b652e/attachment-0001.html>