8:14 p.m.
Hi!
We had a meeting today about the IRC feature.
Meetbot minutes:
https://meetbot.fedoraproject.org/teams/hubs-devel/hubs-devel.2017-02-08-...
Etherpad:
https://etherpad.gnome.org/p/fedora-hubs-irc-widget
Summary:
- Sayan identified a hole in the mockups - the case where the user has an IRC nick
registered already. We need to let them give us their already-registered nick and pass so
we can auth them. mizmo will update design accordingly.
- we will need database fields irc_enabled, irc_configured
- why a separate irc_configured field? because we know the IRC nick if they filled out in
FAS, it's been a FAS field well before ircb so we can't key just based on if the
irc nick field is populated
- If the irc_configured is False then we take the user through the nickname / freenode
registration wizard
Now that I'm reading through the minutes, I understand something I misread live in the
meeting - so Sayan proposed that we take input from the user from the wizard and only
until they complete the wizard, communicate with ircb. The problem is we need to be in
constant communication with IRC through each screen -
- First screen (nickname selection), we need to query nickserv or do a /info on the
nicknames the user tries to see if they are available or not. There is no other way to
check this.
- Second screen (email, password), we need to run a REGISTER command with nickserv over
IRC
- Third screen (email verification), we need to run a verify command with nickserv over
IRC
So it's not possible to gather all the info and then submit to IRC in one go. Or am I
missing something?
~m