We need to standardise and improve the coding environment used by TWikiContributors

• Educate coders: SubversionReadme, PatchGuidelines, TWikiDebugging, SVK, HowDoesTheDEVELOPBranchWork
  • Firm up the API documentation in CodevDocumentationProject
• Develop a TWikiSDK
  • Part facilitated by the Rafael's TWikiShellContrib project (delivered, early, on 22 Oct 2004.)
    • The EmptyPlugin needs a default hook to the TWikiShellContrib
• Develop the TWikiTestInfrastructure and PerlUnitTesting code to ensure functionality continuity in existing modules
  • Change the EmptyPlugin so that it incorporates hooks out to the TWikiTestInfrastructure.
    • This will ensure plugin authors know about, and how to, do automated testing.
    • Catering to a testing infrastructure also ensures better modularity as the code now needs to be executed from multiple fronts (CGI + Test).
  • Schedule a DailyBuildAndSmokeTest so that everything is tested continually - and we know as soon as we have broken something
  • monitor error logs (especially 500 errors)
  • Develop an automated reporting mechanism, that relates broken tests with recent check-ins.
• Correlate code against CodingStandards: use PerlMetricsPluginDev, PerlDocPlugin in CodevDocumentationProject

-- MartinCleaver - 15 Oct 2004