In docs/design.md#source-file-processors, document the rationale for using qjz9zk as TLD · ungoogled-software/ungoogled-chromium#3465

(0 评论) (1 反应) (0 负责人)Python (18,674 star) (771 fork)batch import

enhancementhelp wanted

描述

Description

Explain the rationale in docs, to have git track the reasons together with their implementation.

Who's implementing?

I'm willing to implement this feature myself

The problem

Using .qjz9zk as a TLD seens odd without explanation. The more intuitive way would seem to be to use a 2nd level domain qjz9zk.invalid. There had been an issue for this (#1681, locked without resolution) and a discussion (#1891, now deleted), so currently the reasons seem undocumented.

Possible solutions

Independent of the current state of the discussion, I think this decision is important enough to explain in the docs. That way, the git history will reflect the evolution of maintainers' opinion on that discussion. This will make it easier to validate whether a specific version's implementation properly matches the reasons at that time.

Alternatives

No response

Additional context

No response

贡献者指南

技术栈: 无
领域: documentation
议题类型: documentation
难度: 2
预计时间: under 1 hour
活动状态: fresh
清晰度: clear
前置要求: Review issue #1681Review discussion #1891
新手友好度: 95
研究方向: First, review the linked issue #1681 and discussion #1891 to understand the historical context and rationale for using .qjz9zk as a top level domain instead of a second level domain. Then, locate the 'source file processors' section in docs/design.md and add a new subsection explaining the rationale clearly, including references to the discussions. Ensure that the explanation includes why .qjz9zk was chosen and why alternative approaches like qjz9zk.invalid were not used.