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

Let's bare with existing terms a little bit longer, I don't buy your definition of `account` just yet. Here is why: 1. `person`: a Living Thing (Human, Dog, or Alien) 2. `user`: a `person` who is using Apache DevLake to collect and analyze DevOps data 3. `platform`: a website(github.com/gitla

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

I am changing the email title to branch out and avoid distracting your main thread. Right, this is not a big deal, so let’s conclude quickly. You know, ambiguity can only be resolved by defining the concepts. Otherwise, `persons` do not help either. What I proposed was to just define `accounts`

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

+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 > - No unexpected binary files > - All source files have ASF headers > > On 6/13/22 23:48

Re: [discuss] team entity design

Hi Klesh, Thanks for initiating the discussion! On the *first topic* of how to find a developer's commits when they commit with multiple emails/names, I looked up GitHub's documentation

Re: [discuss] team entity design

I'm ok with any name as long as @Julien @Keon @Hezheng are ok with it. As of `table.accounts`, I don't understand, how can it represents  `unified users` while it representing multiple accounts? For example, we are collecting `commits` data by `gitextractor`, in order to associate a specific

Re: [discuss] team entity design

Just a comment: `people` should better be `persons` to make it consistent with other plural names as well as `person_teams`, etc. I see the reasons for this name, but I am still against `people` or `persons` because our system should not model natural persons at all. In some sense, it cannot be

Re: Podling Website check

Just in case of any confusion, Louis’ latest question and comment are below. His previous email layout is strange with a reverse order. Hi Willem, Yumeng has fiexed most of the issues except this one. [cid:C9D306AD-8E69-47A2-B241-6ABD9D8896C8] We researched other projects’ trademarks here (ht

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

+1 (binding) I checked these items: - Download links are valid. - Checksums and signatures. - LICENSE/NOTICE/DISCLAIMER files exist - No unexpected binary files - All source files have ASF headers On 6/13/22 23:48, Liang Zhang wrote: Hello all, This is a call for vote to release Apache DevLake

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

+1 Here we go v0.11.0-rc1 !!! I went through the following steps: 1. manually deploy and run devlake 2. compare the data between raw, tool and domain layer, also compare to source web 3. And use golint to check all files with ASF header > 2022年6月13日 23:48，Liang Zhang 写道： > > Hello all, > >

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

+1 Here we go v0.11.0-rc1 !!! 获取 Outlook for iOS 发件人: Liang Zhang 发送时间: Monday, June 13, 2022 11:48:18 PM 收件人: dev@devlake.apache.org 主题: [VOTE] Release Apache DevLake (Incubating) v0.11.0-rc1 Hello all, This is a call for vote to release