Ryan Pavlik (code - art - life) on cleardefinition.com
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
33
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
33
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in
/homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/functions.php on line
33
May 27, 2008
Google Summer of Code 2008 officially starts this week in the “main section” - coding! In my case, I’ll be working on revamping the Styles support and interface, and to avoid having to code it three times, I’m starting first with a design phase. As such, I’ve been working on an interview script, which should be ready to use now. The purpose of the interviews will be to confirm or fail to confirm the characterization of use cases I made in my proposal. I will also do bug triage here tomorrow, looking through the open Styles bugs and seeing if I can also filter out the Styles bugs in the Front End components in Bugzilla - see what actual software flaws there are to resolve, what insight/ideas I can glean from enhancement requests, etc. With this I’ll be able to create a more comprehensive plan and schedule, as well as give me something to chew on when I don’t have test subjects available to provide interview results or prototyping feedback.
Though I’ve done the Summer of Code once before, this will be a totally different experience - new mentor, different codebase region (by a lot!), and entirely different focus - I’ll be replacing working but not human-friendly with friendly, efficient, and hopefully still working! 
Oh, and how did I prepare for the summer of code? Well… I built a new desk! (I already took care of community bonding a couple of years ago.) An ergonomic, efficient desk area will inspire an efficient, ergonomic design - at least that’s the idea!
PS. The hackergotchi on Planet AbiSource right now is not very flattering, not to mention fairly old - if one of the cool AbiFolk could change it to my new one, that would rock. Bonus points if you put in a good word with the p.g.o folks too - get some AbiWord representation on the planet! (It seems the “put your stuff in this table on the wiki” page disappeared from l.g.o without my request being fulfilled…)
No comments yet.
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/link-template.php on line 73
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/27/d92327250/htdocs/domains/cleardefinition/blog/wp-includes/link-template.php on line 98
RSS feed for comments on this post. TrackBack URL
Copyright 2004-2008 Ryan Pavlik. Code released under the appropriate license to contribute.
