## S1-level module There are a few suggestions for clarifying the S1-level module. An S1-level module is a module that does not follow the restrictions outlined in the S0. Specifically, an S1-level module is usually used as dependencies by other major modules in the project.
The considerations that go into the S1-module are also not about how good the code is. As a matter of fact, if it is possible to maintain clearly isolated components while being useful in general to a broader set of users. Keeping modules in S0-level scoping is even desirable. When there is a need to affect a broader set of modules, however, certainly such broader scope would trigger more careful discussions among more people. It again boils down to the level of open-mindedness due to the different scopes of impacts. > Requiring 3 endorsing committers who agree to own/maintain is a very high bar > and would be exclusionary to newer contributors. We need a clear set of people who can review/maintain the code and maintain the overall review quality bar following the same process of all modules, so at least one is necessary. The volunteers also do not have to write code, but need to be responsible for code reviews and follow up actions, and contribute their time on a part-time basis. Likely the supporting PMC members would be able to serve that role initially. This being said, we anticipate new contributors being bought in as committers. The goal is to grow a set of contributions rather than restricting them. > Is there any guide about how to get this PMC member, assuming the S0 RFC is > not proposed by a PMC member? Also what should we do if the champion doesn't > response on time during the upstreaming process? Should the owner find > another PMC/committer for help? Great question. We anticipate the champion to signal such intent during the pre-RFC stage (at the forum). Normally we expect champions to be able to land a commitment of their time. A new champion is certainly possible if it is not the case. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/95#issuecomment-1285388768 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/95/c1285388...@github.com>
