On Sun, Dec 13, 2009 at 4:19 AM, Holger Freyther wrote:
> On Saturday 12 December 2009 22:42:34 Maciej Stachowiak wrote:
>> I think questioning someone's priorities in an open source project is
>> generally not polite, unless there is some direct relationship between
>> different tasks. For exampl
On Sat, Dec 12, 2009 at 8:40 PM, Mike Emmel wrote:
> I don't know the right answer just that its probably
> time to overhaul the build system a bit and I can help.
You are certainly welcome to look at the GYP system that the Chromium
project uses to create builds for multiple OSes, JS engines,
On Sat, Dec 12, 2009 at 6:19 PM, Holger Freyther wrote:
> On Saturday 12 December 2009 22:42:34 Maciej Stachowiak wrote:
>> I think questioning someone's priorities in an open source project is
>> generally not polite, unless there is some direct relationship between
>> different tasks. For exampl
On Saturday 12 December 2009 22:42:34 Maciej Stachowiak wrote:
> I think questioning someone's priorities in an open source project is
> generally not polite, unless there is some direct relationship between
> different tasks. For example, if someone introduce a new feature
> (let's say support for
I think questioning someone's priorities in an open source project is
generally not polite, unless there is some direct relationship between
different tasks. For example, if someone introduce a new feature
(let's say support for parts of the FooML language) and it had lots of
bugs, it mig
I'm really surprised that other members of the community are
questioning your priorities. You're free to work on whatever you
think is important. That's the first principle of open source
software outlined in The Cathedral and the Bazaar:
http://catb.org/esr/writings/cathedral-bazaar/cathedral-b
The work was done for my employer for their own reasons. I both
understand why they chose V8 and agree with the decision. I'm not
comfortable giving a detailed reason for the decision and I think
thats understandable. A clearer explanation would require a more
formal response and its tied to our
On Friday 11 December 2009 23:55:06 Eric Seidel wrote:
> I don't see a patch on the bug, but I look forward to seeing it when
> it's posted.
>
> I'm surprised that having switch-able JS engines would bubble up on
> the list of things to do above things like passing the layout tests:
> http://trac.
My two cents are that you can pick the priorities for your own
contributions. If you think this work is more important than working
on LayoutTests, I think that's your decision to make as a contributor
to the project.
I have some technical questions, but we can discuss those on the bug.
Adam
O
I changed the cc list the patch should be there now hmm not sure why
it did not go on the initial submit.
I don't know anything about the layout test issues.
The patches relationship to the gtk port itself is minor its the one I
happen to use.
The gtk specific issues have a lot more to do with th
I don't see a patch on the bug, but I look forward to seeing it when
it's posted.
I'm surprised that having switch-able JS engines would bubble up on
the list of things to do above things like passing the layout tests:
http://trac.webkit.org/browser/trunk/LayoutTests/platform/gtk/Skipped
:/
-eri
Hi all. Its been a while.
I just pushed a large patch that will need some serious work.
https://bugs.webkit.org/show_bug.cgi?id=32452
It allows the v8 js engine and debugger to work with the gtk webkit port.
Including remote debugging for arm or embedded platforms using chromedevtools.
I'm also
12 matches
Mail list logo
