Patrick Shanahan <ptilopteri(a)gmail.com> writes:
* Susanne Oberhauser <froh(a)novell.com> [11-18-08
I agree with this.
And I wonder how the build server is really meant to be used as a
collaboration tool. I think having a clear common picture of that
would give me a better understanding of what is really missing.
Perhaps prior to an individual introducing a package, that package
particulars should be broadcast to a wiki/database for simi-automagic
comparison of those already in existance. Would possible provide
information to preclude duplicated efforts.
Maybe, yes. Maybe the obs could also support people in dropping old,
outdated package versions.
Hermes could even annoy maintainers about hosting an old package
version. As it could annoy maintainers about new package versions
that are available.
Yet then you'd need a flag to tell 'Yes I know. This is the
maintained version, that needs to be here, too, for compatibility.'
And the obs could help users to find a 'good' package based on the
ratings Marko is working on or based on actual test results of real
Or all three of them.
There is many solutions to this.
And several ankles to it.
So where's that place where we put this thinking down in a structured
way that at the end gives us not just technology but a way to jointly
provide prepackaged, tested open source software? On the distro of
your choice? And as part of openSUSE proper?
Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business
OPS Engineering Maxfeldstraße 5
Processes and Infrastructure Nürnberg
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org