Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Foster Community

Jump to bottom
María Arias de Reyna edited this page Sep 13, 2019 · 22 revisions
  • Use Public Channels for communication
    • 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) - we can discuss alternatives to IRC (align with Camel?)
    • Report issues on GH
  • Improve learning curve
    • Increase efforts on QuickStarts
    • Simple install procedure and/or demo site to try it out: Have a standalone distribution for the design time #6556
    • Publish the user doc on the community site.
    • Regular releases of the Syndesis cmdline tool that can be used to install the Syndnesis Operator and thus everything. We seem to already have this: https://github.com/syndesisio/syndesis/releases and if it works ok, then lets document this
  • Outreach
    • Market ourselves as Integration Lego
    • Attract community by creating more reusable components. Our connector wizards are very dynamic and can maybe be reused/extended. Look at extension mechanism.
    • Blogs, Presentations, Social Media to spread the word ("Open Source Marketing")
      • Official Blog Syndesis, not really used. Does it make sense?
      • Twitter using RSS feeds to publish stuff?
      • Do we have more social media?
    • Some Real World examples - 'user success stories'
    • Have release logs with new and noteworthy features
  • Relation with Other Communities
    • Leverage the Camel Community - no longer hide that we are using Camel
    • Split into many Open Source communities see also
    • Should Syndesis Releases numbers map to Camel Releases?
  • Refactoring
    • Support view source feature in the UI
    • Different Modality (Arch View, Dev View)
    • Our runtime could be just the (we should be able to remove our runtime source code) - this part would be maintained as part of the Apache Camel Project Camel-K module
    • Remove dependencies on Fuse bits (use Camel instead)
  • Further Features
    • The Design Time could produce a Camel-K route definition
    • Tie in with KNative
    • Run on Clouds Link
    • Create Connector Builder from Camel Component - make it easier for people to create and contribute a Connector.
    • Target Dev SaaS thingies (Github)
    • Native App (Desktop, Mobile)
    • Community IOT support to create and manage IOT integrations: nice demos, increase community target group
    • Syndesis should have Quarkus & GraalVM (optional) support, to find issues early and to hop on the Quarkus buzz
Clone this wiki locally