Monday, January 28, 2008

l.c.a.

did lunch with a fellow who is a professor at the university here who is also working on the collaborative editing features in abiword. he got us into the faculty lounge where the food and drink was good and cheap, too good features when it comes to food. we discussed ways to make the abiword collaborative features into a generic library so others applications use some of their fine work on the path to supporting collaborative efforts. he's presenting on his work in abiword tomorrow, so i'll be attending that one for sure.

then it was on to presentations on desktop deployment issues and policykit. we (kde) really need to get our ass in gear when it comes to supporting policykit, in my opinion. we have stubbed in a few places to do this, but there is really no firm code to point at in many places. i need this stuff in plasma, so maybe i'll sit down and write a bit of policykit-ish stuff.

currently i'm sitting in a presentation by Martin Michlmayr on his research on release schedules in large free software projects, and in particular on time based releases. i have a bit of work to do on my slides tonight for thursday, so i think i'll take an early out tonight if possible to do that.

3 comments:

Hubert said...

the professor is Martin Sevior, he also wrote large chunk of AbiWord itself.

liquidat said...

The Pardus guys mentioned several times that they are working at a PolicyKit implementation for KDE. Unfortunately it is not ready yet but maybe you can team up with them?

It is on their roadmap:
http://en.pardus-wiki.org/Pardus:Pardus-2008_Roadmap
Also, there is already some code available:
https://svn.uludag.org.tr/uludag/trunk/PolicyKit-kde/

Wade said...

At minimum, PolicyKit sounds like another good Google SoC project in addition to OpenID and Kiosk/Plasma work.

Have we started a list yet to track potential ideas?