[GSOC] Rewrite chat log backend and frontend

Adam Hamot adamhamot at gmail.com
Wed May 1 03:13:23 EDT 2013

Thanks for the reply Jorge. After reading all of the archives pertaining to
the Chat Log storage many questions came to mind:

Will IMAP be part of this project? I've seen many conflicting statements so
I would just like to get this straightened out. If remote-storage is wanted
it would probably be easier to let the user link their dropbox/google
drive/etc account than have them input an IMAP server address (which I'm
not certain many users know how to do/own their own IMAP server).

What is the recommended storage format? There has been discussion about
storing the chat log in a format that is capable of being read via a
grep-like utility? If we stored via plaintext (like we are currently doing)
then we would be able to just use grep. If we plan on using a database
(most-optimal) then I guess making a command-line utility that acts like
grep would need to be added to the project?

There also has been discussion about writing a seperate library and simply
letting libpurple use this library to record logs. The library function
calls would accept function pointers which would add the log to the storage
unit. Although this might be a bit over-ambitious.

Should I sort of just design how the new backend would be (using these
questions) on the application or is there a particular way you are looking
for it to be implemented?


On Tue, Apr 30, 2013 at 11:47 AM, Jorge Villaseñor <salinasv at gmail.com>wrote:

> On Mon, Apr 29, 2013 at 6:40 PM, Adam Hamot <adamhamot at gmail.com> wrote:
>> Hello everyone,
>> My name is Adam Hamot and I am currently a Computer Science student ('15)
>> at the University of Maryland. I just recently found out that pidgin was
>> part of GSoC this year (after anxiously searching for a great matching
>> organization) and I would love to work with you all over the summer.
>> From browsing the ideas list (
>> https://developer.pidgin.im/wiki/FutureSOCProjects) I saw that the first
>> idea would be a perfect match for me as I am very interested in backend
>> code and love logging my chats! I have been using pidgin for just over 2
>> years now and it has never once failed me. I primarily use it to talk to a
>> couple of friends who are still using AIM and it is always nice to go back
>> and look at our logged chats. Of course the logging feature works but it is
>> not very elegant. I would like to change this by updating the logging
>> screen along with adding more capabilities.
>> I would just like to get some answers from everyone before I start
>> working on my application.
>> 1) What exactly should my proposal for this idea include?
>>    - Should I go through the logging code (so far I've read over
>>    pidgin/gtklog.c and libpurple/log.c) and state how I would store the new
>>    chat log format using existing/new structs?
>>    - Are there more files pertaining to logging that I am missing?
>>    - Would I be better off creating my own file format for this task or
>>    should I use an existing one (JSON, YAML, etc)?
>> 2) Do I have to create my own mockup if I feel the current mockup listed
>> is adequate?
>> 3) Is it better to write my proposal and send it here to get feedback or
>> should I submit my proposal and then ask for feedback here? Mainly I would
>> love to get feedback before the application period ends so that I can have
>> a fully polished application and increase my chances of working with you
>> all.
>> I look forward to hearing from you.
> Hi Adam, I am glad you found the organization.
> I would like you to read the email archive since the last couple of weeks
> we have had a extensive discussion about what to include or not in the
> logging project. Most of your questions are answered there.
> On the file format, I would prefer to have some standard format, I do like
> compatibility.
> If you have a better idea (over the current mockup) just show it, have in
> mind that the current one is available for everyone else too.
> --
> Masca
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20130501/f15b8dd8/attachment-0002.html>

More information about the Devel mailing list