t;>>>> 1. Project Page
>>>>> 2. Maturity Model
>>>>>
>>>>> On Sun, May 16, 2021 at 1:57 PM Felix Cheung
>>>>> wrote:
>>>>>> Agreed it is not a blocker per se, but I figure it will raise some
>>>>
cker per se, but I figure it will raise some questions
> if more board/podling reports are missed.
>
> Maybe worthwhile to setup forwarding from dev@ to slack.
>
>
> From: kishore g mailto:g.kish...@gmail.com>>
> Sent: Saturday, May 15, 2021 6:53 PM
> To: dev@pinot.apa
eports are missed.
>>>>
>>>> Maybe worthwhile to setup forwarding from dev@ to slack.
>>>>
>>>>
>>>> --
>>>> *From:* kishore g
>>>> *Sent:* Saturday, May 15, 2021 6:53 PM
>>>> *
>>>
>>> Maybe worthwhile to setup forwarding from dev@ to slack.
>>>
>>>
>>> --
>>> *From:* kishore g
>>> *Sent:* Saturday, May 15, 2021 6:53 PM
>>> *To:* dev@pinot.apache.org
>>> *Cc
>
>> Maybe worthwhile to setup forwarding from dev@ to slack.
>>
>>
>> --
>> *From:* kishore g
>> *Sent:* Saturday, May 15, 2021 6:53 PM
>> *To:* dev@pinot.apache.org
>> *Cc:* Mayank Shrivastava; j...@apache.org; ol...@apach
rding from dev@ to slack.
>
>
> --
> *From:* kishore g
> *Sent:* Saturday, May 15, 2021 6:53 PM
> *To:* dev@pinot.apache.org
> *Cc:* Mayank Shrivastava; j...@apache.org; ol...@apache.org
> *Subject:* Re: DISCUSS Pinot Graduation
>
> I agree with y
: Mayank Shrivastava; j...@apache.org; ol...@apache.org
Subject: Re: DISCUSS Pinot Graduation
I agree with you on traffic on dev. We tried to move few discussions to dev@
but entire community is active on the slack channel and prefer discussion on
GitHub issues. We push everything to dev@ so folks
I agree with you on traffic on dev. We tried to move few discussions to dev@
but entire community is active on the slack channel and prefer discussion
on GitHub issues. We push everything to dev@ so folks on ML have all the
information.
We have < 100 on @dev vs ~1300 on slack. Trying to push
Generally it looks good, I’ve checked clutch report, website checks etc,
but a few reminders and areas to pay attention to:
- dev@ traffic is very or almost zero? I realize the community is active on
slack and summary is sent to dev@ everyday, but some traffic there will be
good...
- ... because
Mentors - Felix, Olivier, Jim,
Wondering what your thoughts on are for proposing Pinot's graduation. We
have addressed all the issues that have been brought up in the past. If
there are other steps to be taken, please let us know and we can also take
care of those as well. Looking forward to your
+1! Glad to see we've accomplished a lot and the community is pretty strong
and healthy!
On Mon, May 10, 2021 at 11:23 AM Subbu Subramaniam
wrote:
> +1
>
> Let us know how we can help with the graduation, and if there are any
> pending items to be resolved.
>
> -Subbu
>
> On 2021/05/09
+1
Let us know how we can help with the graduation, and if there are any pending
items to be resolved.
-Subbu
On 2021/05/09 14:07:45, kishore g wrote:
> Hello,
>
>
> I would like to start a conversation about the readiness of Apache Pinot to
> graduate. We have come a long way since we
+1 on initiating the graduation process. I also think that we have a
very strong community around the project.
Best,
Seunghyun
On Mon, May 10, 2021 at 9:51 AM Yupeng Fu wrote:
>
> +1 on graduation readiness. Apache Pinot has a lot of accomplishments in the
> past years on project maturity. It
+1 on graduation readiness. Apache Pinot has a lot of accomplishments in
the past years on project maturity. It has a strong community and good
adoption in the industry.
Best,
On Sun, May 9, 2021 at 8:54 AM Mayank Shrivastava
wrote:
> +1 on initiating the discussion on readiness for
+1 on initiating the discussion on readiness for graduation. Apache Pinot now
has a very strong and healthy community around it, formalizing the graduation
will only help further. If there are formalities remaining we will be happy to
address them.
Regards
Mayank
> On May 9, 2021, at 7:08
Hello,
I would like to start a conversation about the readiness of Apache Pinot to
graduate. We have come a long way since we incubated in Apache, with:
-
7800+ contributions from 168 contributors
-
7 releases by various committers
-
6 new committers invited (all accepted)
16 matches
Mail list logo
