trademarks [was: xulrunner 2.0 in rawhide (F15) bundles several system libs]

Bruno Wolff III bruno at wolff.to
Wed Oct 6 16:41:38 UTC 2010


On Wed, Oct 06, 2010 at 12:29:59 -0400,
  Nathaniel McCallum <nathaniel at natemccallum.com> wrote:
> 
> The only possible room for debate that I see is that there is, in
> Firefox, a potential conflict between our "ship upstream" and "don't
> bundle libs" values.  We have FESco to sort that out.

Those are the policies I was refering to.

> In short: No big deal. Close the thread. Move on. ;)

Well the project doesn't seem to be coming to consensus on this issue.
Some of us feel that we should provide an Iceweasel or drop Firefox,
similar to other things the project has decided to not package. Others think
that Firefox is so important to the project, that we must make an exception
for it. (And to some extent, that we should stay close to upstream.) Some have
also hoped that Mozilla would change with regard to bundled libraries in the
near future, but that seems pretty unlikely.

I don't think this is just a FESCO issue. I really think this is a board
issue as it has to do with the relative importance of our bundled libraries
policy, our stay close to upstream policies, the impact on our user base
of replaceing Firefox with an unbranded version or just dropping it and
the morale of various developers if we give or don't give Firefox an
exemption to the no bundled libraries policies.

For example it may be that we can't do an Iceweasel, because the current
packagers of Firefox may refuse to do that as an alterative to packaging
Firefox and we may not find new volunteers to do the packaging work.


More information about the devel mailing list