Creating New Plugins

Planning

• A plugin label needs to be created (similar to wp, jos, mw)
• A subversion repository must be created (Pam and Dale can both do this)
• The SVN:Externals link must be set up to bring down the pwlib and legal directories from the pwcommon repository.
• The plugin-specific code directory needs to be copied from another plugin (it will later be renamed & gutted)
• The pw-config.php file needs to be copied from another plugin.

Integration

• The pw-config.php needs to be changed to reflect the plugin identifier, and path information for the new plugin.
• The pw-claimtypes.php file needs to be changed to reflect the correct minimum set of claims for this enviroment, and the correct data mapping.
• The plugin-specific code directory needs to be renamed to the new plugin indentifier.
• One by one, the wrapper scripts in the plugin-specific code directory need to be adapted to the new framework.
• The following four pieces of code will need to be written from scratch (not adapted):
  1. Write Installation Code.
  2. Create an Administration Page
  3. Integration of the infocard trigger into the existing authentication page.
  4. Creation of new accounts.
  5. Actual authentication of an identified account to the framework.