Our efforts as a team are organized around two themes:
- Platform Thinking
- Robust and stable REST APIs
- A consistent architecture of the entire Digital Business Platform, encompassing content and process.
- Running in AWS
- It needs to be easier to deploy Alfresco in AWS.
- Our proprietary products will take advantage of advanced AWS features. (P)
OS: Unless otherwise noted, all of the below listed efforts are expected to be open source.
- Tooling upgrades:
- Migrating from SVN to Git.
- Splitting the code base into separate projects.
- Replacing GhostScript with PDFium
- This was driven by GhostScript's license change, but PDFium appears to be performing better.
- Product insight from improved monitoring
- We need to better understand how our products are used so that we can invest in the right areas.
- Will replace the web pixel in Community Edition and the Heartbeat in Alfresco Content Services.
- Make it easy for administrators to know what data is being reported, and to opt-out.
- Produce a "Reference Deployment" of Alfresco to demonstrate how it should be used in production
- Based on containers (probably Docker and Kubernetes). See Docker Alfresco Resources?.
- Likely to replace the packaged installers and distribution.zip.
- Additional REST APIs, especially those needed for the Application Development Framework.
- Incorporate feedback on the new APIs
- Architectural changes for our next major upgrade
- Stand-alone identity server used across Content Services and Process Services
- Rework the SSO stack (including the proprietary components like SAML)
- Replace the embedded Activiti with the stand-alone Activiti
- Allow people to use the Activiti designers for "workflow", and make it easy to upgrade for full "process services"
- Improved import / export tooling