mirrorz-org / org Goto Github PK

包括：

• 各个仓库的用途
• 如何添加新镜像站

After some meetings with related party, I can say that we may set up <mirrors.edu.cn> if we have enough participating mirror sites and our frontend and backend are ready and good enough.

The frontend has gone through immense development in the winter, and it is ready undoubtly, so today we focus on the 302 backend.

The development of mirrorz-302 finally comes to the stage of testing. To test the performance and policy of mirrorz-302, we need to get mirror sites involved, so here comes this issue: review and try to provide mirrorz.d.json

In the design of mirrorz-302, most of the parameters from users, mirror sites and operators have been taken into
consideration. These are detailed in the README of mirrorz-302. For the mirror sites, mirrorz.d.json is what they should care, this file tries to model all the parameters being exposed to end users, and these parameters help mirrorz-302 decide which mirror it should redirect users to.

However, this file still needs much review and refinement as admins of mirror sites are more experienced in this topic, therefore in this issue we discuss the refinement of this format. This discussion happens within one week, namely the format of mirrorz.d.json would be freezed to a version number after 2021-08-15 23:59:00 UTC+8.

Also, interested mirror sites can try to provide mirrorz.d.json for testing purpose, as a testing 302 backend has being brought up for demo. The process of generating ASN list can be done by analysing nginx log as instructed in ipasn/README.

To:
BFSU: @happyaron
BJTU: @chestnutprog
CQU: @weearc @Hagb
CQUPT: @Sajotim @ztelliot
DGUT: @AnyMoe @MasterKenway
HIT: @billchenchina
LZU: @prcups
NJU: @njulug
NJUPT: @guliujian
NWAFU: @bianyifan
PKU: @JeremyGuo
SJTUG: @skyzh @PhotonQuantum
SUSTech Cra: @sparkcyf
TUNA: @Harry-Chen
USTC: @taoky @iBug
WSYU: @felixonmars
YNUOSA: @STRRL

Cc:
BIT: @phy25
BYRIO: @FredericDT
XTOM: @Showfom
OpenTUNA: @jiegec