+ 1


---Original---
From: "Xiangdong Huang"<[email protected]&gt;
Date: Thu, Feb 18, 2021 16:22 PM
To: "dev"<[email protected]&gt;;
Subject: Re: [DISCUSS] Create a new Repo to upload binary files (images for 
markdown, compiled thrift binary, etc..)


Hi, any suggestions about this discussion? (I need at least 3 +1 for the
next step or a formal vote)
Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University

&nbsp;黄向东
清华大学 软件学院


jincheng sun <[email protected]&gt; 于2021年2月15日周一 下午10:50写道:

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

Reply via email to