First Committee Meeting

A few weeks before we made the Torque 3D MIT announcement, there was a thread post regarding the direction of T3D. We hadn't made the announcement and we weren't yet prepped to do so. All I could say was that there was a "big announcement" coming and while I was being vague, I did promise the most transparent development process in the history of GarageGames. I don't think we could be any more transparent then putting all development out in the open and allowing anyone to view it. It's a very liberating feeling.

Today we had our first post-launch steering committee meeting. As you may have read in an earlier blog, Scott, David Montgomery-Blake and I are acting committee members and Dave Wyand is taking a full time position. We have decided not to make too many decisions now because our first goal is to replace the acting positions with full time committee members.

In the meantime, I will be posting all meeting notes in the T3D Beginner forums (so that everyone feels welcome to comment). If the committee has a specific question that they want to ask everyone, we will post those threads at the same time as the committee notes. I will use start the subject with the following convention: Committee Meeting: and Committee Topic: ? Note: Please don't think that the Committee Topics are the only feedback we are interested in…they are just specific questions we'd like to pose to the community directly.

I will post links to the forum posts below, but before I do, I have two requests that the committee asked me to address. The first, is that the deadline for submission to be a candidate for the Steering Committee is October 12th. Please contact Dave Wyand for consideration (davew@garagegames.com). We will be picking the committee shortly thereafter. The second topic is an explanation of Development vs. Master branches which I will post below.

Committee Meeting: 9/24/2012
Committee Topic: Issue Management on GitHub

Development vs. Master

We will be developing Torque 3D in a public forum. To make this possible, there will be at least two branches (sometimes there could be three or more depending on how we work) that we will work from. The two primary branches are Dev and Master.

Master is the branch you should fork if reliability is your biggest concern. Before something is moved into master, it will pass some a level of quality assurance before it is deemed the master. Some people call this branch stable.

Development is the branch you should fork if you are more interested in the latest changes. Approved changes that are merged or developed in branch may not be fully vetted, tested, or final. It's not suggested that you work or fork from Dev unless you are a confidence programmer who is able to navigate code that might be broken, half implemented, or buggy.