Committee Meeting Notes: 09/23/2013
by David Wyand · in Torque 3D Beginner · 09/23/2013 (2:26 pm) · 13 replies
Attending Committee members: Mike, Christian, Dave
Nothing was done this past week as Mike was out. 1st person module is nearly complete. Racing module should be ready this week. We talked about Mike putting his changes into a branch for testing out, and to help with the Project Manager changes that will be necessary to work with these modules.
Community Art - Christian
Still looking for people to help.
GitHub Tutorial
Looks like Lukas has volunteered to take this on.
T3D 4.0 Roadmap - Committee
The v4 roadmap as originally outlined by the 1st Steering Committee has not really progressed over the last few months. With Mike being the only remaining active member from the 1st Steering Committee, the search for new Committee members in the Spring, and now a disruption in the 2nd Steering Committee, the v4 roadmap is not really applicable any more.
Today we discussed a change in direction with a proposed, near-term v3.5 release. The v3.5 release will encompass what we have today in the development branch (see here), plus whatever Mike and I (I should have some time in the near term to help Mike out) can merge in over the next couple of weeks. Here is our proposed timeline:
Sept 23 - Oct 11: Merge in changes for v3.5 release
Oct 14 - Oct 25: Community QA testing of development branch
Week of Oct 28: Release v3.5
We're not sure about the availability of the GG QA department to help out with testing v3.5 (they are involved in the same service work that has kept me away from T3D), so we'll be looking for the community to help out this time. The two weeks are to allow for people to test out the development branch and then (hopefully) people reacting to any bugs that are found and submitting changes back to the branch.
The v4 roadmap had reference to docs, tutorials and community art projects. With v3.5 we won't allow those items to hold up the release. This is all about getting a new code drop to those that work with the master branch and the precompiled packages. If someone from the community wants to step up and help with docs, tutorials and community art then it will be an extra bonus.
Steering Committee
As you know, Harrison stepped down from the Steering Committee a few weeks ago leaving a spot vacant. We've decided rather than take the time to look for someone to fill this spot that we will instead focus on getting v3.5 out. Once that project is complete we can then re-evaluate the Committee and start fresh with the direction of T3D. The best way anyone can help out right now is in preparation of the v3.5 release, which includes providing fixes for the GitHub Issues list.
As always please provide your comments below. These are plans that the Steering Committee has recently discussed and we're always open to hearing your point of view as we're here to serve the community.
- Dave
Discussed This Week
Modular Templates - MikeNothing was done this past week as Mike was out. 1st person module is nearly complete. Racing module should be ready this week. We talked about Mike putting his changes into a branch for testing out, and to help with the Project Manager changes that will be necessary to work with these modules.
Community Art - Christian
Still looking for people to help.
GitHub Tutorial
Looks like Lukas has volunteered to take this on.
T3D 4.0 Roadmap - Committee
The v4 roadmap as originally outlined by the 1st Steering Committee has not really progressed over the last few months. With Mike being the only remaining active member from the 1st Steering Committee, the search for new Committee members in the Spring, and now a disruption in the 2nd Steering Committee, the v4 roadmap is not really applicable any more.
Today we discussed a change in direction with a proposed, near-term v3.5 release. The v3.5 release will encompass what we have today in the development branch (see here), plus whatever Mike and I (I should have some time in the near term to help Mike out) can merge in over the next couple of weeks. Here is our proposed timeline:
Sept 23 - Oct 11: Merge in changes for v3.5 release
Oct 14 - Oct 25: Community QA testing of development branch
Week of Oct 28: Release v3.5
We're not sure about the availability of the GG QA department to help out with testing v3.5 (they are involved in the same service work that has kept me away from T3D), so we'll be looking for the community to help out this time. The two weeks are to allow for people to test out the development branch and then (hopefully) people reacting to any bugs that are found and submitting changes back to the branch.
The v4 roadmap had reference to docs, tutorials and community art projects. With v3.5 we won't allow those items to hold up the release. This is all about getting a new code drop to those that work with the master branch and the precompiled packages. If someone from the community wants to step up and help with docs, tutorials and community art then it will be an extra bonus.
Steering Committee
As you know, Harrison stepped down from the Steering Committee a few weeks ago leaving a spot vacant. We've decided rather than take the time to look for someone to fill this spot that we will instead focus on getting v3.5 out. Once that project is complete we can then re-evaluate the Committee and start fresh with the direction of T3D. The best way anyone can help out right now is in preparation of the v3.5 release, which includes providing fixes for the GitHub Issues list.
As always please provide your comments below. These are plans that the Steering Committee has recently discussed and we're always open to hearing your point of view as we're here to serve the community.
- Dave
About the author
A long time Associate of the GarageGames' community and author of the Torque 3D Game Development Cookbook. Buy it today from Packt Publishing!
#2
Also I know this is probably low on the priority list and I haven't seen it mentioned anywhere but is Rift support going to be improved or is that not on the roadmap atm?
09/23/2013 (6:04 pm)
Is there a list of the Docs and Tutorials you need? I'm still new but I'm happy to try and give it a shot to help :)Also I know this is probably low on the priority list and I haven't seen it mentioned anywhere but is Rift support going to be improved or is that not on the roadmap atm?
#3
09/24/2013 (1:19 am)
Thanks for the update and your hard work! 
#4
09/24/2013 (8:11 am)
Thanks for the update! Would be great to see the new templates' progress. I'll definitely try and put some decent effort into testing the new code changes. 
#5
09/24/2013 (8:59 am)
I might finally have some available time to take a look at the old Action-Tactics Hybrid Tutorial next week and update it to be compatible with an MIT branch.
#6
HTML
MarkDown
PDF
It's just a first revision, so it's a bit rough tho tell me what you think and what you think is missing / needs better explanation / sounds like a monkey puking on a fish on Mars.
09/24/2013 (12:14 pm)
Hey guys! I didn't know what format you wanted the GitHub tutorial in, but here is first revision in MarkDown, HTML and PDF format:HTML
MarkDown
It's just a first revision, so it's a bit rough tho tell me what you think and what you think is missing / needs better explanation / sounds like a monkey puking on a fish on Mars.
#8
EDIT: Working with some engineering students using git for the first time. Here's the regimen I recommended:
09/24/2013 (8:04 pm)
Nice work. Do you feel like putting it in a repo? I have some pull requests to suggest ;P.EDIT: Working with some engineering students using git for the first time. Here's the regimen I recommended:
- try.github.io Interactive introduction to git that gets you to type in commands in your browser. Probably a good place to start.
- rogerdudler.github.io/git-guide/ Great simple guide to the basic commands you'll need to use regularly.
- gitready.com/ Tons of little tutorials on specific topics. Most of them won't be needed, but I'd recommend reading some of the 'beginner'articles on stashing, push/pull and branching.
- help.github.com/articles/fork-a-repo Basic guide to working with stuff on GitHub, which we should probably use to host our code. Not sure if we will use fork/pull request method or just all push to the same repo. We can discuss it when we start coding.
#10
No excuse to not git it anymore...
Perhaps you want to add the main title?
09/24/2013 (11:48 pm)
Great Lukas, thanks! No excuse to not git it anymore...
Perhaps you want to add the main title?
#11
@Nin-Nin: not so much a list, just whatever somebody wishes to contribute.
@Steve: you want to update your Tactics-action hybrid for use as a Template or as a module? If the latter, I should start pushing those up in the next week or so. Either way will work since we're not getting rid of the templates or their interaction with the Project Manager.
09/25/2013 (8:56 am)
@Lukas: markdown will do nicely for the wiki. Considering it's your tutorial though you may offer it in any format you wish. By the way, yours is certainly less condescending and insulting than the one I had originally put together ;)@Nin-Nin: not so much a list, just whatever somebody wishes to contribute.
@Steve: you want to update your Tactics-action hybrid for use as a Template or as a module? If the latter, I should start pushing those up in the next week or so. Either way will work since we're not getting rid of the templates or their interaction with the Project Manager.
#12
09/25/2013 (1:13 pm)
So maybe I should put together a tutorial to go with the AI Tutorial that I started....
#13
Tutorials everywhere!
Edit: Also thanks for the positive feedback! I will try to polish the tutorial and get a R/C ready asap :)
09/25/2013 (1:18 pm)
Tutorials..Tutorials everywhere!
Edit: Also thanks for the positive feedback! I will try to polish the tutorial and get a R/C ready asap :)
Associate Ron Kapaun
3tdstudios.com
Might be I could find a little time to help if you need it. Let me know.
Ron