[ 
https://issues.apache.org/jira/browse/BEAM-11247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236219#comment-17236219
 ] 

Lynn Root edited comment on BEAM-11247 at 11/20/20, 3:10 PM:
-------------------------------------------------------------

Thanks for the clarification [~bhermann] - what would be the text for the use 
case that you'd like to use for Klio?

 

The Klio logo can be found here: 
[https://github.com/spotify/klio/blob/master/docs/src/_static/images/logo.png]


was (Author: roguelynn):
Thanks for the clarification [~bhermann] - what would be the text for the use 
case text that you'd like to use for Klio?

 

The Klio logo can be found here: 
https://github.com/spotify/klio/blob/master/docs/src/_static/images/logo.png

> Spotify 
> --------
>
>                 Key: BEAM-11247
>                 URL: https://issues.apache.org/jira/browse/BEAM-11247
>             Project: Beam
>          Issue Type: Sub-task
>          Components: website
>            Reporter: Brittany
>            Assignee: Brittany
>            Priority: P1
>              Labels: website-revamp-2020
>
> Hi Lynn,
>  
> I would like to personally thank you again on behalf of the Beam Community 
> for speaking at the Beam Digital Summit! While we are in the process of 
> revamping the Beam website, we would love to add your use case and company 
> logo onto the ["Powered By Apache 
> Beam"|https://beam.apache.org/community/powered-by/] webpage. As an example 
> of what we are hoping to achieve, you can see the Powered By Apache Flink 
> webpage [here|https://flink.apache.org/poweredby.html]. 
>  
> Would you be okay with us adding the text of the use case and give us 
> permissions to showcase the logo of your company? If you are okay with this, 
> could you please review this Jira ticket that I have created specifically for 
> you? Once you give LGTM, we should be good to go. 
>  
> Please let me know if you have any questions! 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to