GSoC is not that important to split the time before and after it (GSoC), but I liked that subject because it reminds of a well known song I was listening to in my earliest youth :>
So what's going on after GSoC (relevant to GSoC)?
The truth is that I don't have much free time, but I try to devote some time in otr4j and SIP Communicator. The SIP Communicator plugin is in a good state but there are some open issues for otr4j.
I have already worked on otr4j issue 3 because there was demand. Currently I'm reading Java I/O so I can work on issue 1 with more confidence.
The code changes required for closing issue 1 would affect 20-25% of the code approximately and will improve code quality and readability a lot and a bit it's efficiency.
Another thing I've started working on is a port of otr4j in .NET (otr4net), I think that will follow IO changes because I want to have a good model before I finish the port.
That's about it :)
otr4j is part of my GSoC 09' project and is encouraged by the SIP Communicator development. otr4j is an implementation of the OTR (Off-the-Record) protocol in java.
Thursday, September 17, 2009
Subscribe to:
Post Comments (Atom)
My Commits to SIP Communicator
Error loading feed.
Mercurial commits to project otr4j on Google Code
- Revision 408c8043ee: Fixed a potential NullPointerException. - Invalid Date
- Revision 64379ae226: Changed some of the OtrEngine methods to throw OtrExceptions instead of calling - Invalid Date
- Revision 8810f92c65: Added tag 0.9 for changeset d59b314765cf - Invalid Date
- Revision d59b314765: # Fixed DataMessage serialization. # Issue 8: non-(ISO Latin 1) characters do no - Invalid Date
- Revision 0d25e99de9: Renamed MessageBase to AbstractMessage and EncodedMessageBase to AbstractEncoded - Invalid Date
No comments:
Post a Comment