Adventures in FPLing: The two-week mark, and what I do all day
I’m approaching the two-week mark in FPL-hood. Now that I’m kind of over the “learn about all these new things” hump, getting through transitioning tasks, and the talk to Media People stuff, I think I’m settling in a bit more into the actual Getting Things Done part of the job. Which is pretty cool, and a nice place to be.
Although we have a nice wiki page about the FPL position itself, and what it vaguely entails, there’s not a concrete list of “what the FPL does,” and certainly FPL to date has brought their own personality to the job, and as such, has had their own list of tasks and to-dos. Of course, there are things the FPL does that wind up being fairly obvious to the community; some of these are actually laid out on the handy-dandy FPL schedule. Most of the scheduled stuf revolves around PR-things, like ensuring (by writing it) that Red Hat puts out a press release at release time, that we’re doing Feature Stories on some of the more high-profile features, that we’re sending USB keys with previews of the new release to press folks, etc., though there are other things (checking in with election wrangler to make sure elections happen, and the like).
But, of course, those aren’t the only things, and attending/running board meetings isn’t the “other thing,” either. Not everything the FPL does is going to be front-and-center obvious to the whole community; not everyone is on every mailing list, not everyone is in all irc channels at all times. Transparency is important in this job, and I’d like to do as good as humanly possible in that regard; while blogging, obviously, is one way to keep everyone up to date on what I’m up to, it’s not comprehensive.
To that end, I’m experimenting a bit with a wiki page I made, that essentially is my “to-do/done” list – you can check it out here. My hope is that it will provide a nice record of what I’m planning to do and getting done, and give a reasonable, without being completely obnoxious in detail, view of what the job entails. I’ve got it divided up into fairly-immediate (week-ish), short-term (month-ish) and long-term goals; we’ll see if that format works out well, or not.
Feedback welcome, of course.