This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 200
Planning for Syndesis 2.0
Kurt T Stam edited this page Sep 11, 2019
·
16 revisions
Capturing ideas for Syndesis 2.0
Syndesis has reached minimum viable product and we should separate us from the product so that we can focus on creating a Syndesis community.
- What is Syndesis?: It's one thing to show how Syndesis works, but for people to be able to contribute we need to define boundaries around our communities: Camel/Camel-K, AtlasMap, Syndesis, OpenShift/Kubernetes. We have to create diagrams as to where is what.
- Support deployment on plain vanilla Kubernetes (Graceful degradation of features that are missing)
- Attract community by creating more reusable components. Our connector wizards are very dynamic and can maybe be reused/extended. Look at extension mechanism.
- Use the syndesis mailing list so it looks like a project that is alive and well (picked up by google search)
- Make sure plain IRC works (picked up by google search)
- Component diagram
- Report issues on GH
- QuickStarts
- Some Real World examples - 'user success stories'
- Blogs, Presentations, Social Media to spread the word
- Simple install procedure and/or demo site to try it out (or link to fuse-online for that)
- Publish the user doc on the community site.