Hi Before I start to submit packages to contrib, I like to have answers for at least the following questions. (Even if Henne sais that we should start with contributing first and afterwards request answers to our questions ;-) Now to my questions - sorry if they're already answered, but I can't find the comlete answers in the wiki... 1) How frozen is frozen? As far as I understand, contrib will contain Contrib:Factory => current development Contrib:<release> => frozen repository Each maintainer should maintain his package for Contrib:Factory and Contrib:<release>, right? As contrib:<release> is frozen (cite: "After the branch no version updates are allowed anymore") - is there really no chance to upgrade a package? I think openSUSE has a very strong policy about frozen packages - but even there some packages have exceptions. If you try to follow the same or a stronger policy in contrib, you lost at least me as packager, as I don't want to maintain leave packages for over 2 years by backporting patches. (I think that's one of the main reasons for the shriveling official repo, btw.) 2) What about orphaned/unfixed packages? If a package fails in contrib:factory or needs a security fix in the contrib:<release> repos - what's the expected response time? Who escalates/detects, if a packager is not responding? (BTW: Just a side note from my experience with the Education repository: freezing in the same time as the official repository doesn't work - at least for Education.) 3) Is there a jury and/or escalation method defined to settle potential disputes between contrib-reviewers and contrib-maintainers (updates/reachability) ? 4) How to test updates? If a packager has to fix a package for a frozen distribution and wants some people to test it - how should this work? * Would there be a Contrib:<release>:testing repository for this? * Should testers add the packagers home repository (containing perhaps other packages) and install from there? 5) How will users be informed about updated packages for their release? Currently, if I add a repository like contrib:<release> as user via zypper, it will be added with "refresh disabled". So zypper will never look for updated packages - and therefore I'll never get informed about an updated package. Even if I refresh the repository, I have to download the new package and hope to find information about the reason for the update in the rpm changelog, right? -> Suggestion: Is it perhaps possible to get a "real update repository" containing patchinfos (the files which can be shown in the updater-applet on my desktop) for released contrib repositories (like Education does ;-)? With kind regards, Lars -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-contrib+help@opensuse.org