1. Summer Recap
It was a busy summer, most of which was detailed in these Center for Student Innovation and FOSS@RIT posts by the student teams and their coordinator. One of the many cool things about the Symposium was the number of projects using Python and other Open Source Technologies. We'll be reaching out to those students and faculty to bring them into the FOSS Box during the upcoming academic year.
It was a busy summer, most of which was detailed in these Center for Student Innovation and FOSS@RIT posts by the student teams and their coordinator. One of the many cool things about the Symposium was the number of projects using Python and other Open Source Technologies. We'll be reaching out to those students and faculty to bring them into the FOSS Box during the upcoming academic year.
Undergraduate Research and Innovation Symposium was huge!
We worked on several FOSS projects during our visit to Boston
FOSS@RIT returns to OLPC HQ
and FOSS@RIT was a clear leader in Open SOurce and Government Transparency on the Senate floor this summer too.
2. The New FOSS@RIT page on Teaching Open Source
It briefly covers history and current status of course and other FOSS educational efforts since we began
It briefly covers history and current status of course and other FOSS educational efforts since we began
There is, of course, a direct link to the new syllabus on Teaching Open Source too.
Some new assignments in it include a community architecture assignment, extra credit for involvement in, and blogging about, Software Freedom Day and blogging or presenting at Bar Camp Rochester on top of regular blogs, wiki posts, etc.
Looking forward to comments and feedback on the new Wiki content.
3. Open Content Game Mechanics Database Project
This will emerge from a seminar in Gameplay I'll be teaching at RIT this fall. The design and implementation of the DB will be done by my research collaborators Dr. Erik Vick of RIT and Thomas McDaniel of UCF with me shouting from the peanut gallery. The students will be supplying some content and acting as initial consumers to force iteration in the design.
There are numerous static lists and a few community wiki resources in this area already. The downside to them is that they are not structures to serve as underlying tech for larger projects and/or they are somewhat idiosyncratic.
We want ours to be a bit more flexible and to support the work we began in our paper "Using semiotic grammars for the rapid design of evolving video game mechanics" Its one of two Vick, McDaniel and myself have written on Semiotics and Game Design over the past 18 months. They were both accepted at the Games Papers sessions on SIGGRAPH 2009 and 2010.
We'll likely run it through a few versions between now and Thanksgiving during the run of the course, then open it up to a larger test group and finally the community as a whole to beat up.
We want ours to be a bit more flexible and to support the work we began in our paper "Using semiotic grammars for the rapid design of evolving video game mechanics" Its one of two Vick, McDaniel and myself have written on Semiotics and Game Design over the past 18 months. They were both accepted at the Games Papers sessions on SIGGRAPH 2009 and 2010.
We'll likely run it through a few versions between now and Thanksgiving during the run of the course, then open it up to a larger test group and finally the community as a whole to beat up.
No comments:
Post a Comment