X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=TODO.mutt-ng;h=36f5cc9f188a723682eacc2a5427c2b25d1d4714;hp=f319dcae8477bde6b0963e573891a5fa8ad33398;hb=7268d1308fc75ad77a6bf6d48362a0dc1fd6104b;hpb=ba6e54aa3353a57727af57294bedf31b3578b953 diff --git a/TODO.mutt-ng b/TODO.mutt-ng index f319dca..36f5cc9 100644 --- a/TODO.mutt-ng +++ b/TODO.mutt-ng @@ -1,14 +1,24 @@ -Here's a list of all mutt-ng specific TODOs: +Here's a list of all mutt-ng specific TODOs (not in priority order): -We need to modify the build scripts and paths in the source so that mutt-ng doesn't conflict in any -way with mutt. +- We need to do a security audit. At least remove all the unsafe + function calls, even when they're marked with "secure" or "checked", + and replace it with secure alternatives instead. In this process, + remove any calls of functions for which we have internal library + alternatives already. -We need to do a security audit. At least remove all the unsafe function calls, even when they're -marked with "secure" or "checked", and replace it with secure alternatives instead. +- Start cleanup and finally make all the patches work together. As some + starting hints: kill the caching for NNTP in favor of the header + caching patch, move as much code of optional compile-time features out + to their subdirectories, and so forth. -Remove all the multibyte-character handling stuff. It only makes the source code complicated, and -doesn't add any special functionality - no, in one case, it already caused lots of problems. +- Stop making up names of global functions with mutt_*; give meaningful + names and declare them in the right headers to eventually obsolote + protos.h. This counts for data typedef's, too! Write one header and + one source file per datatype, do proper information hiding and thus + provide sane internal abstraction to get "future ready." For example, + for all the mailbox handling, the mbox_*/mmdf_* and mh_*/maildir_* + functions should only be called directly in the right abstraction + layer's implementation. And so forth. -Update the ChangeLog file or create a new ChangeLog.mutt-ng file. - -Incorporate a lot more patches that are floating around in the web. +- Improve documentation, update/rewrite/remove README.SSL and files in doc/ + all other documents in directory root are up-to-date