The other day I was asked in IRC if I did all the PackageKit coding myself. My response was “I do most of the C, but that's mainly boiler-plate stuff; the backend team do all the hard work“. The next question was “what is the development team like?” which got me thinking:
There's some top class guys doing a lot of work behind the scenes that need some recognition:
- Robin Norwood, new to the project, already rocking with expanding Description with package size and the file list in the daemon and client library.
- Luke Macken, a yum dude, helping to add unimplemented backend functions and fixing the yum backend.
- Tim Lauridsen, another yum dude that is always super quick and efficient. This guy is a yum legend.
- Tom Parker, the apt dude, although he's generally a whizz with C and C++ and general daemon stuff.
- Ken VanDine, the main conary dude, always great for bouncing ideas off and great for thinking outside the box. Always a friendly face in the irc channel.
There's other people as well (sorry to those I left out!) but these guys above are the “core” developers thus far. If you want to get involved, grab an entry from the TODO, email the mailing list and start hacking. We normally hang out in #PackageKit on freenode and are normally a friendly bunch.
If you're not a coder then you can help too. Check out the sources and compile and test test test like there is no tomorrow. Above all else, PackageKit needs more people to talk about it to raise the profile. Articles for news blogs or magazines would be great (email me if interested) – basically anything to raise its profile in the Linux community. I know I'm posting pretty frequently on p.g.o, but the majority of developers will probably miss these. Thanks.