<div dir="ltr"><h2 id="Purpose_.26_Common_Goals"><font size="2"><span style="font-weight:normal">Here's my first shot. Invite adding more, yet keeping it simple so we don't get hung up on this simple step.</span></font></h2><br><h2 id="Purpose_.26_Common_Goals"><span style="font-weight:normal">Purpose & Common Goals</span></h2>
<span class="" id="line-12"></span><p class="">To help connect Pythonistas in Cuba with the PSF in terms of providing resources and support to User Groups and Events, such as Pycons or PyDays in Cuba.<span class="" id="line-13"></span><span class="" id="line-14"></span></p><p class="">
</p><h2 id="Active_Time"><span style="font-weight:normal">Active Time</span></h2>
<span class="" id="line-15"></span><p class="">The workgroup will consider disbanding after a few Python-related events in Cuba occur smoothly, with PSF participation and support. Our job will be done then.<span class="" id="line-16"></span><span class="" id="line-17"></span></p><p class="">
</p><h2 id="Core_Values_.26_Internal_Governance"><span style="font-weight:normal">Core Values & Internal Governance</span></h2>
<span class="" id="line-18"></span><p class="">The group will abide by the guidelines of the PSF when it comes to advising others as to its stipulations regarding use of trademarks the PSF works to protect.<span class="" id="line-19"></span><span class="" id="line-20"></span></p><p class="">
</p><h2 id="Rules_.26_Decision_Making_Procedures"><span style="font-weight:normal">Rules & Decision Making Procedures</span></h2>
<span class="" id="line-21"></span><p class="">The working group may draw up memoranda of intent conveying plans to provide support which may require PSF Board approval. We will move forward by consensus punctuated by periods of brainstorming and free-wheeling debate.<span class="" id="line-22"></span><span class="" id="line-23"></span></p><p class="">
</p><h2 id="Communication_Plan"><span style="font-weight:normal">Communication Plan</span></h2>
<span class="" id="line-24"></span><p class="">The working group takes the form of a mail-man listserv within Python.org. It has a public archive. One joins by approval of the moderator.<span class="" id="line-25"></span><span class="" id="line-26"></span></p><p class="">
</p><h2 id="List_of_Participants.2FWho_we_are"><span style="font-weight:normal">List of Participants/Who we are</span></h2>
<span class="" id="line-27"></span><p class="">David Mertz is the moderator. Other members of the group are currently: .... One does not need to be a member of the PSF, voting or otherwise, in order to join the working group. We may seek to invite guest subscribers to share expert advice and perspectives.<br></p><p class="">
</p><h2 id="Support_Requirements"><span style="font-weight:normal">Support Requirements</span></h2>
<span class="" id="line-30"></span>Simply a mail-man listserv in the Python.org domain with a public archive and a public listing as a Working Group.<br><div class="gmail_extra"><br><div class="gmail_quote"><br>==<br><br></div><div class="gmail_quote"><b>WG vs SIG?</b><br></div><div class="gmail_quote"><p>I am curious what charter is required simply for a listserv, such as
<a href="mailto:i18n@python.org">i18n@python.org</a> -- what is the difference between a SIG and a Working
Group I wonder. <br></p><p>Part of the reason I ask is there's been
some talk of a psf-community to allow public engagement in our
electronic voting (e-voting) experiments, something the PSF is engaged
in of intrinsic interest to voters everywhere.<br></p><p>I was thinking in terms of evote-sig or psf-elections-sig more as a
listserv than as a working group and need to learn more about the
difference.</p><p><br></p><p>Kirby<br></p><br></div><br></div></div>