526
Comment:
|
528
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
Potential plans for the EmailSigSprint | === Potential plans for the EmailSigSprint === |
Line 3: | Line 3: |
Here are some things we could do during an email sprint. I'm not sure whether there is 4 days worth of work here, or just two. |
Here are some things we could do during an email sprint. I'm not sure whether there is 4 days worth of work here, or just two. |
Line 7: | Line 5: |
- Design the API for email v3.0 | * Design the API for email v3.0 |
Line 9: | Line 7: |
- Implementation of email 3.0 changes | * Implementation of email 3.0 changes |
Line 11: | Line 9: |
- Fix references to codecs (i.e. CJKCodecs issue) | * Fix references to codecs (i.e. CJKCodecs issue) |
Line 13: | Line 11: |
- Design and implement a new parser | * Design and implement a new parser |
Line 15: | Line 13: |
- Implement support for more RFCs | * Implement support for more RFCs |
Line 17: | Line 15: |
- Write a suite of email address validators that doesn't depend on rfc822.py and is more consistent with RFC 2822. |
* Write a suite of email address validators that doesn't depend on rfc822.py and is more consistent with RFC 2822. |
Line 21: | Line 17: |
* Other topics? |
Potential plans for the EmailSigSprint
Here are some things we could do during an email sprint. I'm not sure whether there is 4 days worth of work here, or just two.
- Design the API for email v3.0
- Implementation of email 3.0 changes
- Fix references to codecs (i.e. CJKCodecs issue)
- Design and implement a new parser
- Implement support for more RFCs
- Write a suite of email address validators that doesn't depend on rfc822.py and is more consistent with RFC 2822.
- Other topics?