This post is a summary of a discussion which took place at the Neos code sprint in Vienna.
Neos namespace:
- packages which are included in the distribution
- they have to be compatible with the old and the recent releases
Flowpack namespace:
What Flowpack is, will be told by the new website. If you are interested, have a look here:
ToDos:
- archive old packages like:
- GitHub - Flowpack/Flowpack.Behat: [READ-ONLY] Behat support package for Neos Flow
- GitHub - Flowpack/Flowpack.SingleSignOn.Client: A Flow Single Sign-On client for the Flowpack SSO Server
- GitHub - Flowpack/Flowpack.SingleSignOn.Server: A Single Sign-On Server based on Flow
- GitHub - Flowpack/Flowpack.SingleSignOn.DemoServer: Flow package which provides the user interface and configuration for a demo server for the Flowpack SSO
- GitHub - Flowpack/Flowpack.SingleSignon.TestSuite: A Behat test suite for the Flowpack SSO server / client solution
- GitHub - Flowpack/Flowpack.SingleSignOn.DemoInstance: Flow package which provides the user interface and configuration for a demo instance for the Flowpack SSO
- GitHub - Flowpack/Flowpack.SingleSignOn.DemoServer-Distribution: Flow Distribution which provides the server part of the Flowpack SSO demo setup
- GitHub - Flowpack/Flowpack.SingleSignOn.DemoInstance-Distribution: Flow Distribution which provides the instance (client) part of the Flowpack SSO demo setup
- GitHub - Flowpack/Flowpack.SingleSignOn.Demo-Vagrant: Demo Vagrant box for the Flowpack Single-Sign-On for Flow
- push flowpack website
- work on what is flowpack
- work how to get in guideline - incubator