On Thu, Mar 1, 2012 at 1:07 AM, Kyle Huey <m...@kylehuey.com> wrote:
> On Wed, Feb 29, 2012 at 4:30 PM, lkcl luke <luke.l...@gmail.com> wrote:
>> oh i know - because pyxpcom has been relegated to third party status.
> Yes, exactly.
now i am spending considerable time spending considerable core
mozilla community's time dealing with the mess caused by that
>> how is this going to get fixed? (a so that this stops happening b
>> these specific coding errors so i can get some working code)
> It's not going to get fixed unless someone steps up to fix it.
ok, this is inappropriate to be discussing when there is still
silence from ben when i've answered the issues he raised, pointed out
that they are moot, and am waiting for him to run and install
all this is with a view to getting on the same page in order to
demonstrate what the benefits of doing so are...
... but for the sake of argument, even though it risks wasting
everybody's time, i'm going to provide an answer - because you asked.
a) who is going to pay for their time?
b) who is going to train them or answer their questions?
c) how much time is it going to take to train them and answer their questions?
... it's going to be the core mozilla developers, isn't it?
how long do you think it would take the core mozilla team to keep a
small codebase like pyxpcom up-to-date vs having to continuously
answer under-informed bugreports such as this one, here:
boris, for example, who has been extremely helpful up until now, is
getting _really_ fed up - and that's just the one bugreport!
i'm going to keep on, and on, and on, and on, and on, and on at this
until i get answers, and pyxpcom works.
then, in a couple of months, i'm going to try again. and i'll find
more bugs. and i'll raise bugreports again and again until i get
and that loop will be repeated, working from an under-informed
position where i don't have the time or money to attend mozilla
conferences, or listen to mozilla phone calls (b2g), or trawl through
mozilla documentation, or trawl through millions of lines of mozilla
are you _getting_ it yet?
i don't _like_ having to do this kind of thing. it's not fun for me
to have to point these kinds of things out, but somebody has to.
> And as has
> been stated several times,
... and as the points which _answer_ those statements have been
ignored several times...
> the core Mozilla community has no interest in
> doing so.
kyle, that's really not helpful right now.
this is complex: the core developers don't understand the issues, and
i'm endeavouring to help them to understand.