Maintainer's tasks 1. * The package should follow the SUSE Package Conventions, it has to build on both ix86 and x86_64 and you should test it at least on ix86 (??? OK if the maintainer has no x86_64 machine for testing?). You should be prepared to fix build errors, which sometimes occur due to changes in Factory (this is especially true for Kernel Module Packages). See also Contrib#Rules for inclusion of packages in Contrib for further restrictions and requirements. I think packages need to be tested on either x86 or x86-64, not both. For kernel packages, we need to test on both architectures. 2. # # (??? Add the package to a staging repository first? See http://lists.opensuse.org/opensuse-factory/2008-08/msg00264.html) What do you mean ? "contrib-devel" repo ? Ahh I see - it is more like "temp". I don't see any advantage of that versus User OBS, but I may be wrong. Opinions. ==================================================== Reviewers' Tasks 1. # # If the package is actively maintained upstream (??? Relax this rule for packages with little or no security risks, like games without multiplayer mode?) Yes, I think we can relax this rule for non-network packages. -- -Alexey Eromenko "Technologov" -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org