Actually, no nothing is being "hidden" and I'm not sure what could possibly happen at a BOG meeting that would violate the COC or COR. Remember...Board meetings of corporations are NOT open to the public (or even to the shareholders (read owners) of a company). They are a place where business gets done. The minutes are kept as a reference of what happened at that meeting for use by the founders and/or BOG members who either weren't present or want to go back and see what happened. Nothing in the VATSIM rules requires that a meeting be "open" to the membership and there are some very good reasons why it should not be. Executive session is a totally different issue. As articulated in 2.07(F) of the CoR, the Founders recognized there would be times when issues being discussed should remain confidential and nor be made public. That is what Executive Session exists for. The open session part of the BOG meetings is made public via the minutes (as required by 2.07(D) of the CoR).
The minutes accurately reflect what issues were discussed at a meeting, what decisions were made and what votes were taken (with their results). If you read all of the minutes of previous BoG meetings, you get a pretty good feel for what is discussed. 99% of the discussions/votes are simply "the business" of VATSIM...things like approving software, changes to VATSIM policies, and strategic-level decisions for the network.
At this meeting we had:
- an update by Kyle Ramsey on the status of the Pilot Rating Scheme. We then spent a good deal of time discussing the technical changes that would be required (new data fields in CERT, web interfaces to grant the ratings, etc.). Lastly, we spent time discussing how we would get this pilot training system accurately translated and distributed to parts of the world where English is not the native language but where we need to grow as a network (Asia for example). We also discussed when we would advertise to fill the VP, Pilot Training BOG position that is presently vacant with Kyle covering it as "acting" (much as I covered VP, SOA for several months while I was VP, Operations back in 2006).
- Florian gave us an update on the status of the new website. How the server was handling the load, whether we had a need to move the site to a more high-powered server to support additional functionality, etc. We also discussed making some changes to the website to make it easier to find certain areas/documents (for example, did you know that what you see on the menus changes based on whether or not you are logged in? I did not realize this until another BOG member brought it up and we discussed whether that was something we wanted to maintain or not...and if so, how to we ensure the membership knows this so they log in?)
- Terry gave us an update on commercial activities that want to use the VATSIM network. Specifically an FBO/flight school has approached the network requesting use of the network to assist in flight training. Terry had consulted with VATSIM's attorney and was briefing us on what (and why) the VATSIM position on this kind of activity was.
- We had a discussion on how/if we should recognize senior Staff members who have contributed much to VATSIM and now "retired" from staff positions. There is a recognition by the BOG that there are some people who have truly done A LOT for VATSIM and they may warrant some kind of formal recognition. We discussed a number of different ways this might be done (granting use of a special, reserved callsign, a special rating, a "wall of fame" on the website, a special avatar or rank in the forums, etc.).
- We had a discussion on if there is a need to add to the code of conduct or code of regulations with regards to people who are in staff positions at VATSIM. Those people have unique access to databases, forums, etc. yet all present regulations/rules are written for "normal" members meaning mis-use of those privileges is not cleanly a violation of the rules (other than the general ones like A.12 of the CoC). We also discussed the fact we expect to hold staff to a higher standard (for example with regards to conduct in forums and online) but there isn't presently anything that lays that out in writing with the exception of a document sent to all supervisors by VP, Supervisors when they are appointed supervisors.
- We discussed the results of a 2 month test in VATPAC where the FSS position (and extended range) was approved to cover most of Australia with a single controller to maximize ATC availability in the area. Server loads, how that one position logging in affected the server he/she was logged into as well as the data exchange to that FSD server was reviewed with an eye to if this could be something we authorize in the future for other parts of the network.
- We discussed the need for and a plan to develop a COOP (Continuity of Operations) Plan for VATSIM. Basically a set of backups and accesses to ensure things don't get brought to a halt if one or more key staff members suddenly go offline (family emergency, hurricane, earthquake, death, etc.). It's a problem we've had to address and we're going to develop a formal COOP plan because it is the right thing to do for the network.
There really is no secret cabal sitting around tossing chicken bones and discussing/gossiping about various members. To be honest, we don't have the time or the inclination to do that kind of stuff...we have enough work to do as it is! I can't speak for what happened before I joined the BoG, but since I joined the minutes have accurately reported what happened at BOG meetings and since CoR 2.07(D) requires them, I suspect that has been the case since the very first BOG meeting.
As far as "only the EC portion being confidential and that being why we don't want to release a recording", that simply isn't the case. By EC I assume you actually mean "executive session" where we discuss things that are either sensitive, proprietary or confidential and those things are (and always have been) discussed in Executive Session as authorized by the CoR for just that reason. I already told you what reasons several BoG members put forward for why releasing a recording would not be a good idea:
(1) it might stifle discussion
(2) an informed opinion that doing so might violate some laws
Bottom line is that recordings are not typically released of Board meetings of any organization (public or privately held) that I know of. Minutes of those meetings are typically required by law at least in the United States and those minutes may or may not be released publicly based on law, the articles of incorporation, or bylaws of the specific organization in question. VATSIM is fully in compliance with those requirements by releasing the minutes of meetings and for some good reasons has determined that it should not release a recording of the meetings. Period.
I'm not sure why you feel the need for a recording is so essential and if you also feel that the Board of Directors of General Electric, Boeing, Coca Cola, the American Red Cross, the Boy Scouts of America or any other organization should release a recording of their meetings, but I suspect you would get the same answer from them you are getting from VATSIM. If you would care to discuss this further, I'm happy to move it to email as I don' think a forum is an appropriate place for a conversation between two people and I believe this thread has served it's purpose, to wit: In another thread I had said I would look into doing something and report back and this thread reports back on the results.
all the best,
Dave