> 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.
Luke, I think it is unlikely that you will accomplish your goals if you make trolling your primary strategy. We are pretty bad at ignoring trolls, here at Mozilla, but I expect that if you troll hard enough, we will eventually learn to ignore you. You've tried to argue that it's in our best interests to maintain the python-xpcom bindings. Those in this thread have heard your argument, and they disagree. You think that's our loss, and maybe you're right! But just because you think we're wrong doesn't give you the right to waste everyone's time. You are not entitled to anyone's attention here or in bugzilla. Maintaining xpcom bindings for Python is work! You're probably right that it would be more work for you than it would be for a core xpcom contributor. But it's work either way, and I think you are unlikely to convince someone to do work by threatening to be a troll. Regards, -Justin On Wed, Feb 29, 2012 at 9:10 PM, lkcl luke <[email protected]> wrote: > On Thu, Mar 1, 2012 at 1:07 AM, Kyle Huey <[email protected]> wrote: >> On Wed, Feb 29, 2012 at 4:30 PM, lkcl luke <[email protected]> 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 > decision. > > >>> 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 > pyjamas-desktop. > > 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: > > https://bugzilla.mozilla.org/show_bug.cgi?id=731121 > > 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 > answers. > > 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 > source code. > > 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. > > please don't interfere. > > thank you. > > l. > _______________________________________________ > dev-platform mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
