Identity/EngPlan: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 3: Line 3:
[[https://wiki.mozilla.org/Identity|Identity]] Engineering plan.  
[[https://wiki.mozilla.org/Identity|Identity]] Engineering plan.  


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


= Key People =
Please refer to the linked documents for a discussion of each segments requirements and milestones.
 
{{ProjectTeam
|techLead=[[jconlin|JR Conlin]] (VES)
|addedDevs=[[rmiller| Rob Miller]] (wVEC), [[ddahl| Dave Dahl]] (fVEC)
|projMgr=[[dmills| Dan Mills]]
|prodMgr=[[dmills| Dan Mills]]
|ux=TBD
}}
 
= Work Items =
== Verified Email Server ==
Top-level tracking bug: {{https://bugzilla.mozilla.org/show_bug.cgi?id=663887|663887}}
 
{{WorkItem
|workItemDesc= Port existing code to new VEP specifications
|assignee=jrconlin
|bug=663276
|assumes=Finalization of the internal Certificate format
|workingEst=*code complete as of 2011Jun13*
|bestCase=
|worstCase=
|mostLikely=
 
}}
 
{{WorkItem
|workItemDesc=Integrate to Clients
|assignee=jrconlin
|bug=TBD
|assumes=completion of baseline server and client
|workingEst=4 days
|bestCase=2 days
|worstCase=6 days
|mostLikely=4 days
}}
 
{{WorkItem
|workItemDesc=Complete work on server admin page (address registration)
|assignee=jrconlin
|bug='''TBD'''
|assumes=Completion of UX designs, Completion of core server
|workingEst=*code complete as of 2011Jun13*
|bestCase=3 days
|worstCase=4 days
|mostLikely=6 days
}}
 
{{WorkItem
|workItemDesc=Long term data storage for VES
|assignee=jrconlin
|bug='''TBD'''
|assumes=finalization of the VES data requirements
|workingEst=*code complete as of 2011Jun13*
|bestCase=
|worstCase=
|mostLikely=
}}
 
{{WorkItem
|workItemDesc=Performance testing for VES
|assignee=jrconlin
|bug='''TBD'''
|assumes=Working VES
|workingEst=4 days
|bestCase=1 day
|worstCase=6 days
|mostLikely=4 days
}}
 
{{WorkItem
|workItemDesc=Validating unit test coverage for QA
|assignee=jrconlin
|bug='''TBD'''
|assumes=Working VES
|workingEst=4 days
|bestCase=1 day
|worstCase=6 days
|mostLikely=4 days
}}
 
{{WorkItem
|workItemDesc=Misc. server deployment tasks and checks (LDAP connection, Mail server, etc.)
|assignee=jrconlin
|bug='''TBD'''
|assumes=Working VES
|workingEst=*code complete as of 2011Jun14*
|bestCase=1 day
|worstCase=5 days
|mostLikely=1 days
}}
 
=== External Dependencies ===
 
{{WorkItem
|workItemDesc=Security Review
|assignee=jrconlin, opsec-TBD
|bug='''TBD'''
|assumes=
|workingEst='''REQUIRES SCHEDULING'''
|bestCase=
|worstCase=
|mostLikely=
}}
 
{{WorkItem
|workItemDesc=Package and Deploy server to Beta
|assignee=jrconlin
|bug='''TBD'''
|assumes=Working service, Available beta platform
|workingEst='''TBD'''
|bestCase=
|worstCase=
|mostLikely=
}}
 
{{WorkItem
|workItemDesc=Q.A. testing
|assignee='''TBD'''
|bug='''TBD'''
|assumes=Working Service; jrconlin provides proper testing architecture
|workingEst=11 days
|bestCase=5 days
|worstCase=20 days
|mostLikely=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'''

Revision as of 21:52, 15 June 2011

Overview

[[1]] Engineering plan.

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

Please refer to the linked documents for a discussion of each segments requirements and milestones.