8
edits
Changes
m
no edit summary
Yes, though you may need to get vouched again before September 30th.
* If you attended the Mozilla Summit 2013, you have received 3 automatic vouches and can vouch for others.
* If your mozilliansMozillians.org profile is associated with a mozilla.org/mozilla.com/mozillafoundation.org email address, you have received 1 automatic vouch.
* If neither of the above apply to you and you were previously vouched, someone will need to vouch for you again and give a reason. You still have a legacy vouch and can use the site normally until September 30th. If you do not receive a new vouch by September 30th, you will lose your vouched status until someone vouches for you again.
=== Someone asked me to vouch for them. Should I vouch for them? ===
Only vouch for contributors who have make made significant contributions to one of Mozilla's projects. If you cannot verify their contributions and do not know the person, ask them to have someone they have worked with vouch for them instead.
=== Can I still vouch for others? ===
It depends.
* Most fields on your profile have "per-field" privacy settings. You can set a field to "public", which means anyone on the internet can search for and view those fields (and therefore also can view your username). Also, "public" profile fields are shared through [[Mozillians/API|the Mozillians.org API]] with any vouched Mozillian who requests a "vouched" API key.
* You can also set a field to "Mozillians" which means any vouched Mozillian can view it. Also, [[Mozillians/API#Sites_using_the_API|certain reviewed applications]] have been given elevated access to the API in order to help Mozilla's platforms interoperateinter-operate. These reviewed applications can read fields through the API that you have marked for "Mozillians" only.
* Mozillians.org is maintained by employees of Mozilla, including engineers, system administrators and database administrators. These people have access to the raw data of your profile in a variety of formats, but they only encounter it while doing their jobs.
=== Why is the vouching system changing? ===
Mozillians.org has outgrown its simple vouching model. Vouching wasn't well explained and it wasn't clear why someone was vouched. We are adding descriptions to vouches to explain why individuals are vouched.
Mozillians.org has become a mature platform and a valuable source of information about people who contribute to Mozilla’s products and mission, and it is likely to be important to Mozilla's ambitious contributor goals over the next decade. But Mozillians.org has outgrown the authorization paradigms it started with. Therefore, in order to prevent data safety issues and questions about product integrity, we must design and implement an authorization system that accommodates current and future data and users. We are applying this system evenly to both the UI and the API.
Read more about the [http://hoosteeno.com/2013/10/14/refactoring-the-mozillians-org-authorization-scheme/ analysis of the original authorization system].
