Hi,

This discussion has received 3 +1 votes from PMC/Committers.

Jialin Qiao,
Chao Wang,
Jincheng Sun,

and the 4th, me.

If there is no negative opinion, I will create a new repo tomorrow.

Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Jialin Qiao <[email protected]> 于2021年2月18日周四 下午5:04写道:

> +1
>
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> &gt; -----原始邮件-----
> &gt; 发件人: "Chao Wang" &lt;[email protected]&gt;
> &gt; 发送时间: 2021-02-18 16:35:20 (星期四)
> &gt; 收件人: dev <[email protected]>
> &gt; 抄送:
> &gt; 主题: Re: [DISCUSS] Create a new Repo to upload binary files (images
> for markdown, compiled thrift binary, etc..)
> &gt;
> &gt; + 1
> &gt;
> &gt;
> &gt;
> &gt; ---Original---
> &gt; From: "Xiangdong Huang"<[email protected]&gt;> Date: Thu, Feb 18,
> 2021 16:22 PM
> &gt; To: "dev"<[email protected]&gt;;> Subject: Re: [DISCUSS] Create a
> new Repo to upload binary files (images for markdown, compiled thrift
> binary, etc..)
> &gt;
> &gt;
> &gt; Hi, any suggestions about this discussion? (I need at least 3 +1 for
> the
> &gt; next step or a formal vote)
> &gt; Best,
> &gt; -----------------------------------
> &gt; Xiangdong Huang
> &gt; School of Software, Tsinghua University
> &gt;
> &gt; &nbsp;黄向东
> &gt; 清华大学 软件学院
> &gt;
> &gt;
> &gt; jincheng sun <[email protected]&gt; 于2021年2月15日周一=""
> 下午10:50写道:="">
> &gt; &gt; Thanks for bring up this discussion, Xiangdong!
> &gt; &gt;
> &gt; &gt; The problem of network access is really a long-term problem for
> Chinese
> &gt; &gt; users. For the convenience of users, we really need a special
> warehouse to
> &gt; &gt; store the current and future pictures and binary files.
> &gt; &gt;
> &gt; &gt; So, +1 for creating the `apache/iotdb-resources` to&nbsp; store
> all these files
> &gt; &gt; for both `iotdb` and `iotdb-website` repo.
> &gt; &gt;
> &gt; &gt; Best,
> &gt; &gt; Jincheng
> &gt; &gt;
> &gt; &gt;
> &gt; &gt; Xiangdong Huang <[email protected]&gt; 于2021年2月15日周一=""
> 上午9:02写道:=""> &gt;
> &gt; &gt; &gt; Hi Chris,
> &gt; &gt; &gt;
> &gt; &gt; &gt; 1. About thrift.
> &gt; &gt; &gt; Indeed we learned from PLC4x and maintain a module to
> compile thrift (as
> &gt; &gt; &gt; well as boost initially, but it still requires installing
> flex and bison.
> &gt; &gt; &gt; and finally we give up compiling boost, and only maintain
> compiling
> &gt; &gt; &gt; thrift). But now it is just used to generate static or
> dynamic library
> &gt; &gt; for
> &gt; &gt; &gt; c++ codes.
> &gt; &gt; &gt;
> &gt; &gt; &gt; The question is, users who want to compile the source code
> has to install
> &gt; &gt; &gt; flex, bison, and boost (byw, flex and bison have version
> requirements)
> &gt; &gt; &gt; first... It is not very friendly (and time consuming) for
> new users.
> &gt; &gt; &gt;
> &gt; &gt; &gt; 2. For images
> &gt; &gt; &gt; In our docs (in markdown files), we use external links
> (e.g., [1],
> &gt; &gt; provided
> &gt; &gt; &gt; by github). They are not accessible in China.
> &gt; &gt; &gt;
> &gt; &gt; &gt; A simple solution is saving the original image files to
> our&nbsp; repo (e.g.,
> &gt; &gt; &gt; create a folder called 'imgs'), and use relative path in
> our markdowns.
> &gt; &gt; &gt; After compiling the website, the generated static htmls
> will keep using
> &gt; &gt; the
> &gt; &gt; &gt; relative path and thereby they will be accessible in China
> (as they will
> &gt; &gt; be
> &gt; &gt; &gt; upload to iotdb.apache.org).
> &gt; &gt; &gt;
> &gt; &gt; &gt; But the drawback is it will increase the size of the repo
> (images are
> &gt; &gt; &gt; binary files so that once we update an image, the whole
> file will be
> &gt; &gt; &gt; replaced, and the git history has few meaning). That is why
> I'd like to
> &gt; &gt; &gt; create a new repo and users/developers can choose whether
> they need to
> &gt; &gt; &gt; clone the repo.
> &gt; &gt; &gt;
> &gt; &gt; &gt;
> &gt; &gt; &gt; [1]
> &gt; &gt; &gt;
> &gt; &gt; &gt;
> &gt; &gt;
> https://user-images.githubusercontent.com/19167280/73625222-ddd88680-467e-11ea-9098-e808ed4979c5.png
> &gt; &gt; &gt;
> &gt; &gt; &gt; Best,
> &gt; &gt; &gt; -----------------------------------
> &gt; &gt; &gt; Xiangdong Huang
> &gt; &gt; &gt; School of Software, Tsinghua University
> &gt; &gt; &gt;
> &gt; &gt; &gt;&nbsp; 黄向东
> &gt; &gt; &gt; 清华大学 软件学院
> &gt; &gt; &gt;
> &gt; &gt; &gt;
> &gt; &gt; &gt; Christofer Dutz <[email protected]&gt;
> 于2021年2月14日周日="" 下午11:14写道:=""> &gt; &gt;
> &gt; &gt; &gt; &gt; Hi Xiangdong,
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; regarding thrift ... how about doing it similar to our
> Maven-triggered
> &gt; &gt; &gt; &gt; Thrift build in PLC4X?
> &gt; &gt; &gt; &gt; I'm admittedly not a fan of requiring stuff in Apache
> projects which is
> &gt; &gt; &gt; &gt; maintained by individuals.
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; It doesn't have to be built every time but it would be
> great if there
> &gt; &gt; was
> &gt; &gt; &gt; &gt; a job we could manually trigger to build the Thrift
> compiler
> &gt; &gt; executalbes
> &gt; &gt; &gt; &gt; every time we need them.
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; But regarding images: ... where are these referenced?
> Why not put the
> &gt; &gt; &gt; &gt; image resources in the repo where also the content is
> located? Perhaps
> &gt; &gt; &gt; &gt; however I'm not understanding the setup correctly
> though.
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; Chris
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; -----Ursprüngliche Nachricht-----
> &gt; &gt; &gt; &gt; Von: Xiangdong Huang <[email protected]&gt;> &gt;
> &gt; &gt; Gesendet: Sonntag, 14. Februar 2021 15:08
> &gt; &gt; &gt; &gt; An: dev <[email protected]&gt;> &gt; &gt; &gt;
> Betreff: [DISCUSS] Create a new Repo to upload binary files (images for
> &gt; &gt; &gt; &gt; markdown, compiled thrift binary, etc..)
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; Hi,
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; Currently, we upload all figures to github's issues to
> get a public URL
> &gt; &gt; &gt; &gt; and use it in our markdown files. The question is, it
> is hard to
> &gt; &gt; maintain
> &gt; &gt; &gt; &gt; the figures, and, the URL is *.githubusercontent.com/*,
> which maybe
> &gt; &gt; can
> &gt; &gt; &gt; &gt; not be accessed in China.
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; Besides, we are using compiled thrift binary from
> &gt; &gt; &gt; &gt; https://github.com/jt2594838/mvn-thrift-compiler/.
> Though it is
> &gt; &gt; compiled
> &gt; &gt; &gt; &gt; by our committer Tian Jiang, it is a personal repo and
> may get
> &gt; &gt; suspected
> &gt; &gt; &gt; by
> &gt; &gt; &gt; &gt; users.
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; Therefore, I'd like to apply for creating a new repo,
> &gt; &gt; &gt; &gt; apache/iotdb-resources to collect all these files.
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; The repo can be as a git submodule of iotdb, and so
> that all figures
> &gt; &gt; can
> &gt; &gt; &gt; &gt; be used as a relative path in markdowns. As a result,
> the figures will
> &gt; &gt; be
> &gt; &gt; &gt; &gt; compiled as local files for our website (i.e., all
> figures' URL are
> &gt; &gt; &gt; &gt; iotdb.apache.org/* rather than githubusercontent.com/*
> ).
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; thrift compiler will also be download from
> apache/iotdb-resources,
> &gt; &gt; which
> &gt; &gt; &gt; &gt; will convincing users and is more controllable.
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; Why not upload these resources directly to
> apache/iotdb: for
> &gt; &gt; controlling
> &gt; &gt; &gt; &gt; the size of iotdb's repo.
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt; Best,
> &gt; &gt; &gt; &gt; -----------------------------------
> &gt; &gt; &gt; &gt; Xiangdong Huang
> &gt; &gt; &gt; &gt; School of Software, Tsinghua University
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt; &gt;&nbsp; 黄向东
> &gt; &gt; &gt; &gt; 清华大学 软件学院
> &gt; &gt; &gt; &gt;
> &gt; &gt; &gt;
> &gt; &gt;
> </[email protected]&gt;></[email protected]&gt;></
> [email protected]&gt;></[email protected]&gt;></
> [email protected]&gt;></[email protected]&gt;;></
> [email protected]&gt;></[email protected]>

Reply via email to