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 <[email protected]> 
Gesendet: Sonntag, 14. Februar 2021 15:08
An: dev <[email protected]>
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

 黄向东
清华大学 软件学院

Reply via email to