@@ -20,22 +20,23 @@ many of us can get together in one place and talk about what we can agree would
20
20
be the best steps to make email better. There isn’t, yet, a carved-in-stone
21
21
agenda, but here’s what we expect we’ll be doing:
22
22
23
- ** When** : October 30th - November 1st , all day
23
+ ** When** : November 9th - November 11th , all day
24
24
25
- ** Where** : London, England
25
+ ** Where** : Montreal, Canada
26
26
27
27
** What** : We’ll talk about…
28
28
29
+ * standardizing autoconfiguration and authentication across clients and
30
+ protocols
31
+ * practical problems related to interoperability and user confusion that can be
32
+ addressed by changing how we work
29
33
* what features (especially those already standardized) would give users a
30
34
faster, more reliable experience if widely implemented
31
35
* what features would reduce network traffic, round trips, and other server
32
36
cost if widely implemented
33
- * what features are * not* yet standardized, but seem like the next thing
34
- everybody wants in their client — and how we can prioritize standardizing
35
- them
37
+ * the wins of JMAP, in quantitative terms
36
38
* how to begin leveraging JMAP without having to totally rewrite IMAP code,
37
39
especially for server-pushed change notifications
38
- * how to prepare for more widespread transition to OAuth and JMAP
39
40
40
41
We’ve got a list of RFCs and draft standards that we think make good talking
41
42
points to start, but we'd also love to hear from you in advance about what you
0 commit comments