Mark Loeser wrote: > Basically, it would be something that allowed you to "browse" the current > tree of submitted ebuilds. This way users that submit something can > categorize it for devs to easily look for ebuilds they may be interested > in, and we can make it so we could easily grab the ebuilds from this hacked > up idea of a tree. It would make it a lot easier to do automated checks > against submitted ebuilds for QA issues, and we would offload all of those > submissions from bugs.g.o to this app. I guess you could think of it as > the overlays.g.o idea, but I tend to think overlays are experimental > things that aren't necessarily going to be added to the tree. This > would be for ebuilds/packages that are ready to be added to the tree, > but just lack someone that wants to maintain them.
A big advantage of the current system is that people tend to add bug reports to those maintainer-wanted ebuild bugs, so the community can actually iterate through ebuilds for a non-tree package without too much pain. Separating the pending ebuilds from bugs would make that harder. -g2boojum-
signature.asc
Description: OpenPGP digital signature
