[about duplication of packages in the build service] On Sat, Nov 15, 2008 at 01:55:08PM +0100, Pascal Bleser wrote:
2) We don't have a lot of collaboration tooling around the OBS at this point. The branches/patching approach is not trivial and it doesn't really help wrt communication between packagers. Packagers who do their work during their free time, which is usually at night with whatever timezone, might also have a hard time to poke people who can give them maintainer role or create a new non-home: project quickly. Personally, I think it is an issue because waiting a few days for such stuff getting done is a major annoyance when you maintain several dozens of packages.
This is a real problem, I agree.
Maybe a broader coverage of "super-maintainers" (I only know of Adrian having such root powers on the OBS, and.. darix maybe ?) would help there.
And I think this might be the short-term way to deal with it. It would need to be obvious though how to reach those helpful people.
I really think that we should get rid of home: repositories for anything else then playing around. The current situation is problematic because some home: repositories are really just playgrounds for experimenting or learning, and other home: repositories contain proper packages that are adequate for public consumption by the masses.
I think this could be a good approach.
If we could at least move such proper packages to non-home: repositories, the easy rule would be "don't use home: unless you _really_ know what you're doing". And also, for example, not return search results from home: repositories unless explicitly for (e.g. a checkbox on the search page).
Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development