• View
• Edit
• History
• Print

Planning for Monday the 24th, November 2008

InstantBoss + Programmer’s Block and Unit Testing by Alex Schroeder, 2008-10-04 + Todo

Morning

1. code all this INSIDE the wiki
   1. write down every time IN the wiki WHEN we have to go out of it
      1. access to the code of an existing module
      2. loading a new module
      3. periodic job / crontab / bot
2. do (coherently) the WikiBot
   1. thanks to the meta-plugin = (seedeamodulesbuilding)
      1. based on the existing module (seedeaoimpinterface2)
         1. copy the code of (seedeaoimpinterface2) as a normal wikipage : MetaModuleData.SeedeaOimpInterface?
         2. now we have 4 levels : A definition of the module (Seedea.Optmodules) + B running module as PHP pmwiki module code (http://seedea.free.fr/wiki/cookbook/) + C pmwiki normal page with the code (MetaModuleData.MetaModuleData) + D running code like this (running now to display this very page)
3. prepare cascading unit tests
   1. wasn't required
4. code
5. delimit (harder than expected, maybe this should come later on)
   1. Seedea core (see also Architecture) -> seedea.php
   2. Seedea modules -> seedeamodules.php
      1. they should ALL be listed there
         1. Todo
         2. SandIdeabox
         3. Oimp
      2. be ordered by importance
      3. distinguish what is Seedea/NotSeedea/NotEvenRequired
      4. then and ONLY THEN update the Core/Architecture thanks to central factorized functions
6. re-order (again) by priority for USERS!

Afternoon

1. tests
   1. ok but security isn't good... it's a wiki though but it's not a good habit
2. presentation on #wiki
   1. not confident enough ;)
3. return on experience
   1. pretty effective : stuff has been done
      1. meta-module
      2. started wikibot across API
   2. a bit chaotic : not really defined process
   3. should prepare for tomorrow or the next day but that could sound too "short sighted"
   4. InstantBoss is especially good to "force" focus on 1 thing, no divergent multitasking allowed especially socially based
4. SCRUM compatibility
   1. no idea, should ask Sylvain