The simple answer is to use the Apache Software Foundation's workspace 
(the-asf.slack.com) for Apache Pinot. Let StarTree expand *their* workspace as 
they see fit, and the Apache Pinot community can join the 400 other public 
channels over at the-asf.slack.com. Have somebody create #pinot, and adjust the 
website/docco to point there.

Cheers,
-g

On 2022/05/25 20:59:11 siddharth teotia 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
> >
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pinot.apache.org
For additional commands, e-mail: dev-h...@pinot.apache.org

Reply via email to