Archive

Posts Tagged ‘daily_notes’

June 11-12, 2011

June 12, 2011 Leave a comment

Dynamic pages:

  • Read the basics of storm/sqlite
  • Got the basic understanding of Andrew’s approach through his blog.
  • Configured apache and tested python scripts with CGI and mod_wsgi. It seems that mod_wsgi offers many advantages compared to CGI. Though, for mailocate project, CGI was used.

Static Html

  • Update the html file of the conversation list: the entry corresponding to the updated conversation needs to be updated as well. ✔
  • Some issues with hide_quotes ✔
  • indentation in conversation ✔
  • differentiate between article.body() and article.html_body() ✔
  • clean up the code ✎
    • merge _in_reply_to and in_reply_to fields
  • commit.. ✔
  • Write down instructions and other notes to be able to install and see my modified code in a working condition ✔✎
Advertisements

June 6-9, 2011

June 10, 2011 Leave a comment
  • Update the html file of the conversation list: the entry corresponding to the updated conversation needs to be updated as well. ✔✎
  • Some issues with hide_quotes ✔
  • indentation in conversation ✎
  • differentiate between article.body() and article.html_body() ✔
  • clean up the code ✔✎
  • commit.. ✔
  • Write down instructions and other notes to be able to install and see my modified code in a working condition ✔✎

✔: finished | ✔✎: unfinished | ✎: todo

I hope to complete all these unfinished tasks by today. Then, I’ll discuss my overall strategy with mentors.

June 2-6, 2011

June 6, 2011 Leave a comment
  • in archive-ui, when a message is archived, all the conversations are generated again. Ideally, we should do minimum amount of work on archiving a message. Finalised a strategy to achive this.
  • Implemented it.
    • Similar to {date, subject, article, author, thread}, keep a new dumbBTree of conversations which stores the mapping: thread_addr –> list of msgids present in that conversation
    • when a new message is archived, conversation file corresponding to its thread_addr is built from list of msgids.
  • TO-DO:
    • Update the html file of the conversation list: the entry corresponding to the updated conversation needs to be updated as well.
    • Some issues with hide_quotes and indentation in conversation
    • differentiate between article.body() and article.html_body()
    • clean up the code
    • commit..

May 31 – June 1, 2011

June 2, 2011 Leave a comment
  • Thought about lots of issues about archive-ui and discussed them on mailing list.
  1. Arranging conversations by months: In pipermail, all the static htmls generated for each message(that goes into archives) are arranged in directories corresponding to different months.
    Whereas in archive-ui, all the conversations are stored in a single directory. The reason is that since a conversation can span across months, it is somewhat ambiguous where to keep that conversation.Conclusion:

    1. No advantage of arranging messages on a monthly basis.
    2. Implement  “searching for messages by period” functionality. This was not implemented in archive-ui but a use case and solution was developed.
  2. Readable urls:URL corresponding to a conversation can be created from subject of the first message of a conversation (in the same way as various blog sites do).Conclusion:
    1. Some part of it is already implemented in archive-ui. I’ll leave it for now.
  3. in archive-ui, when a message is archived, all the conversations are generated again. Ideally, we should do minimum amount of work on archiving a message.Conclusion:
    1. No decision on this. Will try to discuss about it more.

mailocate -> Work by Priya to implement search capabilities in mailman.

  • Wrote the basic function for “search by date” functionality. Checked out the code of “mailocate”. The interface for “search by date” will also be implemented in mailocate.
  • Updated some more templates of pipermail to match archive-ui.
  • Handling Top/Bottom Posting
    By default, the quoted text can either be all hidden or all displayed. It might also be good to only hide the quoted text when it is at the end of the message, as when it is in the middle, the user is likely to want to see it for context.Started working to test this on mm3 and also, to account for one more test case:
    ->On mailing lists, people generally use ‘inline posting’ to reply. One level of inline posting is helpful to see the context, but if it goes beyond one level then, it might be a good idea to hide the old quoted text

May 30, 2011

June 1, 2011 Leave a comment
  • Completed checking out pipermail and archive-ui once again
  • Figured out the areas which need to be changed/improved
  • some doubts regarding logic and use-cases of archive-ui

May 27-28, 2011

May 28, 2011 Leave a comment
  • Modified archive-ui code to substitute templates using new string substitution feature which is used in mm3.
  • Made a little modification in adding an article to the database
  • Finally, for the first time, on adding a new message to the archives, I can see conversation-list page and each conversation page – both working perfectly!!
  • But in most of the code, I have used little hacks to just make it work. So, its time to go through the archive-ui and pipermail code once again, and then, write a good code to achieve that basic functionality. Have already started working in this direction.
  • After that, next thing would be to make some new changes and add more features to the archive-ui for mm3.

May 26, 2011

May 27, 2011 Leave a comment

[Written on May 27]

  •  Archive-ui was written on top of systers’ implementation of mailman, which supports some extra mailman extensions e.g. DList and conversations view also shows email address corresponding to the conversation. But Dlist has not been ported to mm3. So, I got confused but later realised that conversation view can be shown without DList feature. Overall, it took some time to search mailman and systers archives to learn more about DList and its current status.
  • Progressed a little more in modifying archive-ui code for mm3. It turned out I needed very minor changes to make account for the changed MailingList structure(from mm2.1 to mm3). It will be a good idea to understand what major changes have been done in mailman while going from mm2.1 to mm3.
  • Currently, working on substitution of templates to generate static htmls. mm2.1 and mm3 have different ways to substitute values inside templates from a dictionary.