Re: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc1

2022-06-15 Thread shimin an
+1 From: Hezheng Yin Date: Thursday, June 16, 2022 at 11:35 To: dev@devlake.apache.org Subject: Re: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc1 +1 On Tue, Jun 14, 2022 at 6:59 PM Kaiyun Zhang wrote: > +1 > > Thanks everybody. > > > > > 2022年6月14日 下午5:28,Klesh Wong 写道: > > > > +

?????? [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc1

2022-06-15 Thread ????????
+1 --  -- ??: "dev" https://dist.apache.org/re

Re: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc1

2022-06-15 Thread Hezheng Yin
+1 On Tue, Jun 14, 2022 at 6:59 PM Kaiyun Zhang wrote: > +1 > > Thanks everybody. > > > > > 2022年6月14日 下午5:28,Klesh Wong 写道: > > > > +1 (binding) > > > > I checked these items: > > - Download links are valid. > > - Checksums and signatures. > > - LICENSE/NOTICE/DISCLAIMER files exist > > - N

Re: [discuss] team entity design => table name

2022-06-15 Thread Klesh Wong
I see, make sense to me. I would like to use `user` as `unified identity` as well, as I said, we picked `person` over `user` because it is ambiguous, it can be used to refer `unified identity`, or `account` on some platforms, or whoever using Apache DevLake depends on the context. I will tal

Re: [discuss] team entity design => table name

2022-06-15 Thread Jinglei Ren
OK, if `user` and `account` have been exchanged, there is surely no reason to go back. But why did you need `person`? Now `user` is the “person” you referred to, right? If so, that’s totally fine. With that said, let’s clarify the root cause for the mess. Otherwise, more mess will show up in t

Re: [discuss] team entity design => table name

2022-06-15 Thread Klesh Wong
I see, yeah, we all agreed that it was better to keep the `users` as it was, and add another entity to represent `unified identity` couple days back. But it have caused mess during multiple discussions, many of us can't even express himself including myself. so we gave up and agreed that it i

Re: [discuss] team entity design

2022-06-15 Thread Kaiyun Zhang
Hi team, From a product point of view, there might be 3 possible user journeys. User Journey 1 1. User downloads a CSV file that contains all the data from the accounts table, except with an extra field named person_id 2. User goes through each record, makes sure the person_ids were co

Re: [discuss] team entity design => table name

2022-06-15 Thread Jinglei Ren
The bad smell comes from “a living thing” which the system should not model. We can follow most of your model but (1) merge `person` and `user` in your model and name it `account`; (2) rename the `account` in your model to `user`. The reason for (2) is that, as mentioned in https://github.com/a