My Links

• SiteChanges
• ReleaseBlockers
• MyItems

Tasks related to my extensions

Task	Applies To	Summary	Current State	Priority
Item14551	FastCGIEngineContrib	Update the default Nginx configuration examples	Waiting for Feedback	Enhancement
Item11707	FoswikiRequest, ModPerlEngineContrib	Foswiki behaves differently between CGI and mod_perl when mixing GET and POST parameters	Confirmed	Normal
Item13506	ModPerlEngineContrib	"JSON-RPC Failed - no method" and Other Weirdness When Apache2::Request Not Installed	Confirmed	Normal
Item2527	ModPerlEngineContrib, DebianPackage	troubles getting ModPerlEngineContrib running from debian repository	Needs Developer	Normal
Item2631	ModPerlEngineContrib, NativeSearchContrib	Sometimes renders blank page	Confirmed	Normal
Total	DebianPackage: 1 FastCGIEngineContrib: 1 FoswikiRequest: 1 ModPerlEngineContrib: 3 ModPerlEngineContrib: 1 NativeSearchContrib: 1		Confirmed: 3 Needs Developer: 1 Waiting for Feedback: 1	Enhancement: 1 Normal: 4

My proposals

Proposal	Status	Concern Raised By	Committed Developers
FSAPluginHooks	ParkedProposal		GilmarSantosJr

Proposals that I am concerned with

Proposal	Status	Concern Raised By	Committed Developers
AccessRightsChange	ParkedProposal	GilmarSantosJr, KennethLavrsen

Active Task Teams that I'm involved with

• SecurityTaskTeam - Security Task Team handles security per the community agreed process

Topics I'm Interested In

• Development.MakeFoswikiPSGIConformant
• Development.PostgreSQLSchemaForStore
• Development.RegisterSectionTagHandler
• Development.VirtualHosting

Personal Roadmap

Foswiki Standalone

1. Complete unit tests to FSA code
2. Update documentation (Tasks.Item4662#Documentation_updates)
3. Release ModPerlEngineContrib, FastCGIEngineContrib and HTTPEngineContrib
   • I'll rewrite HTTP engine from scratch, based on CPAN:Net::Server, that is more powerful and flexible than CPAN:HTTP::Daemon
     • Add support to run configure and legacy CGI scripts from HTTP engine
4. Work on architectural refactoring
   1. FSAPluginHooks
   2. Perform some tasks only once when persistent engines are in use
   3. Make VirtualHosting possible in persistent environments
   4. Make it possible to use shared memory
   5. Reduce coupling level
   6. Independent permission access (make it possible to use FastCGI Authorizer Role and PerlAuthzHandler mod_perl handler).
      • Fast permission check when accessing attachments
   7. Plugins test on persistent environments (guided by some relevancy/popularity order)

Benchmark Framework

• Documentation
• Infra-structure
  • Measures: elapsed time, used RAM, accouting (blocked and running time)
  • Test packages
    • Scalability-oriented
    • Few variables measured at a time (many packages)
  • Integrated tests
    • Use case oriented
    • Variables: OS, concurrency level, runtime engine, web server, hardware characteristics
  • Charts and Reports

Storage

• Optimized preferences storage
• Optimized forms storage (one table for each form )
  • Deal with form updates
  • Syntax to define/indicate indexes
• Snapshots (view consistently how the wiki (and not only a topic) was at some point in the past)
  • Deal with permissions ( Maybe a new permission related to view history [and why not another related to diffs ])
• Export/Import/Exchange data among wikis (like a distributed wiki. One can fetch data to a personal wiki, work on it and commit changes back)

Indexed Searches

• query search → SQL queries
• plain text → Xapian (not in core. Core should not have such a dependency)
• regex → brute force

TML Parser

• LALR-like
  • Generate DOM-like trees
• Pre-compiled topics
  • Integration with FoswikiCache and related HTTP headers
• Create new plugin hooks. Deprecate others (like commonTagsHandler)
  • Extend registerTagHandler to take tag properties (static, random, user-dependent, etc)
  • Let plugins to extend TML syntax
  • Update of core plugins
    • Use Ajax and REST in EditTablePlugin and TablePlugin
  • Update guide for extension developers
• HTML generation with HTML::Tiny and completely drop CGI.pm from core and default extensions.
  • Consider using some template engine

Improve test-infrastructure

• Use Devel::Cover to guide new tests
• Build test environments (Virtual machine images to perform tests and certify compatibility/limitations)

Foswiki as a Personal Knowledge Management Tool

• Wizards to define/update forms
  • Locate topics needing update after form change (Deal with form versions)
• Let plugins to add form field types/handlers (It is already in core since PLUGINS 2.0!)
  • Inheritance
  • Plugin implementing automata form field (the next value depends on the current)
  • Plugin implementing a form field type whose values depends on the values of other fields
• Visualization plugin: use graphviz to draw topic relations
• Wizard to perform complex searches
• Use HTTPEngineContrib to make it easier for personal use, including portable use from a memory stick.
• Usable without the concept of WikiWord

Other Stuff

• It would be nice to run foswiki inside a jail.I want to achieve this somehow (HTTP engine will help a lot)

My Personal Preferences

Uncomment preferences variables to activate them (remove the #-sign). Help and details on preferences variables are available in %TWIKIWEB%.DefaultPreferences.

• Show tool-tip topic info on mouse-over of WikiWord links, on or off:
  • Set NOWYSIWYG = 1
  • Set FINALPREFERENCES = NOWYSIWYG