[OpenID board] Admins of the Membership / Election Tool?

[David Recordon]

So far (it's been less than an hour) it has had no impact.  One new  
member who hasn't yet paid and was not on the spreadsheet that I  
emailed.

--David

On Dec 6, 2008, at 2:33 PM, Brian Kissel wrote:

> By the way David, what have you found out about the impact of the  
> membership outreach, can you share the results with us?
>
> Cheers,
>
> Brian
> ==============
> Brian Kissel
> Cell: 503.866.4424
> Fax: 503.296.5502
>
>
> -----Original Message-----
> From: board-bounces at openid.net [mailto:board-bounces at openid.net] On  
> Behalf Of David Recordon
> Sent: Saturday, December 06, 2008 1:59 PM
> To: board at openid.net
> Subject: [OpenID board] Admins of the Membership / Election Tool?
>
> After sending out the pending member emails, I wanted to figure out
> how I could see if they have any impact in terms of new
> registrations.  Figured the easiest way to do this (since I'm not an
> admin on the web tool) was to count the rows in the database table
> that only lists members (I'm specifically avoiding looking at anything
> that has to do with the ongoing election).  One thing I noticed is
> that we currently have four "admins": Peat, Darin, Mart, and Brian.  I
> understand Peat and Darin, Mart became an admin just to troubleshoot a
> member's login issue this morning, but why is Brian Kissel an admin?
>
> Can anyone shed some light on this?  For the time being, I've removed
> Brian as an admin especially since he is also running in this  
> election.
>
> Thanks,
> --David
>
> _______________________________________________
> board mailing list
> board at openid.net
> http://openid.net/mailman/listinfo/board
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus  
> signature database 3668 (20081206) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus  
> signature database 3668 (20081206) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>