FSG A11y Logistics/Resources Discussion

FSG Infrastructure

• FSG A11y email distributions lists
  
• FSG A11y development at http://gforge.freestandards.org/projects/a11y/
• CVS modules
• FSG A11y bugs at http://bugs.freestandards.org/
• 
  

Project Management

• The workgroup and/or subgroups should manage tasks and milestones for deliverables.
  
• Each subgroup to role up information to workgroup chair (or project manager)
  
• Practice elementary project management  using Mr Project or other suitable means
• Large orphaned tasks should be described and sized to be outsourced to corporations or grants.
• Subgroups should meet weekly, fortnightly, or monthly
  

• Example tasks
• Convert keyboard draft specification to DocBook SGML then get it CVS commited
• Review all relivant manual pages (ie., ATK, IDL, ....)
• Fix makefile oxygen builds of IDL documents
  

Specifications

• Draft and final documents should be formatted in DocBook SGML which can be converted to text, PDF, RTF, and HTML.
• Draft specifications should be live documents accessed via CVS
• Nightly build of draft documents, then dated version published online.
• Text of documents are written and formatted manually.  Tables of APIs, ABIs, and commands are dynamically generated by perl scripts mining information out of a database.
• FSG A11y specifications can reference other versioned documents such as ATK man pages.   The source of those referenced man pages stay with the upstream source of the libraries.   This keeps everything in sync.
• Referenced specifications can be archived for safe keeping.
• FSG A11y's ATSPI might have a general IDL specification with multiple language binding addendums.  Not sure if there will need to be multiple architecture addendums similar to what the LSB has.