|
Commit Access Policy - draft for comment
|
| |
[I've had no responses to the below so am currently assuming that it's all absolutely fine. But just in case it's not, here's a repost including .planning to try and attract more comment. I wouldn't want people to feel blindsided. If you know people who might want to comment on this and you think they won't have seen it, please tell them.]... more »
|
|
Commit Access Policy - draft for comment
|
| |
"Currently, Mozilla has a large number of code trees in various source code management systems, many of which have differing requirements for access. This is confusing and difficult for both developers and administrators. This document is the first draft of a vision for what a unified commit access policy might look like. Having a clear commit... more »
|
|
Proposed Clarification to Site Licensing Policy
|
| |
Mozilla is proposing to clarify the language in our Site Licensing Policy that explains what elements of the web site are not licensed under the Creative Commons license. This language appears at [link] (and is part of what is underneath the Legal Notices link). It currently states:... more »
|
|
New Activities Modules
|
| |
For a while we have been in the process of identifying "Activities Modules" - non-code activities undertaken by the Mozilla project - and applying the module owner structure to them. [link] The existing Activities Modules are "Governance", "Planet Mozilla" and... more »
|
|
FYI: Concerns about IPS SERVIDORES root certificate
|
| |
This posting is for informational purposes only. Any follow-up should be posted in the mozilla.dev.security.policy newsgroup in the discussion thread called “Resolving concerns about the IPS SERVIDORES root certificate”. There have recently been some issues in regards to the following root certificate owned by IPS:... more »
|
|
Bugzilla and localizations components/products
|
| |
Hi, we're having two bugs open right now [1] that may or may not merge, and I wonder where the off-the-bug discussion should be. Trying .governance. We may want to have more than one bug component per locale on the one hand, and we have more and more stuff tracked in bugs that's not strictly "Client Software", like website bugs etc.... more »
|
|
Dormant Accounts - summary
|
| |
Thank you to everyone who contributed to the dormant accounts discussion. The new policy is going to be as follows: "SCM accounts inactive for more than 6 months may be disabled. If your account has been disabled, you can have it re-enabled by <a>filing a bug</a> in mozilla.org/Server Operations: Account Requests. Please make... more »
|
|
Dormant Accounts
|
| |
I've received a list of all SCM accounts from Mozilla IT, and so have been able to compare it to the output of my "active-accounts.pl" script. Setting the time interval at six months, I get the following statistics (fixed-width font required; note these numbers and percentages are _active_, not _inactive_):... more »
|
|
|