You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@drill.apache.org by Charles Givre <cg...@gmail.com> on 2020/05/15 14:48:39 UTC
Drill's Future
Dear Drill Users,
I hope everyone weathering the COVID storm and staying safe.
As you may or may not be aware, I found out this week that MapR's successor, HPE has for all intents and purposes ended its support for Drill. Whilst they will be contributing minimal bug fixes, they will not be adding any new functionality or new features. This leaves the open source Drill without a primary backer. Under the Apache rules, to commit code to the code base it must be reviewed and voted upon. While we have committers, we do not currently have enough code reviewers to review new commits.
My question to you as a Drill user is whether or not Drill is offering value to you and your organization. If it is, and you would like to see Drill development continue, then we need additional volunteers to step up and review pull requests.
If you're interested in reviewing code for Drill, please let me know.
Thank you for your continued support and stay safe!
-- Charles
Re: Drill's Future
Posted by Charles Givre <cg...@gmail.com>.
Hi Herman,
Thanks for your offer to assist with testing and documentation. This is definitely something that Drill could use some assistance with. If you'd like to start with some documentation, there really is a lot of undocumented functionality in Drill. I'd recommend doing a search in the codebase for README.md files and then looking at the docs to see if that info is in the documentation anywhere.
Here's the info for updating the Drill site:
https://github.com/apache/drill-site <https://github.com/apache/drill-site>
https://github.com/apache/drill/tree/gh-pages-master <https://github.com/apache/drill/tree/gh-pages-master>
Thank you very much for stepping up and I look forward to working with you!
Best,
-- C
> On May 19, 2020, at 5:23 AM, Herman Tan <he...@redcubesg.com> wrote:
>
> Hi,
>
> I appreciate the work that this community have put into Drill.
> I am using it regularly and promoting it's use.
> I can help with testing and documentation.
>
>
> Regards,
> Herman Tan
>
> On Sun, 17 May 2020, 9:56 pm Charles Givre, <cg...@gmail.com> wrote:
>
>> Hey Bob,
>> Great to hear from you and thanks for volunteering. Between you and me,
>> I've been considering forking Drill, moving it to the OWASP foundation, and
>> integrating a lot of security-related stuff that either hasn't been
>> accepted or I haven't submitted. I suspect this would help increase Drill's
>> user base and hence get better features etc.
>>
>> What do you think?
>> -- C
>>
>>
>>
>>> On May 15, 2020, at 6:31 PM, Bob Rudis <bo...@rud.is> wrote:
>>>
>>> I can carve out work-time to review PRs.
>>>
>>> -boB
>>>
>>> On Fri, May 15, 2020 at 11:25 AM Prabhakar Bhosaale
>>> <bh...@gmail.com> wrote:
>>>>
>>>> HI Charles,
>>>> I have never contributed to any open source community before this. Also
>> I
>>>> am not expert on JAVA but willing to contribute for sure. Please let me
>>>> know in what capacity i can be helpful here.
>>>>
>>>> Also, I would like to know if there any efforts going on to identify
>>>> primary support for Apache drill and what is its future in case there
>> is no
>>>> primary supporter? My organization is planning to build some tools using
>>>> drill and this news will definitely impact the same. thx
>>>>
>>>> Regards
>>>> Prabhakar
>>>>
>>>> On Fri, May 15, 2020 at 8:18 PM Charles Givre <cg...@gmail.com> wrote:
>>>>
>>>>> Dear Drill Users,
>>>>> I hope everyone weathering the COVID storm and staying safe.
>>>>>
>>>>> As you may or may not be aware, I found out this week that MapR's
>>>>> successor, HPE has for all intents and purposes ended its support for
>>>>> Drill. Whilst they will be contributing minimal bug fixes, they will
>> not
>>>>> be adding any new functionality or new features. This leaves the open
>>>>> source Drill without a primary backer. Under the Apache rules, to
>> commit
>>>>> code to the code base it must be reviewed and voted upon. While we have
>>>>> committers, we do not currently have enough code reviewers to review
>> new
>>>>> commits.
>>>>>
>>>>> My question to you as a Drill user is whether or not Drill is offering
>>>>> value to you and your organization. If it is, and you would like to
>> see
>>>>> Drill development continue, then we need additional volunteers to step
>> up
>>>>> and review pull requests.
>>>>>
>>>>> If you're interested in reviewing code for Drill, please let me know.
>>>>>
>>>>> Thank you for your continued support and stay safe!
>>>>> -- Charles
>>
>>
Re: Drill's Future
Posted by Herman Tan <he...@redcubesg.com>.
Hi,
I appreciate the work that this community have put into Drill.
I am using it regularly and promoting it's use.
I can help with testing and documentation.
Regards,
Herman Tan
On Sun, 17 May 2020, 9:56 pm Charles Givre, <cg...@gmail.com> wrote:
> Hey Bob,
> Great to hear from you and thanks for volunteering. Between you and me,
> I've been considering forking Drill, moving it to the OWASP foundation, and
> integrating a lot of security-related stuff that either hasn't been
> accepted or I haven't submitted. I suspect this would help increase Drill's
> user base and hence get better features etc.
>
> What do you think?
> -- C
>
>
>
> > On May 15, 2020, at 6:31 PM, Bob Rudis <bo...@rud.is> wrote:
> >
> > I can carve out work-time to review PRs.
> >
> > -boB
> >
> > On Fri, May 15, 2020 at 11:25 AM Prabhakar Bhosaale
> > <bh...@gmail.com> wrote:
> >>
> >> HI Charles,
> >> I have never contributed to any open source community before this. Also
> I
> >> am not expert on JAVA but willing to contribute for sure. Please let me
> >> know in what capacity i can be helpful here.
> >>
> >> Also, I would like to know if there any efforts going on to identify
> >> primary support for Apache drill and what is its future in case there
> is no
> >> primary supporter? My organization is planning to build some tools using
> >> drill and this news will definitely impact the same. thx
> >>
> >> Regards
> >> Prabhakar
> >>
> >> On Fri, May 15, 2020 at 8:18 PM Charles Givre <cg...@gmail.com> wrote:
> >>
> >>> Dear Drill Users,
> >>> I hope everyone weathering the COVID storm and staying safe.
> >>>
> >>> As you may or may not be aware, I found out this week that MapR's
> >>> successor, HPE has for all intents and purposes ended its support for
> >>> Drill. Whilst they will be contributing minimal bug fixes, they will
> not
> >>> be adding any new functionality or new features. This leaves the open
> >>> source Drill without a primary backer. Under the Apache rules, to
> commit
> >>> code to the code base it must be reviewed and voted upon. While we have
> >>> committers, we do not currently have enough code reviewers to review
> new
> >>> commits.
> >>>
> >>> My question to you as a Drill user is whether or not Drill is offering
> >>> value to you and your organization. If it is, and you would like to
> see
> >>> Drill development continue, then we need additional volunteers to step
> up
> >>> and review pull requests.
> >>>
> >>> If you're interested in reviewing code for Drill, please let me know.
> >>>
> >>> Thank you for your continued support and stay safe!
> >>> -- Charles
>
>
Re: Drill's Future
Posted by Charles Givre <cg...@gmail.com>.
Hey Bob,
Great to hear from you and thanks for volunteering. Between you and me, I've been considering forking Drill, moving it to the OWASP foundation, and integrating a lot of security-related stuff that either hasn't been accepted or I haven't submitted. I suspect this would help increase Drill's user base and hence get better features etc.
What do you think?
-- C
> On May 15, 2020, at 6:31 PM, Bob Rudis <bo...@rud.is> wrote:
>
> I can carve out work-time to review PRs.
>
> -boB
>
> On Fri, May 15, 2020 at 11:25 AM Prabhakar Bhosaale
> <bh...@gmail.com> wrote:
>>
>> HI Charles,
>> I have never contributed to any open source community before this. Also I
>> am not expert on JAVA but willing to contribute for sure. Please let me
>> know in what capacity i can be helpful here.
>>
>> Also, I would like to know if there any efforts going on to identify
>> primary support for Apache drill and what is its future in case there is no
>> primary supporter? My organization is planning to build some tools using
>> drill and this news will definitely impact the same. thx
>>
>> Regards
>> Prabhakar
>>
>> On Fri, May 15, 2020 at 8:18 PM Charles Givre <cg...@gmail.com> wrote:
>>
>>> Dear Drill Users,
>>> I hope everyone weathering the COVID storm and staying safe.
>>>
>>> As you may or may not be aware, I found out this week that MapR's
>>> successor, HPE has for all intents and purposes ended its support for
>>> Drill. Whilst they will be contributing minimal bug fixes, they will not
>>> be adding any new functionality or new features. This leaves the open
>>> source Drill without a primary backer. Under the Apache rules, to commit
>>> code to the code base it must be reviewed and voted upon. While we have
>>> committers, we do not currently have enough code reviewers to review new
>>> commits.
>>>
>>> My question to you as a Drill user is whether or not Drill is offering
>>> value to you and your organization. If it is, and you would like to see
>>> Drill development continue, then we need additional volunteers to step up
>>> and review pull requests.
>>>
>>> If you're interested in reviewing code for Drill, please let me know.
>>>
>>> Thank you for your continued support and stay safe!
>>> -- Charles
Re: Drill's Future
Posted by Bob Rudis <bo...@rud.is>.
I can carve out work-time to review PRs.
-boB
On Fri, May 15, 2020 at 11:25 AM Prabhakar Bhosaale
<bh...@gmail.com> wrote:
>
> HI Charles,
> I have never contributed to any open source community before this. Also I
> am not expert on JAVA but willing to contribute for sure. Please let me
> know in what capacity i can be helpful here.
>
> Also, I would like to know if there any efforts going on to identify
> primary support for Apache drill and what is its future in case there is no
> primary supporter? My organization is planning to build some tools using
> drill and this news will definitely impact the same. thx
>
> Regards
> Prabhakar
>
> On Fri, May 15, 2020 at 8:18 PM Charles Givre <cg...@gmail.com> wrote:
>
> > Dear Drill Users,
> > I hope everyone weathering the COVID storm and staying safe.
> >
> > As you may or may not be aware, I found out this week that MapR's
> > successor, HPE has for all intents and purposes ended its support for
> > Drill. Whilst they will be contributing minimal bug fixes, they will not
> > be adding any new functionality or new features. This leaves the open
> > source Drill without a primary backer. Under the Apache rules, to commit
> > code to the code base it must be reviewed and voted upon. While we have
> > committers, we do not currently have enough code reviewers to review new
> > commits.
> >
> > My question to you as a Drill user is whether or not Drill is offering
> > value to you and your organization. If it is, and you would like to see
> > Drill development continue, then we need additional volunteers to step up
> > and review pull requests.
> >
> > If you're interested in reviewing code for Drill, please let me know.
> >
> > Thank you for your continued support and stay safe!
> > -- Charles
Re: Drill's Future
Posted by Prabhakar Bhosaale <bh...@gmail.com>.
HI Charles,
I have never contributed to any open source community before this. Also I
am not expert on JAVA but willing to contribute for sure. Please let me
know in what capacity i can be helpful here.
Also, I would like to know if there any efforts going on to identify
primary support for Apache drill and what is its future in case there is no
primary supporter? My organization is planning to build some tools using
drill and this news will definitely impact the same. thx
Regards
Prabhakar
On Fri, May 15, 2020 at 8:18 PM Charles Givre <cg...@gmail.com> wrote:
> Dear Drill Users,
> I hope everyone weathering the COVID storm and staying safe.
>
> As you may or may not be aware, I found out this week that MapR's
> successor, HPE has for all intents and purposes ended its support for
> Drill. Whilst they will be contributing minimal bug fixes, they will not
> be adding any new functionality or new features. This leaves the open
> source Drill without a primary backer. Under the Apache rules, to commit
> code to the code base it must be reviewed and voted upon. While we have
> committers, we do not currently have enough code reviewers to review new
> commits.
>
> My question to you as a Drill user is whether or not Drill is offering
> value to you and your organization. If it is, and you would like to see
> Drill development continue, then we need additional volunteers to step up
> and review pull requests.
>
> If you're interested in reviewing code for Drill, please let me know.
>
> Thank you for your continued support and stay safe!
> -- Charles