Identity/EngPlan

From MozillaWiki
Jump to navigation Jump to search

Overview

[[1]] Engineering plan.

This document addresses the build portions of the Identity service, including the Verified Email Protocol (VEP), [[VESEngPlan|Verified Email Service] (VES), Web Based Verified Email Client (wVEC), Firefox Native Verified Email Client (fVEC)

Key People

Technical Lead: JR Conlin (VES)
Additional Developers: Rob Miller (wVEC), Dave Dahl (fVEC)
Project Manager: Dan Mills
Product Manager: Dan Mills
UX: TBD

Work Items

Verified Email Server

Top-level tracking bug: Template:Https://bugzilla.mozilla.org/show bug.cgi?id=663887

Port existing code to new VEP specifications

Assigned to: jrconlin
Bug: 663276
Assumes/Depends On: Finalization of the internal Certificate format
Working Estimate: *code complete as of 2011Jun13*

Best case:
Worst case:
Most Likely:

Integrate to Clients

Assigned to: jrconlin
Bug: TBD
Assumes/Depends On: completion of baseline server and client
Working Estimate: 4 days

Best case: 2 days
Worst case: 6 days
Most Likely: 4 days

Complete work on server admin page (address registration)

Assigned to: jrconlin
Bug: TBD
Assumes/Depends On: Completion of UX designs, Completion of core server
Working Estimate: *code complete as of 2011Jun13*

Best case: 3 days
Worst case: 4 days
Most Likely: 6 days

Long term data storage for VES

Assigned to: jrconlin
Bug: TBD
Assumes/Depends On: finalization of the VES data requirements
Working Estimate: *code complete as of 2011Jun13*

Best case:
Worst case:
Most Likely:

Performance testing for VES

Assigned to: jrconlin
Bug: TBD
Assumes/Depends On: Working VES
Working Estimate: 4 days

Best case: 1 day
Worst case: 6 days
Most Likely: 4 days

Validating unit test coverage for QA

Assigned to: jrconlin
Bug: TBD
Assumes/Depends On: Working VES
Working Estimate: 4 days

Best case: 1 day
Worst case: 6 days
Most Likely: 4 days

Misc. server deployment tasks and checks (LDAP connection, Mail server, etc.)

Assigned to: jrconlin
Bug: TBD
Assumes/Depends On: Working VES
Working Estimate: *code complete as of 2011Jun14*

Best case: 1 day
Worst case: 5 days
Most Likely: 1 days

External Dependencies

Security Review

Assigned to: jrconlin, opsec-TBD
Bug: TBD
Assumes/Depends On:
Working Estimate: 'REQUIRES SCHEDULING'

Best case:
Worst case:
Most Likely:

Package and Deploy server to Beta

Assigned to: jrconlin
Bug: TBD
Assumes/Depends On: Working service, Available beta platform
Working Estimate: 'TBD'

Best case:
Worst case:
Most Likely:

Q.A. testing

Assigned to: TBD
Bug: TBD
Assumes/Depends On: Working Service; jrconlin provides proper testing architecture
Working Estimate: 11 days

Best case: 5 days
Worst case: 20 days
Most Likely: 10 days

Timeline

Expected Completion

Most tasks can be parallelized with clients working off of the base server. There is some imperative in getting the base server operational on a test platform in order to provide the clients with a baseline to work from.

Working Estimate: 58 days

Milestones

Milestone 1: Completion of the Identity Server

  • server should be deployed to a test configuration with access to test LDAP and some level of backend storage.
  • user should be able to perform minimal account related actions
  • Working Estimate: Done
  • Expected completion: Done


Milestone 2: Working integration of server and client code

  • client should be able to work with the existing server
  • client should be able to provide basic VEP service to a demo 3rd party site
  • Working Estimate: 4 days
  • Target Completion: Jun 21

Milestone 3: QA and Infrasec signoff

  • library test suite is finalized and infrasec has reviewed the code and found no major security violations.
  • Working Estimate: TBD days
  • Completion Date: TBD

Milestone 4: Deployment to Beta server

  • Code is deployed to a public accessible server (beta) for preliminary testing and user feedback.
  • Pending Issues: Beta Server configuration.
  • Working Estimate: TBD
  • Target Completion: TBD