[ lead developer of pdf.js]
h2@fsfe.org
pdf.js is an open technology and we are very interested in other parties adopting it. We could jointly approach Google for example and see if they are willing to obsolete their proprietary closed-source native code PDF reader (based on FoxIt I believe) in favor of an open solution.
That is something we thought about as well, indeed proprietary default plugins in Chrome are worrisome. As I mentioned before, we were in contact with the Chrom[e|ium] team and also Chris DiBona on the matter about a year ago. If we prove that one can actually make a good portable Free PDF-Plugin that will counter some of their arguments.
Last but not least, FSF(E) and the Mozilla Foundation are obviously closely aligned in their mission. It might make sense for you to talk to our foundation and see if Mozilla should join this campaign. In the end, we are all interested in ridding the web of proprietary technology.
That sounds like a good idea. We are currently discussing some things internally concerning the future of the campaign, and we are also discussing with our sister organization, the FSF about some changes. I am not sure whether it would be possible for Mozilla to "join" the campaign in the current form, because - as stated above - we are vendor neutral, but I am very confident that we could cooperate more closely on these issues and future actions.
Who would we have to contact at the Mozilla foundation on this matter?
My idea is that we * keep pushing Mozilla to put more resources into pdf.js, so that it gets done more quickly * work on redesigning pdfreaders.org * launch the new pdfreaders.org simultaneously with the first Firefox version that ships with native PDF-support * we write a press release together with the Mozilla foundation in which we ...* highlight the importance of open standards and Free Software reading Open Standards, ...* mention both the PDFReaders Site update and the Firefox plugin that is now default ...* say that we are disappointed that Google is not helping in this matter, but instead developing a proprietary plugin; that we would greatly appreciate if they adopt the Free js-based Plugin or release the source of their PDF-plugin
This of course implies 1) we can agree on working together with Mozilla on this 2) the timeframes for our redesign and bringing the plugin to a useable state somewhat coincide
What do you think?
mk, feel free to fwd this to team@ if you think it relevant to the discussion there.