Hi, On Mon, Feb 11, 2013 at 11:44 PM, Eric Seidel <e...@webkit.org> wrote:
> This entire email thread makes me sad. > > I'm sad because we did this to ourselves (our porting systems/policies > are lacking), we did this very abruptly (the last port we kicked out > of webkit.org took a year?), and we don't have any clear policy for > this sort of thing (adding/removing ports in webkit.org). > I agree that this is sad. Wouldn't it be better to first agree on policies for adding/removing ports from WebKit BEFORE giving Kevin his walking papers? Why don't we first decide that aspect of things, before giving small teams the bum's rush? I think that moving closer to one build system will help, but won't > help those trying to advance WebCore from having to deal with 8 > different port APIs, 5 different networking libraries, 2 different XML > parser, 4 different GraphicsContext implementations, and countless > other configuration options! > Not to mention two JavaScript engines! > Of course saying Wx is "dead code", begs the question as to what is > needed for a port to be considered "live" in WebKit.org? With our > current porting architecture, I would argue that at least 3 full time > people are probably needed, and that this should be considered before > accepting new ports. > This is tantamount to saying that the only ports allowed in WebKit are corporate-sponsored efforts. Is that what we want this project to be? -Brent
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
