diff options
| -rw-r--r-- | todo.txt | 134 |
1 files changed, 63 insertions, 71 deletions
@@ -1,11 +1,3 @@ -Froze during reindex: - - ActsAsXapian.rebuild_index InfoRequestEvent 16061 - - foi 23175 0.0 0.0 5176 1472 pts/1 S+ 14:16 0:00 /bin/sh /usr/bin/wvText /tmp/foiextract20100619-20578-1gcbuqz-0 /tmp/foiextract20100619-20578-1gcbuqz-0.txt - foi 23180 0.0 0.0 4664 1220 pts/1 S+ 14:16 0:00 /bin/sh /usr/bin/wvHtml -1 /tmp/foiextract20100619-20578-1gcbuqz-0 --targetdir=/tmp wv-XeJwGT - - Next (things that will reduce admin time mainly) ==== @@ -16,66 +8,41 @@ Handle bounce messages from alerts automatically Make outgoing requests and follow ups get CCed to our backup mailbox, so that can do data recovery more easily -sending an email alert for this query takes crazy long - query = 'variety:response (status:successful OR status:partially_successful)' -something to do with the way event_digest loops with lots of responses? -This is causing cron spam so needs fixing - Make it so when you make followups the whole request is shown on the page. +Remove all show_response URLs, and replace with a special version of the +request URL with a new input box at the bottom and a hash link to it? +<< when following links such as "I'm about to send clarification", a +form appears into which the reply can be typed. However, the +previous correspondence in that thread is not shown. +I usually open a new tab to see what was written previously before +writing in the form. It might be useful if the previous +correspondence were instead shown on the page in which the form +appears. >> Word doc conversion never works for Lisa, maybe use more software to try to convert her docs. -Finish profile photo +Finish profile photo - maybe use Gravatar, but opt in for existing users? Ask people for annotation immediately after they have submitted their request Ask for annotation about what they learnt from request? -Have proper house rules / site terms and conditions page. -Perhaps borrow from these house rules: - http://www.theyworkforyou.com/houserules/ -Particularly that it is a permanent public archive - do you own your request? - -Make request addresses easier to type in again, and routing work better: -* Put the request from address in the database, - XXX make sure it knows the type, as need fuzzy rule for matching/guessing according to type -then change the rule for making it. -* Change holding pen to lookup hash e.g. 1bd8ea of the request address in database - (so gives good guess it the hash is right, but the number is wrong) -* Use maybe words for generated email address? Name of the person and a request -number (i.e. number of that persons request, so there are few numbers)? -julian.todd@section44.whatdotheyknow.com -* Use words from a dictionary, e.g. cat, mouse, rat, hat etc. -* Use single words from the request, e.g. section, terrorism, allotment -* Make sure avoid FROM_ENDS_IN_NUMS rule in Spam Assassin -* It looks like an error generated by GFI MailEssentials, see p62 of chapter - 11 of the manual at http://www.gfi.com/mes/me11manual.pdf which states: - 7. Check if emails contain more than X numbers in the MIME from: - Frequently, more than 3 numbers in the MIME from means that the sender is a - spammer. The reason for this is that spammers often use tools to - automatically create reply-to: addresses on hotmail and other free email - services. Frequently they use 3 or more numbers in the name to make sure - the reply-to: is unique. -* Use FOI code allocated by authority to work out where emails are to go -* Second request to same authority by same person - tell them to be sure -to use the right email -* Improve routing from Exim so copes with addresses not having request- prefix. - -check-recent-requests-sent probably doesn't work, as exim log lines wouldn't -be load in case where the envelope from gets broken? - Admin button to resend request one off to particular address Private request premium feature http://www.activemerchant.org/ +Froze during reindex, is the doc files inside the .zip here: + http://www.whatdotheyknow.com/request/last_collection_times#incoming-8405 + ActsAsXapian.rebuild_index InfoRequestEvent 16061 + foi 23175 0.0 0.0 5176 1472 pts/1 S+ 14:16 0:00 /bin/sh /usr/bin/wvText /tmp/foiextract20100619-20578-1gcbuqz-0 /tmp/foiextract20100619-20578-1gcbuqz-0.txt + foi 23180 0.0 0.0 4664 1220 pts/1 S+ 14:16 0:00 /bin/sh /usr/bin/wvHtml -1 /tmp/foiextract20100619-20578-1gcbuqz-0 --targetdir=/tmp wv-XeJwGT +Also freezes Abiword, but not catdoc + Performance =========== -When sending alerts, alter way track_thing.track_things_sent_emails so it -doesn't get *all* previously sent items. - Enable Directory Indexing, and disable atime (@glynwintle suggests) http://www.softpanorama.org/Internals/Filesystems/linux_ext2_ext3.shtml (as/if we have caches with lots of files in a direcory) @@ -118,6 +85,46 @@ Remove comments visible Later ===== +check-recent-requests-sent probably doesn't work, as exim log lines wouldn't +be load in case where the envelope from gets broken? + +Point all MX records to one server, so can see incoming messages in exim logs also. +Hmmm, but less robust. Run the exim log grabber across all mail servers? + +XXX Not sure all this matters really, requests seems to be getting through better these days? +Make request addresses easier to type in again, and routing work better: +* Put the request from address in the database, + XXX make sure it knows the type, as need fuzzy rule for matching/guessing according to type +then change the rule for making it. +* Change holding pen to lookup hash e.g. 1bd8ea of the request address in database + (so gives good guess it the hash is right, but the number is wrong) +* Use maybe words for generated email address? Name of the person and a request +number (i.e. number of that persons request, so there are few numbers)? +julian.todd@section44.whatdotheyknow.com +* Use words from a dictionary, e.g. cat, mouse, rat, hat etc. +* Use single words from the request, e.g. section, terrorism, allotment +* Make sure avoid FROM_ENDS_IN_NUMS rule in Spam Assassin +* It looks like an error generated by GFI MailEssentials, see p62 of chapter + 11 of the manual at http://www.gfi.com/mes/me11manual.pdf which states: + 7. Check if emails contain more than X numbers in the MIME from: + Frequently, more than 3 numbers in the MIME from means that the sender is a + spammer. The reason for this is that spammers often use tools to + automatically create reply-to: addresses on hotmail and other free email + services. Frequently they use 3 or more numbers in the name to make sure + the reply-to: is unique. +* Use FOI code allocated by authority to work out where emails are to go +* Second request to same authority by same person - tell them to be sure +to use the right email +* Improve routing from Exim so copes with addresses not having request- prefix. + +When on a small screen, the actual form when making a new request is below +the fold, and it isn't obvious what you need to do. (Seen while watching +a new user try to make a request) + +Put public body name in search text for each info request, so that people +typing in a word and a body name in the search (have seen people new +to the site doing that) do find things + Completely remove the "feed" option from tracks Show the Subject: lines on request pages. Perhaps only show them where they are @@ -157,25 +164,12 @@ For followups, have radio button to say is it a new request or followup Do by uncommenting the "new information" option when writing a followup, so that it makes a new request -Point all MX records to one server, so can see incoming messages in exim logs also. -Hmmm, but less robust. Run the exim log grabber across all mail servers? - -Change it to store emails as files in the filesystem? For speed. +Change it to store emails as files in the filesystem? For speed of backup if nothing else. Should have simpler system for us to upload files sent to us via CD etc. Currently we have to manually put them in the files directory on the vhost. Make it so web upload interface copes gracefully with arbitarily large messages (it causes speed trouble having them in the database right now) -Remove all show_response URLs, and replace with a special version of the -request URL with a new input box at the bottom and a hash link to it? -<< when following links such as "I'm about to send clarification", a -form appears into which the reply can be typed. However, the -previous correspondence in that thread is not shown. -I usually open a new tab to see what was written previously before -writing in the form. It might be useful if the previous -correspondence were instead shown on the page in which the form -appears. >> - When it prompts error_message people to send annotation, maybe just show them the email address of the error to check then and there? @@ -183,7 +177,7 @@ If you've already conducted an internal review, at all places - when on unhappy/url - when on not held link - on the page for the request -don't offer it again. +don't offer it again, as they've already done it. Example of completed review: http://www.whatdotheyknow.com/request/request_for_full_disclosure_of_b#incoming-9267 @@ -227,7 +221,7 @@ CSS / design things but some magic Ruby thing is printing the error span. - Improve CSS on IE7 for large images in docs http://www.whatdotheyknow.com/request/3289/response/7810/attach/html/3/20081023ReplyLetter.pdf.html - - favicon.ico would be nice + - favicon.ico would be nice, maybe the ? from the logo - Get Atom feed of search results to include stylesheet for highlighting words in yellow somehow @@ -235,11 +229,9 @@ When doing search, people often just want it to show the whole page. Perhaps all listing should just link to top of page, rather than # links for outgoing incoming, or perhaps just some of them. -Help page improvements: - Add "Who should I make my request to?" - make flow better after first section, to abrupt now - Some more traditional help (in a new section in the help) such as: - * Information about how to track requests and RSS feeds - * Information about how to contacting other users +Some more traditional help (in a new section in the help) such as: + * Information about how to track requests and RSS feeds + * Information about how to contacting other users Show similar requests after you have filed yours - maybe on preview too. |