<div class="gmail_quote">Bernie,<br><br>On Sun, Aug 23, 2009 at 17:23, Bernie Innocenti <span dir="ltr"><<a href="mailto:bernie@codewiz.org">bernie@codewiz.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* We need to state clearly what the criteria for selection is.<br>
Our current membership policy [1] is located in an obscure place.<br>
It could be moved to a separate page and linked from relevant<br>
pages (members list, etc)<br>
</blockquote><div><br>Good idea. I'll see if I can get to that tomorrow. <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;">
* Can we state that anyone who writes to <a href="mailto:members@sugarlabs.org">members@sugarlabs.org</a><br>
will receive an answer within X days? I'm concerned that potential<br>
members might be frustrated by silence.<br>
</blockquote><div> <br>Does two days seem reasonable?<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;">
* Since two people (you and Sebastian) are volunteering for<br>
membership screening, how are they going to coordinate to avoid<br>
answering twice (or not at all)? Something like an RT queue would<br>
seem useful, but installing an RT instancy only for this purpose<br>
seems overkill.</blockquote><div><br>We've set up a collaborative worksheet, and are CCing each other on all replies we make. By the way, if anybody else wants to help out, feel free to raise your hand on/off list :)<br>
</div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* I'm looking at last year's membership list and I'm seeing a<br>
lot of people who disappeared a long time ago. How are we<br>
going to clear old memberships? Wouldn't it be better if we<br>
asked people to confirm their membership every year? (asking<br>
for a small amount of money for membership would make the<br>
latter step more natural, but I'm not sure we want to do that<br>
at this time)</blockquote><div><br>I was planning on sending an initial "hiya folks, you still around and interested?" email on Sept 3th or 4th. If we don't get a reply in 7 days, we'll send another email. If we *still* don't get a yay/nay, we'll put them on a "grey area" list and remove them for next year if we don't get a reply by next time around. <br>
</div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
* Is our wiki good enough as a membership management tool? Shouldn't<br>
we look at some specific application? I could ask the FSF what<br>
they're using to manage their members.<br>
</blockquote><div><br>Well, assuming we eventually migrate to Launchpad, we can use that. (that's used to manage Ubuntu Members, among other things, and would be intergrated with everything else) In the interim, the IML page should be sufficient. <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>
* We're only giving one week of advance notice to potential<br>
contributors in a period when people are generally on vacation<br>
Why couldn't we extend the deadline for submission closer<br>
to Sep 12?</blockquote></div><br>Sure. Those were just dates I thought would be reasonable. When should they be changed to?<br><br clear="all">Disclaimer: Sebastian and I are both running for SLOB slots in the upcoming election. <br>
-- <br>Luke Faraone<br><a href="http://luke.faraone.cc">http://luke.faraone.cc</a><br>