Aizhamal, what is the plan for your document? Would it be fine if we add > this powered_by page now, and edit as we go? > Yes. The document was created as a plan to add all those sections, but it would be great to start adding them as soon as possible.
> Ahmet > > On Tue, May 26, 2020 at 2:30 PM Aizhamal Nurmamat kyzy < > [email protected]> wrote: > >> >> Oops, just saw you linked it earlier Aizhamal. Is it still open for input? >>> >>> Yes, it is! Feel free to add suggestions right in the doc. The doc will >> eventually need some cleanup/reorg, but now is a good time to add >> suggestions. Thanks Matthias! >> >> >> >>> On Mon, 25 May 2020 at 09:20, Matthias Baetens < >>> [email protected]> wrote: >>> >>>> I think this is a great idea. We could support the page with relevant >>>> Meetup / Summit talks as well. >>>> >>>> Is there a place where we the website redesign is being planned and >>>> where we can contribute ideas or discuss the structure of such a page? >>>> >>>> On Fri, 1 May 2020 at 20:00, Aizhamal Nurmamat kyzy < >>>> [email protected]> wrote: >>>> >>>>> Another example of similar pages: >>>>> https://www.instaclustr.com/resource-type/case-studies/. The whole >>>>> resources section is very useful. It would be good for Beam to have links >>>>> to webinars, meetups, books, whitepapers, etc. from the website where new >>>>> users land. >>>>> Simpler example: https://flink.apache.org/poweredby.html . It shows >>>>> snippets and links to external (mostly) resources. Seems easier to manage. >>>>> >>>>> >>>>> On Fri, May 1, 2020 at 6:28 AM Kenneth Knowles <[email protected]> >>>>> wrote: >>>>> >>>>>> +1 to a "Powered By" style page. These are pretty common. Like >>>>>> https://calcite.apache.org/docs/powered_by.html >>>>>> >>>>>> I think applying a designer's skills might result in something a bit >>>>>> cooler looking... >>>>>> >>>>>> Kenn >>>>>> >>>>>> On Thu, Apr 30, 2020 at 9:24 AM Austin Bennett < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> A first pass, something like: >>>>>>> >>>>>>> https://druid.apache.org/druid-powered >>>>>>> https://spark.apache.org/powered-by.html >>>>>>> >>>>>>> or even as simple as: >>>>>>> https://github.com/apache/airflow#who-uses-apache-airflow >>>>>>> >>>>>>> Would go a long way in the sorts of very high-level conversations >>>>>>> I'm having around technology adoption/standardization. >>>>>>> >>>>>>> Getting into more specifics/testimonials/case-studies is also great, >>>>>>> but I wouldn't expect those to get looked at by most, until passing the >>>>>>> first bar of seeming to having a significant adoption. >>>>>>> >>>>>>> @Aizhamal Nurmamat kyzy <[email protected]> - happy to >>>>>>> contribute as I can. >>>>>>> >>>>>>> On Tue, Apr 28, 2020 at 10:13 PM Jean-Baptiste Onofre < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> We already have some testimonials on Beam home page (I did the one >>>>>>>> about Beam use at Talend). >>>>>>>> >>>>>>>> It makes sense to have a dedicated section as it gives ideas about >>>>>>>> use case and production system running with Beam. >>>>>>>> >>>>>>>> Regards >>>>>>>> JB >>>>>>>> >>>>>>>> > Le 28 avr. 2020 à 23:42, Austin Bennett < >>>>>>>> [email protected]> a écrit : >>>>>>>> > >>>>>>>> > Hi All, >>>>>>>> > >>>>>>>> > Have we considered getting onto our website or our our GitHub >>>>>>>> repo the ability for individuals to share that their company is using >>>>>>>> Beam? Seeing - what I believe to be a reasonable list of - companies >>>>>>>> productively using Beam would be helpful to point others to. For >>>>>>>> instance, >>>>>>>> a common question I get is whether anyone or who is using? I'm not >>>>>>>> sure >>>>>>>> that's the best metric or datapoint in many cases for adoption, but a >>>>>>>> heuristic that some rely upon. >>>>>>>> > >>>>>>>> > Naturally, we could ask for a roll-call, esp. via user list, but >>>>>>>> imagining a persistent web-list would be of interest. >>>>>>>> > >>>>>>>> > Cheers, >>>>>>>> > Austin >>>>>>>> > >>>>>>>> > >>>>>>>> > P.S. If putting such a list into our repo, that would also get >>>>>>>> some people to submit PRs (so more contributors!) :-) >>>>>>>> > >>>>>>>> > >>>>>>>> >>>>>>>>
