jauto

Bad week, bad…
Bad in my personal life, but it was so hard, that it influenced my work and I didn’t do everything I planned, sadly. But fortunately all the bad is gone now, and I could grow stronger!

XMPP Component is.. hmm… 50% complete. I still need to add some request handling logic, but it should be fine really soon.

Plans for next week

Finish XMPP Component

More Python fun!

Prepare demo for mid-term evaluation

Next week, I need to show my progress to my mentor. Got to finish and polish unfinished things!

Exams at last!

Aaaaaaaa!!!!

As you can see, I managed to set up something that looks like a project website

Other news: Psi patch is 90% done. As a side effect, I improved stanza error handling in Psi
Since error handling will be probably a bit modified before including in Psi mainline, I’d like to wait for the official version and then create my patch, so it can be easier applied. If, however, this takes much time, I’ll release a dev-version of the patch.

I also did some research on Apache modules for authentication.

And I’m in the middle of getting in touch with JEP-0070 original author to get his help.

Plans for next week

XMPP Component

let’s have some fun with Python!

preparing for exams at univ

why? oh why?…

6AM. So you think I’m getting up so early to code? Wrong! I’m going to sleep at this hour! ;)

This was a nice week.

First of all, Jacek Konieczny became my mentor. At last I can easily talk with someone about my project (yes! he’s from Poland, just like me :)).

Second, as decided previousely, I did some coding this week, to “forget” about problems with The JEP. There are problems at HTTP side, so I did some coding on XMPP side :)

My Psi can - more or less - display incoming confirmation requests.

Moreover, they are sent by something that looks a bit like HTTP-Auth XMPP component. But at the same time, this something looks much like the example component from PyXMPP package ;)

Plans for next week

Set up nice website on SourceForge

I created project really long time ago, but: First, some people suggested that using SF (located in the USA) may be a problem when stating that no US activity was involved in my SoC development (yes, tax forms), so I was waiting for official statement about this. Then I was busy. Then I had time, but SF was down for maintaince ;) Etc, etc.

Talk with JEP authors to get their opinion and advice

I cannot run away from HTTP part forever ;)

Code a bit more

I’d like to release some code this week.

Study for my exams…

Note: “Week 1″ means “status report after week #1″

While some happy students are already coding, I’m reading the docs. And it’s really good that I started with reading. The more I read, the more problems with JEP-0070 I discover (magic realm usage, unreadable transaction id in Digest schema). It seems that instead of implementing the JEP, I will have to fix it first.

In the meanwhile, I did some research and now I more-or-less know what-and-how I need to do in Apache part of my project.

Since much of decisions depend on what JEP-0070 is really going to say, and it takes some time to create The Right Solution, and I need to consult with other - smarter - people, who also need some time to think about it, I decided to leave this alone for now and do some coding in area which is unlikely to change (much): XMPP Client - a patch for Psi.