Difference between revisions of "Google Summer of Code/2008"
(Add link to SOC 2008 specific category)
|Line 91:||Line 91:|
Latest revision as of 08:12, 10 February 2013
The 2008 Google Summer of Code was announced on February 25, 2008. BZFlag has been accepted again this year as a mentoring organization. Given our enormously successful participation in the program in 2007, we're very excited to be participating again and we're very happy to see the applications that were submitted. BZFlag accepted student project proposals from March 24 until April 7 ending at 5:00 PDT (0:00 April 8 GMT). Further information on our proposal ideas are below. Hints and tips on getting started, preparing a submission, and the application process were available. Accepted student proposals will be announced here and on the Google Summer of Code homepage on April 21 at around 12:00 PM PDT (19:00 GMT).
- 1 Promotion Flyers
- 2 Proposal Ideas
- 2.1 Suggest your own idea
- 2.2 Cheat preventions
- 2.3 Global authentication daemon
- 2.4 BZWorkBench world editor enhancement
- 2.5 Enhanced server listing
- 2.6 Modularization of game logic
- 2.7 Dead Reckoning and other Networking Enhancements
- 2.8 Enhanced cross-platform multiple display support
- 2.9 Enhanced Statistics system
- 2.10 Integrated BZFS web interface
- 2.11 Network Testing and Simulation Environment
- 2.12 Cross server communications system
- 2.13 In-game profile management
- 3 Mentors
- 4 Thanks & Appreciation
Provided below is a promotional flyer to help spread the word about our involvement with the Google Summer of Code. Flyers are available in various languages that we have mentors for so that students from all over the globe can be informed about the program. While many developers can converse fluently in other languages, English is still expected for most developer discussions. Feel free to distribute the flyer around your local colleges and universities.
High praise and special thanks to Harry Keller (aka Saturos) for designing our 2008 GSoC flyer.
While there are lots of Ideas floating around of varying utility to the game, the ideas listed below are the specific areas that we are predominantly interested in seeing worked on as part of the GSoC. Please note that students are also welcome and encouraged to apply with their own ideas. They should run those ideas by one of the developers beforehand to make sure they are consistent with the scope and focus of the project, though, as there are some ideas which will not be accepted regardless of the quality of the application and applicant. We've additionally provided several project ideas important to BZFlag development that we would very much like to see proposals for, shown in following.
Suggest your own idea
BZFlag is always open to new development ideas and is under constant improvement. If you are familiar with BZFlag's current capabilities and would like to propose some new enhancement, we'd be happy to hear about. Please discuss any new ideas with the existing core developers (on our IRC channel), if only to make sure the ideas are in-line with the spirit and constraints of the game.
This task involves making BZFlag more robust towards preventing various cheats from working in the game. This task implicitly requires adding protections on the server, moving game logic from the client to the server, and/or adding heuristics and other measures for detecting and dealing with cheat clients. The student should have a strong grasp of the variety of BZFlag cheats that are available. Please go into detail about which cheats you're interested in preventing and how you intend to employ those preventive measures. For information on known cheats, check out the Known Cheats wiki page.
Global authentication daemon
The goal of this project would be to provide global account management system daemon that the client and servers would communicate with for account, group membership, and profile information. This effort preferably be written in C++, would need to talk to an LDAP server for persistent storage on the backend, and allow chaining across multiple daemons for data replication and failover service. The daemon would need to provide a well structured simple communications API that the game client and game servers can securely talk to.
BZWorkBench world editor enhancement
As a participant in last year's program, Jude Nelson started work on BZWorkBench. It is a world file editor with a very solid foundation but much work still remains to be done, including a cross-platform GUI, mesh support, and other editor features. Ideally, two students would work on this. For example, one student could focus on improving the GUI's workflow and ease-of-use, and another could focus on finishing the back-end object manipulation. The current GUI does not conform to a specific HIG, nor does its usability resemble many other 3D editors; this should change. The back-end still lacks support for many of the objects added in BZFlag 2.0, such as Meshes, texture matrices, dynamic colors, etc.
Enhanced server listing
The game client includes a simplistic listing of publicly available servers. This task would involve significantly enhancing the listing section in BZFlag to allow for various sortings (e.g. ping time, country, name, etc), favorites, recently used, specific additional information on specific servers, and all existing information. The task would involve coming up with a user-friendly design that is fully keyboard-accessible. It could leverage external gui toolkits, use BZFlag's existing gui library, and/or extend the existing capabilities. The focus would be on creating an intuitive and informative listing enhancement within the constraints of the gaming interface.
Modularization of game logic
Much of the game logic is presently mixed in with BZFlag's graphics code. This lack of organization make it difficult to find code when necessary, and does not allow bzfs, bzrobots, or other tools to utilize the game logic. The game code should be modularized into libgame so that all that is left in the client code is the graphics subsystem. This will also ease the possible future integration of a 3D graphics engine.
Dead Reckoning and other Networking Enhancements
The basic idea is to improve BZFlag's networking by performing dead reckoning on the server along with context-sensitive packet delivery culling. Much work has gone into the game towards moving more and more of the game state to the server, but there is additional migration and protocol changes required. Similarly, network utilization can be optimized by not relaying certain packets (like miniscule position updates to distant players) based on the current game state. Some useful background reading for this task include "Fairness in Dead-Reckoning based Distributed Multi-Player Games (pdf)" and "Accuracy in Dead-Reckoning Based Distributed Multi-Player Games (pdf)".
Enhanced cross-platform multiple display support
Add the ability to effectively manage multiple display environments from within the game allowing for the detection, alignment/orientation specification, and resolution parameters for each display via menu options as well as proper full-screen and/or windowed support. An additional feature could involve allowing the user to dedicate a display to the various primary gui elements (the 3D environment, the radar, and the chat console). BZFlag's current context management is mostly handled by SDL or other platform-specific modules, so this could be taken into consideration. There's also the possibility of our move to an integrated graphics engine would similarly impact how multidisplay contexts are created and managed.
Enhanced Statistics system
The goal of this idea would be to extend the existing web based statistics system to be more robust.
Features could include:
- Better integration with the list server.
- Use of a plug-in or server based stat "push" system instead of the current "pull" system.
- Better publishing of stats
- Publishing of recorded stat data to other sites.
- Better tracking of registered and unregistered players
- Tracking of leagues and individual match games.
- Generalizing the stats system to be used in other games/projects.
Integrated BZFS web interface
The BZFlag game server, BZFS, could benefit from having a browser-accessible http/https interface for viewing server statistics, setting various parameters, and otherwise controlling the server daemon while it is running. Similar to how your network router has a web interface for changing configuration parameters, this idea is simply to create this interface in a maintainable and portable manner. Please go into detail on how exactly you'd go about doing this.
Network Testing and Simulation Environment
This task should provide a controlled testing environment for simulating network behavioral characteristics, including the ability to change virtual network parameters to induce different network conditions of lag and packet loss. This environment should provide a viewer capability to observe interactions of BZFlag clients being tested from the perspective of the player, the server, and third-party observers. This simulation framework should work with the client and server directly so that testing of actual changes may be performed in a stand-alone environment.
Cross server communications system
This task would be the design and implementation of a server spanning chat system. It would allow players from one server to send chat messages to players on other servers. It should also be able to be used to allow players to know where there friends or "buddies" are playing if they are online. The system should tie into the central user name registration system. Added benefits would be the use of existing protocols or applications, such as Jabber or IRC, if they can be integrated cleanly. Support for using off-line apps for chat and friends list access as well as server management would be a plus.
In-game profile management
BZFlag allows players to specify a callsign and team in addition to other player characteristics and preferences. This enhancement would focus on allowing the user to specify and manage multiple profiles from within the game. Profiles could be linked together and should be presented in an intuitive manner (proposal should highlight how you'd go about achieving that). The profiles would need to associate with global account information as well.
The mentors for 2008 are;
- Sean Morrison (brlcad/learner)
- Daniel Remenak (DTRemenak/Erroneous)
- Jeffrey Myers (JeffM/JeffM2501)
- Julio Jiménez Borreguero (Manu/jujibo)
- Scott Wichser (Blast/Blast007)
- David Wollner (JB diGriz)
- Joe VanOverberghe (Donny_Baker)
- James Lawrence (spldart)
Thanks & Appreciation
Thank you to the following individuals in the BZFlag community that helped prepare GSoC-related marketing materials:
- Harry Keller (aka Saturos)
- Julio Jiménez Borreguero (aka jujibo aka Manu)
- Dexter Mason (aka whodaman)
- Sean Morrison (aka learner aka brlcad)
- Jeffrey Myers (aka JeffM)