The new page is at:
http://www.mozilla.org/about/policies/
If you have any comments or suggestions, feel free to reply here or in
the following bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=444455
Thanks,
David
On Oct 1, 11:12 am, davidwboswell <davidwbosw...@yahoo.com> wrote:
...
> If you have any comments or suggestions, feel free to reply here:
Great to see the policies all in one place!
Should we note draft polices (e.g.
http://groups.google.com/group/mozilla.governance/browse_thread/thread/f025af50cfe4f5e9)
on this page as well?
Cheers!
--zak
> Should we note draft polices (e.g.http://groups.google.com/group/mozilla.governance/browse_thread/threa...) on this page as well?
I think it makes sense to add links to new policies that are under
consideration on the Policies page. I'll add a link to the relevant
thread from the Policies page about the consolidated Privacy Policy
section.
As far as using the word draft for new policies that are under
consideration, it seems that draft is already being used for existing
policies that are in use. For instance, the Mozilla Community Edition
Policy is labeled as a draft but it is in use. It might be worth
discussing removing the draft label from any policies that are
actually being used.
David
Would this be an appropriate location to find the Mozilla (Firefox)
product end of life policy?
We are looking for a document stating the end of life policies at
Mozilla. Several places make mention of the 6 month policy for Firefox
however I cannot find a page stating that this is the policy. Are
there different EoL policies for Thunderbird, SeaMonkey, Fennec, etc.?
Is there an intranet document that can be made public? Should someone
draft one?
On Fri, Oct 3, 2008 at 14:32, David Boswell <davidw...@yahoo.com> wrote:
> Kevin,
>
> Thanks for looking around for that. Could you post that information to the Governance list and we can see if anyone there knows of where we should be linking?
>
> Thanks,
> David
>
>
>> I don't know of an exact place of the policy though it
>> is discussed in
>> several locations such as
>> https://wiki.mozilla.org/ReleaseRoadmap and
>> http://developer.mozilla.org/devnews/index.php/2007/05/30/firefox-2004-and-firefox-15012-security-and-stability-update/
>> Additionally a Google site specific search of mozilla.org
>> for end of
>> life or 6 months does not turn up a clear page discussing
>> this policy.
>
I can't see why we would want to have a draft label on a policy that
is in use. Shall we catch up with the relecant policy owners to see
what they have to say?
Cheers!
--zak
We can certainly look at each policy with the draft label on discuss
what to do with it. The three that I see are:
- Mozilla Trademark Policy for Web Sites Created by Localization Teams
http://www.mozilla.org/foundation/trademarks/l10n-website-policy.html
- Mozilla Trademark Policy for Distribution Partners
http://www.mozilla.org/foundation/trademarks/distribution-policy.html
- Mozilla Community Edition Policy
http://www.mozilla.org/foundation/trademarks/community-edition-policy.html
I'm not sure of the history of the draft label and what purpose it
had. If anyone has the background on the label in general or it's use
on any of these policies, please let us know.
David
Community Edition is under discussion on m.governance to be terminated.
I think the distribution partner policy is largely covered by the main
policy (unaltered official binaries are ok, otherwise need
permission), so I think it probably can die.
The l10n website policy may not be widely used or necessary/desirable,
especially since we have mozilla-europe and mozilla.com with fully
translated pages...
-- Mike
And how is that related to websites created by our (l10n) communities?
I'm currently working on Mozilla Community Sites project which will
empower and promote creation of custom community sites and I believe
that it is fully in line with our manifesto statements about
participatory Internet in which we promote creating communities of
people involved in Internet a better experience for us all.
mozilla-europe, mozilla.com solves the problem of translation of our
websites, not creation of community, fully localized websites that
don't have to be narrowed to Mozilla Corporation products and/or
Mozilla Foundation, but rather are fulfilling the goals of Mozilla
Manifesto.
Greetings
Zbigniew Braniecki
--
Mozilla (http://www.mozilla.org)
-- Mike