I agree with this approach. That way there's no limit to the usercount to be added. <br><br>Does everyone agree? I'll steal Ilya's form and use it instead of the one I'm using.<br><br>B.<br><br> <br><div class="gmail_quote">
On Mon, Feb 25, 2008 at 1:02 PM, Ilya Sytchev <<a href="mailto:ilyas@mit.edu">ilyas@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;">
I think we need a simpler form. Here's a mock up of what I have in mind<br>
(fields borrowed from <a href="http://pandora.com" target="_blank">pandora.com</a>):<br>
<br>
<a href="http://openwetware.org/wiki/User:Ilya/Sandbox" target="_blank">http://openwetware.org/wiki/User:Ilya/Sandbox</a><br>
<div><div></div><div class="Wj3C7c"><br>
<br>
Jason Kelly wrote:<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>
>> They probably can just send it to a mailing list.<br>
><br>
> I think it would be nice to list multiple addresses in case you want<br>
> to invite a few of your friends. Also, not sure why they need to put<br>
> in the name of the invitee, email address should be enough.<br>
><br>
> cool, this is a great addition for outreach / recruitment.<br>
><br>
> thanks,<br>
> jason<br>
><br>
> 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>
>> > 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>
>> Definitely. Avoid being a spam relay.<br>
>><br>
>><br>
>> > B. Should the name of the member be included in the message?<br>
>><br>
>> Yes. That's much more likely to get a response.<br>
>><br>
>><br>
>> > C. Where should we put the button or label to send the invitation?<br>
>><br>
>> Maybe on the how to join page.<br>
>><br>
>><br>
>> > 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>
>> 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>
>><br>
>><br>
>> > E. Should we allow the person submitting the invitation to add an additional<br>
>> > comment?<br>
>><br>
>> Can't think of why not.<br>
>><br>
>><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>
>> They probably can just send it to a mailing list.<br>
>><br>
>><br>
>> > G. Should we offer to cc: the message sent out to the person sending the<br>
>> > invitation?<br>
>><br>
>> Sure why not.<br>
>><br>
>><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>
>><br>
>> 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>
>><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>
>><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>
_______________________________________________<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>
</div></div></blockquote></div><br>