Clearly you are more concerned about getting Paludis ready. spb has other
priorities, fair enough, but this is something that seems fairly important
for gentoo as a whole.
In process terms, I can't understand why the team working on it isn't a
pkgcore dev (eg marienz if you can't communicate with ferringb), a portage
dev such as zmedico, yourself from paludis and say antarus from
treecleaners. I'd add in someone like jakub or spanky from bug wranglers
and Gianelloni for the infrastructure. Having it all from one set of devs
(paludis) is like having w3c standards written by one company.
While treecleaners really doesn't have anything to do with PMS; I am a
portage dev. However I'm not really interested in writing the spec
itself; I plan on looking at it when it is closer to completion. I
don't claim to have the requisite bash or ebuild magic to author this
document (nor do I really care about certain aspects of PMS).
I'm more concerned about people changing the tree for paludis
compatability; but in most of the cases I've seen the changes requested
seemed reasonable to me.
I think the whole deal is blown out of proportion, mostly because many
people dislike Ciaran, and unfortunately Ciaran dislikes (or distrusts,
may be a better word) many other people (myself and Brian Harring
included). If the aim is to get everyone to work together to make a big
happy spec; I just don't see it happening (the teams really don't get
along well when discussing technical issues). The only potential issue
is that PMS comes out and the aforementioned 'meddlers' make their
statements and it is a situation that is beyond reconcilliation. You've
basically written a PMS that may never get approved just because we will
never agree on a standard anyway (due to specific differences in how we
view a PM working).
In essence, delaying all the confrontation to the end. Which is cool
with me; tbh ;)
--
gentoo-dev@gentoo.org mailing list
