Moving Apache Lens project to Attic

[Amareshwari Sriramdasu]

Hi all,

After the PMC vote, and board approval, have created the ticket to move the
project to Attic. Here is the tracking ticket
https://issues.apache.org/jira/browse/ATTIC-186

Thanks
Amareshwari

[RESULT] [VOTE] Move Apache Lens and to attic

[Amareshwari Sriramdasu]

Thanks all for voting on this.

Here is the result

6 binding votes for : [+1] To move the project to attic
0 votes :  [0] No objection to move to attic.
0 votes : [-1] To NOT move the project to attic.

Vote passes. Will do the next steps.

Thanks
Amareshwari

On Wed, Jul 22, 2020 at 12:43 PM Raghavendra Singh
 wrote:

> +1
>
> Get Outlook for Android<https://aka.ms/ghei36>
>
> 
> From: Raju Bairishetti 
> Sent: Wednesday, July 22, 2020 5:09:12 AM
> To: dev 
> Subject: Re: [VOTE] Move Apache Lens and to attic
>
> +1 (binding)
>
> On Tue, 21 Jul 2020, 13:11 Puneet Gupta,  wrote:
>
> > +1 (binding)  to move the project to attic
> >
> > On Sat, 18 Jul, 2020, 10:39 am Jean-Baptiste Onofre, 
> > wrote:
> >
> > > +1 to move to attic
> > >
> > > Regards
> > > JB
> > >
> > > > Le 17 juil. 2020 à 10:41, Amareshwari Sriramdasu <
> > amareshw...@apache.org>
> > > a écrit :
> > > >
> > > > Hi Lens dev and PMC,
> > > >
> > > > As we are seeing no roadmap ahead and no interest to keep the project
> > > > active, as per the discussion on the email thread on dev and user
> list
> > > > <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail-archives.apache.org%2Fmod_mbox%2Flens-dev%2F202005.mbox%2F%253CCANOygOJTAA%253DHxH22E1JOYoqqpUTC-hb9s2seMdHi2i0wR2nvoA%2540mail.gmail.com%253Edata=02%7C01%7Craghavendra.singh%40inmobi.com%7C30ef534ff45142ffee1e08d82dcf4ecd%7C89359cf49e60409980c4775a0cfe27a7%7C0%7C1%7C637309715720773977sdata=X7XSxxll8ZkNlIqUFaqnZapVjbM3wIjQB316z4opOi0%3Dreserved=0
> > > >,
> > > > seeking
> > > > your vote to terminate the project Apache Lens, dissolve the PMC and
> > move
> > > > the project to attic. As per the process
> > > > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fattic.apache.org%2Fprocess.htmldata=02%7C01%7Craghavendra.singh%40inmobi.com%7C30ef534ff45142ffee1e08d82dcf4ecd%7C89359cf49e60409980c4775a0cfe27a7%7C0%7C1%7C637309715720783972sdata=ZGUPB3FPaaIKW%2BV7N1TwG6aWw7f3E8gU5hk2qcxf21A%3Dreserved=0>,
> it requires a PMC vote on the
> > > > public dev list, for the same.
> > > >
> > > > The vote will remain open till 24th July (leaving it for 1 week to
> get
> > > > enough votes). Do vote with your option as one of the below.
> > > >
> > > > [+1] To move the project to attic
> > > > [0] No objection to move to attic.
> > > > [-1] To NOT move the project to attic.
> > > >
> > > > Thanks
> > > > Amareshwari
> > >
> > >
> >
>

Re: [VOTE] Move Apache Lens and to attic

[Amareshwari Sriramdasu]

Here is my vote :

[+1] To move the project to attic (binding)

Thanks
Amareshwari

On Fri, Jul 17, 2020 at 2:11 PM Amareshwari Sriramdasu <
amareshw...@apache.org> wrote:

> Hi Lens dev and PMC,
>
> As we are seeing no roadmap ahead and no interest to keep the project
> active, as per the discussion on the email thread on dev and user list
> <http://mail-archives.apache.org/mod_mbox/lens-dev/202005.mbox/%3CCANOygOJTAA%3DHxH22E1JOYoqqpUTC-hb9s2seMdHi2i0wR2nvoA%40mail.gmail.com%3E>,
>  seeking
> your vote to terminate the project Apache Lens, dissolve the PMC and move
> the project to attic. As per the process
> <https://attic.apache.org/process.html>, it requires a PMC vote on the
> public dev list, for the same.
>
> The vote will remain open till 24th July (leaving it for 1 week to get
> enough votes). Do vote with your option as one of the below.
>
> [+1] To move the project to attic
> [0] No objection to move to attic.
> [-1] To NOT move the project to attic.
>
> Thanks
> Amareshwari
>
>

[VOTE] Move Apache Lens and to attic

[Amareshwari Sriramdasu]

Hi Lens dev and PMC,

As we are seeing no roadmap ahead and no interest to keep the project
active, as per the discussion on the email thread on dev and user list
,
seeking
your vote to terminate the project Apache Lens, dissolve the PMC and move
the project to attic. As per the process
, it requires a PMC vote on the
public dev list, for the same.

The vote will remain open till 24th July (leaving it for 1 week to get
enough votes). Do vote with your option as one of the below.

[+1] To move the project to attic
[0] No objection to move to attic.
[-1] To NOT move the project to attic.

Thanks
Amareshwari

Re: Lens RoadMap - Discussion

[Amareshwari Sriramdasu]

Hi,

Reminder to all, to respond to this thread with your thoughts/comments.

Thanks
Amareshwari

On Wed, May 13, 2020 at 9:57 AM Amareshwari Sriramdasu <
amareshw...@apache.org> wrote:

> Hi all,
>
> Hope you are all doing well.
>
> Seeing the activity and contribution for the last one year, seeking
> inputs/suggestions from you all on taking the project forward. Would like
> to know if any of you have any feature or roadmap suggestions and are
> willing to contribute for the same.
>
>
> Rajashekhar and others, are you still planning to do the changes proposed
> last time?
>
>
> If there aren't any suggestions forth coming, we may have to move the
>
> project to attic. As per https://attic.apache.org/process.html, mailing
> list will be closed down and jira project/source code would become
> read-only. That would mean that any existing users would have challenges in
> reaching out for community support.
>
> We will keep this thread open till 30th Jun, 2020, for hearing from you
> all.
>
> Thanks
> Amareshwari
>
> -- Forwarded message -
> From: amareshwarisr . 
> Date: Wed, Feb 12, 2020 at 10:29 AM
> Subject: Re: Updated invitation: Lens RoadMap - Discussion @ Sat Aug 24,
> 2019 11am - 12pm (IST) (dev@lens.apache.org)
> To: Rajashekhar Choukimath 
> Cc: Puneet Gupta , dev , <
> billbillson...@gmail.com>, Rajat Khandelwal ,
> Avadh Pandey , 
>
>
> Rajashekhar,
>
> Do let us know if you have update on this.
>
> Thanks
> Amareshwari
>
>
>
> On Fri, Nov 8, 2019 at 5:39 PM Rajashekhar Choukimath 
> wrote:
>
>> Hi Amareshwari,
>> We were supposed to start working on Lens Road Map, but till date we were
>> busy with *Azure Migrations + China Migrations* within the company. I
>> will start on the Road Map this month.
>>
>>
>> On Fri, Nov 8, 2019 at 11:12 AM amareshwarisr . 
>> wrote:
>>
>>> Rajashekhar,
>>>
>>> Are you planning to take up next steps on this?
>>>
>>> Thanks
>>>
>>> On Wed, Aug 28, 2019 at 4:31 PM amareshwarisr . 
>>> wrote:
>>>
>>>> Essentially, the ask is to separate metastore and query services into
>>>> two separate projects, so they can be build separately. Query service would
>>>> have dependency on metastore service.
>>>>
>>>> Since the adaption of current stack is limited, fine separate the
>>>> project into two sub projects which can help them evolve separately. We
>>>> iterated the same in the call as well, where three PMC members 
>>>> participated.
>>>> Shall call out a vote for the same. PMC do express you concerns or
>>>> comments on the vote.
>>>>
>>>> Thanks
>>>>
>>>>
>>>> On Wed, Aug 28, 2019 at 3:44 PM Rajashekhar Choukimath <
>>>> raju.n...@gmail.com> wrote:
>>>>
>>>>>
>>>>> *Phase 1:*To enable the business, we are not making changes in any of
>>>>> the projects, we only need smaller version of lens-server(with just much
>>>>> less features, as discussed in the doc) and we are calling that as
>>>>> clarity-query-builder(new module in clarity stack and it is not in lens).
>>>>>
>>>>> 1) we require only following projects
>>>>> -- lens-cube
>>>>> -- lens-api
>>>>> -- lens-server-api
>>>>> 2) from the Lens-driver-jdbc
>>>>> -- we require only JDBCDriver.rewrite() method
>>>>> 3) from lens-server
>>>>> -- we require the entire package -- org.apache.lens.server.metastore
>>>>>
>>>>> We will create our own server call it clarity-qurery-builder and have
>>>>> -- item 2 and 3 code copied
>>>>> -- for item 1, we will have maven dependencies.
>>>>>
>>>>>
>>>>> *Phase 2:*If we need to make any major feature changes in lens-cube
>>>>> like the way we added segmentations, in that case, we need to refactor the
>>>>> following projects(mainly interfaces):
>>>>>  -- lens-api
>>>>>  -- lens-server-api
>>>>>
>>>>> split the projects of lens into 2 build jobs
>>>>> 1) Build Job 1:
>>>>> -- Lens-cube + needed interfaces of lens-api and lens-server-api.
>>>>> 2) Build Job 2:
>>>>> -- All the remaining projects
>>>>> -- the above projects will have dependencies on the projects of Build
>>>>> Job 1.
>

Lens RoadMap - Discussion

[Amareshwari Sriramdasu]

Hi all,

Hope you are all doing well.

Seeing the activity and contribution for the last one year, seeking
inputs/suggestions from you all on taking the project forward. Would like
to know if any of you have any feature or roadmap suggestions and are
willing to contribute for the same.


Rajashekhar and others, are you still planning to do the changes proposed
last time?


If there aren't any suggestions forth coming, we may have to move the

project to attic. As per https://attic.apache.org/process.html, mailing
list will be closed down and jira project/source code would become
read-only. That would mean that any existing users would have challenges in
reaching out for community support.

We will keep this thread open till 30th Jun, 2020, for hearing from you all.

Thanks
Amareshwari

-- Forwarded message -
From: amareshwarisr . 
Date: Wed, Feb 12, 2020 at 10:29 AM
Subject: Re: Updated invitation: Lens RoadMap - Discussion @ Sat Aug 24,
2019 11am - 12pm (IST) (dev@lens.apache.org)
To: Rajashekhar Choukimath 
Cc: Puneet Gupta , dev , <
billbillson...@gmail.com>, Rajat Khandelwal , Avadh
Pandey , 


Rajashekhar,

Do let us know if you have update on this.

Thanks
Amareshwari



On Fri, Nov 8, 2019 at 5:39 PM Rajashekhar Choukimath 
wrote:

> Hi Amareshwari,
> We were supposed to start working on Lens Road Map, but till date we were
> busy with *Azure Migrations + China Migrations* within the company. I
> will start on the Road Map this month.
>
>
> On Fri, Nov 8, 2019 at 11:12 AM amareshwarisr . 
> wrote:
>
>> Rajashekhar,
>>
>> Are you planning to take up next steps on this?
>>
>> Thanks
>>
>> On Wed, Aug 28, 2019 at 4:31 PM amareshwarisr . 
>> wrote:
>>
>>> Essentially, the ask is to separate metastore and query services into
>>> two separate projects, so they can be build separately. Query service would
>>> have dependency on metastore service.
>>>
>>> Since the adaption of current stack is limited, fine separate the
>>> project into two sub projects which can help them evolve separately. We
>>> iterated the same in the call as well, where three PMC members participated.
>>> Shall call out a vote for the same. PMC do express you concerns or
>>> comments on the vote.
>>>
>>> Thanks
>>>
>>>
>>> On Wed, Aug 28, 2019 at 3:44 PM Rajashekhar Choukimath <
>>> raju.n...@gmail.com> wrote:
>>>

 *Phase 1:*To enable the business, we are not making changes in any of
 the projects, we only need smaller version of lens-server(with just much
 less features, as discussed in the doc) and we are calling that as
 clarity-query-builder(new module in clarity stack and it is not in lens).

 1) we require only following projects
 -- lens-cube
 -- lens-api
 -- lens-server-api
 2) from the Lens-driver-jdbc
 -- we require only JDBCDriver.rewrite() method
 3) from lens-server
 -- we require the entire package -- org.apache.lens.server.metastore

 We will create our own server call it clarity-qurery-builder and have
 -- item 2 and 3 code copied
 -- for item 1, we will have maven dependencies.


 *Phase 2:*If we need to make any major feature changes in lens-cube
 like the way we added segmentations, in that case, we need to refactor the
 following projects(mainly interfaces):
  -- lens-api
  -- lens-server-api

 split the projects of lens into 2 build jobs
 1) Build Job 1:
 -- Lens-cube + needed interfaces of lens-api and lens-server-api.
 2) Build Job 2:
 -- All the remaining projects
 -- the above projects will have dependencies on the projects of Build
 Job 1.



 On Wed, Aug 28, 2019 at 2:20 PM Rajashekhar Choukimath <
 raju.n...@gmail.com> wrote:

> I will send it today
>
> On Wed 28 Aug, 2019, 11:52 AM Puneet Gupta, 
> wrote:
>
>> Hi Rajashekhar,
>>
>> Can u please share the minutes of meeting .
>>
>> Thanks,
>> Puneet
>>
>> On Fri, 23 Aug, 2019, 5:10 PM ,  wrote:
>>
>>> *This event has been changed.*
>>> more details »
>>> 
>>> Lens RoadMap - Discussion
>>>
>>> *When*
>>> Sat Aug 24, 2019 11am – 12pm India Standard Time - Kolkata
>>> *Video call*
>>> *Changed: *Join video call
>>> 
>>> *Calendar*
>>> dev@lens.apache.org
>>> *Who*
>>> •
>>> raju.n...@gmail.com - organizer
>>> •
>>> amareshw...@gmail.com
>>> •
>>> billbillson...@gmail.com
>>> •
>>> rajatgupt...@gmail.com
>>> •
>>> Ankit Kailaswar
>>> •
>>> dev@lens.apache.org
>>> •
>>> Avadh Pandey
>>> •
>>> 

Report for May, 2020

[Amareshwari Sriramdasu]

Hi,

I have added report for May, 2020 here :
https://cwiki.apache.org/confluence/display/LENS/May%2C+2020

Mainly calling out


*There has been no activity on the project for the past quarter. Though we
have discussed **roadmap and suggestion in the earlier quarter, there is no
work done in past quarter for the same. **We will reinitiate the thread on
roadmap, and see if we can do any changes or improvements **to the project.
If there is no clear roadmap, we will call for retiring the project next
quarter. *


Let me know you comments.


Thanks

Amareshwari

Report for Feb, 2020

[Amareshwari Sriramdasu]

Hi Lens Dev,

Have updated report for Feb month here -
https://cwiki.apache.org/confluence/display/LENS/February%2C+2020. Please
share your comments.

Thanks

Report for November, 2019

[Amareshwari Sriramdasu]

Hi,

Have put up draft for Nov,2019 report
https://cwiki.apache.org/confluence/display/LENS/November%2C+2019. Please
review and let me know your comments. Shall submit to board@ tomorrow.

Thanks
Amareshwari

[RESULT][VOTE] Break up lens code into two sub projects

[Amareshwari Sriramdasu]

Concluding the vote with six binding +1 votes (out of seven +1 votes) and
no 0 or no -1 votes.

Thanks
Amareshwari


On Fri, Sep 13, 2019 at 1:08 PM Raghavendra Singh
 wrote:

> +1
>
> On Fri, Sep 13, 2019 at 11:44 AM Srikanth Sundarrajan  >
> wrote:
>
> > +1 (binding)
> >
> > Regards
> > Srikanth Sundarrajan
> > 
> > From: rajitha r 
> > Sent: Friday, September 13, 2019 10:22 AM
> > To: dev 
> > Subject: Re: [VOTE] Break up lens code into two sub projects
> >
> > +1
> >
> > On Fri, Sep 13, 2019 at 9:39 AM Raju Bairishetti 
> > wrote:
> >
> > > +1
> > >
> > > On Thu, 12 Sep 2019, 11:53 Rajat Khandelwal, 
> > > wrote:
> > >
> > > > +1
> > > >
> > > >
> > > > Rajat Khandelwal
> > > >
> > > > On Wed, 28 Aug, 2019, 17:18 Puneet Gupta, 
> > > wrote:
> > > >
> > > > > +1 from me.
> > > > >
> > > > > On Wed, 28 Aug, 2019, 4:42 PM Amareshwari Sriramdasu, <
> > > > > amareshw...@apache.org> wrote:
> > > > >
> > > > > > +1 from my side.
> > > > > >
> > > > > > On Wed, Aug 28, 2019 at 4:41 PM Amareshwari Sriramdasu <
> > > > > > amareshw...@apache.org> wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > After the discussion on Lens roadmap thread, calling this vote
> to
> > > get
> > > > > > > consensus from developers of Lens for the proposal.
> > > > > > >
> > > > > > > Lens codebase can be broken down into two sub projects : one
> for
> > > > > > metastore
> > > > > > > and other for query. Query service can have dependency on
> > metastore
> > > > > > > service. This shall help these subprojects evolve separately.
> > > > > > >
> > > > > > > To achieve the same we shall do 2.8 release from current master
> > > with
> > > > > all
> > > > > > > changes for current stack. Move master to 3.0 with refactored
> > code
> > > of
> > > > > > > subprojects, which can be build separately.
> > > > > > >
> > > > > > > Lens developers, do cast your vote for the above
> > > > > > >
> > > > > > > [+1] if you approve
> > > > > > > [0] if no opinion
> > > > > > > [-] if you are not approving, with reasons.
> > > > > > >
> > > > > > > Do express your comments as well.
> > > > > > >
> > > > > > > Thanks
> > > > > > > Amareshwari
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> > Regards,
> >
> > Rajitha.R
> >
>
> --
> _
> The
> information contained in this communication is intended solely for the use
> of the individual or entity to whom it is addressed and others authorized
> to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in
> reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete
> transmission
> of the information contained in this communication nor for any delay in
> its
> receipt.
>

Re: [VOTE] Break up lens code into two sub projects

[Amareshwari Sriramdasu]

+1 from my side.

On Wed, Aug 28, 2019 at 4:41 PM Amareshwari Sriramdasu <
amareshw...@apache.org> wrote:

> Hi,
>
> After the discussion on Lens roadmap thread, calling this vote to get
> consensus from developers of Lens for the proposal.
>
> Lens codebase can be broken down into two sub projects : one for metastore
> and other for query. Query service can have dependency on metastore
> service. This shall help these subprojects evolve separately.
>
> To achieve the same we shall do 2.8 release from current master with all
> changes for current stack. Move master to 3.0 with refactored code of
> subprojects, which can be build separately.
>
> Lens developers, do cast your vote for the above
>
> [+1] if you approve
> [0] if no opinion
> [-] if you are not approving, with reasons.
>
> Do express your comments as well.
>
> Thanks
> Amareshwari
>
>
>

[VOTE] Break up lens code into two sub projects

[Amareshwari Sriramdasu]

Hi,

After the discussion on Lens roadmap thread, calling this vote to get
consensus from developers of Lens for the proposal.

Lens codebase can be broken down into two sub projects : one for metastore
and other for query. Query service can have dependency on metastore
service. This shall help these subprojects evolve separately.

To achieve the same we shall do 2.8 release from current master with all
changes for current stack. Move master to 3.0 with refactored code of
subprojects, which can be build separately.

Lens developers, do cast your vote for the above

[+1] if you approve
[0] if no opinion
[-] if you are not approving, with reasons.

Do express your comments as well.

Thanks
Amareshwari

Release 2.8

[Amareshwari Sriramdasu]

Hello Lens dev,

We have not a done a release for a huge time. As some changes (features/
bug fixes) went into the code base, any one interested to volunteer for the
release 2.8?

Thanks
Amareshwari

June 2019

[Amareshwari Sriramdasu]

Hi all,

On the last month's report we got feedback to resubmit the report, I have
put together the draft here :
https://cwiki.apache.org/confluence/display/LENS/June%2C+2019. Do review
and let me know your comments. Will be submitting report EOD.

Thanks
Amareshwari

Report for May, 2019

[Amareshwari Sriramdasu]

Hi,

Have put up report at
https://cwiki.apache.org/confluence/display/LENS/May%2C+2019. Please review
and provide comments.

Thanks

Report Feb,2019

[Amareshwari Sriramdasu]

Hi,

Have updated the report for the month Feb,2019 at
https://cwiki.apache.org/confluence/display/LENS/February%2C2019. Do review
and let me know your comments.

Thanks

Re: [VOTE] Lens - Code Commit using Pull Requests

[Amareshwari Sriramdasu]

Rajitha,

Can we make sure emails for the new pull requests and the comments on pull
requests come to dev@lens.apache.org as part of this change?

Thanks

On Sun, Jan 20, 2019 at 10:29 AM Amareshwari Sriramdasu <
amareshw...@apache.org> wrote:

> +1
>
> On Sat, Jan 19, 2019 at 2:54 PM Rajat Khandelwal 
> wrote:
>
>> +1
>>
>

Re: [VOTE] Lens - Code Commit using Pull Requests

[Amareshwari Sriramdasu]

+1

On Sat, Jan 19, 2019 at 2:54 PM Rajat Khandelwal  wrote:

> +1
>

Re: [DISCUSS] Lens Migration from Git-wip to Gitbox

[Amareshwari Sriramdasu]

+1

On Mon, Jan 7, 2019 at 10:59 AM Rajitha R  wrote:

> Hi All,
>
> ASF infra has decided to move all git repositories from
> git-wip-us.apache.org URL to gitbox.apache.org with the former service
> being decommisioned.
>
> This mail is to get a consensus from all of you regarding the migration.
>
> Please vote within next 24 hours, which can help me in raising the Infra
> jira before the published timeline.
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>
> +1 from my side for the activity.
>
> For folks looking for more details, please refer this link :
>
> https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories
>
> Regards,
> Rajitha.R
>

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

[Amareshwari Sriramdasu]

Rajitha,

Can you please help with this?

Thanks

On Thu, Jan 3, 2019 at 6:49 PM Apache Infrastructure Team <
infrastruct...@apache.org> wrote:

> Hello, lens folks.
> As stated earlier in 2018, all git repositories must be migrated from
> the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> is being decommissioned. Your project is receiving this email because
> you still have repositories on git-wip-us that needs to be migrated.
>
> The following repositories on git-wip-us belong to your project:
>  - lens.git
>
>
> We are now entering the mandated (coordinated) move stage of the roadmap,
> and you are asked to please coordinate migration with the Apache
> Infrastructure Team before February 7th. All repositories not migrated
> on February 7th will be mass migrated without warning, and we'd appreciate
> it if we could work together to avoid a big mess that day :-).
>
> Moving to gitbox means you will get full write access on GitHub as well,
> and be able to close/merge pull requests and much more.
>
> To have your repositories moved, please follow these steps:
>
> - Ensure consensus on the move (a link to a lists.apache.org thread will
>   suffice for us as evidence).
> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
>
> Your migration should only take a few minutes. If you wish to migrate
> at a specific time of day or date, please do let us know in the ticket.
>
> As always, we appreciate your understanding and patience as we move
> things around and work to provide better services and features for
> the Apache Family.
>
> Should you wish to contact us with feedback or questions, please do so
> at: us...@infra.apache.org.
>
>
> With regards,
> Apache Infrastructure
>
>

Report for November, 2018

[Amareshwari Sriramdasu]

Hi,

Have updated draft report for November,2018 at
https://cwiki.apache.org/confluence/display/LENS/November%2C2018. Please
review and let me know your comments.

Thanks
Amareshwari

Report for August, 2018

[Amareshwari Sriramdasu]

Hi,

Have put up draft for August,2018 report
https://cwiki.apache.org/confluence/display/LENS/August%2C+2018.

Please review and let me know your comments.

Thanks
Amareshwari

Fwd: checksum file Release Distribution Policy

[Amareshwari Sriramdasu]

-- Forwarded message --
From: "Henk P. Penning" 
Date: Mar 5, 2018 4:48 PM
Subject: checksum file Release Distribution Policy
To: 
Cc:

Hi Pmcs,

   The Release Distribution Policy[1] changed regarding checksum files.
   See under "Cryptographic Signatures and Checksums Requirements" [2].

 MD5-file == a .md5 file
 SHA-file == a .sha1, sha256 or .sha512 file

  Old policy :

 -- MUST provide a MD5-file
 -- SHOULD provide a SHA-file [SHA-512 recommended]

  New policy :

 -- MUST provide a SHA- or MD5-file
 -- SHOULD provide a SHA-file
 -- SHOULD NOT provide a MD5-file

 Providing MD5 checksum files is now discouraged for new releases,
 but still allowed for past releases.

  Why this change :

 -- MD5 is broken for many purposes ; we should move away from it.
https://en.wikipedia.org/wiki/MD5#Overview_of_security_issues

  Impact for PMCs :

 -- for new releases :
-- please do provide a SHA-file (one or more, if you like)
-- do NOT provide a MD5-file

 -- for past releases :
-- you are not required to change anything
-- for artifacts accompanied by a SHA-file /and/ a MD5-file,
   it would be nice if you removed the MD5-file

 -- if, at the moment, you provide MD5-files,
please adjust your release tooling.

  Please mail me (he...@apache.org) if you have any questions etc.

  FYI :

   Many projects are not (entirely, strictly) checksum file compliant.
   For an overview/inventory (by project) see :

https://checker.apache.org/dist/unsummed.html

  At the moment :

 -- no checksum : 176 packages in 28 projects ; non-compliant
 -- only MD5: 495 packages in 44 projects ; update tooling
 -- only SHA: 135 packages in 13 projects ; now comliant

   In many cases, only a few (among many) checksum file are missing ;
   you may want to fix that.

   [1] http://www.apache.org/dev/release-distribution
   [2] http://www.apache.org/dev/release-distribution#sigs-and-sums

  Thanks, groeten,

  Henk Penning -- apache.org infrastructure ; dist & mirrors.

   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL

F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

Report for Feb, 2018

[Amareshwari Sriramdasu]

Hi,

Have put the report for Feb,2018 here -
https://cwiki.apache.org/confluence/display/LENS/Feb%2C2018

Please review and let me know your comments.

Thanks

Re: [ANNOUNCE] New Apache Lens committer : Rajitha R

[Amareshwari Sriramdasu]

Congratulations Rajitha !

On Fri, Feb 9, 2018 at 10:58 AM, Puneet Gupta 
wrote:

> The PMC for Apache Lens has asked Rajitha to become Lens Committer. We are
> pleased to announce that she has accepted.
>
> Being a committer enables access to commit to the source repositories
> and binding
> votes for code reviews.
>
> Join me in Congratulating Rajitha!
>
> Congratulations Rajitha! Looking forward for more of your contributions in
> Apache Lens.
>
> Thanks
> Puneet
>

Re: [ANNOUNCE] Apache Lens 2.7.1 released

[Amareshwari Sriramdasu]

Great work Raju!

Your perseverance made this release possible. Thank you so much for
volunteering and completing this release.

Thanks
Amareshwari

On Tue, Feb 6, 2018 at 11:48 AM, Raju Bairishetti  wrote:

> Hi All,
>
> The Apache Lens team is proud to announce the release of Apache Lens
> 2.7.1.
>
> This release includes features like cube segmentation, unioning data across
> facts, retry on transient errors, support for source data completion
> checking and many more bug fixes and improvements.
>
> Apache Lens provides a Unified Analytics interface. Lens aims to cut the
> Data Analytics silos by providing a single view of data across multiple
> tiered data stores and optimal execution environment for the analytical
> query. It seamlessly integrates Hadoop with traditional data warehouses to
> appear like one.
>
>
> More details on Apache Lens can be found at
> http://lens.apache.org/
>
> Getting started available at
> http://lens.apache.org/lenshome/quick-start.html
>
> For quick ramp-up, you can watch a video at
> http://cwiki.apache.org/confluence/display/LENS/2015/
> 07/13/20+Minute+video+demo+of+Apache+Lens+through+examples
>
> How to for Contributors available at
> http://lens.apache.org/developer/contribute.html
>
> The release artifacts are downloadable from
> http://lens.apache.org/releases/download.html
>
> Maven jar artifacts have also been made available on
> https://repository.apache.org/content/repositories/releases/
> org/apache/lens
>
> Release notes available at
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12315923=12336851
>
> We would like to thank all the contributors who made this release possible.
>
>
> Thanks,
> Raju Bairishetti
>

Re: [VOTE] Release of Apache Lens 2.7.1

[Amareshwari Sriramdasu]

+1

+ Verified signatures.
+ Verified checksums.
+ License looks fine. Minor issue in NOTICE file.
+ No binary files in source zip
+ mvn clean package -DskipTests passes

Few points to take care, but not blocking the release.
* NOTICE file contains the year as 2014-2016 : Needs to be updated to 21018.
* Version number in 'contrib/clients/python/lens/client/__init__.py' is
2.6.1, same with setup.py - Not sure if it needs to be updated for project
version to work correctly.

Thanks
Amareshwari

On Wed, Jan 31, 2018 at 2:21 PM, Rajat Khandelwal <
rajat.khandel...@inmobi.com> wrote:

> +1
>
> On Wed, Jan 31, 2018 at 1:50 PM, Siddharth Raj Jain <
> siddharth@inmobi.com> wrote:
>
> > +1
> >
> > On Wed, Jan 24, 2018 at 12:33 PM, Raju Bairishetti 
> > wrote:
> >
> > > Hi everyone,
> > >
> > > I propose the following RC to be released as official Apache Lens
> > 2.7.1
> > > release.
> > >
> > > The commit id is 865d20267e8128134bb981f1db9dab9108661061
> <091086%2061061>:
> > > http://git-wip-us.apache.org/repos/asf/lens/commit/865d2026
> > >
> > > This corresponds to the tag: apache-lens-2.7.1:
> > > https://git-wip-us.apache.org/repos/asf?p=lens.git;a=tag;h=
> > > refs/tags/apache-lens-2.7.1
> > >
> > > Release archives (tar.gz/zip) signature and checksums are here:
> > > https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.7.1-rc0/
> > >
> > > You can find the KEYS file here:
> > > https://dist.apache.org/repos/dist/dev/lens/KEYS
> > >
> > > The release candidate consists of the following source distribution
> > archive
> > > apache-lens-2.7.1-source-release.zip:
> > > https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.7.
> > > 1-rc0/apache-lens-2.7.1-source-release.zip
> > >
> > > In addition, the following supplementary binary distributions are
> > provided
> > > for user convenience at the same location: apache-lens-2.7.1-bin.tar.gz
> > > https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.7.
> > > 1-rc0/apache-lens-2.7.1-bin.tar.gz
> > >
> > > the licensing of bundled bits in the archives are documented at
> > > https://cwiki.apache.org/confluence/display/LENS/
> > Licensing+in+Apache+Lens
> > >
> > > Nexus staging url:
> > > https://repository.apache.org/content/repositories/orgapachelens-1012
> > >
> > > Release notes available at
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12315923=12336851
> > >
> > > Vote will be open for at least 72 hours
> > >
> > > [ ] +1 approve
> > > [ ]  0  no opinion
> > > [ ]  -1 disapprove (and reason why)
> > >
> > > +1 from my side for the release.
> > >
> > > For folks not familiar with vetting a release, please refer to
> > >
> > > http://incubator.apache.org/guides/releasemanagement.html#check-list
> > >
> > > --
> > > Thanks,
> > > Raju Bairishetti,
> > > www.lazada.com
> > >
> >
> > --
> > _
> > The information contained in this communication is intended solely for
> the
> > use of the individual or entity to whom it is addressed and others
> > authorized to receive it. It may contain confidential or legally
> privileged
> > information. If you are not the intended recipient you are hereby
> notified
> > that any disclosure, copying, distribution or taking any action in
> reliance
> > on the contents of this information is strictly prohibited and may be
> > unlawful. If you have received this communication in error, please notify
> > us immediately by responding to this email and then delete it from your
> > system. The firm is neither liable for the proper and complete
> transmission
> > of the information contained in this communication nor for any delay in
> its
> > receipt.
> >
>
>
>
> --
> Rajat Khandelwal
> Tech Lead
>
> --
> _
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.
>

Report for November,2017

[Amareshwari Sriramdasu]

Hi,

Have put November, 2017 report here -
https://cwiki.apache.org/confluence/display/LENS/November%2C2017.

Please review and let me know your comments.

Thanks
Amareshwari

Volunteers for 2.7 release

[Amareshwari Sriramdasu]

Hi,

Now that we have major features like fact to fact union and cube
segmentation checked in, any volunteers for managing the release?

Thanks

Report for the month of February

[Amareshwari Sriramdasu]

Hello Lens contributors,

Have put up the report for the month here -
https://cwiki.apache.org/confluence/display/LENS/February%2C2017. Please
review and post your comments.

I see this quarter has the least engagement wrt mailing lists, jira
activity and commits. More details on putting this up in the report will
help.

---
## JIRA activity:

 - 15 JIRA tickets created in the last 3 months
 - 16 JIRA tickets closed/resolved in the last 3 months
---
## Mailing list activity:

 - dev@lens.apache.org:
- 401 emails sent to list (2402 in previous quarter)

 - u...@lens.apache.org:
- 2 emails sent to list (150 in previous quarter)
---

Thanks
Amareshwari

November 2016 report

[Amareshwari Sriramdasu]

Hello Lens dev,

Have put up report for November month at
https://cwiki.apache.org/confluence/display/LENS/November%2C2016.

Please review and let me know your comments.

Will post the report to board EOD.

Thanks
Amareshwari

Fwd: [VOTE] Release of Apache Lens 2.6.1

[Amareshwari Sriramdasu]

+1 to release the candidate. But found a couple of issues with release
which are noted down.

Verified the following :
+ Jars in Nexus repo  : Good.
+ Signatures : Good
+ Checksums : Good
+ No unexpected binaries found in the source release.
+ NOTICE is good.
+ Building from source : Successful
- LICENSE issues : found an issue with one of the files
: ./lens-ui/app/dispatcher/AppDispatcher.js
The file is having copyright from Facebook and text says the license is BSD
style which is in root directory of the source. But I don't see any
corresponding license in root directory of the source. Seems the file is
added in 2.5 release itself, but we need to put its corresponding license
to top level LICENSE file. I'm fine fixing it in next release.
- Ran examples from binary distribution : Seeing all cube queries are
failing. Not sure if the issue is only with examples.



Successful queries 14 out of 151queries

Total time for running examples(in millis) :39462

---

Thanks
Amareshwari

On Tue, Sep 27, 2016 at 7:43 PM, Puneet Gupta 
wrote:

> Hi everyone,
>
> I propose the following RC to be released as official Apache Lens 2.6.1
> release.
>
> The commit id is 7224d832de56ac7a22a06bb285808cfac33f32f2:
> http://git-wip-us.apache.org/repos/asf/lens/commit/7224d832d
>
> This corresponds to the tag: apache-lens-2.6.1:
> https://git-wip-us.apache.org/repos/asf?p=lens.git;a=tag;h=r
> efs/tags/apache-lens-2.6.1
>
> Release archives (tar.gz/.zip), signature, and checksums are here:
> https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.6.1-rc0/
>
> You can find the KEYS file here:
> https://dist.apache.org/repos/dist/release/lens/KEYS
>
> The release candidate consists of the following source distribution archive
> apache-lens-2.6.1-source-release.zip:
> https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.6.
> 1-rc0/apache-lens-2.6.1-source-release.zip
>
> In addition, the following supplementary binary distributions are provided
> for user convenience at the same location:apache-lens-2.6.1-bin.tar.gz:
> https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.6.
> 1-rc0/apache-lens-2.6.1-bin.tar.gz
>
> The licensing of bundled bits in the archives are documented at
> https://cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens
>
> Nexus staging url:
> https://repository.apache.org/content/repositories/orgapachelens-1010/
>
> Release notes available at
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12315923=12333846
>
>
> Vote will be open for at least 72 hours
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>
> +1 from my side for the release.
>
> For folks not familiar with vetting a release, please refer to
>
> http://incubator.apache.org/guides/releasemanagement.html#check-list
>

[ANNOUNCE] New Apache Lens PMC member : Puneet Gupta

[Amareshwari Sriramdasu]

The Apache Lens PMC has asked Puneet Gupta to join Lens PMC. We are pleased
to announce that he has accepted.

Being a PMC member enables Puneet to guide the direction of the project.

Join me in Congratulating Puneet !

Congratulations, Puneet! Looking forward for more of your contributions in
Apache Lens.

Thanks

Report - August, 2016

[Amareshwari Sriramdasu]

Hi all,

I have put the project report to be submitted for August at
https://cwiki.apache.org/confluence/display/LENS/August%2C2016.

Please review and let me know your comments.

Thanks
Amareshwari

[ANNOUNCE] New Apache Lens PMC member : Deepak Barr

[Amareshwari Sriramdasu]

The Apache Lens PMC has asked Deepak Barr to join Lens PMC. We are pleased
to announce that he has accepted.

Being a PMC member enables Deepak to guide the direction of the project.

Join me in Congratulating Deepak !

Congratulations, Deepak! Looking forward for more of your contributions in
Apache Lens.

Thanks

[ANNOUNCE] New Apache Lens committer : Archana H

[Amareshwari Sriramdasu]

The Apache Lens PMC has asked Archana H to become Lens committer. We are
pleased to announce that she has accepted.

Being a committer enables access to commit to the source repositories
and binding
votes for code reviews.

Join me in Congratulating Archana !

Congratulations, Archana! Looking forward for more of your contributions in
Apache Lens.

Thanks

[ANNOUNCE] New Apache Lens committer : Puneet Gupta

[Amareshwari Sriramdasu]

The PMC for Apache Lens has asked Puneet to become Lens Committer. We are
pleased to announce that he has accepted.

Being a committer enables access to commit to the source repositories
and binding
votes for code reviews.

Join me in Congratulating Puneet!

Congratulations Puneet! Looking forward for more of your contributions in
Apache Lens.

Thanks
Amareshwari

February report

[Amareshwari Sriramdasu]

Hi all,

I have drafted February report at
https://cwiki.apache.org/confluence/display/LENS/February%2C2016.

Let me know your comments. Will update the report Monday, 5pm IST.

Thanks
Amareshwari

November report

[Amareshwari Sriramdasu]

Hi all,

I have put November report for the project -
https://cwiki.apache.org/confluence/display/LENS/November%2C2015.

Please review and let me know if I have missed anything.

Thanks
Amareshwari

[REPORT] Apache Lens

[Amareshwari Sriramdasu]

Apache Lens report for September, 2015

## Description:
Apache Lens is a platform that enables multi-dimensional queries in a
  unified way over datasets stored in multiple warehouses. Lens integrates
  Apache Hive with other data warehouses by tiering them together to form
  logical data cubes.

## Project Activity:
 - The project is actively working on stabilizing user errors seen from
accessing the api.
 - New execution driver for Elastic search has been added.
 - Feature with respect to throttling query submission has been completed.
 - Logging in the project has been moved from log4j to slf4j and logback.
 - New improved web client is being under development.

## Project Activity with respect to TLP move:
 - Apache Lens graduated to TLP from incubator on 2015-08-19.
 - The project infrastructure move from Incubator to TLP completed.
 - Project has made first TLP release.
 - Apache Blog announcing Lens as TLP went Live on 2015-08-26.

## Issues for the board:
 - There are no issues requiring board attention at this time

## LDAP committee group/Committership changes:
 - Currently 16 committers and 16 LDAP committee group members.
 - New committers:
- Raju Bairishetti was added as a committer on July 18 2015
- Yash Sharma was added as a committer on July 18  2015

## Community:
 - 59 subscribers on dev list (+8 from last report)
 - 52 subscribes on user list (+12 from last report)
 - 27 subscribers on commits list (+5 from last report)

## Mailing list activity
 - 1040 mails on dev@lens
 - 42 mails on user@lens
 - 135 mails on commits@lens

## JIRA activity:
 - 58 issues created during August, 2015.
 - 57 issues resolved during August, 2015.

## Releases:
 - 2.3.0-beta released on 2015-08-28
 - 2.2.0-beta-incubating released on 2015-07-17.


Thanks
Amareshwari

September report

[Amareshwari Sriramdasu]

Hello all,

I have put the report for the month of september at
https://cwiki.apache.org/confluence/display/LENS/September+Report.

Please review and let me know your comments and if any thing needs to be
added or removed.

Please share your feedback. I will send the report to board tomorrow 5pm
IST.

Thanks
Amareshwari

Going as TLP !

[Amareshwari Sriramdasu]

Hello all,

All the following graduation tasks are finished :

- Almost all the infrastructure setup is done.
- The doc on website updated to be TLP.
- The status on incubator site updated to TLP.

I would ask everyone to go through
http://incubator.apache.org/guides/graduation.html#life-after-graduation to
see if we missed any.

Pending tasks :
- Review board update to new repo and mailing list (
https://issues.apache.org/jira/browse/INFRA-10161)
- Do release as TLP (is in-progress)

Members of the new PMC need to go through following, if not already done :

Review appropriate documentation:

 - Apache PMC Guide http://www.apache.org/dev/pmc.html

 - Related documentation http://www.apache.org/dev/#pmc

and please see
http://incubator.apache.org/guides/graduation.html#new-responsibilities

Wishing good luck to all the PMC, contributors and the project going
forward.

Thanks

Amareshwari