GSoC status update, week 0

Your hacking starts... NOW! Official coding period has started yesterday. Dependencies have been downloaded, first lines of code have been written, first commit has just been pushed to the repository. The real work has started; now it's time to write actual code. ;) From now on, updates will be posted twice a week, every Tuesday and Friday.

Work done this week

  • Initialized code repository
  • Did research and initial choices on libraries:
    • Hunchentoot and Drakma for initial HTTP server and client
    • Ironclad for cryptography-related stuff
    • FiveAM for unit tests
    • For XML, no final decision yet… I'll start with XMLS for its simplicity, and maybe move on if it doesn't work well
    • Probably will need something for safe random number generation, will leave that one for later and stick with (RANDOM), seeded with /dev/random if possible, for now
    • Possibly some library for parsing will be needed; CL-PPCRE, or maybe some variant of Meta?
  • Linked and described repository, needed libraries, darcsweb and cut-and-paste HOWTO for getting the code with dependencies on Wiki front page
  • Prepared workplace, without local OpenID Provider for testing yet

Problems

Small delays related with final exams. Didn't complete list of existing implementations and reference providers, neither read much about the XRI thing. Still have some exams this week, and at least two more on June 9 and 11, but they should not cause significant delays

Plans for next half-week

  • Finish list of implementation and providers
  • Set up local OpenID Provider on my workstation for testing
  • Initial work on ID normalization plus unit tests

Lemonodor-fame is but a hack away!

GSoC status update, week -1

This week I spent mostly fighting with infrastructure (Trac, web page, mailing lists, and so on), and reading further into specs. Just a week of research, and coding start date, May 26th, should be just right to actually start coding.

Today, I received a surprise book from Google. All the rumours on students' mailing list about it being beautiful are fully confirmed ;]

Work done this week

  • Further work on infrastructure: Trac versions, milestones, ticket types etc
  • Establishing rough roadmap, published at Roadmap page of project's Trac.
  • Completed referenes on ProtocolInformation Wiki page
  • Started a list of existing implementations and providers on ExistingImplementations Wiki page
  • More documentation reading: finished OpenID and Yadis; XRI and relevant RFCs are still left to read

Plans for next week

  • Initialize Darcs repository with code skeleton (directory structure, .asd file, package, etc), link darcsweb from main page and wiki
  • Finish list of existing implementation and providers
  • Complete list of libraries that I will use (especially cryptography and XML-related ones)

GSoC status update, week -2

Dla polskich czytelników: od teraz do września na blogu publikował będę raz lub dwa razy w tygodniu status swojego projektu w Summer of Code 2008 (piszę lispową implementację OpenID, strona projektu jest pod adresem http://common-lisp.net/project/cl-openid/). Jest to jeden z oficjalnych kanałów komunikacji związanej z projektem, więc wiadomości pojawiać się będą w języku angielskim.

This year, I got accepted to Google Summer of Code programme. I will work on Common Lisp implementation of OpenID protocol; project page is at http://common-lisp.net/project/cl-openid/, and full proposal is available on project's Trac Wiki at OriginalProposal page. I will publish status updates twice a week (weekly before coding, which starts May 26) on this blog, in category CL-OpenID (RSS). This is the first update, two weeks before coding start.

Work done this far

  • Discussed project organization with mentor, Anton Vodonosov;
  • Chosen the license (LLGPL), version control method (darcs), and hosting (common-lisp.net);
  • Created common-lisp.net project, with mailing lists and Trac Wiki and issue tracker;
  • Initial overall design, described on InitialDesign Wiki page;
  • Initial reading of the specification.

Plans for next week

  • Further reading into specifications, especially RFCs referred to by OpenID spec;
  • Estimating rough project time line;
  • Research on existing OpenID implementations for comparison, ideas and testing.