In recent weeks, several folks have asked why Flock is building a browser, not an extension, and about our relationship to the Mozilla community.
Jagan Mohan, Mozilla Web Developer
The decision of Flock to build a whole browser on Mozilla code makes perfect sense that I think this lengthy explaination is some what redundant.
The whole internet community is far from being homogenous and there are various whole large groups of users who use generic browsers for various sets of common purposes.
Thus the necessity for hundreds of browsers built around hundreds of core purposes is a reality.
One IE or Firefox won’t fit the needs of everybody.. although firefox tries to give the user the flexibility to extend and customise the functionality, it is far from perfect.
I think that a browser custom made for the blogging community like FLOCK for example would prove pioneering for others to take up to develop such niche browsers.
Hey, afterall, why can we install two or three browsers and use them all in diffferent situations?
I now have firefox, opera and flock installed and I use them ALL. There is no rule I see that I have to use just one and transfer ALL my loyality to it alone.
Bart Rockman, web application developer in Texas
One of the questions people are asking today is “Why are we releasing our code under the GPL, instead of triple-licensing it under the GPL/MPL/LGPL?”
The answer is that intellectual property issues are big complicated things that have critical business impacts. Areas to cover include: source code licensing, trademarks (securing trademarks, trademark usage policies), EULAs, third party partners code licensing, patents issues, etc. Dealing with all of these is a tremendous endeavor. I recall it taking many many months for the Mozilla Foundation to flush out its trademarks policy, for example. I suspect the discussions inside of Mozilla around the triple-licensing policy took many months as well.
The MPL made sense for Netscape in 1998 in view of their business outlook. It seems to work well for the Mozilla Foundation and the Mozilla Corporation. I’m not sure that it’s the right licensing scheme for Flock.
So we are taking things one step at a time when it comes to our source code licensing policies. We’ve already made a couple of big strategic decisions on the source code licensing front: (i) our code will be largely (maybe even entirely) open source, (ii) we’re putting it out to the world right now under the GPL, (iii) we’re asking contributors to assign copyrights to us. These steps mean that we are open source and provide us with the flexibility to evolve our source code licensing policies over time.
As I’ve indicated above, we are serious about working with the Mozilla community. As we work with folks at the Mozilla Foundation/Corporation and identify areas where it makes sense for our code to go back upstream, then we will relicense those pieces of code under the triple license.
Kevin Nilson, Netscape admirer
It’s interesting to read how everyone seems to define Flock in their own way (it’s just a browser; it competes with FIrefox; it’s only for bloggers and pic sharers, it’ll destroy the effort to gain marketshare on IE, etc.) I don’t do many of those things – I just want a browser to do what I want to do when I want to do it. I moved from IE to Firefox, to Camino before stumbling on Flock while reading about a plug-in to trick IE-only websites into thinking you were using IE if you visited with a Mozila-based browser (I needed to overcome MS Exchange Webmail’s bad habit of asking for a password for every iteration of an icon it was loading on a pageif you were using anything except IE). Even better, Flock soved the password demand problem without needing to install the plug-in. It seems faster and the toolbar customization organizes things to fly even faster still. Good stuff from an end user perspective. Thanks!