But really even a partnership should have one representative surely? In a two-man company somebody is always the CEO or "final say" guy, this should be the same surely.

Sent from my iPhone

On Mar 2, 2013, at 1:45 PM, Pádraic Brady <notifications@github.com> wrote:

> In bylaws/003-membership.md:
> 
> > +Project Representatives
> > +-----------------------
> > +
> > +The votes of all Voting Members are cast by Project Representives who have been
> > +authorised to do so by the Voting Member. The Project Representative is chosen
> > +solely by the Voting Member and their selection is not subject to the approval
> > +of PHP-FIG.
> > +
> > +To prevent illegal or erroneous voting, the Project Representative must be
> > +confirmed by the Voting Member to be authorised to act in such a capacity
> > +in an email to the the main [php-fig mailing list][list] where
> > +practical and where this does not conflict with the Voting Member's policies.
> > +The other Voting Members may seek confirmation through other channels as
> > +necessary.
> > +
> > +A Voting Member may have more than one Project Representative with the
> A project is free to organise itself as it sees fit. I put it in because someone mentioned in an email thread that Composer was on the partnership end of the scale vs something more rigid like ZF2 where there's some limited codifying of the meritocracy at the top.
> 
> —
> Reply to this email directly or view it on GitHub.