User:Rflint/Microsummaries:Schedule
		
		
		
		
		
		Jump to navigation
		Jump to search
		
		
	
Tasks
Application
P1
| Status | Description | Link | 
|---|---|---|
| Microsummary service doesn't guarantee cache loaded before updating | bug 336837 | |
| Automatically update installed microsummary generators | bug 341341 | |
| Microsummary generator installation gives no indication that it succeeded | bug 341818 | |
| Microformat or meta tag? | Enable pages to specify microsummaries within the pages themselves | bug 358105 | 
| Needs bug 102699 | Use DOMParser to parse HTML | bug 361449 | 
| Check HTTP status code to determine auth (and other) failures | bug 370242 | |
| Complete | Generated titles (microsummaries) are not used in tree and menu places views | bug 373500 | 
| Microsummary service test suite | bug 387207 | |
| Import generatedTitles and set staticTitles appropriately | bug 389579 | 
P2
| Status | Description | Link | 
|---|---|---|
| Need to check with one of the Mikes | UI for removing microsummary generators | bug 341336 | 
| Privacy concerns? | Set the referrer header when downloading a generator linked by a page | bug 342591 | 
| Microsummaries should update when manually visiting the site | bug 355525 | |
| At Risk | Enable script execution in Microsummaries | bug 361026 | 
| Allow getMicrosummaries() to take an optional document argument | bug 387206 | 
Future
| Status | Description | Link | 
|---|---|---|
| Needs spec | Support rich text microsummaries | bug 341347 | 
Web
P1
| Status | Description | Link | 
|---|---|---|
| Complete | Design database schema | schema.sql | 
| Design/implement API | ||
| Design/implement user-facing features | ||
| Implement administration tools | 
Extension
P1
| Status | Description | Link | 
|---|---|---|
| Utilize web API | 
P2
| Status | Description | Link | 
|---|---|---|
| Extend support for author meta-data | ||
| Implement generator updates for 1.8 | 
Schedule
M7
- All blockers in
 
M7+1 week
- Update feature in
 - Definitive answer on new UI/mockups
 
M7+2 weeks
- First-pass implementation of web app complete
 - Majority of P1s complete
 
M7+3 weeks
- P1s complete
 - Majority of P2s complete
 
August 20
- End of project under SoC
 - Web app fully completed, tested and deployed to a temporary home along with companion extension
 
M7+4 weeks - M8+
- Polish and regression fixes as needed
 - Find more permanent home for web app