This bug will track the work we do to refactor our authorization scheme, a large effort we'll begin specifying in Q42013. I wrote a blog post advocating for this work: http://hoosteeno.com/2013/10/14/refactoring-the-mozillians-org-authorization-scheme/
Because this bug may generate some discussion, I created a thread here: https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.community-tools/9903oqZsaOM That's a great place for opinions, questions, ideas about Mozillians.org authorization; we'll capture decisions here.
No longer depends on: 926673
Summary: [tracker] Refactor authorization scheme → [tracker] Improve the vouching process (was: "refactor authorization scheme")
No longer depends on: 961001
:sancus, :mbrandt and I met to talk about the launch plan for bugs in this feature. We want to build this feature without making a major feature branch deployed to a dedicated feature demo instance. That means this work will go on alongside other mozillians.org development, such as patches submitted by volunteer contributors, bug fixes, and other minor features. We'll have 3 major releases. Each release must include code for the bugs specified as well as any other code merged at that time. This means our release cycles may be a bit longer since there's more code to do and more testing to do, but we still want to keep things moving forward quickly. Any of these bugs can be coded now; we just have to merge them in the right sequence. Release 1 (http://mzl.la/1hS10g7) --> At this point the userprofile implementation of vouching has been replaced by a dedicated model, and all existing vouches have been migrated to the new model. Also, employees are auto-vouched by an auto-vouching account. * vouch model, without multi-vouching enabled: https://bugzilla.mozilla.org/show_bug.cgi?id=997400 * partial migration: Remove date_vouched and vouched_by, and replace with properties on the model that address the new model. And migrate all existing vouches to the new model. Keep is_vouched. https://bugzilla.mozilla.org/show_bug.cgi?id=997425 * create autovouching account: https://bugzilla.mozilla.org/show_bug.cgi?id=997407 * autovouch employees: https://bugzilla.mozilla.org/show_bug.cgi?id=997417 Release 2 (http://mzl.la/1gxbzdC): --> At this point multiple vouches don't mean anything -- they don't imply any extra functionality -- but they are allowed. The interfaces are all a part of this release, and therefore the FAQ and communications about this new functionality must be a part of this release too. * release vouch input interface: https://bugzilla.mozilla.org/show_bug.cgi?id=997451 * enable multi-vouching: https://bugzilla.mozilla.org/show_bug.cgi?id=1011719 * enable new vouches shown on profile interface: https://bugzilla.mozilla.org/show_bug.cgi?id=997473 * communicate about changes to signup/vouching https://bugzilla.mozilla.org/show_bug.cgi?id=997422 * explain the vouching process in an FAQ: https://bugzilla.mozilla.org/show_bug.cgi?id=1011230 Release 3 (http://mzl.la/1n28jtq): --> At this point the feature is completely released. We have a new vouching system. * only people with 3 vouches can vouch:https://bugzilla.mozilla.org/show_bug.cgi?id=997473 * summit people get 3 vouches: https://bugzilla.mozilla.org/show_bug.cgi?id=997460
Updated release schedule: We release this feature in 2 phases: 1. First phase has all functionality (http://mzl.la/1hS10g7) 2. Second phase deletes legacy vouches and legacy vouch code (http://mzl.la/1gxbzdC)
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.