In addition to the ongoing work on Neos 2.0 the team has been working hard to set up an independent infrastructure for the Neos Project. The goal is to have a solid technical foundation for you - the Neos community - to stay up-to-date with development, team discussions, code sprints and really everything concerning Neos and Flow.
As most of you are aware, Slack exists for chat communication within the Neos community. Slack even agreed to sponsor a standard plan for the community - thanks Slack folks! You can signup to Slack here.
Why did we choose to use Discourse over mailing lists or GitHub? We want to establish a modern platform that is not just for developers but also for designers, marketing-experts and all other non-technical community members.
For user management
The account system is built on top of Atlassian Crowd and will support single-sign-on for all services in the future.
For tickets, documentation and translations
We moved our Jira system to jira.neos.io. Help us keeping track of any Neos or Flow bugs you find and see what's planned for the next release.
Neos user backend translations can now be accessed at translate.neos.io.
You may have noticed that neos.typo3.org has moved to www.neos.io. We have set up redundant, load-balanced servers on AWS including a CDN. This setup should provide sufficient performance and reliability for our website.
- Atlassian - Crowd and Jira licenses
- Digital Ocean - hosting of Discourse
- Flownative - setup of Discourse, id.neos.io and hosting of neos.io – approx. 2,5 weeks of work time
- Netlogix - setup of id.neos.io, hosting for Jira and Crowd
- Networkteam & Stefan Bruggmann|dotpulse AG - development support for id.neos.io
- Sandstorm - 3 weeks of effort so far for the funding process
- Slack - standard plan for the Neos slack
Special thanks go to our community who offered and provided a tremendous amount of help!