* [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

> I'd hazard a guess that you may have hit a bigger problem than your
> comment indicates.  I'm pretty sure there would be great pressure to
> use `quick and dirty hacks' to get stuff done when devs are nearly
> always overworked.

Actually, they IMHO *are*. Look at the large amount of patches in the 
tree and the uncountable discussions which are not gentoo specific.
And the same happens also in other distros. An really large amount
of work could be done easily outside specific distros, but in an 
more general way. 

But as long as the devs refuse cooperation with such distro-agnostic
(meta-)projects like OSS-QM, there aren't much changes for it 
becoming better ;-P

> > One little step out could be the OSS-QM project (http://oss-qm.metux.de/)
> > It collects fixes for a lot packages and makes them accessible in 100% 
> > automated ways. So in a way it can be seen as an kind of overlay against 
> > the upstream. Most of the patches are things that upstream's tend to forget 
> > but importand for fully automated builds (eg. proper relocation, clean 
> > feature switching, fixing buildfiles, pkg-config, etc) - they do NOT harm 
> > the core functionality. So exactly what the vast majority of distro's 
> > patches do, but in generic (distro agnostic) ways.
> 
> The theory sounds very sensible.
> After looking at that page and some of the links briefly it wasn't
> clear to me where this is being used.  I see a very short list of pkgs
> being worked on.. and guessing it is because of being short handed
> there. 

There's not documentation yet. Feel free to join the maillist/board and
improve it ;-)
 
> But what wasn't clear is how work comes in and where it goes when it
> goes out.

Well, everyone is free to join the project as an "vendor". 
(vendor = someone who supplies code). Each vendor has it's own namespace,
for patches as well as patchsets (patchset = list of patches for an specific 
version of an specific package). You can see the bunch of patchsets from 
some vendor as an kind of overlay against the upstream. Combined with CSDB 
you can fetch source + patchset for an specific package in an specific 
version completely automatically.

> PS-The `help' link under `navigation' brings up what appears to be
> something it is not intended to, and may even be a hack on those pages
> or something.  (The content that comes up may even be sort of off the
> wall.)

The usual wiki vandalism :(


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
        http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
        http://patches.metux.de/
---------------------------------------------------------------------
-- 
gentoo-user@lists.gentoo.org mailing list

Reply via email to