User:ThePoet444/notepad: Difference between revisions
Jump to navigation
Jump to search
ThePoet444 (talk | contribs) mNo edit summary |
ThePoet444 (talk | contribs) |
||
| Line 1: | Line 1: | ||
==Things to do== | ==Things to do== | ||
1 get PBF703 ready for release. Both Xwing and Tie. Start whipping testers | 1 get PBF703 ready for release. Both Xwing and Tie. Start whipping testers | ||
2 | 2 <del>update past missions to include the R2W missions</del> | ||
2 <del>Include Briefings and MRM winner narratives in zip files for R2F missions</del> | |||
2 get all PBF/R2F squad missions on the [http://pbf.rebelsquadrons.org/missions/ past missions] page | |||
3 update [[Squad missions]] | |||
4 get working on the [[fleet websites|Fleet website]] updating | |||
5 get working on the [[wing websites]] | |||
6 get working on the [[squadron websites]] | |||
7 help out on the [[website to-do list]] | |||
PBF Academy projects | PBF Academy projects | ||
Revision as of 12:35, 9 August 2006
Things to do
1 get PBF703 ready for release. Both Xwing and Tie. Start whipping testers 2update past missions to include the R2W missions2Include Briefings and MRM winner narratives in zip files for R2F missions2 get all PBF/R2F squad missions on the past missions page 3 update Squad missions 4 get working on the Fleet website updating 5 get working on the wing websites 6 get working on the squadron websites 7 help out on the website to-do list
PBF Academy projects
1. Setup definition of TO's Job 2. Get all instructors cross trained on both games 3. Define what each instructor should be doing. (I know this sounds obvious, but it's not) 4. make sure PBF website is clear on both XWing and TIE instructions.
From Licah's Taskforces
Improvements Subgroup * Conduct usability interviews to determine problems and successes of various parts of the website. * Test main and unit websites for compatibility with each major browser, and note those that need to be fixed. * Consult the "website to-do list" and complete and/or comment on each suggestion. Add new suggestions as necessary. * Read about design issues, usability, coding standards, and accessibility, and apply these theories as necessary to the RS website.