This wiki is archived and useful information is being migrated to the main bzflag.org website
Editing Jwir3:csproposal
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.
The administrator who locked it offered this explanation: Archived wiki
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 23: | Line 23: | ||
== Project Schedule == | == Project Schedule == | ||
− | The first | + | The first week will be used to research the BZFlag codebase, as well as outline the exact specifications for development. Once this is complete, the bugplug plugin will be the first change that is made, in order to facilitate debugging of other items of the code. When this is complete and tested, the functionality will be broken into iterations as described in the development methodology. Implementation, testing/debugging, and documentation will take up the largest portion of the project, and is estimated to take roughly 1.5 months. Once complete, the project will be delivered to the BZFlag community for evaluation and initial recommendations. Final testing and debugging will then be done before final submission to Google. The initial project schedule will be: |
* May 28 - Jun 10: Integration of bugplug | * May 28 - Jun 10: Integration of bugplug | ||
Line 32: | Line 32: | ||
* Aug 14 - Aug 19 Final Code Documentation and Code Polishing | * Aug 14 - Aug 19 Final Code Documentation and Code Polishing | ||
* Aug 20: Final Release to Google and Community | * Aug 20: Final Release to Google and Community | ||
− | |||
− | |||
== Bio == | == Bio == |