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
#general@dangngoctan2012: @dangngoctan2012 has joined the channel@priya.shivakumar: @priya.shivakumar has joined the channel@arnaud.zdziobeck: @arnaud.zdziobeck has joined the channel@ralph.debusmann967: One basic question about data preparation (for ingestion into Pinot) - how do you combine e.g.
+1 to a separate slack workspace for StarTree related channels.
On Wed, May 25, 2022 at 4:04 PM Tim Berglund wrote:
> These are great things! My team and I at Confluent worked hard to help new
> hires come up to speed with a list like this and to keep events like Kafka
> Summit and our meetups
These are great things! My team and I at Confluent worked hard to help new
hires come up to speed with a list like this and to keep events like Kafka
Summit and our meetups operating with integrity. Not everybody gets it
right away, but we always got them on board with sufficient help. I've seen
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
*
> 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
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
I wasn't aware the project was using Slack to coordinate its work! But then
it stands to reason that I wouldn't see that activity. I thought that kind
of thing was supposed to happen on public email lists—although I certainly
understand why you'd want to use Slack instead for most of that. I am
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
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
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
11 matches
Mail list logo
