109
edits
Raindrop/Milestone/Maple: Difference between revisions
no edit summary
(Created page with 'Maple is the first post-reveal milestone. End date is Nov 10, 2009. Trying to pick Tuesdays since they correspond with a weekly call. Current list of items being considered is b…') |
No edit summary |
||
| Line 2: | Line 2: | ||
Current list of items being considered is below. We should focus on one to two bigger items and some smaller clean-up items. | Current list of items being considered is below. We should focus on one to two bigger items and some smaller clean-up items. | ||
View [http://trac.mozillamessaging.com/raindrop/query?status=new&status=assigned&status=reopened&milestone=Maple&order=priority Maple Trac tickets] | |||
== Big == | == Big == | ||
* Inflow Design #3: Bryan and Andy have worked out the start of iteration 3, which is a combination of inflow #1 and inflowgrid. Basically, use inflow #1 for personal conversations, but use grid layout to the right of it to show grouped conversations. Specific tasks: | * Inflow Design #3: Bryan and Andy have worked out the start of iteration 3, which is a combination of inflow #1 and inflowgrid. Basically, use inflow #1 for personal conversations, but use grid layout to the right of it to show grouped conversations. Specific tasks: | ||
** Bryan and Andy | ** Bryan and Andy posted to design blog about the design. They continue to iterate. | ||
** James | ** James tagged the tree as 0.1, updated wiki page to point to the tag if people want to see the code that was in the reveal, and mentioned different things are happening on the trunk. | ||
** James to clean up the inflow and client/lib to be optimized for iteration 3. Inflow #1 and inflowgrid will be deleted, and the widgets will be cleaned up to fit iteration 3's | ** James to clean up the inflow and client/lib to be optimized for iteration 3. Inflow #1 and inflowgrid will be deleted, and the widgets will be cleaned up to fit iteration 3's needs. | ||
* Define set of message combinations we can see (direct message turned to a group message, group message forwarded to an individual, different types of notifications, newsletters vs. listserv mail). Then seed Jean's account with that info. | * Define set of message combinations we can see (direct message turned to a group message, group message forwarded to an individual, different types of notifications, newsletters vs. listserv mail). Then seed Jean's account with that info. | ||
| Line 30: | Line 32: | ||
* Explore some JavaScript server side options. At this point we want to try to avoid an option that requires Java, but just to cut down on our code dependencies. It may be considered later if a suitable solution is not found. Two options stand out: | * Explore some JavaScript server side options. At this point we want to try to avoid an option that requires Java, but just to cut down on our code dependencies. It may be considered later if a suitable solution is not found. Two options stand out: | ||
** Explore couchJS. Can it be used for our purposes? Need network and probably restricted file access to load some JS library code. | ** Explore couchJS. Can it be used for our purposes? Need network and probably restricted file access to load some JS library code. Mark has done a pass on this, and we need fixes in CouchDB for curl support in couchjs. | ||
** Explore [http://www.toolness.com/wp/?p=678 Pydermonkey]. Would be nice particularly if it has access to Python libraries, but at a minimum need network and restricted file access. | ** Explore [http://www.toolness.com/wp/?p=678 Pydermonkey]. Would be nice particularly if it has access to Python libraries, but at a minimum need network and restricted file access. | ||