You cut the video link, but it was relevant. At Hortonworks, we found it worthwhile to train the engineers, marketing, & events teams on: * Apache structure and roles * The Apache Way * Apache License * Why Hortonworks chooses to work with Apache * Being both a Hortonworker and a part of Apache * Practical tips: what works & mistakes not to repeat * Trademarks
.. Owen On Wed, May 25, 2022 at 9:51 PM Tim Berglund <tlbergl...@gmail.com> wrote: > > > I'd also suggest that Startree work on training their marketing and > sales team on working with Apache projects. > > May I ask you to be more specific here? I've been doing some internal > training in the past two months to help with problems like the one I'm > rectifying here. Maintaining proper boundaries and ASF branding guidelines > is important. > > > On Wed, May 25, 2022 at 3:48 PM Owen O'Malley <owen.omal...@gmail.com> > wrote: > >> As an Apache member observer, unless the project wants to abandon Slack, >> it seems to me that Startree should make a new Slack workspace rather than >> taking the Apache Pinot one. >> >> I'd also suggest that Startree work on training their marketing and sales >> team on working with Apache projects. Take a look at Alan Gate's >> presentation on 'Training Our Teams on the Apache Way.' >> https://youtu.be/uFNE0IpKOxU >> >> .. Owen >> >> On Wed, May 25, 2022 at 9:17 PM Seunghyun Lee <sn...@apache.org> wrote: >> >>> I also definitely agree that Startree has put a tremendous effort to >>> grow the ASF Pinot community slack channel and helping people for >>> troubleshooting/debug the issue. >>> >>> On the other hand, the community slack channel was created as part of >>> the Apache incubation process and this workspace has always been regarded >>> as one of the community growth metrics for ASF Pinot. >>> >>> As Sidd mentioned, a lot of ASF Pinot-related discussions are happening >>> in the slack channel (e.g. contributor/committer/pmc discussions, cross org >>> collaboration on the features etc). From what Tim is highlighting, I think >>> that maybe it is better to keep a separate workspace: one for Startree >>> customers and the other for only ASF Pinot users and contributors. >>> >>> Best, >>> Seunghyun >>> >>> >>> >>> >>> On Wed, May 25, 2022 at 2:00 PM siddharth teotia < >>> siddharthteo...@gmail.com> wrote: >>> >>>> Hi Tim, >>>> >>>> Thank you for sharing this. >>>> >>>> > StarTree is committed to making Pinot famous—that’s my actual job, >>>> in fact—and to helping users of the open-source project be successful with >>>> it, but we need to keep the boundaries between the ASF and StarTree clearly >>>> defined. Renaming this Slack is an important part of that distinction >>>> >>>> I understand where you are coming from and why you may want to keep >>>> distinction between ASF Pinot and Startree. However, I am not quite sure >>>> how renaming this is going to help with distinction because then all the >>>> ASF Pinot related conversations (between contributors / committers / PMCs >>>> for release, PR, issue etc discussion) will have to go through Startree >>>> workspace which may not be the correct place to do so because these >>>> discussions are orthogonal to Startree or any company using / contributing >>>> to ASF Pinot. >>>> >>>> This workspace was initially created to help grow the ASF Pinot >>>> community and have the related discussions there. I completely agree that >>>> Startree has done a great job in bringing more folks to the workspace, >>>> helping them on a day to day basis etc. However, renaming will actually >>>> blur the distinction to be honest. >>>> >>>> Shall we discuss this to see if there is any alternative to achieve >>>> this distinction ? >>>> >>>> Thanks >>>> Sidd >>>> >>>> >>>> >>>> >>>> >>>> On Wed, May 25, 2022 at 11:56 AM Tim Berglund <tlbergl...@gmail.com> >>>> wrote: >>>> >>>>> Pinot Dev, >>>>> >>>>> I’m Tim Berglund. The barest intro of me: I run Developer Relations at >>>>> StarTree. I wanted to go over a change I’m making to our Slack workspace >>>>> so >>>>> it is not a surprise to you and we have a chance to talk through any >>>>> questions. >>>>> >>>>> On June 1, 2022, we will rename the Apache Pinot™ Slack Workspace to >>>>> the StarTree Community Slack Workspace. Let me explain my thinking here. >>>>> >>>>> First, of the top ten lifetime contributors in this Slack, six are >>>>> StarTree employees, accounting for about 80% of messages. I’m concerned by >>>>> the StarTree-heavy presence in a workspace that borrows the Apache >>>>> branding. It made sense to name the workspace “Apache Pinot” when Kishore >>>>> first made it, but as its usage has evolved and will continue to evolve, >>>>> keeping the Apache name is not appropriate. StarTree is committed to >>>>> making >>>>> Pinot famous—that’s my actual job, in fact—and to helping users of the >>>>> open-source project be successful with it, but we need to keep the >>>>> boundaries between the ASF and StarTree clearly defined. Renaming this >>>>> Slack is an important part of that distinction, and something I’d rather >>>>> do >>>>> sooner than later. >>>>> >>>>> Second, the continued evolution of the workspace is sure to include >>>>> channels to support StarTree’s cloud service and other community-licensed >>>>> products we might release in the future. Our broad commitment to and >>>>> investment in the support and advocacy for Apache Pinot will remain. >>>>> Renaming of the Slack will not cause it to become a place for vendor sales >>>>> pitches. (Indeed, those are forbidden, and sales people who come into >>>>> Slack >>>>> to sell will answer to me.) >>>>> >>>>> The Slack is home to many other community members who have no >>>>> association with the ASF at all, and of course will continue to be an >>>>> inclusive space open to anyone who wants to talk about Pinot. It’s our >>>>> goal >>>>> for it to continue to grow and thrive, and for StarTree to continue to >>>>> invest heavily in it as a helpful and welcoming place. >>>>> >>>>> Warmly, >>>>> >>>>> Tim Berglund >>>>> >>>>> VP Developer Relations >>>>> StarTree >>>>> >>>>
