Can be found in markdown files in the repo like the README or on our web site here: https://www.attendize.com.

Attendize has been in a bit of a flux the past few years with regards to maintenance, adding new features, merging pull requests and responding to issue reports. The current team of maintainers is working to catch up on the backlog of work, modernise the code base, and get back into a consistent release cycle. The following plans are currently in progress to make this happen:

• Triage all issues, close duplicates/obsoletes, tag all issues into categories
• Triage all pull requests, close duplicates/obsoletes, tag all PR's into categories
• Triage new issues and PR's regularly
• Add contributing guide
• Add code of conduct
• Resolve backlog of open PR's in the following order of priority:
  • security
  • bugs
  • enhancements
  • maintenance
  • features
  • support
  • question
• Resolve backlog of open issues in the following order of priority:
  • security
  • bugs
  • enhancements
  • maintenance
  • features
  • support
  • question
• Create a release process and release schedule, document in a release guide
• Upgrade the codebase and environment to current or modern releases/best practices
  • docker
  • php
  • composer
  • mysql
• Create and publish roadmap for future releases
• Create comprehensive documentation
  • technical documentation
  • end user documentation