Hi, I was thinking about that as well hence the blog post on running StreamPipes on K8s via our helm chart.
In general, we should discuss various „channels“ to promote StreamPipes and to grow our community. Blog posts is definitely a good approach - however there are more ways. Apache Beam has a really nice overview of various communication strategies [1] that may help us to adopt some ideas (tech talks at conferences, webinars, documentation, blogs, twitter, etc) What we def should do is focus on technical blog posts to show whats how SP works under the hood (tailored for our technical audience) as well as showcasing potential realizations for business relevant scenarios in IoT/IIoT. Therefore, I created a wiki page [2] to describe ways how to grow the community that contains a first draft of ideas. Thus, we can discuss potentials ways on the mailing list and update the wiki accordingly. Patrick [1] https://cwiki.apache.org/confluence/display/BEAM/Communication+strategy <https://cwiki.apache.org/confluence/display/BEAM/Communication+strategy> [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=152114865 <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=152114865> > Am 06.05.2020 um 19:52 schrieb Dominik Riemer <[email protected]>: > > Hi, > > > > I was also thinking about ways how to promote our first ASF release once it > has been approved. > > > > Patrick has already written a cool blog post on Kubernetes and edge > deployment and probably we can write a few more posts on new features such > as the new dashboard and notification view. Writing about use cases we > implemented with StreamPipes might also be a good way to grow the community. > Do you have any further ideas? > > > > Several people already told me that we are "underselling" features on our > website - so I guess there is some improvement potential for the website. > > > > Do you have any ideas what could be missing/restructured/improved in the > website and documentation? E.g.: > > * Mentioning StreamPipes Connect in the documentation > * Extending the features section with subpages explaining the > different modules > * Adding real use cases to the use case page > * Updating the SDK/developer documentation > * Probably many more things we can improve. > > > > Is anyone interested to support improving the website & docs? > > > > Dominik > > >
