Hi, everyone. There's general consensus that we want to terminate XULRunner as a project and replace it with a Firefox Platform SDK (name to be determined). [1] However, what precisely we want that SDK to do, and to support, we haven't figured out yet.
I recently submitted a bug and patch to copy the stub executable and application bundling script (install_app.py) from XULRunner to Firefox. Mike Hommey (glandium) thinks that's a bad idea. [2] His objection is that "that just makes it stay outdated each time browser/app/nsBrowserApp.cpp is changed, which is one of the many reasons we want to get rid of xulrunner." Okay, fine. I'm all in favor of doing things the right way instead of the fast, hacky way. I'm also willing (and with my bosses' backing, somewhat able) to put in the time necessary to implement the right way. Getting XULRunner into an actually-usable state took a lot of hacks anyway... So we have to figure out what we really want. What I propose is writing our Firefox Platform SDK requirements down. [3] I'll put a first draft together as soon as practical (probably this weekend or next). First, a "Where Do We Stand" section, expressing what we currently have, what SDK and XULRunner customers currently try to do and demand from the Platform SDK, and operating-system-specific issues we face. Second, a list of concise "What The Platform SDK Must Or Should Support" sentences to clearly define our requirements. Third, a "Owners' Vote" section where a group of contributors vote yea or nay on the second section as it stands on the date they last read it. Specific objections and commentary may be written afterward. Also, constructive edits anywhere in the document (in particular, clarifying requirements or adding important requirements that I missed) are welcome. The idea is to arrive at a clear consensus on requirements. Finally, while I want to get this done and done right, I don't want to spend an inordinate amount of time on getting the requirements done. External parties want a Firefox Platform SDK yesterday. Firefox 30 development just started on mozilla-central. I'd like to have these requirements drafted and finalized before Firefox 31 development starts. That gives us six weeks from now. [4] I think that's reasonable for a requirements document. As for delivery dates on the actual Firefox Platform SDK: I don't know. I had hoped to put the pieces together before Firefox 31 entered the Aurora channel, so that it could be part of the "extended service release" for the 2014-2015 year. Until we can clarify what we want, though, that's just a dream. We can't really estimate the work, and how long it'll take, until we have the requirements hammered out. Again, folks: I'm willing and able to put in the time to make this work. Not just for my prototype XML editor project, either: the company I work for has a vested interest in XULRunner and in upgrading our platform. This is important, and shouldn't be rushed... but it should be done as promptly as is practical. Alex Vincent software engineer, FileThis, Inc. author, Verbosio XML Editor prototype [1] https://groups.google.com/forum/#!topic/mozilla.dev.platform/o99wQZBjIJw [2] https://bugzilla.mozilla.org/show_bug.cgi?id=961936 [3] https://etherpad.mozilla.org/s5jInveqm5 [4] https://wiki.mozilla.org/RapidRelease/Calendar _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
