Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
recognize voting vs nonvoting shareholders in the captable #219
they are excused from receiving notices and from voting on (almost all) members resolutions. so only voting shareholders receive members resolutions.
how should our system model this business logic?
just as we have defined roles of shareholder vs new_investor vs brand_new_investor, let us also define specialized subclasses of shareholder, as voting_shareholder vs nonvoting_shareholder.
these specializations should be available to the developer somewhere in the captable round object hierarchy.
we should then update the demo master's available_templates sheet so the "To" column describes
along the way we may also update various templates to use