The official PASS Blog is where you’ll find the latest blog posts from PASS community members and the PASS Board. Contributors share their thoughts and discuss a wide variety of topics spanning PASS and the data community.

History of PASS, Part 3: Bylaws Version 1

This blog has been reposted from its original source: https://www.sentryone.com/blog/history-of-pass-part-3-bylaws-version-1

I’ve been taking some spare time, which doesn’t come along very often, to record some of the details of PASS during its very first years of existence. In case you haven’t seen the earlier entries in this series, here they are:

In the History of PASS, Part 1: Foundation, I described how the money, the executive willpower, and the corporate support came together to set the wheels in motion.

In the History of PASS, Part 2: Board of Directors, I described how the original founding board of nine independent experts and community organizers came together as the first board of directors.

In this entry, I’ll tell you about the earliest iteration or two of our Bylaws, how they came to be, what they focused on, and the first couple rounds of changes that we made to them as a team.

Where to Start With Bylaws?

Creating the bylaws for a large professional associate out of whole cloth would have been outside of our skills as technologists. However, the association management company that was contracted to run our everyday affairs, SmithBucklin & Associates (SBA), had attorneys on staff to incorporate the organization and were actively managing all the other big database vendor user groups as well as quite a few other leading hardware and software vendors. Adding PASS wouldn’t be anything unusual for them. So, we felt very fortunate that to have access to a set of very compatible templates from the other DBMS user groups at our fingertips.

Non-Profit Versus Not-for-Profit

One of the first and foremost aspects of a professional association is that its intended purpose is not to enrich its owners since, in fact, the membership are the owners. Once you decide to create a corporate entity that is not intended to make a profit, you must make some hard choices about organization rules, lines of command and authority, and perhaps most importantly, revenue and taxation.

The most desirable structure is a non-profit organization. It is most desirable because under the law, the organization is perceived as a charity and thus reaps LOADS of tax benefits. If you’re a non-profit, in the eyes of the law (and the taxman) you’re in the same category as a church, university, or humanitarian organization like Goodwill. However, to qualify for that status as a professional association, you must represent the interests of many corporations in addition to the individual members. Although we went several rounds with the IRS arguing that we qualified, at the end of the day they said we only advanced the interests of Microsoft. So, we were relegated to not-for-profit status.

PASS Community Summit

As an organizational construct, a not-for-profit does not have federal tax benefits since you’re taxed like any enterprise with a general ledger. However, it does have benefits in terms of simplified terms of ownership and, in the state of Illinois where we are incorporated, have special state-level benefits. We made the best of those limited benefits and got to work on the rest of PASS’s governance.

Sidebar: A recent proposed change to the bylaws suggested that additional vendor seats be made available, since CA no longer exercises their right to two board liaison seats. I personally think this is a great idea and, depending on the vendor, might present an opportunity to readdress non-profit status.

Key Tenets

Although I’d like for everybody interested in PASS to read and keep up with the bylaws, I know that is like asking a kid to swallow a very nasty medicine. So, I’ll boil a few thought down to something a bit more consumable.

If you are feeling heroic, you can read the current version of the PASS Bylaws, but it does not contain any historical Bylaws. You can, however, read meeting minutes back to 2016.

PASS Community Summit Seattle

First, I’ll point out a few of the key tenets of the bylaws, not so much to enable you to write your own bylaws but to point out how very different cultural expectations were in the late 1990s, a time when the internet was only static HTML webpages, a nice computer monitor weighed 35 pounds, and smartphones were still many years in the future:

  • Voting rights were based on paying dues. You could pay a couple different rates, such as Student or Individual rate, averaging about $150/year, to join via postal mail or a phone call. Sorry, no online shopping cart for that! Plus, every attendee of the PASS Summit received automatic enfranchisement. Assuming you caused no offenses at a PASS event, you received the status of “member in good standing” for the next year. The annual PASS Summit, according to the bylaws, is also the annual member meeting. (That is main reason that you must sit through a few minutes of organizational finances and strategic data on Day 2 of the PASS Summit to this day. It’s the annual member meeting as well as a massive technical conference).
  • All communication between members, prospects, and HQ was conducted by postal mail. Printing and paper costs, as a line item on the budget, were many thousands of dollars. Members could also call PASS for issues related to joining the association or updating their account details, but we didn’t do call center activities like membership drives or general marketing by phone.
  • Committees were a big deal. In general, I think PASS of the 90s and 2000s had a lot more committees than PASS of the 2010s. We had committees for awards, for student scholarships, for chapters, for content and book reviews, and for stuff you probably have never heard of. For example, one committee with an interesting mission was the Advocacy Committee. This committee was responsible for collection suggestions for improvement to the SQL Server toolkit. Why? Remember, back then the internet was barely functional and there was no such thing as Microsoft Connect or its decedents. At that time, you had to know somebody on the team to make your thoughts known.
  • A Not-So-Executive Executive Committee (ExeCo) was established at the inception of the organization. This committee was composed of the Executive Director, President, Vice President of Finance, Vice President of Marketing, and Immediate Past President. However, for the first four years of the organization, any action of significance required a vote by the entire board. Later, the board realized that this structure was too cumbersome for an organization trying to respond at Internet speeds and so the ExeCo was granted the power to move on important decisions that required quick turnaround, while the board continued to operate as usual for all but quick decisions.

PASS COMPASS 1999

Call For Speakers: First PASS Summit, 1999

So, that’s just a quick recap of what was in the first round of PASS bylaws and governance documents.

In our next installment, I’ll describe a few problem situations for PASS in which we made changes to the bylaws and some of the early, but existential, crisis that we face and how we survived them.

Kevin Kline
About the author

Kevin Kline is a database and industry expert serving as Principal Program Manager at SentryOne, the industry leading SQL Server database tools vendor. A Microsoft SQL Server MVP since 2003, he is a founder and former president of PASS. Kevin is an author of many books, blogger, columnist, and popular international speaker. Kevin’s best known book is the best-selling SQL in a Nutshell and contributes monthly to Database Trends & Applications magazine. He tweets at @kekline and blogs at http://Blogs.SQLSentry.com/Author/KevinKline.

Please login or register to post comments.

Back to Top
cage-aids
cage-aids
cage-aids
cage-aids