<br><br><div class="gmail_quote">On Sun, Feb 24, 2008 at 3:41 PM, Austin Che <<a href="mailto:austin@csail.mit.edu">austin@csail.mit.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
> 3. The person who invited the user currently isn't being sent. I think this<br>
> may be important; I've added support for it but I have a few questions.<br>
><br>
> A. Should people need to be logged in to send the message?<br>
<br>
</div> Definitely. Avoid being a spam relay.<br>
<div class="Ih2E3d"></div></blockquote><div><br>>>Excellent point. I should have thought of that before.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
> B. Should the name of the member be included in the message?<br>
<br>
</div> Yes. That's much more likely to get a response.<br>
<div class="Ih2E3d"></div></blockquote><div><br>>> Since they're logged in, I'll add it. I can use the template to fill in the username of the person sending the message in the text.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
> C. Where should we put the button or label to send the invitation?<br>
<br>
</div> Maybe on the how to join page.</blockquote><div><br>>>Good place for now.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><div class="Ih2E3d">
> D. Should we record the invite and then send a message to the person who<br>
> submitted the invitation when the invitee registers?<br>
<br>
</div> That might be difficult to tell unless you have some unique cookie<br>
or something for them to accept the invitation. It would be easier<br>
to do the reverse and have a field on registration that has the<br>
inviter's user name. Even better, it should be possible to<br>
generate a link that when clicked, pre-fills out the registration<br>
form with various items (such as inviter's name, maybe the lab, etc.)<br>
<div class="Ih2E3d"></div></blockquote><div><br>>>The email address is unique. I'll use it for now. If they join with a different email address, we lose. No big deal. <br><br>>>We can also do the same thing that gets done via the email confirm: we put a token in that they can click on to register.<br>
When they click on it, we preload the email address and get the context that allows us to send the thank you message to the inviter.<br>I've re-used the MediaWiki code to do this before. </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
> E. Should we allow the person submitting the invitation to add an additional<br>
> comment?<br>
<br>
</div> Can't think of why not.<br>
<div class="Ih2E3d"></div></blockquote><div><br>>>Done.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
<br>
> F. Should we allow for sending invitations to more than one person? We can<br>
> do a whole lab if we want; I'm current;y taking in just one name.<br>
<br>
</div> They probably can just send it to a mailing list.<br>
<div class="Ih2E3d"></div></blockquote><div><br>>>I''m adding support for 5 addresses. Copy and past. <br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
> G. Should we offer to cc: the message sent out to the person sending the<br>
> invitation?<br>
<br>
</div> Sure why not.<br>
<div class="Ih2E3d"></div></blockquote><div><br>>>OK.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
> Recording the invitation isn't a lot more effort to implement and would make<br>
> for a way to let users know we appreciate their efforts. It also gives us<br>
> quantitative info on who's being invited and how often the inviation is<br>
> acted upon.<br>
</div></blockquote><div><br>>> Database table is now present for invites. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><br>
</div> Might as well record it if possible.<br>
<br>
I think we need to implement a karma system. 'Worthless' numbers<br>
indicating the value of a member is surprisingly good at<br>
motivating people to do things in communities. We can do something<br>
like the weighted sum of:<br>
- number of invited people<br>
- total number of edits<br>
- number of articles created<br>
- number of emails sent to discuss mailing list<br>
- etc.<br>
<font color="#888888"></font></blockquote><div><br>>> We need to talk about this. Sounds like a great idea.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<font color="#888888"><br>
--<br>
Austin Che <<a href="mailto:austin@csail.mit.edu">austin@csail.mit.edu</a>> (617)253-5899<br>
_______________________________________________<br>
OpenWetWare Discussion Mailing List<br>
<a href="mailto:discuss@openwetware.org">discuss@openwetware.org</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/oww-discuss" target="_blank">http://mailman.mit.edu/mailman/listinfo/oww-discuss</a><br>
</font></blockquote></div><br>