> Imagine a case when a module is being needed by more than eight organizations > -- many of them are industry players, but not all other members.
In such a situation, I would expect that with the combined resources of those eight organizations, they could address any concerns raised by the community through the standard process. That's the behaviour I'd anticpate of any new organization looking to contribute to an OSS project - they'd first and foremost prioritize listening to and respecting the existing community. I'd expect this S0 process to more commonly apply to smaller contributions where the contributor doesn't necessarily have the bandwidth to make long term commitments nor to continue parallel (forked) development. In those cases, I can see that a higher barrier to making a contribution (like requiring roadmaps, further technical documentation, tutorials, and extensive review) might exceed what is reasonable to ask of an individual/small team. Industrial contributors, however, should easily have the resource to clear that barrier, as it would almost certainly already form part of their internal process. The only exception I can see to this would be where a proposal is being maliciously vetoed (e.g. with entirely unreasonable requests or no justification at all). I've personally never seen this happen in the TVM community, and hope things remain that way. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/95#issuecomment-1339729885 You are receiving this because you are subscribed to this thread. Message ID: <apache/tvm-rfcs/pull/95/c1339729...@github.com>
