Lars Vogdt mentioned some of his review criteria in a: http://lists.opensuse.org/opensuse-packaging/2013-04/msg00091.html This reminded me that review process has too weak, or even missing, actual feedback from users of packaged software. The reason to think like that are titles that came out without being able to perform basic task they are designed for [1]. In effect we can't prevent situation where package that works for distros with different library version, but not with openSUSE, is shipped as part of the release. One can argue that such things happen and blame lack of testing, but it is actually only lack of in-house testing, as in example [1] it was easy to find problem reports and fixes on the web, but I doubt that many of our packagers will have time to look for them. Solution would be to add component to review process that will collect external feedback and make it available to reviewers and packagers. Collecting feedback does not require as much sophistication as packaging, so it will be accessible to many more people willing to contribute. Once when online instructions are created it is possible to list it on the wiki under "How to contribute", and point interested people to that. [1] Example that I have in mind was video editing software kdenlive few releases ago, which was the only one that will not crash right on the start, or in the middle of the work. I gave up on attempts to use it, so I don't know current status, nor I remember details. The issue was that at the time it had a bug that was valid only for specific library version that was included in openSUSE. It will pass compilation and packaging, and it will actually ran, but one could not render final video after editing. Newer library was fixed and kdenlive worked fine. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org