Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=532880
--- Comment #5 from fujiwara tfujiwar@redhat.com 2009-11-04 04:08:13 EDT --- I'm not sure if the cultures are different here.
I think the module integration in community and managing RPMs in each distributor are different situations. It's ok to add modules in each community if the community maintainers give the approvals. But if we integrate the RPMs into our distributions, I think the codes should be reviewed by the distribution before the integration is proceeded.
It's not special for me to put RPMs on network for minority users, which are completely managed by external community and our distributions/engineers don't check/use RPMs. But is it special for Red Hat people if you argue this case :)?
If you strongly like to maintain t-code/trycode in CD/DVD, I'd suggest you have the check the module per each release and if it's ok, probably it makes sense for me.
On the other hand, probably network RPM is not big problem for the minority users.
Thoughts?