<div dir="ltr">I agree with Ken.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 11, 2016 at 10:15 PM, Ken Moellman <span dir="ltr"><<a href="mailto:ken.moellman@lpky.org" target="_blank">ken.moellman@lpky.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-size:10pt;font-family:Verdana,Geneva,sans-serif">
<p> </p>
<div>So, I'm breaking this down, and I still have a few concerns. (I never intended to de-rail before, sorry about that.)</div>
<div> </div>
<div> </div>
<div>First, there are committees with no power to spend, but are strategic in nature that would fall under this proposal. Specifically, I can tell you that the Ballot Access Committee has discussed important strategies on how to achieve ballot access. </div>
<div> </div>
<div>I have already heard from some members that they believe committee transparency would expose our strategy, putting us at greater risk of being on the wrong end of shenanigans. By the wording, these substantial strategies would be required to be exposed. </div>
<div> </div>
<div>And it's not even just the Ballot Access Committee. Look at Affiliate Support or Candidate Support; do we really want to let our opposition know our next few chess moves? I foresee a day where our opposition raises money to counter the actions of a candidate to be funded by the LNC before the candidate even gets the money from the LNC. Politics is a game of chess, and telling your opponent your next 3 moves means you're either really good, or really dumb. And I don't see us winning elections, so that might narrow such a move into only one of those two categories...</div>
<div> </div>
<div>I'm all about transparency, but only after the information is of no value to our opponents anymore, and cannot be used by our opponents to cause harm to the party or its candidates.</div>
<div> </div>
<div> </div>
<div>Second, a committee would be able to set their own rules on executive session. What stops a committee from adopting rules that puts them permanently into executive session whenever they're in a business meeting? Unless, of course, we create special rules for every committee (and clutter up the Policy Manual -- sorry, but it's true!)</div>
<div> </div>
<div> </div>
<div>Third, you're talking about creating new mailing lists aliases. That's more work for the LNC staff. </div>
<div> </div>
<div><br>Fourth, the Ballot Access Committee has had one or two emergency meetings. There are times when 48 hours notice is not realistic.</div>
<div> </div>
<div> </div>
<div>Fifth, I strongly oppose publishing my phone number on LP.org. I'm already annoyed enough that I get phone calls from petition coordinators from around the US. It is great to have my phone going off in the middle of the day while I'm trying to be on a conference call, or trying to lead a meeting (sarcasm). Maybe some folks like having their phones blown up and being put on spammer phone lists. I do not.</div>
<div> </div>
<div> </div>
<div>Finally, I would suggest not hardcoding the "public reflector" language. There are better ways to publicize mailing lists that don't involve the current configuration which could be examined in the future. </div>
<div> </div>
<div> </div>
<div> </div>
<div>So, now that I'm through everything that I see wrong with it, here's what I'd counter-propose:</div>
<div> </div>
<div><strong><em>Any committee which has been empowered to expend funds shall notify the LNC chair, in writing, of the exact wording of any motion passed by the committee to expend funds, and the LNC chair shall be responsible for approving those expenditures prior to funds being expended. All expenditures shall be recorded in compliance with the law and this policy manual. All expenditures shall be reported to the full LNC at the next in-person LNC meeting.</em></strong></div>
<div> </div>
<div> </div>
<div>---<br>
<p>Ken C. Moellman, Jr.<br>LNC Region 3 Alternate Representative<br>LPKY Judicial Committee</p>
</div><div><div class="h5">
<p> </p>
<p>On 2016-08-11 22:20, Caryn Ann Harlos wrote:</p>
</div></div><blockquote type="cite" style="padding:0 0.4em;border-left:#1010ff 2px solid;margin:0"><div><div class="h5">
<div dir="ltr">As per the request of several committee members, here once again is what I like to offer as a Policy Manual Amendment:
<div> </div>
<div>
<p><span>2) Committee Transparency</span></p>
<p>The names and contact information (phone number, email address, or both)for all committee members shall be posted on the LP.org website. Unless otherwise specifically excepted on a committee-by-committee basis or within the committee's own published standing rules for "executive session," all committee meetings shall be open to any member of the National Party to observe or listen and all electronic committee correspondences shall bemade available on a public reflector system on the LP.org website, the location of which will be published with the committee contact information. Notices, minutes, agendas, and call-in information of committee meetings shall be published to said reflector list or otherwise on the LP.org <<a href="http://lp.org/" target="_blank"><span>http://lp.org/</span></a>> website, including a record of all substantive committee actions and how each membervoted. At least 48 hours public notice will be given for any committee meeting.</p>
<div> </div>
<div> </div>
<div>My intent for this is that I want to empower committees but will oppose that if it adds a layer of opacity that does not presently exist. Right now, we as an LNC are micromanaging things, but at least the members can see the decisions.</div>
<div> </div>
<div>I would like some real discussion on this and respectfully ask that any discussions about the policy manual being too long, or needing to be consolidated, that do not debate or make suggestions as to the merit of this specific proposal have their own email thread.</div>
<div> </div>
<div>I want to sponsor with Joshua Katz a Candidate Support Committee. But I cannot/will not unless we have transparency in place either in the description of that committee or as a general rule which guides all of our committees.</div>
<div> </div>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div><span style="color:#666666;font-family:arial,helvetica,sans-serif;font-size:large"><strong>In Liberty,</strong></span></div>
<div><span style="color:#666666;font-family:arial,helvetica,sans-serif;font-size:large"><strong>Caryn Ann Harlos</strong></span></div>
<div><span style="font-size:xx-small">Region 1 Representative, Libertarian National Committee </span><span style="font-size:x-small">(Alaska, Arizona, Colorado, Hawaii, Kansas, Montana, Utah, Wyoming, Washington) - <a href="mailto:Caryn.Ann.Harlos@LP.org" target="_blank">Caryn.Ann. Harlos@LP.org</a></span></div>
<div><span style="font-size:x-small">Communications Director, <a href="http://www.lpcolorado.org" target="_blank">Libertarian Party of Colorado</a></span></div>
<div><span style="font-size:x-small">Colorado State Coordinator, <a href="http://www.lpradicalcaucus.org" target="_blank">Libertarian Party Radical Caucus</a></span></div>
<div> </div>
<div> </div>
<div><span style="font-size:x-small"> </span></div>
<div style="font-size:12.8px"> </div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div></div><div style="margin:0;padding:0;font-family:monospace">______________________________<wbr>_________________<br> Lnc-business mailing list<br> <a href="mailto:Lnc-business@hq.lp.org" target="_blank">Lnc-business@hq.lp.org</a><br> <a href="http://hq.lp.org/mailman/listinfo/lnc-business_hq.lp.org" target="_blank">http://hq.lp.org/mailman/<wbr>listinfo/lnc-business_hq.lp.<wbr>org</a></div>
</blockquote>
</div>
<br>______________________________<wbr>_________________<br>
Lnc-business mailing list<br>
<a href="mailto:Lnc-business@hq.lp.org">Lnc-business@hq.lp.org</a><br>
<a href="http://hq.lp.org/mailman/listinfo/lnc-business_hq.lp.org" rel="noreferrer" target="_blank">http://hq.lp.org/mailman/<wbr>listinfo/lnc-business_hq.lp.<wbr>org</a><br>
<br></blockquote></div><br></div>