Re: [ANNOUNCE] The Spotless with google-java-format now in effect

[jincheng sun]

Thanks for the feedback XiangWei!

Just like Xiangdong said, we do not need download the code style file just
import from our project is enough.
I'd like to know if the plug-in works well to you now?

Best,
Jincheng Sun 孙金城


Xiangdong Huang  于2021年2月23日周二 上午12:03写道：

> > The import ordering is not handled by this plugin
>
> Really? On my IDEA, it works.
> I did not set the step: "download the IntelliJ Java Google Style file and
> import it into File→Settings→Editor→Code Style"
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Xiangwei Wei  于2021年2月22日周一 下午4:13写道：
>
> > Hi Jincheng,
> >
> >
> > I followed the user guide in [1], installed the google-java-format plugin
> > and Save Actions plugin. But it seems the import ordering is not handled
> > properly.
> > In the site of google-java-format [2], the problem is mentioned:
> >
> > "The import ordering is not handled by this plugin, unfortunately.
> > To fix the import order, download the IntelliJ Java Google Style file and
> > import it into File→Settings→Editor→Code Style."
> >
> > I did like this, but it was not working. Do you have some solutions?
> >
> > Thank you. Regards
> >
> >
> > [1]
> > http://iotdb.apache.org/Development/ContributeGuide.html#code-formatting
> > [2]
> >
> >
> https://github.com/google/google-java-format#intellij-android-studio-and-other-jetbrains-ides
> >
> >
> > jincheng sun  于2021年2月19日周五 上午9:46写道：
> >
> > > It seems that step 7 should be performed first to ensure that the
> commit
> > > for step 2 is there.
> > >
> > > jincheng sun  于2021年2月18日周四 下午8:57写道：
> > >
> > > > Hi folks,
> > > >
> > > > We have merged the PRs of IOTDB-1156, i.e., the Spotless with
> > > > google-java-format now in effect.
> > > >
> > > > This change touched most of single java file in the repository(70K+).
> > So
> > > > most of PRs will require a rebase, follow the steps below:
> > > >
> > > > 1. git checkout YOUR_PR
> > > > 2. git cherry-pick b1261ecb5893ee0d357fec311b4d92ff9039a989
> > > > 3. mvn spotless:check
> > > > 4. mvn spotless:apply
> > > > 5. git add .
> > > > 6. git commit -m 'Apply Spotless'
> > > >
> > > > # asf  g...@github.com:apache/iotdb.git (fetch)
> > > > # Pull the latest master branch
> > > >
> > > > 7. git checkout -b asf_master asf/master
> > > > 8. git checkout YOUR_PR
> > > > 9. git rebase asf_master
> > > >
> > > > # Resolve your conflict:
> > > > # NOTE: `Accept Yours` for your PR involves files, and `accept
> Theirs`
> > > for
> > > > other files.
> > > >
> > > > 10 git rebase --continue
> > > > # Double check
> > > > 11. mvn spotless:check
> > > > # If you see "build success" successfully, it is proved that rebase
> has
> > > > been successful.
> > > > 12. mvn clean package -DskipTests
> > > > # If you see "build success" successfully, you can push your changes
> to
> > > > you PR branch.
> > > >
> > > > Then you can squash the commits if you want, Good luck!
> > > >
> > > > Most of the changes were done by the commit(70fc76de8b5a032), which
> you
> > > > can exclude from git blame by configuring git as follows:
> > > >
> > > > git config blame.ignoreRevsFile .git-blame-ignore-revs
> > > >
> > > > You can setup the IDE to follow the new code style according [1]
> > > >
> > > > Finally, a big thank you to Xiangdong and Dawei for review and merge
> > PR,
> > > > and the people who involved in the early discussions.[2]
> > > >
> > > > Best,
> > > > Jincheng 孙金城
> > > >
> > > > [1]
> > > >
> > >
> >
> https://iotdb.apache.org/Development/ContributeGuide.html#code-formatting
> > > > [2]
> > > >
> > >
> >
> https://lists.apache.org/thread.html/rd07d66cc819bce546aced54d7f0b0ab4552a910a120f05fe900915dc%40%3Cdev.iotdb.apache.org%3E
> > > >
> > >
> >
> >
> > --
> > Best,
> > Xiangwei Wei
> >
>

Re: [ANNOUNCE] The Spotless with google-java-format now in effect

[jincheng sun]

It seems that step 7 should be performed first to ensure that the commit
for step 2 is there.

jincheng sun  于2021年2月18日周四 下午8:57写道：

> Hi folks,
>
> We have merged the PRs of IOTDB-1156, i.e., the Spotless with
> google-java-format now in effect.
>
> This change touched most of single java file in the repository(70K+). So
> most of PRs will require a rebase, follow the steps below:
>
> 1. git checkout YOUR_PR
> 2. git cherry-pick b1261ecb5893ee0d357fec311b4d92ff9039a989
> 3. mvn spotless:check
> 4. mvn spotless:apply
> 5. git add .
> 6. git commit -m 'Apply Spotless'
>
> # asf  g...@github.com:apache/iotdb.git (fetch)
> # Pull the latest master branch
>
> 7. git checkout -b asf_master asf/master
> 8. git checkout YOUR_PR
> 9. git rebase asf_master
>
> # Resolve your conflict:
> # NOTE: `Accept Yours` for your PR involves files, and `accept Theirs` for
> other files.
>
> 10 git rebase --continue
> # Double check
> 11. mvn spotless:check
> # If you see "build success" successfully, it is proved that rebase has
> been successful.
> 12. mvn clean package -DskipTests
> # If you see "build success" successfully, you can push your changes to
> you PR branch.
>
> Then you can squash the commits if you want, Good luck!
>
> Most of the changes were done by the commit(70fc76de8b5a032), which you
> can exclude from git blame by configuring git as follows:
>
> git config blame.ignoreRevsFile .git-blame-ignore-revs
>
> You can setup the IDE to follow the new code style according [1]
>
> Finally, a big thank you to Xiangdong and Dawei for review and merge PR,
> and the people who involved in the early discussions.[2]
>
> Best,
> Jincheng 孙金城
>
> [1]
> https://iotdb.apache.org/Development/ContributeGuide.html#code-formatting
> [2]
> https://lists.apache.org/thread.html/rd07d66cc819bce546aced54d7f0b0ab4552a910a120f05fe900915dc%40%3Cdev.iotdb.apache.org%3E
>

[ANNOUNCE] The Spotless with google-java-format now in effect

[jincheng sun]

Hi folks,

We have merged the PRs of IOTDB-1156, i.e., the Spotless with
google-java-format now in effect.

This change touched most of single java file in the repository(70K+). So
most of PRs will require a rebase, follow the steps below:

1. git checkout YOUR_PR
2. git cherry-pick b1261ecb5893ee0d357fec311b4d92ff9039a989
3. mvn spotless:check
4. mvn spotless:apply
5. git add .
6. git commit -m 'Apply Spotless'

# asf  g...@github.com:apache/iotdb.git (fetch)
# Pull the latest master branch

7. git checkout -b asf_master asf/master
8. git checkout YOUR_PR
9. git rebase asf_master

# Resolve your conflict:
# NOTE: `Accept Yours` for your PR involves files, and `accept Theirs` for
other files.

10 git rebase --continue
# Double check
11. mvn spotless:check
# If you see "build success" successfully, it is proved that rebase has
been successful.
12. mvn clean package -DskipTests
# If you see "build success" successfully, you can push your changes to you
PR branch.

Then you can squash the commits if you want, Good luck!

Most of the changes were done by the commit(70fc76de8b5a032), which you can
exclude from git blame by configuring git as follows:

git config blame.ignoreRevsFile .git-blame-ignore-revs

You can setup the IDE to follow the new code style according [1]

Finally, a big thank you to Xiangdong and Dawei for review and merge PR,
and the people who involved in the early discussions.[2]

Best,
Jincheng 孙金城

[1]
https://iotdb.apache.org/Development/ContributeGuide.html#code-formatting
[2]
https://lists.apache.org/thread.html/rd07d66cc819bce546aced54d7f0b0ab4552a910a120f05fe900915dc%40%3Cdev.iotdb.apache.org%3E

Re: AW: [DISCUSS] I would like to propose using Spotless for IoTDB coding style check

[jincheng sun]

The difference is between `/**` and `/*`, i.e., we have very strict control
on javadoc annotation, and multi line annotation will be more flexible.

Xiangdong Huang  于2021年2月17日周三 下午9:40写道：

> Hi,
>
> why moving comments ahead of a class into the inside of  the class can
> avoid that?
>
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2021年2月17日周三 下午6:21写道：
>
> > Thank you for your positive feedback, Dawei !
> >
> > #1: May be we can turn special class comments into multiline comments for
> > ensure example readability. more detail can be find [1].
> > #2: We can fix the incorrect license headers, i.e., `/**` to `/*` in
> > license header.
> >
> > It would be great if you have time to review the PR and have your + 1 in
> > PR. Any feedback is welcome !
> >
> > Best,
> > Jincheng
> >
> > [1]
> >
> >
> https://github.com/apache/iotdb/pull/2684/commits/3912051fab0e5df0eb966bb402df04d6b015a3c8
> >
> >
> >
> > Dawei Liu  于2021年2月17日周三 下午3:00写道：
> >
> > > Hi,
> > >
> > >
> > > +1
> > >
> > >
> > > But there are a few minor issues to watch out for:
> > >
> > >
> > > 1.Formed comments will be corrupted, example:
> > > original:
> > >  * +---+ +---+
> > > +---+
> > >  * |1 |0 |1 |1 |0 |0 |1 |1 | |1 |0 |1 |1 |0 |0 |0 |0 | |0 |1 |0 |1 |1
> |0
> > > |1 |0 |
> > >  * +---+ +---+
> > > +---+
> > > modified:
> > > * +---+ +---+
> > > +---+ |1 |0 |1 |1 |0
> > >  * |0 |1 |1 | |1 |0 |1 |1 |0 |0 |0 |0 | |0 |1 |0 |1 |1 |0 |1 |0 |
> > > +---+
> > >  * +---+ +---+ +-+ +-+
> > > +-+ +-+ +-+
> > >
> > >
> > >
> > >
> > > 2.Some license headers that use /** should be changed to /*, otherwise
> > the
> > > content will be changed, example:
> > > original:
> > > /**
> > >  * Licensed to the Apache Software Foundation (ASF) under one
> > >  * or more contributor license agreements.  See the NOTICE file
> > >  * distributed with this work for additional information
> > >  * regarding copyright ownership.  The ASF licenses this file
> > >  * to you under the Apache License, Version 2.0 (the
> > >  * "License"); you may not use this file except in compliance
> > >  * with the License.  You may obtain a copy of the License at
> > >  *
> > >  * http://www.apache.org/licenses/LICENSE-2.0
> > >  *
> > >  * Unless required by applicable law or agreed to in writing,
> > >  * software distributed under the License is distributed on an
> > >  * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
> > >  * KIND, either express or implied.  See the License for the
> > >  * specific language governing permissions and limitations
> > >  * under the License.
> > >  */
> > >
> > >
> > > modified:
> > > /**
> > >  * Licensed to the Apache Software Foundation (ASF) under one or more
> > > contributor license
> > >  * agreements. See the NOTICE file distributed with this work for
> > > additional information regarding
> > >  * copyright ownership. The ASF licenses this file to you under the
> > Apache
> > > License, Version 2.0 (the
> > >  * "License"); you may not use this file except in compliance with the
> > > License. You may obtain a
> > >  * copy of the License at
> > >  *
> > >  * http://www.apache.org/licenses/LICENSE-2.0
> > >  *
> > >  * Unless required by applicable law or agreed to in writing,
> software
> > > distributed under the
> > >  * License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
> > > CONDITIONS OF ANY KIND, either
> > >  * express or implied. See the License for the specific language
> > governing
> > > permissions and
> > >  * limitations under the License.
> > >  */
> > >
> > >
> > > 3. Personally, lambda expressions are not very friendly to me
> > > original:
> > > localMember.getSerialToParallelPool().submit(() -> {
> >

Re: AW: [DISCUSS] I would like to propose using Spotless for IoTDB coding style check

[jincheng sun]

Thank you for your positive feedback, Dawei !

#1: May be we can turn special class comments into multiline comments for
ensure example readability. more detail can be find [1].
#2: We can fix the incorrect license headers, i.e., `/**` to `/*` in
license header.

It would be great if you have time to review the PR and have your + 1 in
PR. Any feedback is welcome !

Best,
Jincheng

[1]
https://github.com/apache/iotdb/pull/2684/commits/3912051fab0e5df0eb966bb402df04d6b015a3c8



Dawei Liu  于2021年2月17日周三 下午3:00写道：

> Hi,
>
>
> +1
>
>
> But there are a few minor issues to watch out for:
>
>
> 1.Formed comments will be corrupted, example:
> original:
>  * +---+ +---+
> +---+
>  * |1 |0 |1 |1 |0 |0 |1 |1 | |1 |0 |1 |1 |0 |0 |0 |0 | |0 |1 |0 |1 |1 |0
> |1 |0 |
>  * +---+ +---+
> +---+
> modified:
> * +---+ +---+
> +---+ |1 |0 |1 |1 |0
>  * |0 |1 |1 | |1 |0 |1 |1 |0 |0 |0 |0 | |0 |1 |0 |1 |1 |0 |1 |0 |
> +---+
>  * +---+ +---+ +-+ +-+
> +-+ +-+ +-+
>
>
>
>
> 2.Some license headers that use /** should be changed to /*, otherwise the
> content will be changed, example:
> original:
> /**
>  * Licensed to the Apache Software Foundation (ASF) under one
>  * or more contributor license agreements.  See the NOTICE file
>  * distributed with this work for additional information
>  * regarding copyright ownership.  The ASF licenses this file
>  * to you under the Apache License, Version 2.0 (the
>  * "License"); you may not use this file except in compliance
>  * with the License.  You may obtain a copy of the License at
>  *
>  * http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing,
>  * software distributed under the License is distributed on an
>  * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
>  * KIND, either express or implied.  See the License for the
>  * specific language governing permissions and limitations
>  * under the License.
>  */
>
>
> modified:
> /**
>  * Licensed to the Apache Software Foundation (ASF) under one or more
> contributor license
>  * agreements. See the NOTICE file distributed with this work for
> additional information regarding
>  * copyright ownership. The ASF licenses this file to you under the Apache
> License, Version 2.0 (the
>  * "License"); you may not use this file except in compliance with the
> License. You may obtain a
>  * copy of the License at
>  *
>  * http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
> distributed under the
>  * License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
> CONDITIONS OF ANY KIND, either
>  * express or implied. See the License for the specific language governing
> permissions and
>  * limitations under the License.
>  */
>
>
> 3. Personally, lambda expressions are not very friendly to me
> original:
> localMember.getSerialToParallelPool().submit(() -> {
> try {
>   long result = client.startElection(request);
>   handler.onComplete(result);
> } catch (Exception e) {
>   handler.onError(e);
> } finally {
>   ClientUtils.putBackSyncHeartbeatClient(client);
> }
>   });
> modified:
> localMember
>  .getSerialToParallelPool()
>  .submit(
>  () -> {
>try {
>  long result = client.startElection(request);
>  handler.onComplete(result);
>} catch (Exception e) {
>  handler.onError(e);
>} finally {
>  ClientUtils.putBackSyncHeartbeatClient(client);
>}
>  });
>
>
>
>
>
>
> Dawei
> On 02/16/2021 15:37，jincheng sun wrote：
> +1
>
> Best,
> Jincheng
>
>
> weizihan0110  于2021年2月16日周二 上午11:16写道：
>
> +1
>
>
> | |
> Al Wei
> |
> |
> 邮箱：wzh1007181...@163.com
> |
>
> 签名由 网易邮箱大师 定制
>
> On 02/16/2021 10:44, Xiangdong Huang wrote:
> +1. 【please pay attention】, If no -1, I will merge the PR [1] (+70K and
> -69K lines of codes).
>
> I have tried the commands for solving conflicts. No much work to do.
>
> [1] https://github.com/apache/iotdb/pull/2684
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>

Re: AW: [DISCUSS] I would like to propose using Spotless for IoTDB coding style check

[jincheng sun]

+1

Best,
Jincheng


weizihan0110  于2021年2月16日周二 上午11:16写道：

> +1
>
>
> | |
> Al Wei
> |
> |
> 邮箱：wzh1007181...@163.com
> |
>
> 签名由 网易邮箱大师 定制
>
> On 02/16/2021 10:44, Xiangdong Huang wrote:
> +1. 【please pay attention】, If no -1, I will merge the PR [1] (+70K and
> -69K lines of codes).
>
> I have tried the commands for solving conflicts. No much work to do.
>
> [1] https://github.com/apache/iotdb/pull/2684
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
> 黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2021年2月15日周一 下午2:32写道：
>
> > Hi,
> >
> > I applied Spotless and Google Java format in the [1] branch, which
> contains
> > two commits, one is the POM configuration of spotless, and the other is
> the
> > change after the code is automatically formatted. I'm glad to see that we
> > have automatically fixed many of our problems of mixing 2-space and
> 4-space
> > in indents.
> >
> > I have merged one PR to spotless branch by following steps:
> >
> > # `asf` is repo of Apache IoTDD
> > git fetch asf pull/2667/head:PR2667
> > git checkout PR2667
> > git cherry-pick 5ef3baaf1915095b74773b110a8f9e4e3c82429b
> > mvn com.diffplug.spotless:spotless-maven-plugin:check
> > mvn com.diffplug.spotless:spotless-maven-plugin:apply
> > git add .
> > git commit -m 'Apply spotless'
> > git rebase asf_spotless
> > // Resolve your conflict
> > git rebase --continue
> > // After squash your commits
> > gck asf_spotless
> > git merge PR2667
> > git push asf asf_spotless:spotless
> >
> > If you agree to apply Spotless, I will create JIRA. and OPEN the PR for
> > apply Spotless add related documents. The document will involve some
> > configuration instructions, such as IDEA configuration:
> >
> > 1. Install google-java-format plugin
> > 2. In the plugin settings, enable the plugin and change the code style to
> > "GOOGLE" (2-space indents)
> > 3. Install the Save Actions plugin
> > 4. Enable the plugin, along with "Optimize imports" and "Reformat file"
> > 5. In the "Save Actions" settings page, setup a "File Path Inclusion" for
> > `.*\.java`. 6. ...
> >
> > and other config items, such as "importOrder" etc.
> >
> > What are your thoughts?
> >
> > Best,
> > Jincheng
> >
> > [1] https://github.com/apache/iotdb/tree/spotless
> >
> >
> >
> > jincheng sun  于2021年2月12日周五 上午7:20写道：
> >
> > > Hi,
> > >
> > > Thank you all for the feedback Chris，Dawei and Xiangdong!
> > >
> > > @Chris You're right. We don't want developers to pay too much attention
> > to
> > > code styles, so I would like to make more efforts to make code styles
> > > automatic, transparent to developers (try our best), when we have
> > finished
> > > the agreed configuration of Spotless,  ` mvn spotless:check ` and `mvn
> > > spotless:apply ` can do check and correct work for us.
> > >
> > > @Dawei Thank you very much for trying and sharing the advanced
> functions
> > > of Spotless. About the problems you encounter, configuring the version
> of
> > > GoogleJavaformat should be able to solve the problem. The version 1.7
> of
> > > GoogleJavaformat can work well on JDK1.8:
> > >
> > > 
> > >   
> > >  
> > > 1.7
> > > ...
> > >  
> > >  ...
> > >  ...
> > >   
> > > 
> > >
> > > @Xiangdong  You're right. Spotless will bring some changes for history
> > > code, fortunately, Spotless can automatically apply the style and
> helped
> > to
> > > easily rebase the PRs, and there is an useful feature in Spotless is
> > > "ratchet" [1]  With this, we can set up Spotless to only apply it's
> rules
> > > to files that were changed after a configured commit. This would allow
> a
> > > gradual application of the new coding style instead of one big change.
> > Of
> > > course, I'd like to provide a PoC to let you see the changes after the
> > > plug-in of Spotless has applied.
> > >
> > > Thanks again for all of your feedback. I'd like to show a PoC later.
> > >
> > > Best,
> > > Jincheng
> > >
> > > [1]
> > >
> >
> https://github.com/diffplug/spotless/blob/main/plugin-m

Re: [DISCUSS] Create a new Repo to upload binary files (images for markdown, compiled thrift binary, etc..)

[jincheng sun]

Thanks for bring up this discussion, Xiangdong!

The problem of network access is really a long-term problem for Chinese
users. For the convenience of users, we really need a special warehouse to
store the current and future pictures and binary files.

So, +1 for creating the `apache/iotdb-resources` to  store all these files
for both `iotdb` and `iotdb-website` repo.

Best,
Jincheng


Xiangdong Huang  于2021年2月15日周一 上午9:02写道：

> Hi Chris,
>
> 1. About thrift.
> Indeed we learned from PLC4x and maintain a module to compile thrift (as
> well as boost initially, but it still requires installing flex and bison.
> and finally we give up compiling boost, and only maintain compiling
> thrift). But now it is just used to generate static or dynamic library for
> c++ codes.
>
> The question is, users who want to compile the source code has to install
> flex, bison, and boost (byw, flex and bison have version requirements)
> first... It is not very friendly (and time consuming) for new users.
>
> 2. For images
> In our docs (in markdown files), we use external links (e.g., [1], provided
> by github). They are not accessible in China.
>
> A simple solution is saving the original image files to our  repo (e.g.,
> create a folder called 'imgs'), and use relative path in our markdowns.
> After compiling the website, the generated static htmls will keep using the
> relative path and thereby they will be accessible in China (as they will be
> upload to iotdb.apache.org).
>
> But the drawback is it will increase the size of the repo (images are
> binary files so that once we update an image, the whole file will be
> replaced, and the git history has few meaning). That is why I'd like to
> create a new repo and users/developers can choose whether they need to
> clone the repo.
>
>
> [1]
>
> https://user-images.githubusercontent.com/19167280/73625222-ddd88680-467e-11ea-9098-e808ed4979c5.png
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Christofer Dutz  于2021年2月14日周日 下午11:14写道：
>
> > Hi Xiangdong,
> >
> > regarding thrift ... how about doing it similar to our Maven-triggered
> > Thrift build in PLC4X?
> > I'm admittedly not a fan of requiring stuff in Apache projects which is
> > maintained by individuals.
> >
> > It doesn't have to be built every time but it would be great if there was
> > a job we could manually trigger to build the Thrift compiler executalbes
> > every time we need them.
> >
> > But regarding images: ... where are these referenced? Why not put the
> > image resources in the repo where also the content is located? Perhaps
> > however I'm not understanding the setup correctly though.
> >
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von: Xiangdong Huang 
> > Gesendet: Sonntag, 14. Februar 2021 15:08
> > An: dev 
> > Betreff: [DISCUSS] Create a new Repo to upload binary files (images for
> > markdown, compiled thrift binary, etc..)
> >
> > Hi,
> >
> > Currently, we upload all figures to github's issues to get a public URL
> > and use it in our markdown files. The question is, it is hard to maintain
> > the figures, and, the URL is *.githubusercontent.com/*, which maybe can
> > not be accessed in China.
> >
> > Besides, we are using compiled thrift binary from
> > https://github.com/jt2594838/mvn-thrift-compiler/. Though it is compiled
> > by our committer Tian Jiang, it is a personal repo and may get suspected
> by
> > users.
> >
> > Therefore, I'd like to apply for creating a new repo,
> > apache/iotdb-resources to collect all these files.
> >
> > The repo can be as a git submodule of iotdb, and so that all figures can
> > be used as a relative path in markdowns. As a result, the figures will be
> > compiled as local files for our website (i.e., all figures' URL are
> > iotdb.apache.org/* rather than githubusercontent.com/*).
> >
> > thrift compiler will also be download from apache/iotdb-resources, which
> > will convincing users and is more controllable.
> >
> > Why not upload these resources directly to apache/iotdb: for controlling
> > the size of iotdb's repo.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
>

Re: AW: [DISCUSS] I would like to propose using Spotless for IoTDB coding style check

[jincheng sun]

Hi,

I applied Spotless and Google Java format in the [1] branch, which contains
two commits, one is the POM configuration of spotless, and the other is the
change after the code is automatically formatted. I'm glad to see that we
have automatically fixed many of our problems of mixing 2-space and 4-space
in indents.

I have merged one PR to spotless branch by following steps:

# `asf` is repo of Apache IoTDD
git fetch asf pull/2667/head:PR2667
git checkout PR2667
git cherry-pick 5ef3baaf1915095b74773b110a8f9e4e3c82429b
mvn com.diffplug.spotless:spotless-maven-plugin:check
mvn com.diffplug.spotless:spotless-maven-plugin:apply
git add .
git commit -m 'Apply spotless'
git rebase asf_spotless
// Resolve your conflict
git rebase --continue
// After squash your commits
gck asf_spotless
git merge PR2667
git push asf asf_spotless:spotless

If you agree to apply Spotless, I will create JIRA. and OPEN the PR for
apply Spotless add related documents. The document will involve some
configuration instructions, such as IDEA configuration:

1. Install google-java-format plugin
2. In the plugin settings, enable the plugin and change the code style to
"GOOGLE" (2-space indents)
3. Install the Save Actions plugin
4. Enable the plugin, along with "Optimize imports" and "Reformat file"
5. In the "Save Actions" settings page, setup a "File Path Inclusion" for
`.*\.java`. 6. ...

and other config items, such as "importOrder" etc.

What are your thoughts?

Best,
Jincheng

[1] https://github.com/apache/iotdb/tree/spotless



jincheng sun  于2021年2月12日周五 上午7:20写道：

> Hi,
>
> Thank you all for the feedback Chris，Dawei and Xiangdong!
>
> @Chris You're right. We don't want developers to pay too much attention to
> code styles, so I would like to make more efforts to make code styles
> automatic, transparent to developers (try our best), when we have finished
> the agreed configuration of Spotless,  ` mvn spotless:check ` and `mvn
> spotless:apply ` can do check and correct work for us.
>
> @Dawei Thank you very much for trying and sharing the advanced functions
> of Spotless. About the problems you encounter, configuring the version of
> GoogleJavaformat should be able to solve the problem. The version 1.7 of
> GoogleJavaformat can work well on JDK1.8:
>
> 
>   
>  
> 1.7
> ...
>  
>  ...
>  ...
>   
> 
>
> @Xiangdong  You're right. Spotless will bring some changes for history
> code, fortunately, Spotless can automatically apply the style and helped to
> easily rebase the PRs, and there is an useful feature in Spotless is
> "ratchet" [1]  With this, we can set up Spotless to only apply it's rules
> to files that were changed after a configured commit. This would allow a
> gradual application of the new coding style instead of one big change.  Of
> course, I'd like to provide a PoC to let you see the changes after the
> plug-in of Spotless has applied.
>
> Thanks again for all of your feedback. I'd like to show a PoC later.
>
> Best,
> Jincheng
>
> [1]
> https://github.com/diffplug/spotless/blob/main/plugin-maven/README.md#ratchet
>
>
> Xiangdong Huang  于2021年2月10日周三 下午10:19写道：
>
>> Take away:
>> I opt for uniforming the code style.  But we have to consider how
>> to maintain current opened PRs (we have about 40+ PRs) to solve potential
>> conflicts.
>>
>> Details:
>> I opt for uniforming the code style.
>> In some PRs, we can find many lines are changed just because the indent is
>> changed...
>>
>> Yes we are using google style, and we have a maven checkstyle plugin,
>> indeed.
>>
>> If you see files under `target`, you can find the checkout-style.xml file.
>> Or, if you add `true` to the configuration
>> of the plugin (about line 769 in pom.xml), and run `mvn validate`,
>> we can see many warnings on the console..
>> If we want to require all contributors obey the style, the
>> " warning " configuration is
>> needed,
>> which will
>> lead to the build failed if there is any violation.
>>
>> The current plugin does not modify the source files automatically but
>> Spotless plugin can do that.
>>
>> However, if too many codes are changed, we have to consider the impact of
>> tracing the history of codes, and we have to consider how to manually
>> maintain current opened PRs (we have about 40+ PRs) to solve confliction.
>>
>> I'd like to preview the changes caused by the plugin. Can you show a patch
>> file or a snippet?
>>
>> Best,
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>>

Re: AW: [DISCUSS] I would like to propose using Spotless for IoTDB coding style check

[jincheng sun]

Hi,

Thank you all for the feedback Chris，Dawei and Xiangdong!

@Chris You're right. We don't want developers to pay too much attention to
code styles, so I would like to make more efforts to make code styles
automatic, transparent to developers (try our best), when we have finished
the agreed configuration of Spotless,  ` mvn spotless:check ` and `mvn
spotless:apply ` can do check and correct work for us.

@Dawei Thank you very much for trying and sharing the advanced functions of
Spotless. About the problems you encounter, configuring the version of
GoogleJavaformat should be able to solve the problem. The version 1.7 of
GoogleJavaformat can work well on JDK1.8:


  
 
1.7
...
 
 ...
 ...
  


@Xiangdong  You're right. Spotless will bring some changes for history
code, fortunately, Spotless can automatically apply the style and helped to
easily rebase the PRs, and there is an useful feature in Spotless is
"ratchet" [1]  With this, we can set up Spotless to only apply it's rules
to files that were changed after a configured commit. This would allow a
gradual application of the new coding style instead of one big change.  Of
course, I'd like to provide a PoC to let you see the changes after the
plug-in of Spotless has applied.

Thanks again for all of your feedback. I'd like to show a PoC later.

Best,
Jincheng

[1]
https://github.com/diffplug/spotless/blob/main/plugin-maven/README.md#ratchet


Xiangdong Huang  于2021年2月10日周三 下午10:19写道：

> Take away:
> I opt for uniforming the code style.  But we have to consider how
> to maintain current opened PRs (we have about 40+ PRs) to solve potential
> conflicts.
>
> Details:
> I opt for uniforming the code style.
> In some PRs, we can find many lines are changed just because the indent is
> changed...
>
> Yes we are using google style, and we have a maven checkstyle plugin,
> indeed.
>
> If you see files under `target`, you can find the checkout-style.xml file.
> Or, if you add `true` to the configuration
> of the plugin (about line 769 in pom.xml), and run `mvn validate`,
> we can see many warnings on the console..
> If we want to require all contributors obey the style, the
> " warning " configuration is needed,
> which will
> lead to the build failed if there is any violation.
>
> The current plugin does not modify the source files automatically but
> Spotless plugin can do that.
>
> However, if too many codes are changed, we have to consider the impact of
> tracing the history of codes, and we have to consider how to manually
> maintain current opened PRs (we have about 40+ PRs) to solve confliction.
>
> I'd like to preview the changes caused by the plugin. Can you show a patch
> file or a snippet?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Dawei Liu  于2021年2月10日周三 下午10:05写道：
>
> > Hi jincheng，
> >
> >
> > Thank you very much for starting this discussion
> >
> >
> > I found a nice feature in the tool that automatically
> > ,
> > which is a common problem in reviews because the IDE collapses imports by
> > default.
> >
> >
> > Unfortunately, it didn't work in my local (JDK 1.8), and he told me:
> > Com/Google/googlejavaformat/Java/JavaFormatterOptions has had been
> > compiled by a more recent version of the Java Runtime (class file version
> > 55.0).
> > This version of the Java Runtime only recognizes the class file versions
> > up to 52.0
> >
> >
> > Do I need to upgrade my JDK?
> >
> >
> > Dawei
> > On 02/9/2021 16:14，Christofer Dutz wrote：
> > Perhaps it's just me, but ...
> >
> > If discussing formatting issues has been consuming a lot of your time, I
> > would consider this time wasted. Especially as for newcomers this is
> > particularly frustrating if you sort of provide the solution for a real
> > problem and your response is "Yeah  thanks fort hat ... but we use 4
> > spaces indentation and curly braces at the END of EVERY condition" ...
> I've
> > been in that situation multiple times and some times just wen't away
> cause
> > I just thought "WTF ... are these folks serious? I don't wanna be part of
> > such a group".
> >
> > Of course would an automated plugin help. In Go I am seeing this happen
> > auotmatically all the time. But we should ask ourselves, if paying too
> much
> > attention to some formatting rules is good.
> >
> > But ... that's just my personal opinion.
> >
> > Chris
> >
> >
> > -Ursprüngliche Nachricht-
> > Von:

[DISCUSS] I would like to propose using Spotless for IoTDB coding style check

[jincheng sun]

Hi folks,

I found that many projects use Spotless to save the time of both
contributors and reviewers.

I like Spotless[1] because it can be used to both check and apply a style.
Then we need a formatter(e.g.: google-java-format) that works with
Spotless. The pretty good thing about Spotless is that it serves as a
verifier for CI but can also apply the configured style automatically. That
is, for the programmer all we should to do is `mvn spotless:apply` to fix
any style violations.

We also have to decide on a coding style if we decide to use Spotless. and
I would propose google-java-format. (It's seems IoTDB project already
prefer Google's code specification, at present, iotdb uses GoogleStyle [2])

So what benefits will Spotless bring us:

  - No longer fussy about the coding style in reviews, which makes it
easier for reviewers and contributors to understand
  - There is no need to fix check style errors manually because Spotless
can fix them automatically

Currently, Spotless has been used in many projects, such as: Apache Beam
[3], Apache Flink [4], Apache Kafka [5] Apache avro [6] etc.

In short words, I believe that the introduction of Spotless will save us a
lot of time and focus more on the development of features.
If you agree to use Spotless, I will create the JIRA. for tracking and add
the detailed design and POC. What are your thoughts?

-
Finally, on the occasion of the Chinese Lunar New Year, I wish community of
IoTDB better and better. I wish you a happy new year, all the best for
2021. :)
㊗️福大家，牛年大吉！

Best,
Jincheng
2021.02.09

[1] https://github.com/diffplug/spotless
[2] https://github.com/apache/iotdb/blob/master/java-google-style.xml
[3]
https://github.com/apache/beam/blob/b74fcf7b30d956fb42830d652a57b265a1546973/buildSrc/build.gradle#L23
[4]
https://github.com/apache/flink/blob/4a5ef8af0bbc49d738717ae477576c172e60e62c/pom.xml#L159
[5]
https://github.com/apache/kafka/blob/42a9355e606bd2bbdb7fd0dd348805edc189/build.gradle#L44
[6]
https://github.com/apache/avro/blob/8026c8ffe4ef67ab419dba73910636bf2c1a691c/lang/java/pom.xml#L307-L334

Re: [NEWS] The largest PR (in 2020) is merged

[jincheng sun]

That's great, Cheers!

Best,
Jincheng

Jialin Qiao  于2020年12月9日周三 下午1:06写道：

> Hi,
>
> Thank for your all :)
> Looking forward to a better IoTDB!
>
> Thanks,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
>  -原始邮件-
>  发件人: "Xin Wang" 
>  发送时间: 2020-12-09 13:00:40 (星期三)
>  收件人: dev@iotdb.apache.org
>  抄送:
>  主题: Re: [NEWS] The largest PR (in 2020) is merged
> 
>  Great news!
> 
>  王超  于2020年12月9日周三 上午10:46写道：
> 
>   Congratulation!
>  
>  
>   I like Jialin's finger which clicked the button.
>  
>  
>   Good job!
>  
>  
>   | |
>   Chao Wang
>   |
>   |
>   BONC, Ltd
>   ccgow...@163.com
>   |
>   签名由网易邮箱大师定制
>   On 12/9/2020 10:26，谭新宇 wrote：
>   Hi,
>  
>  
>   What an exciting moment! Hope the cluster module can be more
> stable and
>   efficient under our effort!
>  
>  
>   Best
>   --
>   XinYu Tan
> 
> 
> 
>  --
>  Thanks,
>  Xin
> 

Re: [VOTE] A new repository for Go client

[jincheng sun]

+1

Best,
Jincheng


田原  于2020年12月2日周三 上午10:34写道：

> Hi,
>
> +1
>
>
> Best,
> ---
> Yuan Tian
>
>

Re: [ANNOUNCE] Apache IoTDB 0.11.0 released

[jincheng sun]

Thanks a lot for the release, Xiangdong!
Also thanks to everyone that make this release possible!

Best,
Jincheng


Jialin Qiao  于2020年11月27日周五 下午12:59写道：

> Hi,
>
> Great work! Thanks Xiangdong!
>
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
>  -原始邮件-
>  发件人: "Xiangdong Huang" 
>  发送时间: 2020-11-27 12:17:05 (星期五)
>  收件人: annou...@apache.org
>  抄送: priv...@iotdb.apache.org, dev 
>  主题: [ANNOUNCE] Apache IoTDB 0.11.0 released
> 
>  The Apache IoTDB team is pleased to announce the release of Apache
> IoTDB
>  0.11.0.
> 
>  Apache IoTDB (Database for Internet of Things) is an IoT native
> database
>  with high performance for data management and analysis, deployable on
> the
>  edge and the cloud.
> 
>  This is the first release version after Apache IoTDB graduated from
> the
>  incubator, which includes two big improvements:
> 
>  * Better memory control for writing data
>  * Data compaction is enabled by default to accelerate queries
> 
>  More:
> 
>  * IOTDB-627 Support range deletion for timeseries
>  * IOTDB-670 Add raw data query interface in Session
>  * IOTDB-716 add lz4 compression
>  * IOTDB-736 Add query performance tracing
>  * IOTDB-776 New memory control strategy
>  * IOTDB-813 Show storage group under given path prefix
>  * IOTDB-848 Support order by time asc/desc
>  * IOTDB-863 add a switch to drop ouf-of-order data
>  * IOTDB-873 Add count devices DDL
>  * IOTDB-876 Add count storage group DDL
>  * IOTDB-926 Support reconnection of Session
>  * IOTDB-941 Support 'delete storage group '
>  * IOTDB-968 Support time predicate in select last, e.g., select last
> * from
>  root where time = t
>  * Support alias if it is used in query (e.g., select s1 as temp from
>  root.a.b)
>  * Add level compaction strategy
>  * Enable partial insert (some failed inserted columns do not impact
> others)
> 
>  Data file format changes:
> 
>  * IOTDB-778 Support double/single quotation in Path
>  * IOTDB-870 change tags and attributes output to two columns with json
>  values
> 
>  The full release note is available at:
> 
> https://raw.githubusercontent.com/apache/iotdb/release/0.11.0/RELEASE_NOTES.md
> 
> ;
>
>  The release is available for download at:
>  http://iotdb.apache.org/Download
> 
>  Maven artifacts for JDBC driver, session SDK, TsFile SDK,
> Spark-connector,
>  Hadoop-connector, Hive-connector and Flink-connector can be found at:
>  https://search.maven.org/search?q=g:org.apache.iotdb
> 
>  Docker image of IoTDB server can be found at:
>  https://hub.docker.com/r/apache/iotdb
> 
>  Python API package can be found at:
>  https://pypi.org/project/apache-iotdb/
> 
>  Regards,
>  The Apache IoTDB team
> 

Re: [VOTE] Apache IoTDB 0.11.0 RC3 release

[jincheng sun]

+1 (binding)， Download and run some command in the CLI.
Best,
Jincheng


Benedict Jin  于2020年11月24日周二 下午2:41写道：

> Hi,
>
> +1 from Contributor
>
>
> I checked the binary distribution in MacOS:
> Download links [ok]
> Start in MacOS, JDK8 [ok]
> Version number in CLI [ok]
> Recover from disk [ok]
> Statements executed successfully:  [ok]
>
> SET STORAGE GROUP TO root.turbine;
> CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE,
> ENCODING=GORILLA;
> insert into root.turbine.d1(timestamp,s0) values(1,1);
> insert into root.turbine.d1(timestamp,s0) values(2,2);
> insert into root.turbine.d1(timestamp,s0) values(3,3);
> SHOW STORAGE GROUP;
> SHOW TIMESERIES;
> select * from root;
>
> Close and Restart server:
>
> SHOW TIMESERIES;
> select * from root;
>
> On 2020/11/24 03:18:35, Xiangwei Wei  wrote:
> > Hi,
> >
> > +1 from Contributor.
> >
> >
> > I checked the binary distribution in Windows:
> > Download links [ok]
> > Start in Windows, jdk8 [ok]
> > Version number in CLI [ok]
> > Recover from disk [ok]
> > Statements executed successfully:  [ok]
> >
> > SET STORAGE GROUP TO root.turbine;
> > CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE,
> ENCODING=GORILLA;
> > insert into root.turbine.d1(timestamp,s0) values(1,1);
> > insert into root.turbine.d1(timestamp,s0) values(2,2);
> > insert into root.turbine.d1(timestamp,s0) values(3,3);
> > SHOW STORAGE GROUP;
> > SHOW TIMESERIES;
> > select * from root;
> >
> > Close and Restart server:
> >
> > SHOW TIMESERIES;
> > select * from root;
> >
> > 孙泽嵩  于2020年11月24日周二 上午10:31写道：
> >
> > > Hi,
> > >
> > > +1 from committer
> > >
> > > I checked:
> > >
> > > - Download links
> > > - Signatures and hashes
> > > - Git tag
> > > - ASF headers in all source files
> > > - Compiling from source
> > > - LICENSE and NOTICE
> > > - Start in Mac
> > > - Run with following statements
> > >
> > > SET STORAGE GROUP TO root.turbine;
> > > CREATE TIMESERIES root.turbine.d1.s0 WITH DATATYPE=DOUBLE,
> > > ENCODING=GORILLA;
> > > insert into root.turbine.d1(timestamp,s0) values(1,1);
> > > insert into root.turbine.d1(timestamp,s0) values(2,2);
> > > insert into root.turbine.d1(timestamp,s0) values(3,3);
> > > select * from root;
> > >
> > > Best,
> > > ---
> > > Zesong Sun
> > > School of Software, Tsinghua University
> > >
> > > 孙泽嵩
> > > 清华大学 软件学院
> > >
> > > > 2020年11月24日 00:25，Lei Rui  写道：
> > > >
> > > > +1
> > > >
> > > >
> > > > I think the doc issues can be solved next time.
> > > >
> > > >
> > > > 1. There is a pair of Chinese single quotes used in English version
> > > "README.md":
> > > > "Insert timeseries data is a basic operation of IoTDB, you can use
> > > ‘INSERT’ command to finish this."
> > > >
> > > >
> > > > SUGGESTION: Use `insert` by the markdown grammar, or use English
> single
> > > or double quotes.
> > > >
> > > >
> > > > 2. The "incubat*" string occurs twice in README_ZH.md:
> > > > (1) "* 使用Docker: dockerfile的路径是
> > > https://github.com/apache/incubat-iotdb/tree/master/docker/src/main;
> > > > (2)
> > >
> "执行完成之后，可以在**distribution/target/apache-iotdb-{project.version}-incubating-bin.zip**找到编译完成的二进制版本(包括服务器和客户端)"
> > > >
> > > >
> > > > Actually, I use the command ( grep -r "incubat" ./ ) to find a lot
> more
> > > files containing "incubat*".
> > > > I think most of them are correct, to give a few examples:
> > > > Example 1: [./RELEASE_NOTES.md] "# Apache IoTDB (incubating) 0.10.1"
> > > > Example 2: [./docs/Community/Materials.md] "2018.12.09, ..,
> IoTDB:
> > > from Tsinghua IoTDB to Apache IoTDB (incubating)."
> > > > Example 3: [./docker/src/main/Dockerfile-0.9.0] "wget
> > >
> https://www-us.apache.org/dist/iotdb/0.9.0-incubating/apache-iotdb-0.9.0-incubating-bin.zip
> > > \"
> > > > Some of them may need updating carefully, for example:
> > > > [./client-py/pypi/README.md] "Apache IoTDB (incubating) (Database for
> > > Internet of Things) is an integrated ..."
> > > >
> > > > --
> > > > What I checked:
> > > > ✔ download staged artifacts. Check their signature and hashes.
> > > > ✔ [RM] verify the reported signature is for an "apache.org" address
> > > ("gpg: Good signature from ...")
> > > > ✔ [RM] verify the reported hashes
> > > > ✔ extract src bundle
> > > > ✔ verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES
> files
> > > in the extracted source bundle
> > > > ✔ [RM] verify the staged source README, RELEASE_NOTE files
> correspond to
> > > those in the extracted source bundle
> > > > ❗ check the contents of LICENSE, NOTICE, README, RELEASE_NOTES
> > > > ✔ UNPACK the binary artefact and check the contents of LICENSE-binary
> > > and NOTICE-binary
> > > > ✔ build from directions in README with an empty maven local repo: mvn
> > > clean package -DskipTests -Dmaven.repo.local=../.m2
> > > > ✔ ./mvnw.sh install
> > > > ✔ ./mvnw.sh site:site
> > > >
> > > >
> > > > Regards,
> > > > Lei Rui
> > > >
> > > >
> > > > On 11/20/2020 14:23，Xiangdong Huang wrote：
> > > > Hi 

Re: [VOTE] disable Travis-CI and migrate to Github Action

[jincheng sun]

Thanks for bring up this discussion Xiangdong!

+1 for using Github Action. No matter which way to use, as long as the
automatic UT/IT test case is the best choice.

Best,
Jincheng


Xiangwei Wei  于2020年11月18日周三 下午10:32写道：

> Hi,
>
>
> Big  +1  :D
>
> Benedict Jin  于2020年11月16日周一 下午6:13写道：
>
> > +1
> >
> > On 2020/11/16 06:16:56, "Jialin Qiao" 
> > wrote:
> > > +1
> > >
> > > --
> > > Jialin Qiao
> > > School of Software, Tsinghua University
> > >
> > > 乔嘉林
> > > 清华大学 软件学院
> > >
> > > > -原始邮件-
> > > > 发件人: "Xiangdong Huang" 
> > > > 发送时间: 2020-11-16 12:03:25 (星期一)
> > > > 收件人: dev 
> > > > 抄送:
> > > > 主题: [VOTE] disable Travis-CI and migrate to Github Action
> > > >
> > > > Hi all,
> > > >
> > > > Github Action is available for project UT/IT test, sonar and code
> > coverage
> > > > check now. [1]
> > > >
> > > > And, the travis-ci still does not recover...
> > > >
> > > > Therefore, I'd like to call a vote to disable Travis-ci and migrate
> to
> > > > Github Action.
> > > >
> > > > [+1] using Github Action is OK
> > > > [+0] does not matter
> > > > [-1] better to use Travis-CI, and explain why...
> > > >
> > > > The vote will open for 72 hours.
> > > >
> > > > Best,
> > > > ---
> > > > Xiangdong Huang
> > > > School of Software, Tsinghua University
> > > >
> > > >  黄向东
> > > > 清华大学 软件学院
> > > 
> >
>
>
> --
> Best,
> Xiangwei Wei
>

Re: [DISCUSS] graduation process: Charter and VP of IoTDB discussion

[jincheng sun]

Big +1 for Xiangdong as first VP of IoTDB!

Cheers,
Jincheng


Willem Jiang  于2020年9月2日周三 上午8:20写道：

> +1 for suggesting Xiangdong as first VP of IoTDB.
> He already earned enough credit in my mind.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Sep 1, 2020 at 1:55 PM Julian Feinauer
>  wrote:
> >
> > Hi,
> >
> > thanks for bringing that up.
> > Indeed I think your short proposal is right.
> >
> > Rergarding the VP, I had a short off-list discussion with @Christofer
> Dutz and we both agreed that it should be someone who speaks Chinese and
> English as our community is kind of bilingual.
> >
> > Regarding the amount of work and support that Xiangdong put into the
> community development and also his work in translating between English and
> Chinese community parts (his English is pretty good, I hope his Chinese
> too^^) I like to suggest Xiangdong, as first VP of IoTDB.
> >
> > What do others think about that?
> >
> > Julian
> >
> > Am 01.09.20, 06:17 schrieb "Xiangdong Huang" :
> >
> > Hi,
> >
> > The vote for start the graduation process has last two days and we
> have
> > received many +1.
> >
> > According to [1], we can begin to discuss the charter (resolution) in
> > parallel.
> >
> > The main task is using one or two sentences to define what IoTDB is:
> >
> > A good resolution is neither too narrow nor too broad. If the
> project’s
> > scope is too narrow, then its activities will be unnecessarily
> constrained.
> > If a project’s scope is too broad then it may lack focus and suffer
> from
> > governance issues.
> >
> > Besides, we need also to elect someone as the VP of the project.
> >
> > So, any ideas?
> >
> > IMO, how about:
> >
> > Apache IoTDB: a native database for storing and analyzing Internet of
> > Things data, on the edge and the cloud.
> >
> > [1]
> >
> https://incubator.apache.org/guides/graduation.html#the_graduation_process
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
>

Re: [DISCUSS] discuss about graduation of Apache IoTDB (incubating)

[jincheng sun]

+1 for IoTDB to graduation!

Because not only is the IoTDB community very active, but also has
ecological integration with many top level projects, such as spark, Flink,
etc. and IoTDB has been put into production and application by many
enterprises.

Cheers,
Jincheng

Julian Feinauer  于2020年8月24日周一 下午11:09写道：

> Hi,
>
> I am no Mentor but rather a community member but speaking in my Role as
> IPMC Member I agree with Chris and Kevin and also think the project and the
> community are in good shape and we are ready for graduation.
>
> Julian
>
> Am 24.08.20, 14:37 schrieb "Willem Jiang" :
>
> +1. I think IotDB is close to graduation :).
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Aug 23, 2020 at 5:04 PM Christofer Dutz
>  wrote:
> >
> > Hi all,
> >
> > I think the project is in great shape and I would happily support
> its graduation.
> >
> > Chris
> > 
> > Von: Xiangdong Huang 
> > Gesendet: Sonntag, 23. August 2020 05:45
> > An: dev ; Justin Mclean <
> jus...@classsoftware.com>
> > Betreff: Re: [DISCUSS] discuss about graduation of Apache IoTDB
> (incubating)
> >
> > Hi everyone,
> >
> > After about one month effort, we finish releasing v0.10.1, which
> exposing
> > some
> > new issues of releasing the project and finally we have fixed them.
> >
> > As about two months have passed since our first discussion about
> graduation,
> > I‘d like to recall this discussion and listen to all of your
> opinions.
> >
> > Thanks
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Dawei Liu  于2020年7月9日周四 上午11:32写道：
> >
> > > Hi,
> > >
> > >
> > > Time flies, I have been work together with all of you for 8 months.
> > >
> > >
> > > I feel connected with the culture of Apache-way. The culture is of
> benefit
> > > to me.
> > >
> > >
> > > I was back to the community end of June after two months of busy
> work in
> > > my company ,
> > > happily finding there is a big improvement in query and write
> performance
> > > of the Master branch.
> > >
> > >
> > > I see a lot of new faces , fresh-up and energetic,
> > > from which I can see the bright future of our IoTDB community.
> > >
> > >
> > > I will be really happy if we reach the demand of graduation.
> > >
> > >
> > > Thanks
> > > ——
> > > Dawei Liu
> > >
> > >
> > > On 07/7/2020 15:30，Christofer Dutz
> wrote：
> > > I for my part am very happy with the progress the project made.
> > >
> > > Taking the amount of "pointing out stuff"-emails (TM) I have to
> write
> > > (Which is almost 0) I wouldn't have any issues right now voting +1
> on your
> > > graduation.
> > >
> > > Chris
> > >
> > >
> > > Am 07.07.20, 08:55 schrieb "Julian Feinauer" <
> > > j.feina...@pragmaticminds.de>:
> > >
> > > Hi,
> > >
> > > thanks for your feedback Justin and I would also be very
> interested in
> > > hearing your opinion on the maturity.
> > > As I'm no mentor and pretty involved in the community know I feel
> that the
> > > community is mature enough but as with every young project, there
> are
> > > always things to improve.
> > >
> > > But I think ist a good point in time now to get some feedback and
> improve
> > > specifics that we are still lacking.
> > >
> > > Julian
> > >
> > > Am 07.07.20, 06:07 schrieb "Justin Mclean" <
> jus...@classsoftware.com>:
> > >
> > > Hi,
> > >
> > > I think the project have made very good progress, but it might be
> a little
> > > bit early to graduate. I’ve have a look over things in a little
> more detail
> > > over the next couple of days and see if that changes my mind.
> > >
> > > Thanks,
> > > Justin
> > >
> > >
> > >
>
>

Re: Re: [VOTE] Start the graduation process

[jincheng sun]

+1 from PPMC

Best,
Jincheng


Tian Jiang  于2020年8月31日周一 上午11:21写道：

> Greetings,
>
>
> +1 from PPMC
>
>
> Best
> Tian Jiang
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> At 2020-08-31 10:27:59, "Ray"  wrote:
> >+1
> >
> >
> >Regards,
> >Lei Rui
> >
> >
> >On 8/30/2020 20:46，Julian Feinauer wrote：
> >Hi folks,
> >
> >as we just had a very positive discussion about the maturity of our
> community [1] I want to formally start the vote if we want to start the
> graduation process.
> >
> >For Information about our maturity assessment please see [2].
> >
> >Do you agree that the IoTDB project is ready for graduation and that we
> should start the graduation process now?
> >
> >As usual, this vote will be open for at least 72hrs.
> >
> >Best
> >Julian
> >
> >
> >
> >[1]
> https://lists.apache.org/thread.html/r7607cbf6ff2020dc7e7cc27eb698ce265b768ed2a63d3e353c2dc572%40%3Cdev.iotdb.apache.org%3E
> >[2]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148645763
> >
>

Re: refactor the modules (for thrift and antlr code generation)

[jincheng sun]

+1 for the proposal, Thanks for bring up this discussion Xiangdong!

Best,
Jincheng


Julian Feinauer  于2020年6月29日周一 下午3:41写道：

> Hi,
>
> good point, I agree.
>
> Julian
>
> Am 29.06.20, 09:03 schrieb "Xiangdong Huang" :
>
> Hi,
>
> > we could also consider migrating to protobuf and grpc then as I like
> their maven plugin and it really works flawlessly (and downloads the
> protoc
> automagically).
>
> I think we can postpone the discussion about the replacement after the
> cluster module is merged... It will be a disaster if we do that now.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Julian Feinauer  于2020年6月29日周一 下午2:58写道：
>
> > Hi,
> >
> > we could also consider migrating to protobuf and grpc then as I like
> their
> > maven plugin and it really works flawlessly (and downloads the protoc
> > automagically).
> >
> > But I would also be fine with extracting it.
> >
> > Julian
> >
> > Am 29.06.20, 08:30 schrieb "Xiangdong Huang" :
> >
> > Hi,
> >
> > I suffer from this issue for a long time:
> >
> > When I checkout to some branch where the version is
> xxx-SNAPSHOT and
> > want
> > to run the source codes on the branch in IDE (IDEA), I have to
> run `mvn
> > generate-sources` first to generate the thrift and antlr4 codes,
> > otherwise,
> > the IDEA will say some classes are not found.
> >
> > However, if the xxx-SNAPSHOT.jar is not on my local maven repo,
> `mvn
> > generate-sources` will fail because the dependency `tsfile.jar`
> is not
> > found...
> > Then I have to run `mvn package -DskipTests` and waste several
> minutes
> > for
> > waiting the compiler.
> >
> > I'd like to extract the .thrift file and .g4 file separately
> into two
> > new
> > modules (without any other module dependencies except for thrift
> and
> > antlr), so that we can run `mvn generate-sources` successfully
> and save
> > time..
> >
> > how do you think?
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
>
>

Re: [ANNOUNCE] Add Jincheng Sun as a new PPMC of IoTDB

[jincheng sun]

Thank you everyone for your warm welcome!

Best,
Jincheng


Xin Wang  于2020年5月12日周二 下午4:43写道：

> Congrats Jincheng!
>
>
>
> Dawei Liu  于2020年5月12日周二 下午4:37写道：
>
> >
> >
> > wow，Congratulations.
> >
> >
> >
> >
> > Thanks
> > 
> > Dawei Liu
> > On 05/12/2020 16:32，Wei Zhong wrote：
> > Congratulations, Jincheng!
> >
> > Best,
> > Wei
> >
> > 在 2020年5月12日，15:56，Xiangdong Huang  写道：
> >
> > Hi all,
> >
> > I am pleased to announce that after discussion and vote among PPMC
> groups,
> > and publicity on IPMC mailing list, Jincheng Sun is nominated as a new
> PPMC
> > of IoTDB.
> >
> > Jincheng Sun has joined the IoTDB community for more than 6 months and is
> > always active in the mailing list.
> >
> > Benefit from his experience of being a Flink PMC (and Apache Member
> > recently), he pointed out many mistakes in IoTDB's documents/website and
> > devoted himself to integrate IoTDB with Apache Flink.
> >
> > Jincheng Sun knows Apache way well and has rich experience working on
> large
> > projects (e.g., Flink), we look forward to his contribution in the
> future.
> >
> > Now we have 24 PPMC totally, which come from Tsinghua University,
> > PragmaticMinds, Alibaba, Microsoft, K2Data, ByteDance, Tencent and
> NELBDS.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> > 黄向东
> > 清华大学 软件学院
> >
>
>
> --
> Thanks,
> Xin
>

Re: new committer:Yuyuan Kang

[jincheng sun]

Congrats and welcome Yuyuan!

+1 for an online Meetup.

Best,
Jincheng



Julian Feinauer  于2020年5月14日周四 下午2:37写道：

> Hi,
>
> what about a (virtual) Online Meetup?
> We can also discuss whether we want to do an english one or you do a
> separate Chinese one (may be easier for some community members, I guess).
>
> What do you think?
> I would also love to hang around with you guys!
>
> Julian
>
> Am 14.05.20, 04:15 schrieb "Dawei Liu" :
>
> Wow,
>
>
> When is a community meeting up? I can't wait to see you
>
>
>
>
> Thanks
> --
> Dawei Liu
> On 05/14/2020 09:54，runhus...@foxmail.com
> wrote：
> Congrats!
>
>
>
> Thanks!
>
> runhus...@foxmail.com
>
> From: Haonan Hou
> Date: 2020-05-14 09:43
> To: dev@iotdb.apache.org
> Subject: Re: new committer:Yuyuan Kang
> Congrats!
>
> Best,
> Haonan
>
> On May 14, 2020, at 9:41 AM, Xin Wang  wrote:
>
> Congrats Yuyuan!
>
>
>
> Jialin Qiao 于2020年5月14日 周四09:18写道：
>
> Hi,
>
>
> The Project Management Committee (PMC) for Apache IoTDB
> has invited Yuyuan Kang to become a committer and we are pleased
> to announce that he has accepted.
>
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
> Being a PMC member enables assistance with the management
> and to guide the direction of the project.
>
>
> You could get the write-access of our repository by:
>
>
> (1) Update your github id in: id.apache.org , also an email (anything
> to
> your apache email will forwart to this email).
> (2) Accept the invitation in github to being a member of the apache
> group.
> (3) Link your accounts via: git.apache.org (To lighten the third
> option
> MFA Status, you need to download Google Authenticator (Google 身份验证器) in
> your mobile)
> (4）Sign in github by Google Authenticator
> (5) Clone repository with ssh.
>
>
> Yours,
> The Apache IoTDB PPMC
>
> --
> Thanks,
> Xin
>
>
>

Re: [RESULT] [VOTE] Add Apache Flink Connector Support for TsFile

[jincheng sun]

Thanks Xiangdong!

I have added design documents to the Wiki [1] , but I find we can have some
improvement for the current document structure. Would be good If we can
discuss the organization of Wiki document structure in the future.

Feel free to change the location of [1] in Wiki page if you have a better
idea :)

Best,
Jincheng

[1]
https://cwiki.apache.org/confluence/display/IOTDB/%5BImprovement+Proposal%5D+Add+Flink+Connector+Support+for+TsFile


Xiangdong Huang  于2020年3月17日周二 下午4:25写道：

> Hi jincheng,
>
> I have added the edit permission to you.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2020年3月17日周二 上午11:18写道：
>
> > Hi everyone,
> >
> > The vote has been closed now. The following 9 person have voted +1 :
> >
> > - Xiangdong Huang
> > - Xin Wang
> > - Zesong Sun
> > - Jialin Qiao
> > - Jack Tsai
> > - Wei Zhong
> > - Willem Jiang
> > - Dawei Liu
> > - Haonan Hou
> >
> > There were no -1 or +0 votes.
> >
> > Therefore, I'm happy to announce that the proposal has been accepted.
> >
> > Thanks for Willem Jiang's reminder, I will update the design document[1]
> to
> > [2]. BTW, I am appreciate if anyone can give me edit permission of [2].
> >
> > Best,
> > Jincheng
> > [1]
> >
> >
> https://docs.google.com/document/d/1h0_aGboUCqlke-CdSKy1yNCsHTBKhw3JHWlwLBtbmGU/edit?usp=sharing
> > [2] https://cwiki.apache.org/confluence/display/iotdb
> >
>

[RESULT] [VOTE] Add Apache Flink Connector Support for TsFile

[jincheng sun]

Hi everyone,

The vote has been closed now. The following 9 person have voted +1 :

- Xiangdong Huang
- Xin Wang
- Zesong Sun
- Jialin Qiao
- Jack Tsai
- Wei Zhong
- Willem Jiang
- Dawei Liu
- Haonan Hou

There were no -1 or +0 votes.

Therefore, I'm happy to announce that the proposal has been accepted.

Thanks for Willem Jiang's reminder, I will update the design document[1] to
[2]. BTW, I am appreciate if anyone can give me edit permission of [2].

Best,
Jincheng
[1]
https://docs.google.com/document/d/1h0_aGboUCqlke-CdSKy1yNCsHTBKhw3JHWlwLBtbmGU/edit?usp=sharing
[2] https://cwiki.apache.org/confluence/display/iotdb

Re: [VOTE] Add Flink Connector Support for TsFile

[jincheng sun]

Thanks everyone for voting. I'm closing the vote now and will post the
result as a separate email.

Best,
Jincheng


Haonan Hou  于2020年3月13日周五 上午12:22写道：

> Hi,
>
> +1 Sounds like a good idea！
>
> Best,
> Haonan Hou
>
> > On Mar 12, 2020, at 9:10 PM, Dawei Liu  wrote:
> >
> > Hi,
> >
> >
> > +1
> >
> > Look forward to the implementation!
> >
> >
> > Thanks
> > ---
> > Dawei Liu
> >
> >
> >
> >> 2020年3月12日 下午8:06，Willem Jiang  写道：
> >>
> >> +1.
> >> Just quick suggestion for the proposal document , we can use
> >> cwiki.apache.org/iotdb to host this kind of documentation.
> >>
> >> Willem Jiang
> >>
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >> On Thu, Mar 12, 2020 at 10:37 AM jincheng sun 
> wrote:
> >>>
> >>> Hi folks,
> >>>
> >>> As we discussed in [1], please vote on the proposal to add Flink
> Connector
> >>> Support for TsFile, and the corresponding design doc [2].
> >>>
> >>> Please vote accordingly:
> >>>
> >>> [ ] +1 approve
> >>> [ ] +0 no opinion
> >>> [ ] -1 disapprove with the reason
> >>>
> >>> The vote is open for the next 72 hours and passes if at least three +1
> >>> votes and more +1 votes than -1 votes.
> >>>
> >>> Best,
> >>> Jincheng
> >>>
> >>> [1]
> >>>
> https://lists.apache.org/thread.html/r6dd6afe4e8e4ca42e3ddfbc80609597788f90b214e7a81788c3b51b3%40%3Cdev.iotdb.apache.org%3E
> >>> [2]
> >>>
> https://docs.google.com/document/d/1h0_aGboUCqlke-CdSKy1yNCsHTBKhw3JHWlwLBtbmGU/edit?usp=sharing
> >
>
>

Re: [VOTE] Add Flink Connector Support for TsFile

[jincheng sun]

Thanks for the reminder Willem Jiang! I would like to  add this design doc
to cwiki.apache.org/iotdb  after the VOTE passed. :)

Best,
Jincheng


Willem Jiang  于2020年3月12日周四 下午8:06写道：

> +1.
> Just quick suggestion for the proposal document , we can use
> cwiki.apache.org/iotdb to host this kind of documentation.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Mar 12, 2020 at 10:37 AM jincheng sun 
> wrote:
> >
> > Hi folks,
> >
> > As we discussed in [1], please vote on the proposal to add Flink
> Connector
> > Support for TsFile, and the corresponding design doc [2].
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > The vote is open for the next 72 hours and passes if at least three +1
> > votes and more +1 votes than -1 votes.
> >
> > Best,
> > Jincheng
> >
> > [1]
> >
> https://lists.apache.org/thread.html/r6dd6afe4e8e4ca42e3ddfbc80609597788f90b214e7a81788c3b51b3%40%3Cdev.iotdb.apache.org%3E
> > [2]
> >
> https://docs.google.com/document/d/1h0_aGboUCqlke-CdSKy1yNCsHTBKhw3JHWlwLBtbmGU/edit?usp=sharing
>

[VOTE] Add Flink Connector Support for TsFile

[jincheng sun]

Hi folks,

As we discussed in [1], please vote on the proposal to add Flink Connector
Support for TsFile, and the corresponding design doc [2].

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

The vote is open for the next 72 hours and passes if at least three +1
votes and more +1 votes than -1 votes.

Best,
Jincheng

[1]
https://lists.apache.org/thread.html/r6dd6afe4e8e4ca42e3ddfbc80609597788f90b214e7a81788c3b51b3%40%3Cdev.iotdb.apache.org%3E
[2]
https://docs.google.com/document/d/1h0_aGboUCqlke-CdSKy1yNCsHTBKhw3JHWlwLBtbmGU/edit?usp=sharing

Re: [DISCUSS] Add Flink Connector Support for TsFile

[jincheng sun]

Hi folks,

I would like to bring up the VOTE thread as there no objections feedback
both in mailing list and design doc for a long time.

Best,
Jincheng



jincheng sun  于2020年2月28日周五 下午11:01写道：

> Hi folks,
>
> TsFile is a columnar storage file format in Apache IoTDB. It is designed
> for time series data and  supports efficient compression and query and is
> easy to be integrated into big data processing frameworks.
>
> Apache Flink is a framework and distributed processing engine for stateful
> computations over unbounded and bounded data streams and becoming more and
> more popular in IOT scenes. So, it would be great to integrate IoTDB and
> Flink.
>
> I would like to introduce the TsFile Flink Connector, i.e., allows Flink
> to read, write TsFile, the detail can be found in the design doc [1].
>
> Welcome any feedback and comments in design doc.
>
> Best,
> Jincheng
>
> [1]
> https://docs.google.com/document/d/1h0_aGboUCqlke-CdSKy1yNCsHTBKhw3JHWlwLBtbmGU/edit?usp=sharing
>
>

Re: [DISCUSS] Remove PropertyPlan and PTree?

[jincheng sun]

Hi Zesong，

Thanks for bring up this discussion!

+1 for your proposal!

Best,
Jincheng



Xiangdong Huang  于2020年2月11日周二 下午9:39写道：

> Hi,
>
> +1. We can pick the removed codes back from the git repo if really
> necessary in the future.
>
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Jialin Qiao  于2020年2月11日周二 下午5:48写道：
>
> > Hi
> >
> > The property tree is a semi-finished function, whose use cases are not
> > clear. I suggest removing it.
> >
> > Thanks,
> > —
> > Jialin Qiao
> > School of Software, Tsinghua University
> >
> > 乔嘉林
> > 清华大学 软件学院
> >
> >
> > 孙泽嵩  于2020年2月11日周二 上午10:08写道：
> >
> > > Hi all,
> > >
> > > I’m currently working on refactoring MManager [1] , when I found that
> the
> > > codes of PTree is a little bit confused.
> > >
> > > It is used in PropertyPlan but I did not find related documents or user
> > > guides except some are used in test codes like:
> > >
> > > "CREATE PROPERTY property1"
> > > "ADD LABEL label1 TO PROPERTY property1"
> > > "DELETE LABEL label1 FROM PROPERTY property1"
> > > "LINK root.m1.m2 TO property1.label1"
> > > "UNLINK root.m1.m2 FROM property1.label1”
> > >
> > > Do you think these statements are useful in the future? Or do you think
> > > PTree and PropertyPlan codes could be removed?
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IOTDB-274# <
> > > https://issues.apache.org/jira/browse/IOTDB-274#>
> > >
> > >
> > > Best,
> > > ---
> > > Zesong Sun
> > > School of Software, Tsinghua University
> > >
> > > 孙泽嵩
> > > 清华大学 软件学院
> > >
> > >
> >
>

Re: About changing Github description topics

[jincheng sun]

Thanks for bring up this discussion!

+1 for add more git hub topics for IoTDB.

I think the examples which Xiangdong mentioned is pretty good. In addition,
we can also add language information, such as: Python, Java, Scala

Best,
Jincheng


Xiangdong Huang  于2020年2月8日周六 下午9:48写道：

> Hi,
>
> +1.  Let's discuss what topics we need to add.
>
> E.g., TimeSeries, TSDB,TimeSeriesDatabase, database, IoT, NoSQL, etc..
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> atoiLiu  于2020年2月8日周六 下午8:20写道：
>
> > Hi，
> >
> > I noticed that IotDB's github topics were not set, which would greatly
> > affect the search.
> >
> > If I'm a person looking for a management solution for time series data,
> > when I search for timeseries on github, IoTDB will not recommended as
> > relevant content to users.
> >
> > I've looked at other apache projects, and they all have Settings, like
> > Flink, and what they set is:
> > Scala Java big-data flink
> >
> > but we only set up IoTDB.
> >
> > Therefore, I suggest adding the following items:
> >
> > database timeseries iot iov big-data Java
> >
> > Any other Suggestions？
>

Re: [ANNOUNCE] Welcome two new committers: Jincheng Sun and Haonan Hou

[jincheng sun]

Thanks Xiangdong,

Really happy to be onboard! It is really a pleasure working with you and
the community.

Congratulations Haonan!

Best,
Jincheng


Xiangdong Huang  于2020年2月5日周三 上午9:00写道：

> Hi folks,
>
> In January, two contributors became IoTDB's new committer: Jincheng Sun and
> Haonan Hou.
>
> They are our 29th and 30th committers.
>
> Jincheng Sun made effort to the community building, contains the JIRA
> management, website info  etc..
>
> Jincheng is also one of Apache Flink PMCs, which make it easier to
> integration IoTDB with Flink.
>
> Haonan Hou made effort to the query engine of IoTDB and the TsFile module.
>
> Welcome them and look forward to more new committers.
>
> Cheers,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>

Re: [QUESTION] The roster page shows "not listed as an incubator committer" message

[jincheng sun]

I see. It seems that it's my ICLA problem, i.e, this is a special case. As
long as it does not need to be added manually every time, there is no need
for the documentation. :)  Thanks again Justin :)

Best,
Jincheng


Justin Mclean  于2020年1月31日周五 下午7:09写道：

> Hi,
>
> > BTW: There is no mention in the new committer process document [1] of
> > adding the committer of the incubator project to the incubator Committee.
>
> It should happen automatically I think, I’ve never had to do this before.
> it may depend on what was put in the ICLA?
>
> Thanks,
> Justin

Re: [QUESTION] The roster page shows "not listed as an incubator committer" message

[jincheng sun]

Hi Justin,

The message "not listed as an incubator committer". is gone. Thanks Justin!
:)

BTW: There is no mention in the new committer process document [1] of
adding the committer of the incubator project to the incubator Committee.
Are there any documents like new incubator committer process to introduce
how to add an incubator’s committer?

Best,
Jincheng

[1] http://community.apache.org/newcommitter.html#new-committer-process

 于2020年1月31日周五 下午3:59写道：

> Hi,
>
> Not a big issue they just had to be added an a s incubator committer. I’ve
> done that.
>
> Thanks,
> Justin

Re: [QUESTION] The roster page shows "not listed as an incubator committer" message

[jincheng sun]

Hi,

I checked the innovator general mailing list and found that the following
information is more useful:

>If PPMC members who don't happen to be IPMC members are authorized to add 
>committers, they will be unable to update the list of committers for the 
>incubator.

more detail can be found in [1].

Which meant that IPMC can update the list of committers for the incubator.
After all, IoTDB has developed a lot of committers. If there is a problem,
the problem should have been found for a long time.
So, I just add some input here. :)

[1]
http://mail-archives.apache.org/mod_mbox/incubator-general/201705.mbox/%3CCAFG6u8FwYART_gZGrpcBMCU8B910X33+nAMmro_v=9x8tbc...@mail.gmail.com%3E


jincheng sun  于2020年1月31日周五 下午2:24写道：

> I checked some document, but I didn't find a solution :(
>
> I think @Justin Mclean   will be more clear and
> can give us more guidance.
> Or CC the mail to `gene...@incubator.apache.org` later if necessary.
>
> Best,
> Jincheng
>
> jincheng sun  于2020年1月31日周五 下午1:09写道：
>
>> I think that tips show that I am not listed in the page [1].
>>
>> Best,
>> Jincheng
>>
>> [1] https://people.apache.org/phonebook.html?unix=incubator
>>
>>
>> Xiangdong Huang  于2020年1月31日周五 上午11:56写道：
>>
>>> Hi,
>>>
>>> I added Jincheng Sun as a new committer on [1] yesterday.
>>> He had Apache ID already.
>>>
>>> However, the page shows a message "not listed as an incubator committer".
>>>
>>> Does someone know why and how to fix?
>>>
>>> [1] https://whimsy.apache.org/roster/ppmc/iotdb#committers
>>>
>>> Best,
>>> ---
>>> Xiangdong Huang
>>> School of Software, Tsinghua University
>>>
>>>  黄向东
>>> 清华大学 软件学院
>>>
>>

Re: [QUESTION] The roster page shows "not listed as an incubator committer" message

[jincheng sun]

I checked some document, but I didn't find a solution :(

I think @Justin Mclean   will be more clear and
can give us more guidance.
Or CC the mail to `gene...@incubator.apache.org` later if necessary.

Best,
Jincheng

jincheng sun  于2020年1月31日周五 下午1:09写道：

> I think that tips show that I am not listed in the page [1].
>
> Best,
> Jincheng
>
> [1] https://people.apache.org/phonebook.html?unix=incubator
>
>
> Xiangdong Huang  于2020年1月31日周五 上午11:56写道：
>
>> Hi,
>>
>> I added Jincheng Sun as a new committer on [1] yesterday.
>> He had Apache ID already.
>>
>> However, the page shows a message "not listed as an incubator committer".
>>
>> Does someone know why and how to fix?
>>
>> [1] https://whimsy.apache.org/roster/ppmc/iotdb#committers
>>
>> Best,
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>>
>>  黄向东
>> 清华大学 软件学院
>>
>

Re: [DISCUSS] How to fix the BUILD-FAILURE(can not sending mail to unregistered user)

[jincheng sun]

Hi Xiangdong,

Thank you for your help in checking. I think the configuration item is a
global configuration and requires administrator role of Jenkins.
The detail can be found in [1] [2].  At the moment I'm not sure if I can
set IoTDB separately. But from my point of view, other projects
should also open this configuration item, and the global configuration is
also reasonable. What do you think?


Best,
Jincheng

[1]
https://issues.apache.org/jira/secure/attachment/12992297/image-2020-01-31-13-17-44-677.png
[2]
https://issues.apache.org/jira/secure/attachment/12992298/image-2020-01-31-13-18-18-411.png

Xiangdong Huang  于2020年1月31日周五 上午11:55写道：

> Hi jincheng,
>
> I have replyed to you on the Jira.
> It is quite strange. Why you are considered as  unregistered user..
> Besides, I can not find the configuration you mentioned.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2020年1月31日周五 上午11:52写道：
>
> > Hi folks,
> >
> > I found that IoTDB‘s Jenkins occasionally had the following exceptions
> > during build:
> >
> > > Not sending mail to unregistered user ruileisurpr...@gmail.com because
> > your SCM claimed this was associated with a user ID ‘ruileisurprise'
> which
> > your security realm does not recognize; you may need changes in your SCM
> > plugin
> >
> > The detail can be found in [1] [2] [3] .
> >
> > I think it's Jenkins configuration problem, such as:
> >
> >1. Edit the following two system properties in jenkins's script:
> >
> >-Dhudson.tasks.MailSender.SEND_TO_UNKNOWN_USERS=true
> >-Dhudson.tasks.MailSender.SEND_TO_USERS_WITHOUT_READ=true
> >
> >   2. Edit the configuration in jenkins's console:
> >  "Manage Jenkins -> Configure System -> Extended E-mail Notification"
> > The detail can be found in [5].
> >
> > I don't have Jenkins' editing permission, so I'm very grateful if someone
> > with permission can help me check whether the above configuration is
> > effective. Or is there a better way?
> >
> > What do you think?
> >
> > Best,
> > Jincheng
> >
> > [1] https://builds.apache.org/job/IoTDB%20Website/87/console
> > [2] https://builds.apache.org/job/IoTDB%20Website/104/console
> > [3] https://builds.apache.org/job/IoTDB%20Website/108/console
> > [4] https://issues.apache.org/jira/browse/IOTDB-437
> > [5]
> >
> >
> https://issues.apache.org/jira/secure/attachment/12992293/image-2020-01-31-11-41-20-213.png
> >
>

Re: [QUESTION] The roster page shows "not listed as an incubator committer" message

[jincheng sun]

I think that tips show that I am not listed in the page [1].

Best,
Jincheng

[1] https://people.apache.org/phonebook.html?unix=incubator


Xiangdong Huang  于2020年1月31日周五 上午11:56写道：

> Hi,
>
> I added Jincheng Sun as a new committer on [1] yesterday.
> He had Apache ID already.
>
> However, the page shows a message "not listed as an incubator committer".
>
> Does someone know why and how to fix?
>
> [1] https://whimsy.apache.org/roster/ppmc/iotdb#committers
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>

Re: [RESULT][VOTE] Add the components definition in JIRA template

[jincheng sun]

Hi Xiangdong,

Thank you for helping to add components to JIRA. I've checked it, and it's
working now. :)

Best,
Jincheng


Xiangdong Huang  于2020年1月29日周三 下午3:01写道：

> Hi jincheng,
>
> I tried and I can set that. :D
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2020年1月29日周三 上午11:41写道：
>
> > I appreciate if anyone can help to check whether PPMC has the authority
> to
> > operate [1] :)
> >
> > [1]
> >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/components
> >
> > Best,
> > Jincheng
> >
> >
> > jincheng sun  于2020年1月29日周三 上午11:39写道：
> >
> > > Hi everyone,
> > >
> > > The vote has been closed now. The following 4 person have voted +1 :
> > >
> > > - Jialin Qiao
> > > - Zesong Sun
> > > - Jincheng Sun
> > > - Xiangdong Huang
> > >
> > > There were no -1 or +0 votes.
> > >
> > > Therefore, I'm happy to announce that the proposal has been accepted.
> > >
> > > I have created the Infrastructure JIRA [1]. Let's push it forward :)
> > >
> > > Best,
> > > Jincheng
> > >
> > > [1] https://issues.apache.org/jira/browse/INFRA-19761
> > >
> >
>

Re: [RESULT][VOTE] Add the components definition in JIRA template

[jincheng sun]

Cool，sounds pretty good！
Best，Jincheng

Xiangdong Huang 于2020年1月29日 周三15:01写道：

> Hi jincheng,
>
> I tried and I can set that. :D
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2020年1月29日周三 上午11:41写道：
>
> > I appreciate if anyone can help to check whether PPMC has the authority
> to
> > operate [1] :)
> >
> > [1]
> >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/components
> >
> > Best,
> > Jincheng
> >
> >
> > jincheng sun  于2020年1月29日周三 上午11:39写道：
> >
> > > Hi everyone,
> > >
> > > The vote has been closed now. The following 4 person have voted +1 :
> > >
> > > - Jialin Qiao
> > > - Zesong Sun
> > > - Jincheng Sun
> > > - Xiangdong Huang
> > >
> > > There were no -1 or +0 votes.
> > >
> > > Therefore, I'm happy to announce that the proposal has been accepted.
> > >
> > > I have created the Infrastructure JIRA [1]. Let's push it forward :)
> > >
> > > Best,
> > > Jincheng
> > >
> > > [1] https://issues.apache.org/jira/browse/INFRA-19761
> > >
> >
>
-- 

Best,
Jincheng
-
Twitter: https://twitter.com/sunjincheng121
-

Re: [RESULT][VOTE] Add the components definition in JIRA template

[jincheng sun]

I appreciate if anyone can help to check whether PPMC has the authority to
operate [1] :)

[1]
https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/components

Best,
Jincheng


jincheng sun  于2020年1月29日周三 上午11:39写道：

> Hi everyone,
>
> The vote has been closed now. The following 4 person have voted +1 :
>
> - Jialin Qiao
> - Zesong Sun
> - Jincheng Sun
> - Xiangdong Huang
>
> There were no -1 or +0 votes.
>
> Therefore, I'm happy to announce that the proposal has been accepted.
>
> I have created the Infrastructure JIRA [1]. Let's push it forward :)
>
> Best,
> Jincheng
>
> [1] https://issues.apache.org/jira/browse/INFRA-19761
>

[RESULT][VOTE] Add the components definition in JIRA template

[jincheng sun]

Hi everyone,

The vote has been closed now. The following 4 person have voted +1 :

- Jialin Qiao
- Zesong Sun
- Jincheng Sun
- Xiangdong Huang

There were no -1 or +0 votes.

Therefore, I'm happy to announce that the proposal has been accepted.

I have created the Infrastructure JIRA [1]. Let's push it forward :)

Best,
Jincheng

[1] https://issues.apache.org/jira/browse/INFRA-19761

Re: [VOTE] Add the components definition in JIRA template

[jincheng sun]

Thanks everyone for voting. I'm closing the vote now and will post the
result as a separate email.

Best,
Jincheng


Xiangdong Huang  于2020年1月29日周三 上午12:14写道：

> Hi, +1
>
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2020年1月27日周一 下午6:03写道：
>
> > +1
> >
> > Best,
> > Jincheng
> > -
> > Twitter: https://twitter.com/sunjincheng121
> > -
> >
> >
> > 孙泽嵩  于2020年1月26日周日 上午12:03写道：
> >
> > > +1
> > >
> > > Best,
> > > ---
> > > Zesong Sun
> > > School of Software, Tsinghua University
> > >
> > > 孙泽嵩
> > > 清华大学 软件学院
> > >
> > > > 2020年1月25日 11:44，Jialin Qiao  写道：
> > > >
> > > > Hi,
> > > >
> > > > +1
> > > >
> > > > jincheng sun  于2020年1月25日周六 上午9:09写道：
> > > >
> > > >> Hi folks,
> > > >>
> > > >> As we discussed in [1], please vote on the proposal to add component
> > > >> definition in JIRA template [2], and the corresponding component
> list
> > > is as
> > > >> follows:
> > > >>
> > > >> ---
> > > >> Connectors
> > > >> Connectors/Grafana
> > > >> Connectors/Spark-TsFile
> > > >> Connectors/Spark-IoTDB
> > > >> Connectors/Hive-tsfile
> > > >> Connectors/Hadoop-tsfile
> > > >>
> > > >> Client
> > > >> Client/Java
> > > >> Client/Python
> > > >>
> > > >> Planner
> > > >> Planner/sql parser
> > > >> Planner/sql optimizer
> > > >>
> > > >> Core
> > > >> Core/TsFile
> > > >> Core/Engine
> > > >> Core/WAL
> > > >>
> > > >> Tools
> > > >> Tools/Sync
> > > >> Tools/Other
> > > >>
> > > >> Authority
> > > >> Distribution
> > > >> Example
> > > >> WebSite
> > > >> Doc
> > > >> Other
> > > >> --
> > > >>
> > > >> Please vote accordingly:
> > > >>
> > > >> [ ] +1 approve
> > > >> [ ] +0 no opinion
> > > >> [ ] -1 disapprove with the reason
> > > >>
> > > >> The vote is open for the next 72 hours and passes if at least three
> +1
> > > >> votes and more +1 votes than -1 votes.
> > > >>
> > > >> Best,
> > > >> Jincheng
> > > >>
> > > >>
> > > >> [1]
> > > >>
> > > >>
> > >
> >
> https://lists.apache.org/thread.html/r6f1af2a913da3632255dc13e982c451d8434d1b953b2efc708ff548c%40%3Cdev.iotdb.apache.org%3E
> > > >> [2]
> > > >>
> > > >>
> > >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/components
> > > >>
> > > >
> > > >
> > > > --
> > > > —
> > > > Jialin Qiao
> > > > School of Software, Tsinghua University
> > > >
> > > > 乔嘉林
> > > > 清华大学 软件学院
> > >
> > >
> >
>

Re: [VOTE] Add the components definition in JIRA template

[jincheng sun]

+1

Best,
Jincheng
-
Twitter: https://twitter.com/sunjincheng121
-


孙泽嵩  于2020年1月26日周日 上午12:03写道：

> +1
>
> Best,
> ---
> Zesong Sun
> School of Software, Tsinghua University
>
> 孙泽嵩
> 清华大学 软件学院
>
> > 2020年1月25日 11:44，Jialin Qiao  写道：
> >
> > Hi,
> >
> > +1
> >
> > jincheng sun  于2020年1月25日周六 上午9:09写道：
> >
> >> Hi folks,
> >>
> >> As we discussed in [1], please vote on the proposal to add component
> >> definition in JIRA template [2], and the corresponding component list
> is as
> >> follows:
> >>
> >> ---
> >> Connectors
> >> Connectors/Grafana
> >> Connectors/Spark-TsFile
> >> Connectors/Spark-IoTDB
> >> Connectors/Hive-tsfile
> >> Connectors/Hadoop-tsfile
> >>
> >> Client
> >> Client/Java
> >> Client/Python
> >>
> >> Planner
> >> Planner/sql parser
> >> Planner/sql optimizer
> >>
> >> Core
> >> Core/TsFile
> >> Core/Engine
> >> Core/WAL
> >>
> >> Tools
> >> Tools/Sync
> >> Tools/Other
> >>
> >> Authority
> >> Distribution
> >> Example
> >> WebSite
> >> Doc
> >> Other
> >> --
> >>
> >> Please vote accordingly:
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove with the reason
> >>
> >> The vote is open for the next 72 hours and passes if at least three +1
> >> votes and more +1 votes than -1 votes.
> >>
> >> Best,
> >> Jincheng
> >>
> >>
> >> [1]
> >>
> >>
> https://lists.apache.org/thread.html/r6f1af2a913da3632255dc13e982c451d8434d1b953b2efc708ff548c%40%3Cdev.iotdb.apache.org%3E
> >> [2]
> >>
> >>
> https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/components
> >>
> >
> >
> > --
> > —
> > Jialin Qiao
> > School of Software, Tsinghua University
> >
> > 乔嘉林
> > 清华大学 软件学院
>
>

[VOTE] Add the components definition in JIRA template

[jincheng sun]

Hi folks,

As we discussed in [1], please vote on the proposal to add component
definition in JIRA template [2], and the corresponding component list is as
follows:

---
Connectors
Connectors/Grafana
Connectors/Spark-TsFile
Connectors/Spark-IoTDB
Connectors/Hive-tsfile
Connectors/Hadoop-tsfile

Client
Client/Java
Client/Python

Planner
Planner/sql parser
Planner/sql optimizer

Core
Core/TsFile
Core/Engine
Core/WAL

Tools
Tools/Sync
Tools/Other

Authority
Distribution
Example
WebSite
Doc
Other
--

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

The vote is open for the next 72 hours and passes if at least three +1
votes and more +1 votes than -1 votes.

Best,
Jincheng


[1]
https://lists.apache.org/thread.html/r6f1af2a913da3632255dc13e982c451d8434d1b953b2efc708ff548c%40%3Cdev.iotdb.apache.org%3E
[2]
https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/components

Re: [REPORT] Annual report of IoTDB 2019

[jincheng sun]

Hi folks,

Very happy to see the great achievements of IoTDB in the past year!
Congratulate!

With the advent of the 5G era, IoT will definitely set off a new wave, and
it will also be the era of IoTDB's grand development. In 2020, I wish the
IoTDB community a continuous state and grows, become a top level project of
Apache as soon as possible!

Happy new Chinese Year!

Best,
Jincheng
-
Twitter: https://twitter.com/sunjincheng121
-


Jack Tsai  于2020年1月24日周五 上午11:17写道：

> Hi,
>
> It’s been proud to be one of the IoTDB community. I really appreciate that
> IoTDB giving me the chance of being engaged in the open source environment
> last year. Happy Chinese New Year to you all!
>
> P.S. I will get back and continue my contribution soon after dealing with
> my personal stuff :-)
>
> Best,
> Jack Tsai
>
> 取得 iOS 版 Outlook
> 
> 寄件者: Xiangdong Huang 
> 寄件日期: Friday, January 24, 2020 1:29:59 AM
> 收件者: dev@iotdb.apache.org 
> 主旨: [REPORT] Annual report of IoTDB 2019
>
> Hi all,
>
> This is  the last day of ""己亥" (like 2019) in Chinese Lunar Calendar. And
> tomorrow is the Chinese New Year, "庚子" year.  Happy new year first of all.
>
> Jialin and I summaries the grows  of IoTDB, both the project and the
> community. The following is a brief report.
>
> *1. The project development.*
> *1.1 Release*
> - 5 versions (i.e., 2 major versions, 3 minor versions) are released:
> 0.8.0, 0.8.1, 0.8.2, 0.9.0, 0.9.1. Among those, 0.8.0 is the first Apache
> release version;
> - Totally we merged 731 PRs, solved 268 JIRA issues.
>  a. Now Github issues is opened.
>
> *1.2 Features*
> - Many new features are developed. Some important features are as follows:
>  a. Merge small files at the backend (Like LSM).
>  b. Partition data according to the time range.
>  c. Support HDFS storage.
>  d. Support TTL.
>  e. More statements for querying data schema.
>  f. Allow data being aligned on a device. Allow data being not aligned.
>  g. Automatically register time series.
>  h. Python API support.
>  i. Native API support.
>  j. Docker Image provided.
>  h. Upgrade data tool is provided.
> - Many other features are not listed. You can get them from the release
> notes:
> https://github.com/apache/incubator-iotdb/blob/master/RELEASE_NOTES.md
>
> *1.3 Improvements*
> - Many improvements and refactors are finished, which improve IoTDB's
> performance, stability and code readability.
>  a. Replace Thrift in TsFile's serialization. (called kill_Thanos in git
> repo)
>  b. Refactor the storage engine.
>  c.  Refactor the query engine (not finished).
>  d. Refactor the Schema/metadata management module.
>
> *2. What are not finished?*
> - The query engine is ongoing.
> - The distributed version is ongoing.
>
> *3. The community development.*
> *3.1 Committers.*
> - According to Github statistics, there are totally 53 contributors, 28 of
> them are committers and 23 of them are PPMCs.
>  a.  6 new committers are nominated, Julian Feinauer, Jack Tsai, Yuan Tian,
> Kaifeng Xue, Zesong Sun, Tianci Zhu.
>  b. 1 new PPMC is nominated, Julian Feinauer.
> - 4 persons played as Release Manager roles: Julian Feinauer (The First
> RM), Xiangdong Huang, Jialin Qiao, Lei Rui.
>
> *3.2 Mailing list*
> - For the dev@mailing list, there are 2945 emails sent by 162 people,
> divided into 1009 topics. The top 10 senders are:
>  a.  Xiangdong Huang: 565 email(s)
>  b. GitBox: 319 email(s) (:-D)
>  c. Julian Feinauer: 231 email(s)
>  d. Christofer Dutz: 172 email(s)
>  e. Jialin Qiao: 130 email(s)
>  f. Justin Mclean: 128 email(s)
>  g. Apache Jenkins Server: 127 email(s)
>  h. Jialin Qiao (Jira): 111 email(s)
>  i. Kevin A. McGrail: 60 email(s)
>  j. Yi Xu (徐毅): 50 email(s)
>
> *3.3 Reports*
> - 4 quarterly reports are submitted.
> - In 2019, we gave talks about IoTDB on Apache Con NA and EU.
> - In 2019 and China, we gave more than 10 talks about IoTDB on difference
> conference.
> - In Jan 2020, IoTDB meetups were hold together with RocketMQ and Pulsar,
> in Dalian and Beijing, China.
>
> *3.4 Awards*
> - IoTDB wined the award "The Most Popular Open Source Project Derive From
> China in 2019 Top 30"
> - IoTDB wined the award "The Excellent Open Source Project in China"
>
> *4. Users*
> - As we know, there are at least more than 10 companies are using IoTDB.
> E.g., Shanghai Metro (and now Chongqing Metro, and Jinan Metro has
> developed IoTDB), Lenovo, China Tower,  Gold Wind, COMAC (Chinese Airplane
> manufacturer),  DCITs, Sangfor, etc..
>
> Thanks so much for all of you, especially for our mentors Justin,
> Christofer, Kevin, and Willem Jiang!
> Thank Julian Feinauer gave the community so many helps!
> Thank all of Chinese contributors that letting IoTDB grows so quick!
> Thank all users that letting us know where IoTDB need to go!
> Thank all contributors that will appear in IoTDB community in the new year!
>
> We hope IoTDB can grows better and better in the new year. We hope 

Re: [DISCUSS] Add the components definition in JIRA template

[jincheng sun]

Great thanks for adding more relationship info about `Merge`  and
`Storage`.  @Xiangdong !

As :
> (now query engine is in the storage engine..) Merge is a submodule of
storage engine and query engine.

I think `query engine` and `storage engine` is make sense to me. Here only
a suggestion that how about use the `Engine` for both `Storage Engine` and
`Query Engine` as they are very close each other and they also have the
common share `Merge`. i.e.,:


Core
Core/TsFile
Core/Engine
Core/WAL
---

What to do you think?

Best,
Jincheng


--
1. --Connectors-
Connectors components include all data integration with external systems,
The components are listed as follows:

Connectors
Connectors/Grafana
Connectors/Spark-TsFile
Connectors/Spark-IoTDB
Connectors/Hive-tsfile
Connectors/Hadoop-tsfile

2. --Client-
Client components involves RPC between client and server, a command-line
interface（multi-languages).The components are listed as follows:

Client
Client/Java
Client/Python

3. --Planner-
Planner components involves the query process in IoTDB, including multiple
types of queries, such as raw data query, aggregations, group by time,
group by device, and includes many optimized rules.The components are
listed as follows:

Planner
Planner/sql parser
Planner/sql optimizer

4. --Core-
Core components is the storage engine of IoTDB. The components are listed
as follows:

Core
Core/TsFile
Core/Engine
Core/WAL

5. --Tools-
Tools components involves many utils of IoTDB, Such as data Sync. The
components are listed as follows:
Tools
Tools/Sync
Tools/Other

6. --Authority-
Authority

7. --Distribution--
Distribution

8. --Example---
Example

9. --WebSite---
WebSite

10. --Doc---
Doc

11. --Other
Other （I'm not sure if we really need the Other component, but there is no
harm in adding one）

Xiangdong Huang  于2020年1月17日周五 上午12:50写道：

> Hi,
>
> Thanks jincheng and jialin.
>
> Sorry for absence of the discussion because of  busy work these days..
>
> Some comments:
>
> > Core
> > Core/TsFile
> > Core/Merge
> > Core/Storage
> > Core/WAL
>
> Not so clearly.. maybe TsFile, WAL, Storage Engine, Query Engine? (now
> query engine is in the storage engine..)
> Merge is a submodule of storage engine and query engine.
> If we pick out the merge module, we also need to pick out the FLUSH,
> MODIFICATION, etc.. I think.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Jialin Qiao  于2020年1月16日周四 下午11:21写道：
>
> > Hi Jincheng,
> >
> > Thank you! Looks good :)
> >
> > jincheng sun  于2020年1月16日周四 下午4:01写道：
> >
> > > Thanks for your explanation! @Jialin
> > >
> > > I thought about the composition of our components from the external
> > system,
> > > the user level, to the IoTDB bottom-level implementation to the
> auxiliary
> > > tools, and I adjusted a little based on yours.  as follows:
> > >
> > > 1. --Connectors-
> > > Connectors components include all data integration with external
> systems,
> > > The components are listed as follows:
> > >
> > > Connectors
> > > Connectors/Grafana
> > > Connectors/Spark-TsFile
> > > Connectors/Spark-IoTDB
> > > Connectors/Hive-tsfile
> > > Connectors/Hadoop-tsfile
> > >
> > > 2. --Client-
> > > Client components involves RPC between client and server, a
> command-line
> > > interface（multi-languages).The components are listed as follows:
> > >
> > > Client
> > > Client/Java
> > > Client/Python
> > >
> > > 3. --Planner-
> > > Planner components involves the query process in IoTDB, including
> > multiple
> > > types of queries, such as raw data query, aggregations, group by time,
> > > group by device, and includes many optimized rules.The components are
> > > listed as follows:
> > >
> > > Planner
> > > Planner/sql parsar
> > > Planner/sql optimizer
> > >
> > > 4. --Core-
> > > Core components is the storage engine of IoTDB. The components are
> listed
> > > as follows:
> > >
> > > Core
> > > Core/TsFile
> > > Core/Merge
> > > Core/Storage
> > > Core/WAL
> > >
> > > 5. --Tools-
> > > Tools components involves many utils of IoTDB, Such as data Sync. The
> > > components are listed as

Re: [DISCUSS] Add the components definition in JIRA template

[jincheng sun]

Thanks for your explanation! @Jialin

I thought about the composition of our components from the external system,
the user level, to the IoTDB bottom-level implementation to the auxiliary
tools, and I adjusted a little based on yours.  as follows:

1. --Connectors-
Connectors components include all data integration with external systems,
The components are listed as follows:

Connectors
Connectors/Grafana
Connectors/Spark-TsFile
Connectors/Spark-IoTDB
Connectors/Hive-tsfile
Connectors/Hadoop-tsfile

2. --Client-
Client components involves RPC between client and server, a command-line
interface（multi-languages).The components are listed as follows:

Client
Client/Java
Client/Python

3. --Planner-
Planner components involves the query process in IoTDB, including multiple
types of queries, such as raw data query, aggregations, group by time,
group by device, and includes many optimized rules.The components are
listed as follows:

Planner
Planner/sql parsar
Planner/sql optimizer

4. --Core-
Core components is the storage engine of IoTDB. The components are listed
as follows:

Core
Core/TsFile
Core/Merge
Core/Storage
Core/WAL

5. --Tools-
Tools components involves many utils of IoTDB, Such as data Sync. The
components are listed as follows:
Tools
Tools/Sync
Tools/Other

6. --Authority-
Authority

7. --Distribution--
Distribution

8. --Example---
Example

9. --WebSite---
WebSite

10. --Doc---
Doc

11. --Other
Other （I'm not sure if we really need the Other component, but there is no
harm in adding one）

This does not change much from your solution. The core is to add a layer of
abstraction.

Does this make sense to you? Anyway we can continue to improve if needed!

Best,
Jincheng

Jialin Qiao  于2020年1月15日周三 下午4:28写道：

> Hi,
>
> WAL has an independent physical layout that has nothing to do with TsFile.
> It is used in the writing process and recovering in IoTDB.
> It could be merged into Storage components.
>
> I'm not sure whether I leave out some components, so I add an Other and
> therefore can not give an example...
>
> Thanks,
>
> jincheng sun  于2020年1月15日周三 下午4:01写道：
>
> > Sorry for the late reply, I just came back from team outing.
> >
> > Thanks for adding more detail information. I have two questions then:
> >
> > - Is WAL a write strategy for TsFlie, can WAL be incorporated into other
> > components and what is the reason for being a separate component?
> > - Can you give an example of what changes belongs to the Other component?
> >
> > Best,
> > Jincheng
> >
> >
> > Jialin Qiao  于2020年1月9日周四 下午6:39写道：
> >
> > > Hi,
> > >
> > > Sure, maybe a bit more...
> > >
> > >   - TsFile : A columnar file format that has flexible schema and data
> > > management for time series.
> > >   - Storage : The storage engine of IoTDB, including writing to
> memtable
> > > (buffer), flushing, system recovery, and memtable management.
> > >   - Query : The query process in IoTDB, including multiple types of
> > > queries, such as raw data query, aggregations, group by time, group by
> > > device.
> > >   - Merge : Compaction of data files, including multiple compaction
> > > strategies, such as (1) merging unsequence TsFile with sequence TsFile,
> > (2)
> > > merging small sequence TsFiles into a large TsFile.
> > >   - Sync: Synchronize data files from one IoTDB instance to another.
> > >   - Authority: Administration of IoTDB, including users, roles and
> > > privileges.
> > >   - WAL : Write-ahead-log.
> > >   - Client: Rpc between client and server, a command-line interface and
> > > client of different languages.
> > >   - Distribution : The shared-nothing distribution of IoTDB, including
> > raft
> > > protocol, data partition, and system information management.
> > >   - Grafana : The connector for using IoTDB as a data source in
> Grafana.
> > >   - Spark-TsFile : A connector that allows users read/write TsFile
> > through
> > > SparkSQL (treat TsFile as an external data source for SparkSQL).
> > >   - Spark-IoTDB : A connector that allows users read/write IoTDB
> through
> > > SparkSQL (treat IoTDB as an external data source for SparkSQL).
> > >   - Hive-tsfile : A connector that maps TsFile as a table in Hive for
> the
> > > query.
> > >   - Hadoop-tsfile : A connector that allows users read/write TsFile
> > through
> > > MapReduce.
> > >   - Tools : Other tools for IoTDB, such as watermark, memory
> estimation,
> > > JMX, query history visualizatio

Re: [DISCUSS] Add the components definition in JIRA template

[jincheng sun]

Sorry for the late reply, I just came back from team outing.

Thanks for adding more detail information. I have two questions then:

- Is WAL a write strategy for TsFlie, can WAL be incorporated into other
components and what is the reason for being a separate component?
- Can you give an example of what changes belongs to the Other component?

Best,
Jincheng


Jialin Qiao  于2020年1月9日周四 下午6:39写道：

> Hi,
>
> Sure, maybe a bit more...
>
>   - TsFile : A columnar file format that has flexible schema and data
> management for time series.
>   - Storage : The storage engine of IoTDB, including writing to memtable
> (buffer), flushing, system recovery, and memtable management.
>   - Query : The query process in IoTDB, including multiple types of
> queries, such as raw data query, aggregations, group by time, group by
> device.
>   - Merge : Compaction of data files, including multiple compaction
> strategies, such as (1) merging unsequence TsFile with sequence TsFile, (2)
> merging small sequence TsFiles into a large TsFile.
>   - Sync: Synchronize data files from one IoTDB instance to another.
>   - Authority: Administration of IoTDB, including users, roles and
> privileges.
>   - WAL : Write-ahead-log.
>   - Client: Rpc between client and server, a command-line interface and
> client of different languages.
>   - Distribution : The shared-nothing distribution of IoTDB, including raft
> protocol, data partition, and system information management.
>   - Grafana : The connector for using IoTDB as a data source in Grafana.
>   - Spark-TsFile : A connector that allows users read/write TsFile through
> SparkSQL (treat TsFile as an external data source for SparkSQL).
>   - Spark-IoTDB : A connector that allows users read/write IoTDB through
> SparkSQL (treat IoTDB as an external data source for SparkSQL).
>   - Hive-tsfile : A connector that maps TsFile as a table in Hive for the
> query.
>   - Hadoop-tsfile : A connector that allows users read/write TsFile through
> MapReduce.
>   - Tools : Other tools for IoTDB, such as watermark, memory estimation,
> JMX, query history visualization.
>   - Example : Examples of different modules, such as JDBC, Session, TsFile.
>   - WebSite : IoTDB official website.
>   - Doc: documents of IoTDB, docs folder under root directory.
>   - Other: Those do not belong to the above components.
>
>
> jincheng sun  于2020年1月9日周四 下午5:28写道：
>
> > Hi,
> >
> > @Xiangdong thank you for helping to clarify my original intention. you
> are
> > right, I really want to list some components to let users choose which
> > component the given issue belongs to.
> >
> > @Jialin I think approach 4 would be more meaningful for IoTDB. Could you
> > please add the detailed description for each component, such as, describe
> > the relationship between `tsfile` and
> > (`tsfile/hive-tsfile/spark-tsfile/Hadoop-tsfile`), and which changes
> belong
> > to `Other` component, etc., which can help us better understand the
> reasons
> > for such classification. On the other hand, we will further discuss
> whether
> > there is optimization space for this component classification.
> >
> > What do you think?
> >
> > Best,
> > Jincheng
> >
> > Xiangdong Huang  于2020年1月9日周四 下午4:46写道：
> >
> > > >  No that is not the Apache Way. No one should be in charge of an area
> > >
> > > I think Jincheng's mean is, we can list some components to let users
> > > choose which component the given issue belongs to.
> > >
> > > As for which components should be listed, we need to have a discussion.
> > >
> > > > No one should be in charge of an area
> > >
> > > Yes everyone can assign an issue to himself/herself.
> > >
> > > Best,
> > > --
> > > Xiangdong Huang
> > > School of Software, Tsinghua University
> > >
> > >  黄向东
> > > 清华大学 软件学院
> > >
> > >
> > > jincheng sun  于2020年1月9日周四 下午4:38写道：
> > >
> > > > > No that is not the Apache Way. No one should be in charge of an
> area.
> > > >
> > > > Oh, great thanks for correcting me Justin, maybe it's my language
> > > > expression problems. I mean some contributors and committers will be
> > very
> > > > interested in some components, then spend more time, and be more
> > familiar
> > > > with the code.
> > > >
> > > > Best,
> > > > Jincheng
> > > >
> > > >
> > > > Justin Mclean  于2020年1月9日周四 下午4:27写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > > When our community grows stronger, each\ module may have some
> > > specific
> > > > > person in charge.
> > > > >
> > > > > No that is not the Apache Way. No one should be in charge of an
> area.
> > > > >
> > > > > Thanks,
> > > > > Justin
> > > >
> > >
> >
>
>
> --
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>

Re: Please update the apache parent pom to version 22

[jincheng sun]

+1 to upgrade the version.

BTW: add the link [1] which more detail about `Reproducible Builds` that
Chris mentioned.

Best,
Jincheng

[1] http://maven.apache.org/pom/asf/


Christofer Dutz  于2020年1月9日周四 下午4:50写道：

> Hi all,
>
> the maven team just released version 22 of the apache parent.
> I would strongly suggest you update to this version. Not only because
> Apache in general likes projects to release using the latest apache parent.
> The main reason I think this is great is that with this you should
> automatically be creating reproducible builds when releasing.
>
> Chris
>

Re: [DISCUSS] Add the components definition in JIRA template

[jincheng sun]

Hi,

@Xiangdong thank you for helping to clarify my original intention. you are
right, I really want to list some components to let users choose which
component the given issue belongs to.

@Jialin I think approach 4 would be more meaningful for IoTDB. Could you
please add the detailed description for each component, such as, describe
the relationship between `tsfile` and
(`tsfile/hive-tsfile/spark-tsfile/Hadoop-tsfile`), and which changes belong
to `Other` component, etc., which can help us better understand the reasons
for such classification. On the other hand, we will further discuss whether
there is optimization space for this component classification.

What do you think?

Best,
Jincheng

Xiangdong Huang  于2020年1月9日周四 下午4:46写道：

> >  No that is not the Apache Way. No one should be in charge of an area
>
> I think Jincheng's mean is, we can list some components to let users
> choose which component the given issue belongs to.
>
> As for which components should be listed, we need to have a discussion.
>
> > No one should be in charge of an area
>
> Yes everyone can assign an issue to himself/herself.
>
> Best,
> --
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2020年1月9日周四 下午4:38写道：
>
> > > No that is not the Apache Way. No one should be in charge of an area.
> >
> > Oh, great thanks for correcting me Justin, maybe it's my language
> > expression problems. I mean some contributors and committers will be very
> > interested in some components, then spend more time, and be more familiar
> > with the code.
> >
> > Best,
> > Jincheng
> >
> >
> > Justin Mclean  于2020年1月9日周四 下午4:27写道：
> >
> > > Hi,
> > >
> > > > When our community grows stronger, each\ module may have some
> specific
> > > person in charge.
> > >
> > > No that is not the Apache Way. No one should be in charge of an area.
> > >
> > > Thanks,
> > > Justin
> >
>

Re: [DISCUSS] Add the components definition in JIRA template

[jincheng sun]

> No that is not the Apache Way. No one should be in charge of an area.

Oh, great thanks for correcting me Justin, maybe it's my language
expression problems. I mean some contributors and committers will be very
interested in some components, then spend more time, and be more familiar
with the code.

Best,
Jincheng


Justin Mclean  于2020年1月9日周四 下午4:27写道：

> Hi,
>
> > When our community grows stronger, each\ module may have some specific
> person in charge.
>
> No that is not the Apache Way. No one should be in charge of an area.
>
> Thanks,
> Justin

[DISCUSS] Add the components definition in JIRA template

[jincheng sun]

Hi folks,

Currently we can not select one components when create a JIRA. [1]. At
present, this problem is not obvious because there are not many
contributors of IoTDB, and the active committers need to have a certain
understanding of each module. When our community grows stronger, each
module may have some specific person in charge. At that time, it is
meaningful for us to specify specific components for JIRA., because that
way, the component owner  can pay attention to them and discuss with the
contributors.

So my proposal is:
Add the components definition in JIRA template [2](there is permission
control, maybe PPMC should be able to access).

If my proposal is accepted by IoTDB community, we should have a discussion
about how to define the components for IoTDB. I'm not familiar with the
components of IoTDB. Maybe PPMC such as Xiangdong and Jialin etc.,  and the
committers of IoTDB will have better solutions.

My two cents:

Approach 1 (align the modules):
- Client
- Server
- Tsfile
- Spark-tsfile
- Hadoop-tsfile
- Spark-iotdb-connector
- Hive-connector
- Grafana
- Distribution
- Service-rpc
- Jdbc
- Session
- Example
- WebSite

Approach 2(Grading management):
- Client
 - Client-java
 - Client-py
 - Service-rpc
 - Jdbc
 - Session
- Server
- Tsfile
  - Spark-tsfile
  - Hadoop-tsfile
- Connector
  - Spark-iotdb-connector
  - Hive-connector
- Grafana
- Distribution
- Example
- WebSite

Approach 3(Pretty simple. We can expand it at any time):
- Client
- Server
- Tsfile
- Connector
- Grafana
- Distribution
- Example
- WebSite

Approach 4（Other better options)

Best,
Jincheng

[1] https://issues.apache.org/jira/browse/IOTDB-410
[2]
https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/components

Re: [CALL FOR VOTES] Release Apache IoTDB 0.9.1

[jincheng sun]

I think Julian is checking for votes now... :)

Lei Rui  于2020年1月9日周四 下午1:17写道：

> Hi,
>
>
> After the vote letter titled "[VOTE] Release Apache IoTDB 0.9.1" was sent
> to gene...@incubator.apache.org on Jan 3,
> two +1 votes have been cast by Justin Mclean and Willem Jiang.
>
>
> We may need more votes, since a minimum of 3 binding +1 votes and more
> binding +1 than binding -1 are required to pass.
>  @Christofer Dutz  @Kevin A. McGrail  @Julian Feinauer
>
>
>
> Regards,
> Lei Rui
>
>

Re: [Discuss] More reasonable issue permission on JIRA

[jincheng sun]

I have checked the issue permission, It works now :) Thanks all of you made
it.

Best,
Jincheng


jincheng sun  于2020年1月8日周三 下午1:10写道：

> Great thanks for driving this Chris！
>
> I have left comment on the JIRA. Hope this can be resolved soon :)
>
> BTW: cc to @dev :)
>
> Best,
> Jincheng
>
>
> Christofer Dutz  于2020年1月7日周二 下午6:19写道：
>
>> Hi all,
>>
>>
>>
>> I just requested a custom permission scheme so we will be able to tweak
>> the settings.
>>
>>
>>
>> https://issues.apache.org/jira/browse/INFRA-19676
>>
>>
>>
>>
>>
>> Chris
>>
>>
>>
>> *Von: *jincheng sun 
>> *Datum: *Samstag, 21. Dezember 2019 um 06:11
>> *An: *"dev@iotdb.apache.org" 
>> *Cc: *Christofer Dutz , "jmcl...@apache.org" <
>> jmcl...@apache.org>, "kmcgr...@apache.org" , "
>> ningji...@apache.org" , Justin Mclean <
>> jus...@classsoftware.com>
>> *Betreff: *Re: [Discuss] More reasonable issue permission on JIRA
>>
>>
>>
>> Is there any progress here to update? :)
>>
>>
>>
>> Best,
>>
>> Jincheng
>>
>>
>>
>>
>>
>> jincheng sun  于2019年12月14日周六 下午10:32写道：
>>
>> Hi Xiangdong,
>>
>>
>>
>> Thanks for bring up this discussion!
>>
>>
>>
>> Big +1 for adding the role of "Contributors" to "Assignable User" list,
>> as  I think allowing JIRA. to be assigned to contributors is a prerequisite
>> for growing our IoTDB, and this improvement will showing the welcome to new
>> contributors. :)
>>
>>
>>
>> Best,
>>
>> Jincheng
>>
>> -
>>
>> Committer & PMC Member at @ApacheFlink
>>
>> Staff Engineer at @Alibaba
>>
>> Blog: https://enjoyment.cool
>>
>> Twitter: https://twitter.com/sunjincheng121
>>
>> --
>>
>>
>>
>>
>>
>> Xiangdong Huang  于2019年12月14日周六 下午1:46写道：
>>
>> Hi,
>>
>> Now IoTDB is using _Default Permission Scheme_ on jira [1].
>>
>> The schema looks good, but one thing that I think we can have a change:
>>
>> Current the "Assignable User" needs to be Administrator/PMC/Committer.
>> However, if someone (who is not a committer) reports a bug and he/she has
>> the ability to fix that and can submit a PR. I think we can assign the
>> issue to him/her.
>>
>> It will give more sense of honor to users who are not the committers but
>> make real contribution to the project.  And, it will attract more users to
>> contribute to IoTDB, I think. Some users also point out that [2].
>>
>> Therefore, I suggest to change "Assignable User" to
>> Administrator/PMC/Committer/Reporter/Contributor..
>>
>> Even though I have the administrator permission of IoTDB JIRA, but the
>> above modification nees jira-administrator permission, which is higher
>> than
>> what I can do.
>>
>> Maybe  @Christofer Dutz   can help us. :-D.
>>
>> [1]
>>
>> https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/permissions
>> [2] https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-365
>>
>> Best,
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>>
>>  黄向东
>> 清华大学 软件学院
>>
>>

Re: [Discuss] More reasonable issue permission on JIRA

[jincheng sun]

Great thanks for driving this Chris！

I have left comment on the JIRA. Hope this can be resolved soon :)

BTW: cc to @dev :)

Best,
Jincheng


Christofer Dutz  于2020年1月7日周二 下午6:19写道：

> Hi all,
>
>
>
> I just requested a custom permission scheme so we will be able to tweak
> the settings.
>
>
>
> https://issues.apache.org/jira/browse/INFRA-19676
>
>
>
>
>
> Chris
>
>
>
> *Von: *jincheng sun 
> *Datum: *Samstag, 21. Dezember 2019 um 06:11
> *An: *"dev@iotdb.apache.org" 
> *Cc: *Christofer Dutz , "jmcl...@apache.org" <
> jmcl...@apache.org>, "kmcgr...@apache.org" , "
> ningji...@apache.org" , Justin Mclean <
> jus...@classsoftware.com>
> *Betreff: *Re: [Discuss] More reasonable issue permission on JIRA
>
>
>
> Is there any progress here to update? :)
>
>
>
> Best,
>
> Jincheng
>
>
>
>
>
> jincheng sun  于2019年12月14日周六 下午10:32写道：
>
> Hi Xiangdong,
>
>
>
> Thanks for bring up this discussion!
>
>
>
> Big +1 for adding the role of "Contributors" to "Assignable User" list,
> as  I think allowing JIRA. to be assigned to contributors is a prerequisite
> for growing our IoTDB, and this improvement will showing the welcome to new
> contributors. :)
>
>
>
> Best,
>
> Jincheng
>
> -
>
> Committer & PMC Member at @ApacheFlink
>
> Staff Engineer at @Alibaba
>
> Blog: https://enjoyment.cool
>
> Twitter: https://twitter.com/sunjincheng121
>
> --
>
>
>
>
>
> Xiangdong Huang  于2019年12月14日周六 下午1:46写道：
>
> Hi,
>
> Now IoTDB is using _Default Permission Scheme_ on jira [1].
>
> The schema looks good, but one thing that I think we can have a change:
>
> Current the "Assignable User" needs to be Administrator/PMC/Committer.
> However, if someone (who is not a committer) reports a bug and he/she has
> the ability to fix that and can submit a PR. I think we can assign the
> issue to him/her.
>
> It will give more sense of honor to users who are not the committers but
> make real contribution to the project.  And, it will attract more users to
> contribute to IoTDB, I think. Some users also point out that [2].
>
> Therefore, I suggest to change "Assignable User" to
> Administrator/PMC/Committer/Reporter/Contributor..
>
> Even though I have the administrator permission of IoTDB JIRA, but the
> above modification nees jira-administrator permission, which is higher than
> what I can do.
>
> Maybe  @Christofer Dutz   can help us. :-D.
>
> [1]
>
> https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/permissions
> [2] https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-365
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>

Re: [DISCUSS] Apache IoTDB (incubating) 0.9.1 RC1

[jincheng sun]

I see. Thanks for your feedback!  Lei Rui & Justin!

As I know, Both Apache Beam[1] and Apache Flink[2] carry website updated
PRs when bring up the release votes. This approach benefits Apache Beam and
Apache Flink as the update changes of Beam and Flink are a little more
complicated compare with Apache IoTDB, this approach speeds up the entire
publishing process. However, the current update of the IoTDB website is a
little bit easy, So, this approach has not brought obvious benefits.

So, I am fine with keep current process of IoTDB.

[1]
https://lists.apache.org/thread.html/2fa0dd0e8710e62deab2e25c6081ed94636448f123d6f91ad190aa21%40%3Cdev.beam.apache.org%3E
[2]
https://lists.apache.org/thread.html/716337faba0160e8382543c8eb10bfa34895efc2419e94a1f3cc8d19%40%3Cdev.flink.apache.org%3E

Best,
Jincheng

Lei Rui  于2020年1月3日周五 下午2:06写道：

> Hi,
>
>
> No need +1.
>
>
> I don't think it's a good practice, because if the released file doesn't
> exist, how can people review a PR like [1] where
> there are download links in it waiting to be checked, e.g.,
>
> https://www.apache.org/dyn/closer.cgi/incubator/iotdb/0.9.0-incubating/apache-iotdb-0.9.0-incubating-source-release.zip
> .
>
>
> Regards,
> Lei Rui
>
>
> [1]
> https://github.com/apache/incubator-iotdb-website/commit/dc4d0226985c976561944068fd012e5cdfab4339
> On 1/3/2020 13:52，jincheng sun wrote：
> No. You should only update the website after the IPMC vote has passes,
> the file put into the Apache mirrors and you waited 24 hours or so for the
> release to propagate.
>
> I mean that prepare the PR when bring up the VOTE,  then people can review
> the PR ASAP. we can merge it when vote has passed and 24 hours later after
> the release .
>
> Best,
> Jincheng
>
>
>
> Lei Rui  于2020年1月3日周五 下午12:22写道：
>
> Thank Justin for the quick reply.
>
>
> Regards,
> Lei Rui
> On 1/3/2020 11:43，Justin Mclean wrote：
> Hi,
>
> Do you think that when bring up a release VOTE, we need to add the PR of
> update the website in VOTE thread? The changes of the PR would be similar
> with
>
> No. You should only update the website after the IPMC vote has passes, the
> file put into the Apache mirrors and you waited 24 hours or so for the
> release to propagate.
>
> Thanks,
> Justin
>

Re: [DISCUSS] Apache IoTDB (incubating) 0.9.1 RC1

[jincheng sun]

> No. You should only update the website after the IPMC vote has passes,
the file put into the Apache mirrors and you waited 24 hours or so for the
release to propagate.

I mean that prepare the PR when bring up the VOTE,  then people can review
the PR ASAP. we can merge it when vote has passed and 24 hours later after
the release .

Best,
Jincheng



Lei Rui  于2020年1月3日周五 下午12:22写道：

> Thank Justin for the quick reply.
>
>
> Regards,
> Lei Rui
> On 1/3/2020 11:43，Justin Mclean wrote：
> Hi,
>
> Do you think that when bring up a release VOTE, we need to add the PR of
> update the website in VOTE thread? The changes of the PR would be similar
> with
>
> No. You should only update the website after the IPMC vote has passes, the
> file put into the Apache mirrors and you waited 24 hours or so for the
> release to propagate.
>
> Thanks,
> Justin

Re: [VOTE] Apache IoTDB (incubating) 0.9.1 RC1

[jincheng sun]

Do you think that when bring up a release VOTE, we need to add the PR of
update the website in VOTE thread? The changes of the PR would be similar
with [1].

[1]
https://github.com/apache/incubator-iotdb-website/commit/dc4d0226985c976561944068fd012e5cdfab4339

jincheng sun  于2020年1月3日周五 上午10:18写道：

> +1(non-binding)
>
> I have done the simply check as follows:
>
> - Successfully build the source
> - Download the binaries and start a server and a client, successfully run
> some of SQL commands.
>
> Best,
> Jincheng
>
>
> Justin Mclean  于2020年1月3日周五 上午7:09写道：
>
>> Hi,
>>
>> +1 (binding)
>>
>> I checked:
>> - incubating in name
>> - signatures and hashed correct
>> - disclaimer exists
>> - license and notice all good
>> - all source files have asf headers
>> - no unexpected binary files
>> - Can compile from source
>>
>> Thanks,
>> Justin
>>
>

Re: [VOTE] Apache IoTDB (incubating) 0.9.1 RC1

[jincheng sun]

+1(non-binding)

I have done the simply check as follows:

- Successfully build the source
- Download the binaries and start a server and a client, successfully run
some of SQL commands.

Best,
Jincheng


Justin Mclean  于2020年1月3日周五 上午7:09写道：

> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signatures and hashed correct
> - disclaimer exists
> - license and notice all good
> - all source files have asf headers
> - no unexpected binary files
> - Can compile from source
>
> Thanks,
> Justin
>

Re: New committer: Yuan Tian, Kaifeng Xue, Tianci Zhu, Zesong Sun

[jincheng sun]

Congrats Yuan Tian, Kaifeng Xue, Tianci Zhu, Zesong Sun，well deserved！
Congrats on the vigorous development of IoTDB community！

Best,
Jincheng



Jialin Qiao  于2019年12月31日周二 上午9:53写道：

> The Project Management Committee (PMC) for Apache IoTDB
> has invited Yuan Tian, Kaifeng Xue, Zesong Sun, Tianci Zhu
> to become a committer and we are pleased to announce that they have
> accepted.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
> Being a PMC member enables assistance with the management
> and to guide the direction of the project.
>
> You could get the write-access of our repository by:
>
> 1) Update your github id in: id.apache.org
> 2) Accept the invitation in github to being a member of the apache group.
> 3) Link your accounts via: git.apache.org (You need to download a two-step
> velidation application (In Chinese: Google 身份验证器) in your mobile)
>
> Yours,
> The Apache IoTDB PMC
>

Re: [DISCUSS] Should I change the year to 2020 in advance when releasing 0.9.1?

[jincheng sun]

I think 2020 would be fine ：）

Christofer Dutz 于2019年12月28日 周六00:45写道：

> +1 From me too
>
> Chris
>
> Am 27.12.19, 17:40 schrieb "Kevin A. McGrail" :
>
> +1 to update in advance just make sure not to announce the release
> until
> 2020.
>
> On 12/27/2019 10:32 AM, Lei Rui wrote:
> > Hi,
> >
> >
> > I am the release manager of the upcoming 0.9.1 and I encounter an
> interesting question:
> >
> >
> > As you can see, Year 2020 is just around the corner and the upcoming
> release vote for 0.9.1
> > is likely to span from 2019 to 2020. So I don't know if I should
> change the year in advance
> > to 2020, or just keep it as 2019, or maybe I postpone the release
> vote until it is 2020?
> >
> >
> > P.s., the year 2019 is now displayed in the NOTICE file like this:
> >> Apache IoTDB
> >> Copyright 2018-2019 The Apache Software Foundation.
> >> 
> >
> > Regards,
> > Lei Rui
> >
> >
> >
> --
> Kevin A. McGrail
> kmcgr...@apache.org
>
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
> --

Best,
Jincheng
-
Twitter: https://twitter.com/sunjincheng121
-

Re: [DISCUSS] Remove all adaptive styles and add specific attribute configurations for specific components

[jincheng sun]

Sorry, I didn't make my proposal clear. My proposal didn't say to give up
"responsive layout". My proposal is to fix all bugs while supporting
"responsive layout", such as: in case of [1], the menu text wrap according
to the window size is already using “responsive layout"”, it's just that
line height is not set, which leads to bugs.

My proposal is consider our IoTDB website style from a global perspective
and add specific attribute configurations for specific components. such as
add a `line-height` style for the whole website.

Best,
Jincheng

[1]
https://issues.apache.org/jira/secure/attachment/12989445/12989445_image-2019-12-25-11-26-45-754.png


Xiangdong Huang  于2019年12月25日周三 下午1:09写道：

> Hi,
>
> > My proposal is: Remove all adaptive styles(such as: justify, default
> height, default width etc.),  and add specific attribute configurations for
> specific components(Consider our IoTDB website style from a global
> perspective).
>
> I am not an expert of front-end tech. If we "remove all adaptive styles",
> is the website still "Responsive Layout"?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2019年12月25日周三 下午12:11写道：
>
> > Hello everyone,
> >
> > I've been focusing on IoTDB for a while. I think the IoTDB architecture
> and
> > the vision of solving the practical problems in the IOT scenario are very
> > great, so I'm very interested in this project. The only feeling is that
> at
> > present, the number of community participants in IoTDB is not too many.
> We
> > should not only use excellent architecture and great vision to attract
> more
> > excellent people to participate in IoTDB, but also let's people who come
> to
> > know IoTDB through the website are attracted by the details of IoTDB. The
> > problems, no matter how big or small, will reflect the community's
> pursuit
> > of IoTDB, especially the details will reflect the spirit of IoTDB
> > excellence. So although the problems I put forward are easy to fix, I
> don't
> > mean to pick up problems and express that IoTDB is not good, but I want
> to
> > help the IoTDB community grow and improve, and do better in details. I
> also
> > believe that IoTDB will develop better and better!
> >
> > So, I will lead to my proposal with two specific questions:
> >
> > - When we narrow the window, there will be problems in our display, as
> > shown in the [1][5], and we can add the height attribute to solve this
> > problem, as shown in [2].
> > - Can not show the menu if we narrow the window, detail can be found in
> [3]
> > [6]
> >
> > The above are two specific problems. My suggestion is to consider the
> > overall style principle of the website from the perspective of the
> overall
> > situation, so as to avoid the endless small problems. The similar
> problems
> > have been solved before, such as [4]. So my proposal is as follows:
> >
> > My proposal is: Remove all adaptive styles(such as: justify, default
> > height, default width etc.),  and add specific attribute configurations
> for
> > specific components(Consider our IoTDB website style from a global
> > perspective).
> >
> > I appreciate if anyone like to make this nice improvement !
> >
> > What do you think?
> >
> > Best,
> > Jincheng
> >
> > [1]
> >
> >
> https://issues.apache.org/jira/secure/attachment/12989445/12989445_image-2019-12-25-11-26-45-754.png
> > [2]
> >
> >
> https://issues.apache.org/jira/secure/attachment/12989444/12989444_image-2019-12-25-11-27-34-645.png
> > [3]
> >
> >
> https://issues.apache.org/jira/secure/attachment/12989447/12989447_image-2019-12-25-11-32-47-738.png
> > [4] https://issues.apache.org/jira/browse/IOTDB-384
> > [5] https://issues.apache.org/jira/browse/IOTDB-390
> > [6] https://issues.apache.org/jira/browse/IOTDB-391
> >
>

[DISCUSS] Remove all adaptive styles and add specific attribute configurations for specific components

[jincheng sun]

Hello everyone,

I've been focusing on IoTDB for a while. I think the IoTDB architecture and
the vision of solving the practical problems in the IOT scenario are very
great, so I'm very interested in this project. The only feeling is that at
present, the number of community participants in IoTDB is not too many. We
should not only use excellent architecture and great vision to attract more
excellent people to participate in IoTDB, but also let's people who come to
know IoTDB through the website are attracted by the details of IoTDB. The
problems, no matter how big or small, will reflect the community's pursuit
of IoTDB, especially the details will reflect the spirit of IoTDB
excellence. So although the problems I put forward are easy to fix, I don't
mean to pick up problems and express that IoTDB is not good, but I want to
help the IoTDB community grow and improve, and do better in details. I also
believe that IoTDB will develop better and better!

So, I will lead to my proposal with two specific questions:

- When we narrow the window, there will be problems in our display, as
shown in the [1][5], and we can add the height attribute to solve this
problem, as shown in [2].
- Can not show the menu if we narrow the window, detail can be found in [3]
[6]

The above are two specific problems. My suggestion is to consider the
overall style principle of the website from the perspective of the overall
situation, so as to avoid the endless small problems. The similar problems
have been solved before, such as [4]. So my proposal is as follows:

My proposal is: Remove all adaptive styles(such as: justify, default
height, default width etc.),  and add specific attribute configurations for
specific components(Consider our IoTDB website style from a global
perspective).

I appreciate if anyone like to make this nice improvement !

What do you think?

Best,
Jincheng

[1]
https://issues.apache.org/jira/secure/attachment/12989445/12989445_image-2019-12-25-11-26-45-754.png
[2]
https://issues.apache.org/jira/secure/attachment/12989444/12989444_image-2019-12-25-11-27-34-645.png
[3]
https://issues.apache.org/jira/secure/attachment/12989447/12989447_image-2019-12-25-11-32-47-738.png
[4] https://issues.apache.org/jira/browse/IOTDB-384
[5] https://issues.apache.org/jira/browse/IOTDB-390
[6] https://issues.apache.org/jira/browse/IOTDB-391

Re: [VOTE] Enrich information of project committers in IOTDB website

[jincheng sun]

[2] ttps://www.apache.org/foundation/voting.html
<https://www.apache.org/foundation/voting.html>

jincheng sun  于2019年12月25日周三 上午10:17写道：

> Hi,
>
> @Justin, Thank you for the explanation about  `Who is permitted to vote,
> and which kind of vote is binding?`!  I have not saw the wiki[1] you
> mentioned before.  The table of `Decision Making` solved my question. :)
>
> As both [1] and [2] mentioned that each project can define its own
> guidelines, i.e.,
> in [1] has mentioned as follows:
>
> > This document defines the guidelines under which a project operates if
> it hasn't defined its own guidelines.
>
> in [2] has mentioned as follows:
>
> > Who is permitted to vote is, to some extent, a community-specific thing.
>
> So, I think we can have of IoTDB's guidelines in future, then we can bring
> up the discussion when the community continues to grow and needs to have
> its own characteristics, for example, define IoTDB Improvement Proposal,
>  similar with "KIP" (Kafka), "SPIP" (Spark), "FLIP" (Flink),
> "AIP"(Airflow). :)
>
> Best,
> Jincheng
>
> [1]
> https://cwiki.apache.org/confluence/display/INCUBATOR/Default+Project+Guidelines
>
>
>
> Justin Mclean  于2019年12月25日周三 上午8:12写道：
>
>> Hi,
>>
>> > - Who is permitted to vote, and which kind of vote is binding?
>>
>> Well technically no votes are actually binding if you are a podling, only
>> PMC votes are binding sat Apache projects so you could take that to mean
>> Incubator PMC votes. That being said most podlings treat PPMC votes as
>> binding but it’s more a social construct than anything else.
>>
>> I would just follow the default guidelines [1]
>>
>> Justin
>>
>> 1.
>> https://cwiki.apache.org/confluence/display/INCUBATOR/Default+Project+Guidelines
>>
>>

Re: [VOTE] Enrich information of project committers in IOTDB website

[jincheng sun]

Hi,

@Justin, Thank you for the explanation about  `Who is permitted to vote,
and which kind of vote is binding?`!  I have not saw the wiki[1] you
mentioned before.  The table of `Decision Making` solved my question. :)

As both [1] and [2] mentioned that each project can define its own
guidelines, i.e.,
in [1] has mentioned as follows:

> This document defines the guidelines under which a project operates if it
hasn't defined its own guidelines.

in [2] has mentioned as follows:

> Who is permitted to vote is, to some extent, a community-specific thing.

So, I think we can have of IoTDB's guidelines in future, then we can bring
up the discussion when the community continues to grow and needs to have
its own characteristics, for example, define IoTDB Improvement Proposal,
 similar with "KIP" (Kafka), "SPIP" (Spark), "FLIP" (Flink),
"AIP"(Airflow). :)

Best,
Jincheng

[1]
https://cwiki.apache.org/confluence/display/INCUBATOR/Default+Project+Guidelines



Justin Mclean  于2019年12月25日周三 上午8:12写道：

> Hi,
>
> > - Who is permitted to vote, and which kind of vote is binding?
>
> Well technically no votes are actually binding if you are a podling, only
> PMC votes are binding sat Apache projects so you could take that to mean
> Incubator PMC votes. That being said most podlings treat PPMC votes as
> binding but it’s more a social construct than anything else.
>
> I would just follow the default guidelines [1]
>
> Justin
>
> 1.
> https://cwiki.apache.org/confluence/display/INCUBATOR/Default+Project+Guidelines
>
>

Re: [VOTE] Enrich information of project committers in IOTDB website

[jincheng sun]

Hi Xiangdong,

Usually we can follow the existing process in [1].  But it's great if we
can have a clearly description regarding some specific things, such as:

- Who is permitted to vote, and which kind of vote is binding?
i.e., Sometimes only PMC members vote for Building, and sometimes Committee
votes for Building.
- Which kind of issues should be bring up the discussion? e.g., we do not
need bring up the discussion for typo issue, but for the interface changes
we should bring up the discussion (may be with  a design document)
- What is the template for discussion and voting, and what elements should
be included? e.g., Voting duration must be included in the voting
template(such as: The vote will be open for at least 72 hours. It is
adopted by a simple majority with a minimum of three positive votes. )

So, I think it's better to have a guideline for our contributors in our
website. What do you think? :)


Best,
Jincheng

[1] https://www.apache.org/foundation/voting.html


Xiangdong Huang  于2019年12月21日周六 下午1:19写道：

> Hi,
>
> @Zesong I think it is your duty to end this vote and summarize the result.
>
> @Jincheng, Do we really need a discussion about that? Maybe all votes
> processes are the same in Apache way?. But an instruction document is good
> for fresh users.
>
> Best,
>
>
>
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2019年12月21日周六 下午12:35写道：
>
> > Hi,
> >
> > Which kind of VOTE is binding?  And under what conditions can this poll
> be
> > ended？
> >
> > BTW: I haven't seen any documentation regarding how to bringup
> discussion,
> > how to finish a VOTE. If not, I suggest launching a discussion to improve
> > the gap in this area.
> >
> > Best,
> > Jincheng
> >
> > Best,
> > Jincheng
> > @sunjincheng121 <https://twitter.com/sunjincheng121>
> >
> >
> > jincheng sun  于2019年12月17日周二 下午6:23写道：
> >
> > > +1, and I have left a few comments in the PR.
> > >
> > > Best,
> > > Jincheng
> > >
> > > Twitter: https://twitter.com/sunjincheng121
> > >
> > >
> > > Jack Tsai  于2019年12月17日周二 下午3:56写道：
> > >
> > >> Hi,
> > >> +1 for this idea.
> > >>
> > >> Best regards,
> > >> Jack Tsai
> > >>
> > >> 取得 iOS 版 Outlook<https://aka.ms/o0ukef>
> > >> 
> > >> 寄件者: Jialin Qiao 
> > >> 寄件日期: Tuesday, December 17, 2019 7:52:33 AM
> > >> 收件者: dev@iotdb.apache.org 
> > >> 主旨: Re: [VOTE] Enrich information of project committers in IOTDB
> website
> > >>
> > >> Hi,
> > >>
> > >> +1,  we could create a confluence page about this if passed.
> > >>
> > >> Thanks,
> > >> Jialin Qiao
> > >>
> > >> Xiangdong Huang  于2019年12月17日周二 下午3:42写道：
> > >>
> > >> > Hi,
> > >> >
> > >> > +1 for the idea.
> > >> >
> > >> > Best,
> > >> > ---
> > >> > Xiangdong Huang
> > >> > School of Software, Tsinghua University
> > >> >
> > >> >  黄向东
> > >> > 清华大学 软件学院
> > >> >
> > >> >
> > >> > 孙泽嵩  于2019年12月17日周二 下午3:29写道：
> > >> >
> > >> > > Hi all,
> > >> > >
> > >> > > Thanks to @Jincheng, we intend to enrich information of project
> > >> > committers
> > >> > > in website. (The last VOTE e-mail was actually in a new thread…
> but
> > >> > somehow
> > >> > > showed together with the DISCUSS thread in some e-mail clients,
> so I
> > >> > change
> > >> > > the theme a little this time ...)
> > >> > >
> > >> > > I have opened a PR [1] in our website repository, so if this VOTE
> > pass
> > >> > and
> > >> > > the PR is merged, every committer and contributor can open PR
> > >> themselves
> > >> > to
> > >> > > maintain their own information. Besides, we also add two lists for
> > >> those
> > >> > > contributors who have submitted PR(s) and propose issue(s) for
> IoTDB
> > >> to
> > >> > > encourage more and more people to join us.
> > >> > >
> > >> > &

Re: [DISCUSS] Using align `left` take over `justify` text-align style in IoTDb website

[jincheng sun]

Hi Zesong,

Don't worry, I believe you will do it pretty great next time! :)

BTW: thank for update the PR, LGTM. :)

Best,
Jincheng


孙泽嵩  于2019年12月23日周一 下午10:16写道：

> Hi @sunjincheng121 ,
>
> Sorry for somehow ignoring the "latest news" part…
> And many thanks for the suggestions! I will notice the PR and commit
> format in the future : )
>
>
> Best,
> ---
> Zesong Sun
> School of Software, Tsinghua University
>
> 孙泽嵩
> 清华大学 软件学院
>
> > 2019年12月23日 22:11，jincheng sun  写道：
> >
> > Thanks for your conformation Jack，Xiangdong！
> >
> > Thanks for the PR Zesong！
> >
> > I manually established the JIRA(IOTDB-384) and PR(54) links, and left the
> > following 3 suggestions in the PR：
> >
> >-  It's better to contain JIRA. number in the PR title. such as:
> > [IOTDB-384] ix main feature text style in homepage. Then the reviewer can
> > know the JIRA of the PR easily.
> >- The commit message should contain the JIRA. number such as :
> > [IOTDB-384] ix main feature text style in homepage.Then the JIRA and the
> PR
> > can make the relation automatically
> >-  It's better to fix the problem of "Latest News " in the PR(54).
> >
> > What do you think ?
> > Best,
> > Jincheng
> >
> >
> > 孙泽嵩  于2019年12月23日周一 下午8:51写道：
> >
> >> Sure, if you all think it will be better : ) Here is PR [1] and result
> >>
> >> [1] https://github.com/apache/incubator-iotdb-website/pull/54 <
> >> https://github.com/apache/incubator-iotdb-website/pull/54>
> >>
> >>
> >>
> >> Best,
> >> ---
> >> Zesong Sun
> >> School of Software, Tsinghua University
> >>
> >> 孙泽嵩
> >> 清华大学 软件学院
> >>
> >>> 2019年12月23日 20:40，Xiangdong Huang  写道：
> >>>
> >>> Hi @Zesong, do you have time to fix the style?
> >>>
> >>> Best,
> >>> -------
> >>> Xiangdong Huang
> >>> School of Software, Tsinghua University
> >>>
> >>> 黄向东
> >>> 清华大学 软件学院
> >>>
> >>>
> >>> Jack Tsai  于2019年12月23日周一 下午5:30写道：
> >>>
> >>>> Hi,
> >>>>
> >>>> Agree. Looks better while applying “align left”.
> >>>>
> >>>> Best regards,
> >>>> Jack Tsai
> >>>>
> >>>> 取得 iOS 版 Outlook<https://aka.ms/o0ukef>
> >>>> 
> >>>> 寄件者: jincheng sun 
> >>>> 寄件日期: Monday, December 23, 2019 9:18:17 AM
> >>>> 收件者: dev@iotdb.apache.org 
> >>>> 主旨: [DISCUSS] Using align `left` take over `justify` text-align style
> in
> >>>> IoTDb website
> >>>>
> >>>> Hi folks,
> >>>>
> >>>> When I reading home of the IoTDB website [1], I feel that the display
> >> style
> >>>> of "Main Features" is very uncomfortable, and the text spacing is
> >>>> different, just like a bug, but it is actually a problem of the
> display
> >>>> style(text align: justify).
> >>>>
> >>>> I propose using align `left` take over `justify` text-align style in
> >> IoTDB
> >>>> website.
> >>>>
> >>>> The modified display effect comparison can be viewed in [2] or [3]
> >>>>
> >>>> BTW. The area of "Latest News " has the same problem, i.e., the style
> of
> >>>> "list-unstyled" should be replace by other style.
> >>>>
> >>>> What do you think? Welcome any feedback :)
> >>>>
> >>>> Best,
> >>>> Jincheng
> >>>>
> >>>> [1] https://iotdb.apache.org
> >>>> [2]
> >>>>
> >>>>
> >>
> https://issues.apache.org/jira/secure/attachment/12989376/image-2019-12-23-16-49-25-077.png
> >>>> [3] https://issues.apache.org/jira/browse/IOTDB-384
> >>>>
> >>
> >>
>
>

Re: [DISCUSS] Using align `left` take over `justify` text-align style in IoTDb website

[jincheng sun]

Thanks for your conformation Jack，Xiangdong！

Thanks for the PR Zesong！

I manually established the JIRA(IOTDB-384) and PR(54) links, and left the
following 3 suggestions in the PR：

-  It's better to contain JIRA. number in the PR title. such as:
[IOTDB-384] ix main feature text style in homepage. Then the reviewer can
know the JIRA of the PR easily.
- The commit message should contain the JIRA. number such as :
[IOTDB-384] ix main feature text style in homepage.Then the JIRA and the PR
can make the relation automatically
-  It's better to fix the problem of "Latest News " in the PR(54).

What do you think ?
Best,
Jincheng


孙泽嵩  于2019年12月23日周一 下午8:51写道：

> Sure, if you all think it will be better : ) Here is PR [1] and result
>
> [1] https://github.com/apache/incubator-iotdb-website/pull/54 <
> https://github.com/apache/incubator-iotdb-website/pull/54>
>
>
>
> Best,
> ---
> Zesong Sun
> School of Software, Tsinghua University
>
> 孙泽嵩
> 清华大学 软件学院
>
> > 2019年12月23日 20:40，Xiangdong Huang  写道：
> >
> > Hi @Zesong, do you have time to fix the style?
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> > 黄向东
> > 清华大学 软件学院
> >
> >
> > Jack Tsai  于2019年12月23日周一 下午5:30写道：
> >
> >> Hi,
> >>
> >> Agree. Looks better while applying “align left”.
> >>
> >> Best regards,
> >> Jack Tsai
> >>
> >> 取得 iOS 版 Outlook<https://aka.ms/o0ukef>
> >> 
> >> 寄件者: jincheng sun 
> >> 寄件日期: Monday, December 23, 2019 9:18:17 AM
> >> 收件者: dev@iotdb.apache.org 
> >> 主旨: [DISCUSS] Using align `left` take over `justify` text-align style in
> >> IoTDb website
> >>
> >> Hi folks,
> >>
> >> When I reading home of the IoTDB website [1], I feel that the display
> style
> >> of "Main Features" is very uncomfortable, and the text spacing is
> >> different, just like a bug, but it is actually a problem of the display
> >> style(text align: justify).
> >>
> >> I propose using align `left` take over `justify` text-align style in
> IoTDB
> >> website.
> >>
> >> The modified display effect comparison can be viewed in [2] or [3]
> >>
> >> BTW. The area of "Latest News " has the same problem, i.e., the style of
> >> "list-unstyled" should be replace by other style.
> >>
> >> What do you think? Welcome any feedback :)
> >>
> >> Best,
> >> Jincheng
> >>
> >> [1] https://iotdb.apache.org
> >> [2]
> >>
> >>
> https://issues.apache.org/jira/secure/attachment/12989376/image-2019-12-23-16-49-25-077.png
> >> [3] https://issues.apache.org/jira/browse/IOTDB-384
> >>
>
>

[DISCUSS] Using align `left` take over `justify` text-align style in IoTDb website

[jincheng sun]

Hi folks,

When I reading home of the IoTDB website [1], I feel that the display style
of "Main Features" is very uncomfortable, and the text spacing is
different, just like a bug, but it is actually a problem of the display
style(text align: justify).

I propose using align `left` take over `justify` text-align style in IoTDB
website.

The modified display effect comparison can be viewed in [2] or [3]

BTW. The area of "Latest News " has the same problem, i.e., the style of
"list-unstyled" should be replace by other style.

What do you think? Welcome any feedback :)

Best,
Jincheng

[1] https://iotdb.apache.org
[2]
https://issues.apache.org/jira/secure/attachment/12989376/image-2019-12-23-16-49-25-077.png
[3] https://issues.apache.org/jira/browse/IOTDB-384

Re: Maintain user roles of IoTDB Jira

[jincheng sun]

Hi Xiangdong,

No worries, it is not urgent! Thank you for your quick response :)

Best,
Jincheng

Xiangdong Huang  于2019年12月21日周六 下午1:13写道：

> Hi jincheng,
>
> Sorry I forgot to maintain that. Thanks for reminding me :D. I will update
> the jira status once I finish it.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2019年12月21日周六 下午12:59写道：
>
> > HI Xiangdong,
> >
> > Thank you for helping fix it. For tracing easy I have create the JIRA
> [1].
> >
> > [1] https://issues.apache.org/jira/browse/IOTDB-381
> >
> > Best,
> > Jincheng
> >
> > Xiangdong Huang  于2019年12月16日周一 上午11:26写道：
> >
> > > Hi, I will fix the inconsistency about the roster.
> > >
> > > jincheng sun 于2019年12月16日 周一上午9:25写道：
> > >
> > > > Yes, I see :). Thank you for clarifying who can perform maintenance
> > > Justin
> > > > !
> > > >
> > > > Best,
> > > > Jincheng
> > > > -
> > > > Committer & PMC Member at @ApacheFlink
> > > > Staff Engineer at @Alibaba
> > > > Blog: https://enjoyment.cool
> > > > Twitter: https://twitter.com/sunjincheng121
> > > > --
> > > >
> > > >
> > > > Justin Mclean  于2019年12月15日周日 上午7:51写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > > I found that the committer information(Number of person) is not
> > > > > > synchronized between [1] and [2] pages. :)
> > > > >
> > > > > It up to the :PMC to do that.
> > > > >
> > > > > Thanks,
> > > > > Justin
> > > > >
> > > >
> > > --
> > > ---
> > > Xiangdong Huang
> > > School of Software, Tsinghua University
> > >
> > >  黄向东
> > > 清华大学 软件学院
> > >
> >
>

Re: [Discuss] More reasonable issue permission on JIRA

[jincheng sun]

Is there any progress here to update? :)

Best,
Jincheng


jincheng sun  于2019年12月14日周六 下午10:32写道：

> Hi Xiangdong,
>
> Thanks for bring up this discussion!
>
> Big +1 for adding the role of "Contributors" to "Assignable User" list,
> as  I think allowing JIRA. to be assigned to contributors is a prerequisite
> for growing our IoTDB, and this improvement will showing the welcome to new
> contributors. :)
>
> Best,
> Jincheng
> -
> Committer & PMC Member at @ApacheFlink
> Staff Engineer at @Alibaba
> Blog: https://enjoyment.cool
> Twitter: https://twitter.com/sunjincheng121
> --
>
>
> Xiangdong Huang  于2019年12月14日周六 下午1:46写道：
>
>> Hi,
>>
>> Now IoTDB is using _Default Permission Scheme_ on jira [1].
>>
>> The schema looks good, but one thing that I think we can have a change:
>>
>> Current the "Assignable User" needs to be Administrator/PMC/Committer.
>> However, if someone (who is not a committer) reports a bug and he/she has
>> the ability to fix that and can submit a PR. I think we can assign the
>> issue to him/her.
>>
>> It will give more sense of honor to users who are not the committers but
>> make real contribution to the project.  And, it will attract more users to
>> contribute to IoTDB, I think. Some users also point out that [2].
>>
>> Therefore, I suggest to change "Assignable User" to
>> Administrator/PMC/Committer/Reporter/Contributor..
>>
>> Even though I have the administrator permission of IoTDB JIRA, but the
>> above modification nees jira-administrator permission, which is higher
>> than
>> what I can do.
>>
>> Maybe  @Christofer Dutz   can help us. :-D.
>>
>> [1]
>>
>> https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/permissions
>> [2] https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-365
>>
>> Best,
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>>
>>  黄向东
>> 清华大学 软件学院
>>
>

Re: Maintain user roles of IoTDB Jira

[jincheng sun]

HI Xiangdong,

Thank you for helping fix it. For tracing easy I have create the JIRA [1].

[1] https://issues.apache.org/jira/browse/IOTDB-381

Best,
Jincheng

Xiangdong Huang  于2019年12月16日周一 上午11:26写道：

> Hi, I will fix the inconsistency about the roster.
>
> jincheng sun 于2019年12月16日 周一上午9:25写道：
>
> > Yes, I see :). Thank you for clarifying who can perform maintenance
> Justin
> > !
> >
> > Best,
> > Jincheng
> > -
> > Committer & PMC Member at @ApacheFlink
> > Staff Engineer at @Alibaba
> > Blog: https://enjoyment.cool
> > Twitter: https://twitter.com/sunjincheng121
> > --
> >
> >
> > Justin Mclean  于2019年12月15日周日 上午7:51写道：
> >
> > > Hi,
> > >
> > > > I found that the committer information(Number of person) is not
> > > > synchronized between [1] and [2] pages. :)
> > >
> > > It up to the :PMC to do that.
> > >
> > > Thanks,
> > > Justin
> > >
> >
> --
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>

Re: [VOTE] Enrich information of project committers in IOTDB website

[jincheng sun]

Hi,

Which kind of VOTE is binding?  And under what conditions can this poll be
ended？

BTW: I haven't seen any documentation regarding how to bringup discussion,
how to finish a VOTE. If not, I suggest launching a discussion to improve
the gap in this area.

Best,
Jincheng

Best,
Jincheng
@sunjincheng121 <https://twitter.com/sunjincheng121>


jincheng sun  于2019年12月17日周二 下午6:23写道：

> +1, and I have left a few comments in the PR.
>
> Best,
> Jincheng
>
> Twitter: https://twitter.com/sunjincheng121
>
>
> Jack Tsai  于2019年12月17日周二 下午3:56写道：
>
>> Hi,
>> +1 for this idea.
>>
>> Best regards,
>> Jack Tsai
>>
>> 取得 iOS 版 Outlook<https://aka.ms/o0ukef>
>> 
>> 寄件者: Jialin Qiao 
>> 寄件日期: Tuesday, December 17, 2019 7:52:33 AM
>> 收件者: dev@iotdb.apache.org 
>> 主旨: Re: [VOTE] Enrich information of project committers in IOTDB website
>>
>> Hi,
>>
>> +1,  we could create a confluence page about this if passed.
>>
>> Thanks,
>> Jialin Qiao
>>
>> Xiangdong Huang  于2019年12月17日周二 下午3:42写道：
>>
>> > Hi,
>> >
>> > +1 for the idea.
>> >
>> > Best,
>> > ---
>> > Xiangdong Huang
>> > School of Software, Tsinghua University
>> >
>> >  黄向东
>> > 清华大学 软件学院
>> >
>> >
>> > 孙泽嵩  于2019年12月17日周二 下午3:29写道：
>> >
>> > > Hi all,
>> > >
>> > > Thanks to @Jincheng, we intend to enrich information of project
>> > committers
>> > > in website. (The last VOTE e-mail was actually in a new thread… but
>> > somehow
>> > > showed together with the DISCUSS thread in some e-mail clients, so I
>> > change
>> > > the theme a little this time ...)
>> > >
>> > > I have opened a PR [1] in our website repository, so if this VOTE pass
>> > and
>> > > the PR is merged, every committer and contributor can open PR
>> themselves
>> > to
>> > > maintain their own information. Besides, we also add two lists for
>> those
>> > > contributors who have submitted PR(s) and propose issue(s) for IoTDB
>> to
>> > > encourage more and more people to join us.
>> > >
>> > > I’d like to briefly introduce how to maintain your information:
>> > >
>> > > 1. Search your name in 'src/views/Contributor.vue' , and update the
>> > > information (including avatar, name, role, organization, apache id,
>> and
>> > > starting date).
>> > >
>> > > 2. If your name hasn't existed in the page, you can just add your
>> > > information in the list accordingly: ‘conList' for committers,
>> > > ‘conWithPRList' for contributors who have submitted PR(s), and
>> > > ‘conWithIssueList' for contributors who have proposed issue(s).
>> > >
>> > > 3. As for avatar, you can either upload a picture (better to limit the
>> > > size <150KB) by adding one in '/assets/img/contributor-avatar', then
>> you
>> > > only need to use the file name in the information; Or, you can use a
>> > photo
>> > > link. (You can see the example in PR description)
>> > >
>> > >
>> > > A minimum of 3 binding +1 votes and more binding +1 than binding -1
>> > > are required to pass.
>> > >
>> > > [ ]  +1 accept
>> > > [ ]  -1 reject (explanation required)
>> > >
>> > > [1] https://github.com/apache/incubator-iotdb-website/pull/50 <
>> > > https://github.com/apache/incubator-iotdb-website/pull/50>
>> > >
>> > >
>> > > Best,
>> > > ---
>> > > Zesong Sun
>> > > School of Software, Tsinghua University
>> > >
>> > > 孙泽嵩
>> > > 清华大学 软件学院
>> > >
>> > >
>> >
>>
>>
>> --
>> —
>> Jialin Qiao
>> School of Software, Tsinghua University
>>
>> 乔嘉林
>> 清华大学 软件学院
>>
>

Re: [REMINDER] JIRA should be closed after the PR is merged :)

[jincheng sun]

That's great Jialin! I received a lot of Jira-report emails. It's looks
pretty nice for current JIRAs status. :)

Best,
Jincheng

Jialin Qiao  于2019年12月18日周三 下午4:10写道：

> Hi,
>
> I have gone through the open issues and closed those already fixed, and you
> should have received the Jira-report email bombing already :D
>
> Thanks,
> Jialin Qiao
>
> jincheng sun  于2019年12月18日周三 下午3:09写道：
>
> > Hi Committers & PPMC,
> >
> > I found that some of JIRAs have not be close even the PR already merged.
> > The first time [1] I thought it was accidentally forgotten, just now
> found
> > [2] have was also forgotten, so let me remind you here.
> >
> > BTW:
> > One suggestion here is: Would be better to left some comments when we
> close
> > the JIRA. such as : Fixed in master: {commit id }, Fixed in 0.9: {commit
> > id}.
> >
> > Feel free to correct me If the reminders and suggestions are not suitable
> > for IoTDB :)
> >
> > What do you think?
> >
> > Best,
> > Jincheng
> > @sunjincheng121 <https://twitter.com/sunjincheng121>
> >
> > [1] https://issues.apache.org/jira/browse/IOTDB-362
> > [2] https://issues.apache.org/jira/browse/IOTDB-365
> >
>
>
> --
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>

Re: Please do me a favor :)

[jincheng sun]

Great, thanks for your kindly help :) Jialin!

Best,
Jincheng
@sunjincheng121 <https://twitter.com/sunjincheng121>


Jialin Qiao  于2019年12月18日周三 下午4:05写道：

> Hi,
>
> Thanks for reminding, I have finalized the release of 0.9.0, 0.8.1 and
> 0.8.2.
> IOTDB-268 is a new feature and IOTDB-344 is an environmental problem, which
> is not a bug inside IoTDB.
> They are not solved, so I removed the fixed version in these two issues and
> tag the affected version of IOTDB-344 to 0.9.0.
> However, I can not assign the affected version of IOTDB-268...  Therefore,
> it is left empty.
>
> Thanks,
> Jialin Qiao
>
> jincheng sun  于2019年12月18日周三 下午3:41写道：
>
> > Hi PPMC,
> >
> > When I do some check for prepare of release IoTDB 0.9.1, I double check
> > that the IoTDB 0.9.1 is already released[1]. But we do not finalized the
> > release version in JIRA.[2].
> > I do n’t have permission to operate this action, so I am grateful to
> anyone
> > who has permission to help complete the final release of IoTDB 0.9.0.
> >
> >
> > We also need reset the fix version for [3][4] from the 0.9.0 to 0.9.1.
> and
> > I have not the permission, also need someone's help :)
> >
> > Best,
> > Jincheng
> > @sunjincheng121 <https://twitter.com/sunjincheng121>
> >
> > [1]
> >
> >
> https://lists.apache.org/thread.html/ebf6b2b4f435868a14e89fa3a767f99a0db71f4e22a7acc9a7b5b22b%40%3Cdev.iotdb.apache.org%3E
> > [2] https://issues.apache.org/jira/projects/IOTDB/versions/12345966
> > [3] https://issues.apache.org/jira/browse/IOTDB-268
> > [4] https://issues.apache.org/jira/browse/IOTDB-344
> >
>
>
> --
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>

Re: [DISCUSS] Release of 0.9.1

[jincheng sun]

I see, thanks for your explanation for IOTDB-300[1] and double check the
IOTDB-268[2] Jialin! :)

Best,
Jincheng
@sunjincheng121 <https://twitter.com/sunjincheng121>

[1] https://issues.apache.org/jira/browse/IOTDB-300
[2] https://issues.apache.org/jira/browse/IOTDB-268


Jialin Qiao  于2019年12月18日周三 下午3:47写道：

> Hi,
>
> IOTDB-300 is already fixed in 0.9.0. It is a bug introduced in
> 0.9.0-SNAPSHOT, therefore it is not included in the Release_Notes from
> 0.8.0 to 0.9.0.
>
> If I don't misunderstand, IOTDB-268 is not a blocker issue that affects the
> running of spark-iotdb-connector module. It is just a new feature that
> wants a new format of timestamp in spark-iotdb-connector.
>
> Thanks,
> Jialin Qiao
>
> jincheng sun  于2019年12月18日周三 下午3:23写道：
>
> > +1 for release IoTDB 0.9.1 as IOTDB-300 is very important fix.
> >
> > And I think the blocker issue [1] should be contains in 0.9.1, or someone
> > should check is whether a blocker issue.
> >
> > What do you think?
> >
> > Best,
> > Jincheng
> > @sunjincheng121 <https://twitter.com/sunjincheng121>
> >
> > [1] [IOTDB-268] When using spark-iotdb-connector, the read time is
> > timestamp
> > <https://issues.apache.org/jira/browse/IOTDB-268>
> >
> > Lei Rui  于2019年12月18日周三 下午2:30写道：
> >
> > > Hi Jialin,
> > >
> > >
> > > That's nice. Thank you.
> > >
> > >
> > > Lei Rui
> > >
> > >
> > > On 12/18/2019 14:25，Jialin Qiao wrote：
> > > Hi,
> > >
> > > That's very kind of you :)  I'd like to offer help and share my
> > experience
> > > if you meet trouble when releasing.
> > >
> > > Thanks,
> > > Jialin Qiao
> > >
> > > Lei Rui  于2019年12月18日周三 下午2:13写道：
> > >
> > > Hi,
> > >
> > >
> > > I want to challenge myself to be the release manager of 0.9.1.
> > >
> > >
> > > Regards,
> > > Lei Rui
> > >
> > >
> > > On 12/17/2019 20:47，Jialin Qiao wrote：
> > > Hi,
> > >
> > > Change list could be inferred from merged PRs in
> > > https://github.com/apache/incubator-iotdb/pulse
> > >
> > > The second, as far as I know, there is no need to do more patches,
> cause
> > I
> > > already cherry-pick all the bug-fix commits, but double-check is
> better.
> > >
> > > Thanks,
> > > Jialin Qiao
> > >
> > > Xiangdong Huang  于2019年12月17日周二 下午8:40写道：
> > >
> > > Hi,
> > >
> > > +1 for releasing 0.9.1.
> > >
> > > Two concerns:
> > >
> > > Actually, when I merge the bug-fix PRs, I also cherry-pick them into
> > > rel/0.9. Therefore, this release will be easier than 0.9.0...
> > >
> > > So, how to maintain the change list?
> > >
> > > The second is similar, how many patches should be involved into 0.9.1?
> > >
> > > Best,
> > > ---
> > > Xiangdong Huang
> > > School of Software, Tsinghua University
> > >
> > > 黄向东
> > > 清华大学 软件学院
> > >
> > >
> > > Jialin Qiao  于2019年12月17日周二 下午8:27写道：
> > >
> > > Hi,
> > >
> > > After releasing 0.9.0, we fixed some bugs that will impact the user
> > > experience. It's time to release 0.9.1, a bug-fix version of 0.9.0. Is
> > > there anyone who wants to be the release manager?
> > >
> > > Actually, when I merge the bug-fix PRs, I also cherry-pick them into
> > > rel/0.9. Therefore, this release will be easier than 0.9.0...
> > >
> > > Thanks,
> > > —
> > > Jialin Qiao
> > > School of Software, Tsinghua University
> > >
> > > 乔嘉林
> > > 清华大学 软件学院
> > >
> > >
> > >
> > >
> > > --
> > > —
> > > Jialin Qiao
> > > School of Software, Tsinghua University
> > >
> > > 乔嘉林
> > > 清华大学 软件学院
> > >
> > >
> > >
> > > --
> > > —
> > > Jialin Qiao
> > > School of Software, Tsinghua University
> > >
> > > 乔嘉林
> > > 清华大学 软件学院
> > >
> >
>
>
> --
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>

Re: [DISCUSS] Release of 0.9.1

[jincheng sun]

+1 for release IoTDB 0.9.1 as IOTDB-300 is very important fix.

And I think the blocker issue [1] should be contains in 0.9.1, or someone
should check is whether a blocker issue.

What do you think?

Best,
Jincheng
@sunjincheng121 

[1] [IOTDB-268] When using spark-iotdb-connector, the read time is timestamp


Lei Rui  于2019年12月18日周三 下午2:30写道：

> Hi Jialin,
>
>
> That's nice. Thank you.
>
>
> Lei Rui
>
>
> On 12/18/2019 14:25，Jialin Qiao wrote：
> Hi,
>
> That's very kind of you :)  I'd like to offer help and share my experience
> if you meet trouble when releasing.
>
> Thanks,
> Jialin Qiao
>
> Lei Rui  于2019年12月18日周三 下午2:13写道：
>
> Hi,
>
>
> I want to challenge myself to be the release manager of 0.9.1.
>
>
> Regards,
> Lei Rui
>
>
> On 12/17/2019 20:47，Jialin Qiao wrote：
> Hi,
>
> Change list could be inferred from merged PRs in
> https://github.com/apache/incubator-iotdb/pulse
>
> The second, as far as I know, there is no need to do more patches, cause I
> already cherry-pick all the bug-fix commits, but double-check is better.
>
> Thanks,
> Jialin Qiao
>
> Xiangdong Huang  于2019年12月17日周二 下午8:40写道：
>
> Hi,
>
> +1 for releasing 0.9.1.
>
> Two concerns:
>
> Actually, when I merge the bug-fix PRs, I also cherry-pick them into
> rel/0.9. Therefore, this release will be easier than 0.9.0...
>
> So, how to maintain the change list?
>
> The second is similar, how many patches should be involved into 0.9.1?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
> 黄向东
> 清华大学 软件学院
>
>
> Jialin Qiao  于2019年12月17日周二 下午8:27写道：
>
> Hi,
>
> After releasing 0.9.0, we fixed some bugs that will impact the user
> experience. It's time to release 0.9.1, a bug-fix version of 0.9.0. Is
> there anyone who wants to be the release manager?
>
> Actually, when I merge the bug-fix PRs, I also cherry-pick them into
> rel/0.9. Therefore, this release will be easier than 0.9.0...
>
> Thanks,
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
>
>
>
> --
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
>
>
> --
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>

[REMINDER] JIRA should be closed after the PR is merged :)

[jincheng sun]

Hi Committers & PPMC,

I found that some of JIRAs have not be close even the PR already merged.
The first time [1] I thought it was accidentally forgotten, just now found
[2] have was also forgotten, so let me remind you here.

BTW:
One suggestion here is: Would be better to left some comments when we close
the JIRA. such as : Fixed in master: {commit id }, Fixed in 0.9: {commit
id}.

Feel free to correct me If the reminders and suggestions are not suitable
for IoTDB :)

What do you think?

Best,
Jincheng
@sunjincheng121 

[1] https://issues.apache.org/jira/browse/IOTDB-362
[2] https://issues.apache.org/jira/browse/IOTDB-365

Re: [VOTE] Enrich information of project committers in IOTDB website

[jincheng sun]

+1, and I have left a few comments in the PR.

Best,
Jincheng

Twitter: https://twitter.com/sunjincheng121


Jack Tsai  于2019年12月17日周二 下午3:56写道：

> Hi,
> +1 for this idea.
>
> Best regards,
> Jack Tsai
>
> 取得 iOS 版 Outlook
> 
> 寄件者: Jialin Qiao 
> 寄件日期: Tuesday, December 17, 2019 7:52:33 AM
> 收件者: dev@iotdb.apache.org 
> 主旨: Re: [VOTE] Enrich information of project committers in IOTDB website
>
> Hi,
>
> +1,  we could create a confluence page about this if passed.
>
> Thanks,
> Jialin Qiao
>
> Xiangdong Huang  于2019年12月17日周二 下午3:42写道：
>
> > Hi,
> >
> > +1 for the idea.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > 孙泽嵩  于2019年12月17日周二 下午3:29写道：
> >
> > > Hi all,
> > >
> > > Thanks to @Jincheng, we intend to enrich information of project
> > committers
> > > in website. (The last VOTE e-mail was actually in a new thread… but
> > somehow
> > > showed together with the DISCUSS thread in some e-mail clients, so I
> > change
> > > the theme a little this time ...)
> > >
> > > I have opened a PR [1] in our website repository, so if this VOTE pass
> > and
> > > the PR is merged, every committer and contributor can open PR
> themselves
> > to
> > > maintain their own information. Besides, we also add two lists for
> those
> > > contributors who have submitted PR(s) and propose issue(s) for IoTDB to
> > > encourage more and more people to join us.
> > >
> > > I’d like to briefly introduce how to maintain your information:
> > >
> > > 1. Search your name in 'src/views/Contributor.vue' , and update the
> > > information (including avatar, name, role, organization, apache id, and
> > > starting date).
> > >
> > > 2. If your name hasn't existed in the page, you can just add your
> > > information in the list accordingly: ‘conList' for committers,
> > > ‘conWithPRList' for contributors who have submitted PR(s), and
> > > ‘conWithIssueList' for contributors who have proposed issue(s).
> > >
> > > 3. As for avatar, you can either upload a picture (better to limit the
> > > size <150KB) by adding one in '/assets/img/contributor-avatar', then
> you
> > > only need to use the file name in the information; Or, you can use a
> > photo
> > > link. (You can see the example in PR description)
> > >
> > >
> > > A minimum of 3 binding +1 votes and more binding +1 than binding -1
> > > are required to pass.
> > >
> > > [ ]  +1 accept
> > > [ ]  -1 reject (explanation required)
> > >
> > > [1] https://github.com/apache/incubator-iotdb-website/pull/50 <
> > > https://github.com/apache/incubator-iotdb-website/pull/50>
> > >
> > >
> > > Best,
> > > ---
> > > Zesong Sun
> > > School of Software, Tsinghua University
> > >
> > > 孙泽嵩
> > > 清华大学 软件学院
> > >
> > >
> >
>
>
> --
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>

Re: [VOTE] Enrich information of project committers in website

[jincheng sun]

+1 for bring up a separate thread for VOTING.

The content of the vote should be consistent with the content of the
discussion. At the same time, the time and method of the end of the vote
should be explained in the vote email, such as:  “The vote is open for the
next 72 hours and passes if a majority of at least three +1 Committer votes
are cast.“

Best,
Jincheng
Twitter: https://twitter.com/sunjincheng121


Xiangdong Huang  于2019年12月17日周二 下午1:44写道：

> Hi Zesong,
>
> Thanks very much.
>
> Can you open a new thread entitled "[VOTE] Enrich information of project
> committers in IoTDB website"?
>
> Current thread name is started with [discuss], which may lead to someones
> omitting the vote.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> 孙泽嵩  于2019年12月17日周二 上午11:39写道：
>
> > Hi all,
> >
> > Thanks to @Jincheng, we intend to enrich information of project
> committers
> > in website.
> >
> > I have opened a PR [1] in our website repository, so if this VOTE pass
> and
> > the PR is merged, every committer and contributor can open PR themselves
> to
> > maintain their own information. Besides, we also add two lists for those
> > contributors who have submitted PR(s) and propose issue(s) for IoTDB to
> > encourage more and more people to join us.
> >
> > I’d like to briefly introduce how to maintain your information:
> >
> > 1. Search your name in 'src/views/Contributor.vue' , and update the
> > information (including avatar, name, role, organization, apache id, and
> > starting date).
> >
> > 2. If your name hasn't existed in the page, you can just add your
> > information in the list accordingly: ‘conList' for committers,
> > ‘conWithPRList' for contributors who have submitted PR(s), and
> > ‘conWithIssueList' for contributors who have proposed issue(s).
> >
> > 3. As for avatar, you can either upload a picture (better to limit the
> > size <150KB) by adding one in '/assets/img/contributor-avatar', then you
> > only need to use the file name in the information; Or, you can use a
> photo
> > link. (You can see the example in PR description)
> >
> >
> > A minimum of 3 binding +1 votes and more binding +1 than binding -1
> > are required to pass.
> >
> > [ ]  +1 accept
> > [ ]  -1 reject (explanation required)
> >
> > [1] https://github.com/apache/incubator-iotdb-website/pull/50
> >
> >
> > Best,
> > ---
> > Zesong Sun
> > School of Software, Tsinghua University
> >
> > 孙泽嵩
> > 清华大学 软件学院
> >
> >
>

Re: [DISCUSS] Enrich information of project committers in website

[jincheng sun]

Hi all,

Sounds pretty good, thank you for pushing forward this work Zesong!

I want to know that do we need to make a VOTE thread to make the final
decision about the change of this discussion?(I didn't find the relevant
documents.)
Of course, this change is very small, and we can also avoid VOTE. I raised
this question to make the development of IoTDB community more clear and
rule-based and healthy growing :)

What do you think?

Best,
Jincheng

Twitter: https://twitter.com/sunjincheng121


孙泽嵩  于2019年12月17日周二 上午9:49写道：

> Hi,
>
>
> I like this idea very much and would like to update our committer page
> like gobblin[1] does.
>
> I’d like to open an “example” PR later as a model in the website
> repository [2], so that every committer and contributor can maintain their
> own information by opening PR themselves.
>
> What do you think?
>
>
> [1] http://gobblin.incubator.apache.org/people/ <
> http://gobblin.incubator.apache.org/people/>
> [2] https://github.com/apache/incubator-iotdb-website <
> https://github.com/apache/incubator-iotdb-website>
>
> Best,
> ---
> Zesong Sun
> School of Software, Tsinghua University
>
> 孙泽嵩
> 清华大学 软件学院
>
> > 2019年12月16日 15:59，jincheng sun  写道：
> >
> > Starting date
>
>

Re: [DISCUSS] Enrich information of project committers in website

[jincheng sun]

Hi Xiangdong,

Thank you for your confirmation of the proposal!

Yes, regarding the `Organization` information, compared with `Apache ID`
and `Name`, the update frequency of `Organization` will be higher, which
will bring some maintenance costs to committer.

You are right, I agree that this information can show the diversity
directly, and considering people contribute as individuals, I prefer reduce
the maintenance costs.

What do you think?

Best,
Jincheng

Twitter: https://twitter.com/sunjincheng121


Xiangdong Huang  于2019年12月16日周一 下午11:08写道：

> Hi,
>
> Thanks for the suggestion.
>
> > So, I proposal that enrich information of project committers as follows
>
> I like the idea. More detailed info may encourage the committers (Give the
> committers more chance to show themselves).
>
> > But I don't know why this information was originally added, maybe
> @Xiangdong know more about this. :)
> > It can be for a number of reasons, some projects which were started by
> one company may want to show how diverse they have become and highlight
> that.
>
> Yes, indeed actually we initially wanted to show the diversity of the
> community. But unfortunately we forgot to maintain the list.
> For example, some guys in the list have graduated and still contribute to
> the project even they have worked for Microsoft, Ali and ByteDance etc..
>
> If we can collect the info and keep update, it would be nice to show the
> diversity. But if we do not maintain that, it is a negative way...
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2019年12月16日周一 下午9:40写道：
>
> > Hi Justin，
> >
> > Thank you for your explanation，It makes more sense to me .
> >
> > +1 for remove the Organization information.
> >
> > Best，
> > Jincheng
> >
> >
> >
> >
> > Justin Mclean 于2019年12月16日 周一19:55写道：
> >
> > > Hi,
> > >
> > > > But I don't know why this information was originally added, maybe
> > > > @Xiangdong know more about this. :)
> > >
> > > It can be for a number of reasons, some projects which were started by
> > one
> > > company may want to show how diverse they have become and highlight
> that.
> > > In some cases some popular projects put IMO  too much emphasis on who
> > their
> > > committers/(P)PMC member work for. In most cases I think it just
> someone
> > > has copied and pasting from another popular project without thinking
> why
> > > that is there.
> > >
> > > Thanks,
> > > Justin
> >
> > --
> >
> > Best,
> > Jincheng
> >
> > Twitter: https://twitter.com/sunjincheng121
> >
>

Re: [DISCUSS] Enrich information of project committers in website

[jincheng sun]

Hi Justin，

Thank you for your explanation，It makes more sense to me .

+1 for remove the Organization information.

Best，
Jincheng




Justin Mclean 于2019年12月16日 周一19:55写道：

> Hi,
>
> > But I don't know why this information was originally added, maybe
> > @Xiangdong know more about this. :)
>
> It can be for a number of reasons, some projects which were started by one
> company may want to show how diverse they have become and highlight that.
> In some cases some popular projects put IMO  too much emphasis on who their
> committers/(P)PMC member work for. In most cases I think it just someone
> has copied and pasting from another popular project without thinking why
> that is there.
>
> Thanks,
> Justin

-- 

Best,
Jincheng

Twitter: https://twitter.com/sunjincheng121

Re: [DISCUSS] Enrich information of project committers in website

[jincheng sun]

Hi Justin,

Personally, for a open source project the `Organization` info is not
necessary.

But I don't know why this information was originally added, maybe
@Xiangdong know more about this. :)

Best,
Jincheng

Twitter: https://twitter.com/sunjincheng121


Justin Mclean  于2019年12月16日周一 下午4:56写道：

> HI,
>
> > - Organization - The organization(school, company)
>
> People contribute as individuals not who they work for so it may be best
> to leave that information out, even if some projects put it in.
>
> Thanks,
> Justin

[DISCUSS] Enrich information of project committers in website

[jincheng sun]

Hi folks,

We can find the committers of IoTDB in the page [1]. Currently, there are
two columns in the infomation table:

  - Name - Full name of a Committer
  - Organization - The organization(school, company, ?)

There are some of incubator project supported same info as IoTDB, such as
[2], and some of incubator projects are add more information about the
committers. Such as [3] Add Role column, [4] Add picture and others, [5]
Add ApacheID.

So, I proposal that enrich information of project committers as follows：

- Avatar - A small photo of the Committer
- Name - Full name of the Committer
- Role - The roles in IoTDB Community, Such as: Committer, PPMC/Committer
- Apache ID - The Apache ID of the Committer.
- Organization - The organization(school, company)
- Starting date - The time of added to list

I think enrich information of project committers can easily know well about
the committer when someone browse the website.

What do you think?

Best,
Jincheng
Twitter: https://twitter.com/sunjincheng121

[1] https://iotdb.apache.org/#/Community/Project%20Committers
[2] https://druid.apache.org/community/
[3] https://cwiki.apache.org/confluence/display/PINOT/Committers
[4] http://gobblin.incubator.apache.org/people/
[5] http://nemo.incubator.apache.org/pages/team/

Re: Maintain user roles of IoTDB Jira

[jincheng sun]

Yes, I see :). Thank you for clarifying who can perform maintenance Justin !

Best,
Jincheng
-
Committer & PMC Member at @ApacheFlink
Staff Engineer at @Alibaba
Blog: https://enjoyment.cool
Twitter: https://twitter.com/sunjincheng121
--


Justin Mclean  于2019年12月15日周日 上午7:51写道：

> Hi,
>
> > I found that the committer information(Number of person) is not
> > synchronized between [1] and [2] pages. :)
>
> It up to the :PMC to do that.
>
> Thanks,
> Justin
>

Re: Maintain user roles of IoTDB Jira

[jincheng sun]

Just a reminder:

I found that the committer information(Number of person) is not
synchronized between [1] and [2] pages. :)

Best,
Jincheng
-
Committer & PMC Member at @ApacheFlink
Staff Engineer at @Alibaba
Blog: https://enjoyment.cool
Twitter: https://twitter.com/sunjincheng121
--
[1] https://whimsy.apache.org/roster/ppmc/iotdb
[2] https://iotdb.apache.org/#/Community/Project%20Committers


jincheng sun  于2019年12月14日周六 下午10:38写道：

> Hi Xiangdong,
>
> Thank you for your kind words. If it can improve the IoTDB community, I am
> happy to share my thoughts :)
>
> Best,
> Jincheng
> -
> Committer & PMC Member at @ApacheFlink
> Staff Engineer at @Alibaba
> Blog: https://enjoyment.cool
> Twitter: https://twitter.com/sunjincheng121
> --
>
>
> Xiangdong Huang  于2019年12月14日周六 下午1:07写道：
>
>> By the way,
>>
>> For PPMC and Apache committers, I recommend you use your Apache ID to
>> login
>> JIRA.
>> Then by default, I can grant all users who are on IoTDB roster[1] the
>> committer permission.
>> It will be more maintainable: once someone are voted as a new committer,
>> we
>> can maintain his/her JIRA permission at the same time.
>>
>> [1] https://whimsy.apache.org/roster/ppmc/iotdb
>>
>> Best,
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>>
>>  黄向东
>> 清华大学 软件学院
>>
>>
>> Xiangdong Huang  于2019年12月14日周六 下午1:03写道：
>>
>> > Hi all committers,
>> >
>> > Thanks @jincheng sun from Flink community, I find the position to
>> maintain
>> > users role on jira...
>> >
>> > Now the project Lead is Justin and Chris and me are administrator roles.
>> >
>> > So, if you are a committer and want to get the permission to assign
>> issues
>> > and close issues, please either: (1) tell me your jira user name; or (2)
>> > make sure you are using Apache id to login the JIRA (jira supports LDAP
>> > now) and tell me about that. Then I will give you the committer/PMC
>> roles.
>> >
>> >
>> > I would like to invite our other mentors to give me the user name and
>> then
>> > I can grant the permissions, too.
>> >
>> > Best,
>> > ---
>> > Xiangdong Huang
>> > School of Software, Tsinghua University
>> >
>> >  黄向东
>> > 清华大学 软件学院
>> >
>>
>

Re: Maintain user roles of IoTDB Jira

[jincheng sun]

Hi Xiangdong,

Thank you for your kind words. If it can improve the IoTDB community, I am
happy to share my thoughts :)

Best,
Jincheng
-
Committer & PMC Member at @ApacheFlink
Staff Engineer at @Alibaba
Blog: https://enjoyment.cool
Twitter: https://twitter.com/sunjincheng121
--


Xiangdong Huang  于2019年12月14日周六 下午1:07写道：

> By the way,
>
> For PPMC and Apache committers, I recommend you use your Apache ID to login
> JIRA.
> Then by default, I can grant all users who are on IoTDB roster[1] the
> committer permission.
> It will be more maintainable: once someone are voted as a new committer, we
> can maintain his/her JIRA permission at the same time.
>
> [1] https://whimsy.apache.org/roster/ppmc/iotdb
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Xiangdong Huang  于2019年12月14日周六 下午1:03写道：
>
> > Hi all committers,
> >
> > Thanks @jincheng sun from Flink community, I find the position to
> maintain
> > users role on jira...
> >
> > Now the project Lead is Justin and Chris and me are administrator roles.
> >
> > So, if you are a committer and want to get the permission to assign
> issues
> > and close issues, please either: (1) tell me your jira user name; or (2)
> > make sure you are using Apache id to login the JIRA (jira supports LDAP
> > now) and tell me about that. Then I will give you the committer/PMC
> roles.
> >
> >
> > I would like to invite our other mentors to give me the user name and
> then
> > I can grant the permissions, too.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
>

Re: [Discuss] More reasonable issue permission on JIRA

[jincheng sun]

Hi Xiangdong,

Thanks for bring up this discussion!

Big +1 for adding the role of "Contributors" to "Assignable User" list, as
I think allowing JIRA. to be assigned to contributors is a prerequisite for
growing our IoTDB, and this improvement will showing the welcome to new
contributors. :)

Best,
Jincheng
-
Committer & PMC Member at @ApacheFlink
Staff Engineer at @Alibaba
Blog: https://enjoyment.cool
Twitter: https://twitter.com/sunjincheng121
--


Xiangdong Huang  于2019年12月14日周六 下午1:46写道：

> Hi,
>
> Now IoTDB is using _Default Permission Scheme_ on jira [1].
>
> The schema looks good, but one thing that I think we can have a change:
>
> Current the "Assignable User" needs to be Administrator/PMC/Committer.
> However, if someone (who is not a committer) reports a bug and he/she has
> the ability to fix that and can submit a PR. I think we can assign the
> issue to him/her.
>
> It will give more sense of honor to users who are not the committers but
> make real contribution to the project.  And, it will attract more users to
> contribute to IoTDB, I think. Some users also point out that [2].
>
> Therefore, I suggest to change "Assignable User" to
> Administrator/PMC/Committer/Reporter/Contributor..
>
> Even though I have the administrator permission of IoTDB JIRA, but the
> above modification nees jira-administrator permission, which is higher than
> what I can do.
>
> Maybe  @Christofer Dutz   can help us. :-D.
>
> [1]
>
> https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/permissions
> [2] https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-365
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>

Re: [jira] [Created] (IOTDB-363) Fix link error for `Development-Contributing.md` and `Development-Document.md`

[jincheng sun]

Thanks for your quick response Jialin!

Would be nice if you can add the comments in JIRA [1] or the PR [2] :)

Best,
jincheng
-
Committer & PMC Member at @ApacheFlink
Staff Engineer at @Alibaba
Blog: https://enjoyment.cool
Twitter: https://twitter.com/sunjincheng121
--

[1] https://issues.apache.org/jira/browse/IOTDB-363
[2] https://github.com/apache/incubator-iotdb/pull/647


Jialin Qiao  于2019年12月12日周四 下午9:02写道：

> Hi,
>
> Welcome!  +1 for the progress version.
>
> Jialin Qiao
>
> sunjincheng (Jira)  于2019年12月12日周四 下午8:39写道：
>
> > sunjincheng created IOTDB-363:
> > -
> >
> >  Summary: Fix link error for `Development-Contributing.md`
> and
> > `Development-Document.md`
> >  Key: IOTDB-363
> >  URL: https://issues.apache.org/jira/browse/IOTDB-363
> >  Project: Apache IoTDB
> >   Issue Type: Bug
> > Reporter: sunjincheng
> >  Fix For: 0.9.1
> >
> >
> > Currently, the link [https://iotdb.apache.org/#/Documents] of docs in [
> > https://iotdb.apache.org/#/Development/Contributing]
> >
> > is incorrect, I think we should correct it as follows:
> >
> > 1) [https://iotdb.apache.org/#/Documents] -> [
> > https://iotdb.apache.org/#/Documents/progress/chap1/sec1]
> >
> > or
> >
> > 2) [https://iotdb.apache.org/#/Documents] -> [
> > https://iotdb.apache.org/#/Documents/0.9.0/chap1/sec1]
> >
> > I prefer to `[https://iotdb.apache.org/#/Documents/progress/chap1/sec1]`
> 
> > 
> >
> > What do you think?
> >
> >
> >
> > --
> > This message was sent by Atlassian Jira
> > (v8.3.4#803005)
> >
>
>
> --
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>

Re: Contributor Permission for IOTDB-362

[jincheng sun]

Hi Xiangdong,

That's all right, thank you so much!

Best Regards,
金竹(jincheng)
--
Committer & PMC Member at @ApacheFlink
Staff Engineer at @Alibaba
Phone number: (+86) 18158190225
Blog: https://enjoyment.cool
Twitter: https://twitter.com/sunjincheng121
--

Xiangdong Huang  于2019年12月12日周四 下午7:45写道：

> Hi Jincheng,
>
> Welcome to contribution!
>
> Sorry I tried to assign the issue to you but failed.
>
> But do not worry, I will merge your PR after the code review.
>
> Best.
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> jincheng sun  于2019年12月12日周四 下午5:11写道：
>
> > Hi,
> >
> > My name is Jincheng Sun, I am just find a bug of IoTDB webside, more
> detail
> > can be found in [1], I'd like to contribute some minor improvements to
> the
> > IotDB, My JIRA user name is 'sunjincheng121'.
> >
> > Best,
> > Jincheng
> >
> > [1] https://issues.apache.org/jira/browse/IOTDB-362
> >
>

Contributor Permission for IOTDB-362

[jincheng sun]

Hi,

My name is Jincheng Sun, I am just find a bug of IoTDB webside, more detail
can be found in [1], I'd like to contribute some minor improvements to the
IotDB, My JIRA user name is 'sunjincheng121'.

Best,
Jincheng

[1] https://issues.apache.org/jira/browse/IOTDB-362