Hello Everyone,
The meeting minutes of the Store discussion are given below;
*Purpose:*
- To discuss the challenges in extending ES with new asset types
- To gather requirements from existing ES internal users
*Participants:*
- *ES*: Nuwan , Ruchira , SameeraM
- *Mobile Team*: Dulitha,
- *API Manager:* Dimuthu, Shiro
- App Factory: Sumedha, Lalaji , Joseph (Jo)
- Isabelle
- Dmitry
- SameeraP
*Observations*
- Encapsulating all asset logic into a single package (e.g. zip) which
would allow a user to reuse extensions
- It should be possible to remotely deploy assets (This would be a
concern that would be handled by the Store Admin app).
- The Store Admin app needs to be an entity that would need to be
gracefully integrated into the Publisher
- One possible suggestion was to have it accessible via link
depending on the permissions of the user.
- Yet another approach proposed the admin app been a simple tab
within the Publisher (Note: This would be problematic from a deployment
standpoint)
- There needs to be a common UI framework with reusable components.A
component should be self contained and open for extensibility
- An existing approach to this problem is the use of Jaggery modules and
the Caramel framework.
*Action Items:*
1. Take more steps to disseminate knowledge on the correct way to build
apps with Jaggery
- Articles on using Caramel to build apps
- Articles on when to create Jaggery modules
2. Enable people to easily locate and reuse Jaggery modules
- i.e. Jaggery Extensions repository [2]
- Improve the documentation of Jaggery modules
3. Define a set of governance principles for Jaggery modules
*Meetings:*
1. Review the usage of Jaggery and ES in existing products (Attendees:
Mobile,App Manager and Connector Stores)
2. Plan a common UI framework (Attendees: Carbon Team,App Factory, API
Manager ,Mobile Team and ES Team)
3. Differentiate between the author vs. the provider when deploying
assets.More details on this topic can found in the Owner of the asset mail
thread [1]
Please let me know if I have missed any important points.
*Reference*
[1] [Architecture] Owner of the asset - role or a user?
[2] Jaggery Extensions directory https://github.com/wso2/jaggery-extensions
Thank You
--
Sameera Medagammaddegedara
Software Engineer
Contact:
Email: [email protected]
Mobile: + 94 077 255 3005
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
