+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!) :-)
>> >
>> >
>>
>>

Reply via email to