<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Allow for individual “memberships” for a nominal annual fee.<div class=""><br class=""></div><div class="">Relatively simple solution IMHO.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 18, 2015, at 12:44 , Arturo Servin <<a href="mailto:arturo.servin@gmail.com" class="">arturo.servin@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="">My opinion is one org, one vote.</div><div class=""><br class=""></div><div class="">And individuals are welcome to help and raise their voice, but only orgs can vote.</div><div class=""><br class=""></div><div class="">I am not against individuals (in fact under my own view I could be excluded to vote unless I am representative of my org), in fact I would really love to give them a vote but I think that it would be a nightmare to measure who is/what is an active participant. For that simple reason I think that giving votes to individuals is unfeasible or full of flaws.</div><div class=""><br class=""></div><div class="">Regards</div><div class="">.as</div><div class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Wed, 18 Nov 2015 at 12:34 Chris Caputo <<a href="mailto:secretary@peeringdb.com" class="">secretary@peeringdb.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">To be clear, there won't be a change during this election.<br class="">
<br class="">
Some data so far on this election, in case useful:<br class="">
<br class="">
- 63 organizations have attempted to register to vote.<br class="">
<br class="">
- 2 organizations have been disallowed from voting due to coming under<br class="">
the purview of the draft bylaws affiliate clause (*). 1 was<br class="">
disallowed because of a parent organization affiliation, and 1 was<br class="">
disallowed because of a common control affiliation.<br class="">
<br class="">
- 1 person has been able to cast two votes, due to being involved with<br class="">
two unaffiliated organizations, while not being in a position of<br class="">
common control.<br class="">
<br class="">
- 1 person has been denied being able to vote, because they do not<br class="">
represent an organization with an active PeeringDB account.<br class="">
<br class="">
- 61 organizations are presently entitled to vote.<br class="">
<br class="">
- 48 votes have been cast.<br class="">
<br class="">
- That's >78% participation from those entitled to vote. (draft bylaws<br class="">
quorum is 10%)<br class="">
<br class="">
> Also, to ponder - if the rule is to keep only one person per org to have<br class="">
> a vote, what's to keep multiples from an org from voting as individuals?<br class="">
<br class="">
Something to think about here is who does PeeringDB exist for? It could<br class="">
be argued it exists for the organizations that have records maintained in<br class="">
the database, and not for individuals. If organizations are who PeeringDB<br class="">
exists for, then it makes sense to have them be the source of votes.<br class="">
<br class="">
An option to consider is to continue with one-vote-per-org but have an<br class="">
additional class of Members, which would be made up of active admins<br class="">
declared by the Board, with a Membership term of 1-year (renewable). The<br class="">
risk with that is that you may have inactive admins fight for a vote,<br class="">
causing strife with the truly active admins. You'll also have to deal<br class="">
with the issue of whether an active admin can vote individually and for an<br class="">
organization or organizations. Respectfully, I am not sure the above 1<br class="">
denied vote makes it worthwhile to figure out, given that carefully<br class="">
crafted bylaws language will be needed.<br class="">
<br class="">
A problem with opening up membership to individuals in general, is that<br class="">
there would likely need to be some criteria to limit the voting pool.<br class="">
Membership fees would be one method, but then you've got the overhead of<br class="">
managing that. By limiting to organizations, we are able to use the<br class="">
notion of an active PeeringDB account as the criteria.<br class="">
<br class="">
> Also, did we anticipate the case where people get multiple votes because<br class="">
> they are multiple orgs?<br class="">
<br class="">
Yes, that was expected. But the affiliate clause (below) limits the<br class="">
frequency of that.<br class="">
<br class="">
As an aside, if you want to vote but haven't, please refer to:<br class="">
<br class="">
<a href="http://lists.peeringdb.com/pipermail/pdb-gov/2015-November/000111.html" rel="noreferrer" target="_blank" class="">http://lists.peeringdb.com/pipermail/pdb-gov/2015-November/000111.html</a><br class="">
<br class="">
Chris<br class="">
<br class="">
* <a href="https://www.caputo.com/pdb/20151112_PeeringDB_DRAFT_Bylaws.pdf" rel="noreferrer" target="_blank" class="">https://www.caputo.com/pdb/20151112_PeeringDB_DRAFT_Bylaws.pdf</a><br class="">
- 2.3.2 Members who are affiliated with each other are entitled to a<br class="">
total of one vote upon each issue. "Affiliate" means, with respect to<br class="">
a particular person, any entity that directly or indirectly controls,<br class="">
is controlled by, or is under common control with such person.<br class="">
<br class="">
On Wed, 18 Nov 2015, Daniel Golding wrote:<br class="">
> I'm with Steve here. I don't like that involved individuals don't get a voice. But changing the rules in the middle of an<br class="">
> election is worse. <br class="">
> Also, to ponder - if the rule is to keep only one person per org to have a vote, what's to keep multiples from an org from voting<br class="">
> as individuals? Also, did we anticipate the case where people get multiple votes because they are multiple orgs?<br class="">
><br class="">
> After this election, I think we should strong consider one person/one vote. Otherwise, its just a mess.<br class="">
><br class="">
> Dan<br class="">
><br class="">
> On Monday, November 16, 2015, Steve Feldman <<a href="mailto:steven.feldman@cbsinteractive.com" target="_blank" class="">steven.feldman@cbsinteractive.com</a>> wrote:<br class="">
> After reviewing the bylaws, I agree with this view.<br class="">
> Sections 2.2 and 2.3 are unambiguously clear that only business entities may be members, and only representatives of<br class="">
> members are entitled to cast votes.<br class="">
><br class="">
> While I think we can agree that this leads to a regrettable effect in this case, it's too late to change the rules for this<br class="">
> election. Doing so could easily give the appearance of impropriety.<br class="">
><br class="">
> The incoming board has the authority and ought to address this and a few other issues I see in the bylaws (especially<br class="">
> clarifying the affiliation rules) well in advance of the next election.<br class="">
><br class="">
> Steve<br class="">
><br class="">
> On Mon, Nov 16, 2015 at 6:11 AM, Dave Temkin <<a href="mailto:dave@temk.in" target="_blank" class="">dave@temk.in</a>> wrote:<br class="">
><br class="">
><br class="">
> On Sun, Nov 15, 2015 at 8:38 PM, Matt Griswold <<a href="mailto:grizz@20c.com" target="_blank" class="">grizz@20c.com</a>> wrote:<br class="">
> * Chris Phillips <<a href="mailto:cphillips@aptient.com" target="_blank" class="">cphillips@aptient.com</a>> [151115 17:20 -0800]:<br class="">
> > Begs the question, what defines a highly-active member? And of which<br class="">
> > community, peering in general or within PeeringDB itself?<br class="">
> Right, which is why we axed giving admins special membership to begin<br class="">
> with.<br class="">
><br class="">
> In this case, I believe he was referring to the PeeringDB community,<br class="">
> since Florian does support tickets and helps out a lot.<br class="">
><br class="">
><br class="">
><br class="">
> I don't like the way this feels. Think about it in this context:<br class="">
><br class="">
> I have two votes today - for FL-IX and Netflix. Does this mean I should have 3 votes, an additional one for the fact<br class="">
> that I'm a PDB admin?<br class="">
><br class="">
> I don't think you're silencing someone by not giving them a vote; I think you're cementing legitimacy in the election<br class="">
> by sticking to a documented process and procedure. This (hopefully) isn't a popularity contest - it's a real election<br class="">
> for a real asset with real responsibilities. <br class="">
><br class="">
> The bylaws are clear- membership is proscribed to an organization (the use of the word "may" there is the opposite of<br class="">
> "may not" and is inclusive), with an individual representative of that organization.<br class="">
><br class="">
> I'm in favor of being an inclusive organization, and Florian absolutely deserves a vote - whether it's his own<br class="">
> through an organization, or proxied through another. This is something that needs to be fixed before the next<br class="">
> election (to be clearer).<br class="">
><br class="">
> Regards,<br class="">
> -Dave<br class="">
><br class="">
> <br class="">
><br class="">
> ><br class="">
> > On 11/15/2015 3:28 PM, Chris Malayter wrote:<br class="">
> > > I agree with Matt. There’s no reason to silence a highly active<br class="">
> > > member of the community.<br class="">
> > ><br class="">
> > > -Chris<br class="">
> > ><br class="">
> > >> On Nov 15, 2015, at 6:21 PM, Matt Griswold <<a href="mailto:grizz@20c.com" target="_blank" class="">grizz@20c.com</a>> wrote:<br class="">
> > >><br class="">
> > >> I read it as (and did when we were making it) a corporation may be<br class="">
> > >> a member in addition to an individual. Not a huge deal and I<br class="">
> > >> agree that we shouldn't change any language now, but thought it<br class="">
> > >> should be brought up for future board consideration.<br class="">
> > >><br class="">
> > >> In cases like this, where Florian isn't currently at an<br class="">
> > >> organization yet retains his account because he's an admin and<br class="">
> > >> does tickets, I think he should still have a voice in any<br class="">
> > >> election.<br class="">
> > >><br class="">
> > >><br class="">
> > >> * Chris Caputo <<a href="mailto:secretary@peeringdb.com" target="_blank" class="">secretary@peeringdb.com</a>> [151115 18:04 +0000]:<br class="">
> > >>> Keeping in mind article 2 of:<br class="">
> > >>><br class="">
> > >>> <a href="https://www.caputo.com/pdb/20151112_PeeringDB_DRAFT_Bylaws.pdf" rel="noreferrer" target="_blank" class="">https://www.caputo.com/pdb/20151112_PeeringDB_DRAFT_Bylaws.pdf</a><br class="">
> > >>><br class="">
> > >>> The intention as written is that there is one class of members and<br class="">
> > >>> that class consists of organizations, each with a single vote.<br class="">
> > >>><br class="">
> > >>> - 2.2 Qualifications for Membership.<br class="">
> > >>> - A corporation, limited liability company, partnership or<br class="">
> > >>> other legal business entity may be a Member of the Corporation.<br class="">
> > >>> Membership is determined by having both an active <a href="http://PeeringDB.com" class="">PeeringDB.com</a><br class="">
> > >>> account and an individual representative or role subscription to<br class="">
> > >>> the PeeringDB Governance mailing list:<br class="">
> > >>><br class="">
> > >>> <a href="http://lists.peeringdb.com/cgi" rel="noreferrer" target="_blank" class="">http://lists.peeringdb.com/cgi</a>bin/mailman/listinfo/pdbgov<br class="">
> > >>><br class="">
> > >>> - Members may have such other qualifications as the Board may<br class="">
> > >>> prescribe by amendment to these Bylaws.<br class="">
> > >>><br class="">
> > >>> So the first part of 2.2 says what "may" be a member, and then<br class="">
> > >>> says that from that pool of possible members, that both an<br class="">
> > >>> active <a href="http://PeeringDB.com" class="">PeeringDB.com</a> account is needed, along with there being a<br class="">
> > >>> representative (individual or role) subscription to this pdb-gov<br class="">
> > >>> list.<br class="">
> > >>><br class="">
> > >>> Implicit by the first sentence is that "active <a href="http://PeeringDB.com" class="">PeeringDB.com</a><br class="">
> > >>> account" in the second sentence refers to organizational, not<br class="">
> > >>> individual, <a href="http://PeeringDB.com" class="">PeeringDB.com</a> accounts.<br class="">
> > >>><br class="">
> > >>> I don't believe it would be wise to revise the draft documents<br class="">
> > >>> during the present election, but once the election is over, the<br class="">
> > >>> initial board (or subsequent board or member meeting) may want<br class="">
> > >>> to clarify that second sentence by inserting the word<br class="">
> > >>> "organizational" between "active" and "<a href="http://PeeringDB.com" class="">PeeringDB.com</a> account",<br class="">
> > >>> but first I'd be curious to know if that was the source of<br class="">
> > >>> confusion.<br class="">
> > >>><br class="">
> > >>> Did you or Matt think that a person with an individual PeeringDB<br class="">
> > >>> account, subscribed to this pdb-gov list, would be sufficient to<br class="">
> > >>> qualify for membership, based on that second sentence of 2.2?<br class="">
> > >>><br class="">
> > >>> In addition to, or instead of, the clarification idea above, a<br class="">
> > >>> future board or member meeting could certainly revise the<br class="">
> > >>> definition of membership to be more inclusive, such as by<br class="">
> > >>> creating a category of membership eligibility for active<br class="">
> > >>> PeeringDB admins.<br class="">
> > >>><br class="">
> > >>> Chris<br class="">
> > >>><br class="">
> > >>> On Sun, 15 Nov 2015, Florian Hibler wrote:<br class="">
> > >>>> Good morning pdb-gov,<br class="">
> > >>>> after my attempt to register for voting on the PDB board<br class="">
> > >>>> yesterday, I figured out, that I am (according to the bylaws,<br class="">
> > >>>> as Chris told me), not eligible to vote, as I am not<br class="">
> > >>>> representing an org with a PeeringDB entry at the moment.<br class="">
> > >>>> Nethertheless I am actively involved into PDB and according to<br class="">
> > >>>> Matt Griswold I should be entitled to vote.<br class="">
> > >>>><br class="">
> > >>>> The paragraph which excludes me from voting is according to Chris<br class="">
> > >>>> the following in the bylaws<br class="">
> > >>>> (<a href="https://www.caputo.com/pdb/20151112_PeeringDB_DRAFT_Bylaws.pdf" rel="noreferrer" target="_blank" class="">https://www.caputo.com/pdb/20151112_PeeringDB_DRAFT_Bylaws.pdf</a>):<br class="">
> > >>>><br class="">
> > >>>> 2.2 Qualifications for Membership:<br class="">
> > >>>> "A corporation, limited liability company, partnership or other<br class="">
> > >>>> legal business entity may be a Member of the Corporation.<br class="">
> > >>>> Membership is determined by having both an active <a href="http://PeeringDB.com" class="">PeeringDB.com</a><br class="">
> > >>>> account and an individual representative or role subscription<br class="">
> > >>>> to the PeeringDB Governance mailing list:<br class="">
> > >>>> <a href="http://lists.peeringdb.com/cgi-" rel="noreferrer" target="_blank" class="">http://lists.peeringdb.com/cgi-</a>bin/mailman/listinfo/pdb-gov<br class="">
> > >>>> Members may have such other qualifications as the Board may<br class="">
> > >>>> prescribe by amendment to these Bylaws."<br class="">
> > >>>><br class="">
> > >>>> Matt sees it a bit different, so we decided to bring the topic up<br class="">
> > >>>> here and see what other people think about it. Your input is<br class="">
> > >>>> highly appreciated and looking very much forward to hear from<br class="">
> > >>>> you on this topic!<br class="">
> > >>>><br class="">
> > >>>> Bests,<br class="">
> > >>>> Florian<br class="">
> > >>>><br class="">
> > >>>> --<br class="">
> > >>>> Florian Hibler <<a href="mailto:fhibler@peeringdb.com" target="_blank" class="">fhibler@peeringdb.com</a>><br class="">
> > >>>> PeeringDB Administrator<br class="">
> > >><br class="">
> > >> _______________________________________________<br class="">
> > >> Pdb-gov mailing list<br class="">
> > >> <a href="mailto:Pdb-gov@lists.peeringdb.com" target="_blank" class="">Pdb-gov@lists.peeringdb.com</a><br class="">
> > >> <a href="http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov" rel="noreferrer" target="_blank" class="">http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov</a><br class="">
> > ><br class="">
> > > _______________________________________________<br class="">
> > > Pdb-gov mailing list<br class="">
> > > <a href="mailto:Pdb-gov@lists.peeringdb.com" target="_blank" class="">Pdb-gov@lists.peeringdb.com</a><br class="">
> > > <a href="http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov" rel="noreferrer" target="_blank" class="">http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov</a><br class="">
> > ><br class="">
> > _______________________________________________<br class="">
> > Pdb-gov mailing list<br class="">
> > <a href="mailto:Pdb-gov@lists.peeringdb.com" target="_blank" class="">Pdb-gov@lists.peeringdb.com</a><br class="">
> > <a href="http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov" rel="noreferrer" target="_blank" class="">http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov</a><br class="">
><br class="">
> _______________________________________________<br class="">
> Pdb-gov mailing list<br class="">
> <a href="mailto:Pdb-gov@lists.peeringdb.com" target="_blank" class="">Pdb-gov@lists.peeringdb.com</a><br class="">
> <a href="http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov" rel="noreferrer" target="_blank" class="">http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov</a><br class="">
><br class="">
><br class="">
><br class="">
> _______________________________________________<br class="">
> Pdb-gov mailing list<br class="">
> <a href="mailto:Pdb-gov@lists.peeringdb.com" target="_blank" class="">Pdb-gov@lists.peeringdb.com</a><br class="">
> <a href="http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov" rel="noreferrer" target="_blank" class="">http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov</a><br class="">
><br class="">
><br class="">
><br class="">
><br class="">
> --<br class="">
> Dan Golding |<br class="">
> Network Infrastructure Engineering |<br class="">
> <a href="mailto:dgolding@google.com" target="_blank" class="">dgolding@google.com</a> |<br class="">
> +1 202-370-5916<br class="">
> <br class="">
><br class="">
><br class="">
><br class="">
> _______________________________________________<br class="">
Pdb-gov mailing list<br class="">
<a href="mailto:Pdb-gov@lists.peeringdb.com" target="_blank" class="">Pdb-gov@lists.peeringdb.com</a><br class="">
<a href="http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov" rel="noreferrer" target="_blank" class="">http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov</a><br class="">
</blockquote></div>
_______________________________________________<br class="">Pdb-gov mailing list<br class=""><a href="mailto:Pdb-gov@lists.peeringdb.com" class="">Pdb-gov@lists.peeringdb.com</a><br class="">http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov<br class=""></div></blockquote></div><br class=""></div></body></html>