Alain Escaffre gives a preview of what we will be working on next year!

1. Insight of the Nuxeo 2016
Roadmap

2. NOS Roadmap

3. Branch Management

4. Three axis
● Application definition and tooling
● Development/Customization Flow in Studio
● NOS Customer portal
NOS Roadmap

5. ● Application definition,
● Nuxeo Package build
● Private marketplace
● Use of Github for hosting Studio Project sources
● Configurability of Nuxeo Studio
NOS - Application Definition and Tooling

6. ● Better separate Core, Process, and UI configuration/development with more
adapted editors:
● Diagram entity relation for the Core part
● UI Visual Designer
● Make sure a Nuxeo Studio project scales (still usable when intensively used)
● Make it more useful in terms of documentation
● Document everywhere
NOS - Studio as a set of multiple editors

7. ● Better features for contact management
● Nice integration of all entry points
NOS - Customer Portal

8. Nuxeo Platform Roadmap

9. Nuxeo Platform Checkup: a tool for easily uploading the instance configuration
and state to jira when creating support tickets.
Nuxeo Platform Checkup

10. Goal: make it easy to
● set up a Nuxeo Cluster
● Deploy an application configuration
● Apply Hotfixes
Proposed Solution: a cluster manager server to which nodes will subscribe.
Nuxeo Cluster

11. ● Some observations: our event bus system is in-house and hasn’t change for
long. It needs integration capability with externals
● Jobs and queues design is also in-house while it is a common piece of
intrastructure
● Many people not happy at Nuxeo of the way it is right now !
⇒ Reimplementation using a messaging framework (ex: Kafka)
Event Bus and Workmanager re-
implementation

12. ● Relationship service as not been advertised much
● Reference field could also be seen as a relation ship definition
● What we wan’t is ability to query (join) relation ships
⇒ Use Elasticsearch to index related documents
⇒ Provide a way to easily declare relations (maybe based on the schemas
definition)
Relationship and Linked Documents Index

13. Goal: make operations on large set of documents work and scale
Solution: use backend capabilities. Ex: MongoDB
Scope: lifecycle update, deletion, acls, quotas, bulk metadata update
Batch Processing

14. ● More coherent automated versioning policies
● Tree Versioning
Versioning

15. ● CouchBase
● PG + JSON
NoSQL Implementations

16. ● Let’s bootstrap a completely new web app using client side components
● Then work on pluggability/extensibility
● Scope: Browse/Create - Search - Workflow - User Experience Roadmap
(Right panel, Image Preview, removable left tree…)
Goal: make sure we are not slowed down to much by legacy and provide a
modern/ responsive UI for LTS 2016.
JSF web app will still be used and released until we are happy we what we have
on the other side. Maybe also we will realize there are good mixed strategies.
UI: A new Web UI Web Component Based

17. ● Scaffolding: allow users to edit UI HTML/XHTML files in Studio
● Visual Web Designer
UI: A new design flow in Studio

18. ● More Productive UI
● A new module : Adaptative Routes
Workflow

19. ● TCK Evolution
● C# client
● Python client
● JavaScript clients merge
● Java client update
TCK and JavaScript Client

20. ● A native mobile web app for Android and iOS
⇒ use of React Native
Mobile

21. Video Management module
● Transcode
● Cut
● Annotate
With a nice wizard and some re-usable operations
Video Management

22. ● Box
● One Drive
Live Connect

23. ● Activities for a user friendly history of what happens in the repository/
workflow
● Notifications for being notified of interesting activities on multiple channels
● in app board
● slack
● email
● mobile app
Activities & Notifications

24. ● FS Decoration
● Better management of the community of users
● Notifications from server
● Document Importer module
Drive