>> There have been announcements that this is in progress for the last
>> year and a half. We are merely coming to technical execution.
>
> I never read until yesterday that you intend to use Netscape special
> priviledges. Which is, um, an important detail.
It has always been my understanding that this is the way it would work.
It has also, as far as I know, always been the understanding of
[EMAIL PROTECTED] I would be interested in pointers to statements
otherwise.
>> Some people oppose the change.
>
> Who are those?
/oppose/may oppose/. I don't know.
>> Netscape feels it wishes to relicense the code under the NPL, and it
>> has the right to do that.
>
> I am not sure about it. Even if it does, it might still not be a good
> idea to do without asking, because that is a major change in the license.
Asking would only be sensible if we were to change our actions based on
the answers we got to the question.
>>> I understand how difficult and time-intensive it is to get *all*
>>> contributors to even *react* at all. But shouldn't you at least make
>>> some modest attempt?
>>
>> the wording which is being used for the permissions email does not
>> specify which licenses the code is being relicensed from; therefore
>> this objection that people are not being informed would only apply to
>> people who have contributed only to NPLed files.
>
> So, you did actually send out permission requests already? When was
> that? Because I got none. Maybe I happen not to have contributed to
> plain MPL files.
Not yet, no. But your point was that people wouldn't find out about it.
>> Eventually, we want people to be able to take and use Mozilla code
>> under a single license.
>
> That's already the case, not?
No - we already have NPLed, MPLed, NPL/GPL, MPL/GPL and (I think)
NPL/LGPLed code in the tree.
>> There is nothing preventing you having a tarball of your code on
>> beonex.org with BSD license headers on it.
>
> huh? If you mean that I could fork, then you know very well that it will
> bitrott.
No, I mean that if you want to make the code you write available on more
generous license terms, there is nothing preventing you from doing so.
Gerv
