Page Comparison

• timeline
• determine committers (~last 12 months); all/nothing rights, enforce socially
• travis-ci

• Nightly servers: IU needs to pass the baton
• DNS server (managed by UMich currently)
• Sakai maven repo (kill or move?)

• Promotional materials (funding from Board)
• CIO/CTO value proposition page
• Announcements outside of the Sakai lists, Facebook, Twitter, news sites
• Product polish (whole package, ref mozilla products)
• Documentation
  • simplified (eg install maven,tomcat etc)
  • clarified (eg java_opts in multiple places)
• sakaiproject.org refinements
• Educause booth

Two ideas:

• https://www.atlassian.com/software/confluence/questions
• Neal manually create TOC for pages we know are useful. Build up over time.
• Process ideas for these experiments
• We can discuss needs behind this, if it is not obvious to all.

• Previous versions of Sakai have been audited, meeting WCAG2 is important for users sake and for market competitiveness' sake
• There are no plans for a full audit of Sakai and a big chunk of accessibility resources are no longer part of project