Aaron Winborn: Last Year’s Successful Charity Effort is Making a Difference

Planet Drupal - Fri, 02/05/2014 - 03:33

Hello, My name is Aaron Winborn, and I was the recipient of the Society for Venturism's charity last year, to receive a future cryonic preservation at the facilities of the Cryonics Institute for when the time comes. I'm indebted to many of you for your contributions, and I want to thank you from the bottom of my heart for the peace of mind that this gives me. I still have an albeitedly diminished bucket list of things to do, but I don't stay up fretting over the things I'm incapable of accomplishing, in large part to this assurance. I know the odds are still not in my favor, but at least I have a significantly better chance of revival than if I were buried or cremated.

That said, This past year has been both challenging and a blessing. Challenging because of all the difficulties brought on by having to adjust to the continuing degeneration brought on by Amyotrophic Lateral Schlerosis, ALS, better known in the United States as Lou Gehrig's Disease, or Motor Neuron Disease in other parts of the world. Although I am not yet completely paralyzed, or locked in as they say, I am confined to my wheelchair, and cannot move my hands or arms. My breathing capacity is no longer measurable, and I cannot go for more than thirty seconds without mechanical ventilation before I'm in distress. I am not yet on a vent with a tracheostomy, but we are considering that as the next step to prolong my life. It's a difficult decision to make, however, because of the extraordinary amount of care that I would require around the clock, not to mention the possible loss of a quality of life. It's no wonder that only about ten percent of patients choose a tracheostomy, and only fifty percent of those go on to survive another year.

If that sounds scary to think about, well yes, it is. I could go on with a report of challenges we face, including the utter loss of the ability to speak or to understand spoken language, to the loss of the ability to eat or drink, to the devastation this awful disease has wreaked on my wife and our two young daughters, but I wouldn't be able to do it justice in a few short paragraphs, especially when I want to make sure that I leave space for the good things in my life. So on with the good.

First, I have, after a year or so of giving up reading anything not available on the Internet, have reawakened my love of literature. I've rediscovered the ebook format, and am now devouring about two books a week. Mostly science fiction, but dotted with the occasional contemporary fiction. I'm also still participating in the Drupal community, with a friend who volunteers two hours a week and a tricked up communication device.

Although I have been largely holed up this winter, I still manage to get out every couple of months to see a movie with some friends, and it's been fun sitting at the picture window and watching the girls play in the snow. Oh, how I look forward to the warmer seasons when I'll be able to "walk" the neighborhood again.

I also have been exploring new ways of communicating with my sweetie. Certainly challenging, because of my inability to use the verbal bandwidth, and because so much of her time is taken up as both my primary caregiver and being almost a single parent. On top of that, my day is so broken up and consumed with my caregiving that I find it difficult to even focus on an email that I find myself consolidating my efforts and try to cheat, by counting in my mind a quick CC in an email, or say a mention in a magazine article or a blog post as a valid form of communication. But I know in my heart that doesn't fully count, so I continue to find new ways to let her know how special she is to me.

I am enjoying the simple things in life. I know that's a cliche, but as with all good cliches, there's an element of truth to it. From when our cat decided that my lap is warm and available for napping, to the spontaneous hugs my youngest daughter gives my leg, to watching my older daughter play computer games, to watching my wife's beautiful smile. These are the things that make up life, and I am so excited to have another day of it each morning I awaken.

Stay strong,
Aaron Winborn

This letter first appeared in the latest issue of Long Life magazine: http://www.cryonics.org/images/uploads/magazines/LLV46_N01.pdf

read more

Categories: Elsewhere

S. M. Bjørklund: How to programmatically create a field in Drupal 7

Planet Drupal - Thu, 01/05/2014 - 22:25

Ever had a site not controlled by the features module or felt that using it, add to much administrative overhead? Or you simply want to learn how to use Drupal field API? This is for you.

In this example I will try to keep the amount of code to the very minimum. Putting too much features into a example have a tendency to put some people off with the amount of code it create. The example will not explain how you create new field types, but rather use one existing provided by Drupal core.

Scope of example
  • Create a custom module named demo_field.
  • Enabling the module create a text field and add it to a content type named article.
  • Disable it remove the field from the content type and delete the field.
demo_field module

Not testing for exiting field name or that the node type (story) actually exist. Make sure field name does not collide and that you have a content type named story. If not, alter the code to match your installation.


name = demo field
core = 7.x
dependencies[] = field


That's right, it is a empty module. The real code is found in til file module_name.install.



* Implements hook_enable().
* Create a field. Fields can be created without any needs to attach them to
* entities.
function demo_field_enable() {
  $field = array(
    'field_name' => 'demo_field',
    'type' => 'text',

   * Bind field to a entity bundle.
  $instance = array(
    'field_name' => $field['field_name'],
    'entity_type' => 'node',
    'bundle' => 'article',

* Implements hook_disable().
* Remove field from node bundle (content type) and then delete the field.
function demo_field_disable() {
  $instance = array(
    'field_name' => 'demo_field',
    'entity_type' => 'node',
    'bundle' => 'article',
  print 'Removed ' . $instance['field_name'] . "\n";

This is all code you need to create a field, add it to a content type. Sharing the field with another content type will only require that we add a single line.

Code breakdown

First thing we do is to define a field:
$field = array(
  'field_name' => 'demo_field',
  'type' => 'text',

The very minimum you need to pass to field_create_field() is a name for the field and the type of field. Created fields in Drupal does not have to added to a content type (entity) right away though when you create them through the UI you do not have a choice. The field API on the other hand give you all the flexibility you need. The text field get Drupal default setting since for the sake of simplicity choose to omit any field settings.

$instance = array(
  'field_name' => $field['field_name'],
  'entity_type' => 'node',
  'bundle' => 'article',

This add the field to the node. The very minimum you need to pass to field_create_instance() is the name of the field you plan to attach, the entity type, and the name of the bundle.

Grab the demo_field code

Code can be found in my github repo.

Categories: Elsewhere

Another Drop in the Drupal Sea: Ways to shoot yourself in the foot: Submit "buttons"

Planet Drupal - Thu, 01/05/2014 - 22:19

I was writing custom forms that needed a validate handler and a submit handler. So, I followed the standard approach of

function my_module_menu(){ $items = array(); $items['my/module/custom-form'] = array( 'title' => 'I am a doofus', 'page callback' => 'drupal_get_form', 'page arguments' => array('my_module_custom_form'), 'access callback' => TRUE, 'type' => MENU_CALLBACK, ); return $items; }

Note: My access callback is just to simplify this example.

read more

Categories: Elsewhere

Daniel Pocock: reSIProcate v1.9 WebRTC available for Fedora 20 testing

Planet Debian - Thu, 01/05/2014 - 22:00

Today I just released reSIProcate v1.9 packages into the Fedora 20 testing updates repository.

This means Fedora 20 users can now try WebRTC more easily.

The same version is already available in Debian wheezy-backports and Ubuntu trusty.

Get started today

Install the resiprocate-repro proxy server package using yum.

Set up a DNS entry, here is what we will use in the example:

Domain sip-ws1.example.org WebSocket URL
Use this in JSCommunicator or JsSIP ws://sip-ws1.example.org IP address of server

so the DNS entry will be

sip-ws1.example.org. IN A

Notice that in the ws:// URL, we do not specify a port. This means port 80 is used by default. You can also use a non-standard port if you prefer or if you dont' have root permissions.

Now edit the file /etc/repro/repro.config, adding a transport definition for WebSockets (WS) and change a few other parameters from their defaults:

# Bind to on port 80 Transport1Interface = # Use WS (can also use WSS for TLS, see repro.config for full details) Transport1Type = WS # if using WSS, must also change the transport param here Transport1RecordRouteUri = sip:sip-ws1.example.org;transport=WS EnableFlowTokens = true DisableOutbound = false # Disable all authentication - just for testing DisableAuth = false # allow http admin access on all interfaces, # default is # HttpBindAddress =

Now set up a password for the web admin tool using htdigest:

# htdigest /etc/repro/users.txt repro admin

After all that, restart the repro process

# service repro restart

Go to the web interface on port 5080 (only listening on localhost by default), go to the "ADD DOMAIN" page and add sip-ws1.example.org

Now restart repro again so it recognises the new domain.

# service repro restart

Finally, you can test it using JSCommunicator or tryit.jssip.net

Next steps
  • Set up a TURN server for NAT traversal
  • Use WebSockets over TLS (WSS) instead of regular WS mode
  • Set up authentication (see the various options, including client certificate support, in repro.confg)
  • Connect to regular SIP infrastructure such as Asterisk

Please come and ask on the repro-users mailing list

Categories: Elsewhere

Lisandro Dami&aacute;n Nicanor P&eacute;rez Meyer: Call for help from Debian's KDE Team

Planet Debian - Thu, 01/05/2014 - 20:58
Hi all!

For quite a while now the KDE team has been severely understaffed. We maintain a lot of packages, with many different kinds of bugs, but we don't have enough people to do all the work that needs to be done. We have tools that help us automate the update to new upstream releases, but that's just the tip of the iceberg of our work and so we are writing to invite more people to get involved in the team and help us get KDE software in Debian into better shape.

Some of the tasks that we need help with are:
  • Bug triaging: there are many many bugs in the BTS. We need people that go through them, understand the problem and how to reproduce it, confirm that they are still present in the latest versions. In particular, there are bugs affecting the version in wheezy, and we need people to go through those as well.
  • Bug forwarding: we are so understaffed that we have been asking users to forward the bugs upstream themselves. Some users do this, but some don't. It would help us a lot to have people in the team in charge of this.
  • Patch forwarding: we have quite a bunch of patches applied in the Debian packages that should be applied upstream. Some need to be generalized instead of being Debian-specific. This work would save us time in the future, so it's very important to get it done.
  • Upgrade-testing: in the past, the upgrade from one Debian stable to the other has been quite traumatic for KDE software users. We need people to try upgrading from wheezy to jessie and report any bugs that they might encounter so that we can fix them ahead of the release.
  • Creating patches: many of the bugs that we have require writing patches, some are easy and some are harder, but any help here would be really appreciated.
  • Packaging other KDE apps: we have packages for the core components of KDE software, but there are many other useful components that still need to get packaged.
  • Updating our welcoming wiki page [1], adding these tasks and any future tasks, and unifying the todo lists [2].
If you are interested in helping with any of these, please join our irc channel #debian-qt-kde in irc.oftc.net, or our mailing list [3]. We are happy to help you get started.

[1]: https://wiki.debian.org/PkgKde[2]: https://wiki.debian.org/KDETodo     https://wiki.debian.org/KdeDebTasks     http://pkg-kde.alioth.debian.org/todo.html     gobby://gobby.debian.org/Teams/KDE/TODO
[3]: https://lists.debian.org/debian-qt-kde/

-- Regards,Maximiliano CuriaOn behalf of the KDE team
Categories: Elsewhere

AGLOBALWAY: Responsive tools

Planet Drupal - Thu, 01/05/2014 - 19:14
Responsive design is hot, real hot. This isn’t new to anyone either, but when developing sometimes you need a little but of help or some assistance from a few modules, libraries or some browser extensions.  Some of the tools I come across quite often seem to be after thoughts, like I need something that I never expected. Say clients putting embed YouTube videos in the ckEditor and they want it responsive. I fixed that with FitVids (https://drupal.org/project/fitvids), which is a very handy, and lightweight jQuery module/library that supports all major video providers.    Always facing challenges making IE8+ websites, and also responsive for everyone else not behind a enterprise firewall or in the dark ages. Media queries help make website scale from 320px iPhone 4 all the way up to 27” 1080p monitor but in IE 8 and down media queries take over and now the website is a huge mobile phone.  No matter what screen size Respond.js (https://github.com/scottjehl/Respond )  to the rescue. Created by Scott Jehl and the Filament Group. Respond.js is a polyfill for min/max-width CSS3 Media Queries that brings your responsive website back in time to work in IE 6 + 8 and also shrinks to your iPhone 4. The trick to get this working in Drupal is to Go to /admin/config/development/performance. Enable Aggregate and compress CSS files. Respond.js only works on <link> tags; it will not work on @import stylesheets. Drupal 7 uses @import when CSS aggregation is disabled, but uses <link> when CSS aggregation is enabled. Duh!! Give it a try then go to your aunt’s house and fire up her 1999 Dell running XP.    The most used responsive tool would have to be responsive frameworks. There are a lot out there but not all work well with Drupal. Bootstrap (https://drupal.org/project/bootstrap ) is great and we’ve used it and tested it and become pretty comfortable with how it works and how we make it work for us. Plus they have a great support community!  Basic (https://drupal.org/project/basic ) is a SASS based grid system using bourbon neat (http://neat.bourbon.io/ ) which is great to use with all the mixins, functions and variables packed up in there.  As the Basic project page says “Basic is perfect if you want a simple, smart, and flexible theme starter.” Which it exactly is.     Responsive Images Community Group (http://responsiveimages.org/ )  ”We’re a group of developers working towards a client-side solution for delivering alternate image data based on device capabilities to prevent wasted bandwidth and optimize display for both screen and print.” Here are some smart guys/girls who are making the Internet a much better place.  They’re pushing picture element and the srcset to the W3C. Here’s more info about the picture element http://picture.responsiveimages.org/ and the srcset http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/ . Before you know it our responsive websites will have responsive images and no more heavy jQuery plugins just good old-fashioned HTML5 and CSS3.    Tags: responsivedrupal planet
Categories: Elsewhere

Joey Hess: who needs whiteboards when you have strange seed pods from the jungle

Planet Debian - Thu, 01/05/2014 - 19:11

Discussing git-annex routing with Vince and Fernao. Might not look like much, but we seem to be close to cracking the most interesting problem with git-annex routing. I need to translate and read Vince's thesis and build some simulations..

(Seed pod, cup, camera = fixed node; mini brick = usb drive; leaves = data.)

Categories: Elsewhere

Blink Reaction: Scaling your team: a practical guide to the value of values

Planet Drupal - Thu, 01/05/2014 - 18:25

With a culture of awesome people that enjoy their work, they can inspire each other to foster and share our values - to become a part of the fabric of how we communicate. So our advice to you as you grow your team - don’t ignore values - don’t create them in a vacuum - build them around your people; nurture them, and let the rest take care of itself.

Categories: Elsewhere

OhTheHugeManatee: Coder vs. Themer Ultimate Grudge Match Smackdown Fight to the Death

Planet Drupal - Thu, 01/05/2014 - 17:15

I’m really excited about a new session that I’ve been doing with my friend and colleague, Adam Juran aka scaragucc: the Coder vs Themer Ultimate Grudge Match Smackdown Fight to the Death! The basic premise: we both start with the same wireframe of a front page to build. But I’m only allowed to use the module layer, and Adam is only allowed to use the theme layer. It’s a really fun and entertaining way to play with the blurry lines between “coder” and “themer”. We get the audience pretty pumped up, which is impressive for a session that’s basically about watching other people code!

If you didn’t catch it at Drupal Dev Days in Szeged, or at Drupalcamp Frankfurt, you’re probably going to have to wait for Drupalcon Amsterdam to take part! But I do have a video of the session at Frankfurt, just to whet your appetite. :)

You can consider this a challenge: if any other themers out there want to challenge me to a coder vs themer style battle, I’ll be keynoting at Drupalcamp Helsinki in a few weeks. I’ll meet you there!

Categories: Elsewhere

John Goerzen: Goodnight

Planet Debian - Thu, 01/05/2014 - 16:25

Me: “Goodnight, Jacob. I love you, and I always will.”

Jacob: *happy sigh* “Goodnight dad. I love you too. But dad, will you love us if you go on a trip?”

Me: “Of course! Even when…”

Jacob, interrupting, and serious: “Dad, you should not take a train trip without me.”

Me: “Jacob, I promise that I will take you on more train trips.”

Jacob: “And Oliver!”

Me: “Oh yes! I promise I will take you and Oliver on more train trips.”

Jacob: Another happy sigh, and a big smile. “Dad, you have to remember your promise forever, OK?”

Me: “Yes, Jacob, I will remember that promise forever. Good night.”

(written January 19, 2013, but somehow forgot to click “publish” back then.)

Categories: Elsewhere

Bluespark Labs: A Beautiful Friendship: How Bluespark and TripAdvisor put relationship best practices to work, and how you can, too.

Planet Drupal - Thu, 01/05/2014 - 11:08

If you’re a consulting company, as Bluespark is--our international team specializes in building beautiful web sites using the Drupal CMS, with an emphasis on powerful user experience and design--you know that excellent work is necessary but not sufficient to achieve a great (or even a good) relationship with your client.

Ultimately, no matter how hard you work, it’s the relationship that will decide whether the project is a success -- or, more to the point, whether your client believes it was a success.

You’re probably already an expert at listening not just to what clients say, but what they don’t say. You’re an accomplished reader of subtext. You work to build trust because if your client isn’t comfortable, you know it’s going to be a lot harder to sell them on your ideas.

You also know that a great relationship doesn’t happen just by chance, and it’s not just because “they don’t question our bills and they pay on time” (though of course that’s something any service company wants).

No, a great relationship is the result of specific acts. And as you might imagine, it’s a two-way street. When it happens, it’s worth looking at what you and your client have done to make it happen.

So we have some ideas for you, whether you’re the client or the vendor.


Become an extension of your client’s team.

People like to talk about this, but it doesn’t happen much. Why? Because vendors have strong ideas about what’s best for their clients. They have experience not only in their client’s industry but most likely in others as well, and they’re more up to date on the best technologies to achieve client goals. They know more (they assume) and so they’re prone to pressing the point on their ideas rather than finding a way to meet clients where they are.

When TripAdvisor, the world’s largest travel site, approached Bluespark looking to improve their existing Wordpress solution for communications with business owners, we felt sure that a Drupal-based solution would best achieve their aims. This was after all a marketing platform with heavy content management requirements reaching a global audience (and they wanted to increase the number of languages supported from 7 to 20).

We weren’t just thinking Drupal because that’s our core platform; we truly believed from the start that it was the best way to go. Nevertheless, we engaged in a comprehensive evaluation with TripAdvisor, providing any information they asked for, and we were willing to talk about Drupal’s limitations in the context of their goals, not just its advantages.

After this process, we jointly agreed that moving to Drupal would provide us with a more flexible framework to meet current and future needs. This wasn’t just performing listening exercises to stroke the client. This was serious work, and in the process we got to know their team, their various concerns, and the way they liked to communicate.

Once we got started on defining the actual project, we were already a tight knit team. We’d earned their trust by being honest. We continued to offer them all the resources they needed.

Be flexible on who does what.

TripAdvisor’s technical team handles implementations concerning the existing TripAdvisor stack, and they also handled the visual design. We brought to the table our UX expertise and the actual Drupal development. We constantly looked for ways to fit what we were doing to their needs.

Be responsive.

This may seem to be a given, but it’s not. One of the most common questions we field when talking with prospective clients, especially ones that have been burned by bad vendor relationships in the past, is, “How fast is your response time?”

Bluespark is an international, distributed team. This presented some challenge in terms of coordinating the regular progress meetings (at least weekly, sometimes more), but it also gave us an advantage--quite simply, we covered more of the clock. Team members in Europe had a head start on the US business day, which came in handy where updates were concerned.

Make your process transparent.

During the project lifecycle, some clients want more of a hands-on role than others. TripAdvisor, with its talented technical and design teams, had the wherewithal and the desire to be deeply involved in everything we worked on together.

So every step of the way, we figured out together how to do the work. We made no assumptions. We  didn’t try to impose our process on them, but we were always willing to talk about how we work and what to expect.

With a project of this scale, even when every player on the team is extremely skilled, coordination and communication is what will ultimately determine success.


Demand the same level of organization from your own team that you expect from your vendor.

Let’s face it, TripAdvisor didn’t get to be the world’s largest travel site by hiring slackers. Their team is at the top of their game. They communicate expectations really well. They are always focused on keeping things on track. They are always, always prepared for meetings. There’s no drama and no one who has to be coddled.

In short, they demand the best--not just from us, but from themselves.

Know who the product owner is.

Do you know what can do the worst to a relationship--and a project? Lack of clarity with respect to who the ultimate decision maker is. Who gets to break the tie? Who bears final responsibility?

TripAdvisor always knows who this person is. After the TripAdvisor designers sign off on the visuals, we have someone who is clearly in charge to take the project from there. They are empowered to make decisions, or they are able to quickly come back to us with an answer.

Opt for a smaller core team.

TripAdvisor is a big company, and the work we’re doing with them reaches a global audience. But the total number of their people with whom we interact on a regular basis is three.

Aside from the designers, there are six or seven others with particular knowledge or expertise that will cycle in and out depending on current project needs.

On our end, it’s the same number--our Chief Technology Officer, Technical Director, and a Senior Developer. Other members of our team are brought in to handle specific pieces of work as needed.

So with two international companies (TripAdvisor being a bit bigger than we are, perhaps!) there is a core group of six people making the decisions and performing the work that reaches millions of people globally.


All this may come off as a love letter of sorts, and we’re OK with that. We love our work, and we love working with TripAdvisor, as well as all our other great clients (expect more love letters in the future).

Our hope is that you can put these ideas to work in your own client or vendor relationships.

Great relationships reinforce what’s best in you and support you in stretching your best even further. TripAdvisor has done that for us, and we like to think we’ve done the same for them.

Tags: Drupal PlanetBest PracticesProject Management
Categories: Elsewhere

Junichi Uekawa: Brainfuck.

Planet Debian - Thu, 01/05/2014 - 10:43
Brainfuck. I've been playing with brainfuck for my holiday project. It seems like an easy enough language to write an interpreter and compiler. So far I've implemented several C++ interpreters and x86_64 assembly, refreshing to read x86_64 ABI documentation to see that it's not quite the same as x86. I thought rax was going to be used as first parameter, but rdi is used instead, hmmm why did I think so.

Categories: Elsewhere

Elena 'valhalla' Grandi: GnuPG Crowdfunding and sticker

Planet Debian - Thu, 01/05/2014 - 10:12
I've just received my laptop sticker from the GnuPG crowdfund: it is of excellent quality, but comes with HOWTO-like detailed instructions to apply it in the proper way.

This strikes me as oddly appropriate.
Categories: Elsewhere

Joseph Bisch: GSoC Welcome Package Received

Planet Debian - Thu, 01/05/2014 - 09:00

A couple days ago I received my welcome package from Google. The welcome package included a pen and a notepad that has stickers.

Since my last update I got the repo setup and started working on the specifications. I have been emailing with my mentors to work out the specs.

You can view the git repo.

To keep up to date on my progress, you can either read this blog, or you can read the soc-corrdination mailing list once coding starts on the 19th.

Categories: Elsewhere

MJ Ray: The Kelly Lessons in About 1555 Characters

Planet Debian - Thu, 01/05/2014 - 06:46

So the Kelly report “of the independent review into the events leading to the Co-operative Bank’s capital shortfall” was published yesterday. During the day, I was putting odd bits from it out in 140 characters with the hashtags #coops #kellylessons. Here they are in one more permanent place. How many of these lessons has your organisation – whether a co-op or not – learned?

  1. “Running a full-service bank… is a complex business… Bank failed to understand the limits of its own capability”
  2. “The most important task for any board is to put in place the right Executive leadership for the business”
  3. “Ownership of a regulated bank…requires a clearly articulated statement addressing…mgmt & gov’nance relationship”
  4. “Failures in board oversight are inevitable if the criteria used to elect… do not require… the necessary skills”
  5. “A bank board must include sufficient numbers of technically competent directors”
  6. “Boards need…good m’gmt info’ and to demand it if it is not forthcoming. Failure to obtain…explains…failings”
  7. “A bank should develop&implement robust risk gov’nce&oversight and an appropriate control framework”
  8. “IT transformation…keep…as simple as poss’, phase delivery.., deploy the right resources, plan for contingencies”
  9. “Bank should have paid closer attention and responded with greater urgency to what the Regulator told it”
  10. “Pay careful attention to the advice of…external advisors. The Group…ignored well-founded…inconvenient advice”
  11. “Postponing dealing with problems is almost never a sustainable solution.”
  12. “Values…need to be translated into meaningful guidance…The Bank’s ethical positioning should be…more apparent”
  13. “Mantras about scale and ethics are no substitute for strategies grounded in a real understanding”
  14. “Talent management is critical… Lack of capability…driven…by weaknesses in its recruitment&subsequent m’gmt”
  15. “Tolerating…culture of underperformance, weak transparency and a lack of accountability, constrains an organisation”

Are there other lessons that you would add?

Categories: Elsewhere

Andrew Pollock: [life] Day 93: A whole lot of running around

Planet Debian - Thu, 01/05/2014 - 06:01

This morning Zoe woke up again at around 4am and ended up in bed with me. I don't even remember why she woke up, and neither does she, but she's assuring me it won't happen tomorrow morning. We'll see.

As a result of the disturbed night's sleep, we had a bit of a slow start to the day. Zoe was happy to go off and watch some TV after she woke up for the day, and that let me have a bit more of a doze before I got up, which made things vaguely better for me.

ABC 4 Kids has been showing a lot of ads for Ha Ha Hairies, which airs at 10:20am, lately, and it's one of the shows that isn't available on iView. Zoe had been lamenting that she never got to see it, and asking me if she could. Today the schedule was fairly open, so I made sure we were home at 10:20am. That involved a quick dash out to Woolies first to get a few bits and pieces for Zoe's birthday party.

While Zoe watched the Ha Ha Hairies, I did some bulk egg hard boiling in the oven. After the Ha Ha Hairies and a little bit of general mucking around, we drove out to Spotlight to pick up the helium tank I'd rented. Zoe nearly fell asleep on the way out there.

We picked up the helium tank and headed back home. That errand alone probably took a bit over an hour all up. We got back home and had lunch, but by the time all of that was out of the way, Zoe seemed to have missed the window for her nap. She did have a bit of a rest in bed, flipping through her library books, and I got to read some of my book as well, so that was nice. During that time, I got the call from Bunkers saying they were about half an hour out with the delivery of Zoe's bunk bed (my birthday present for her). That worked out well, as it was towards the start of the two hour window they'd advised me of.

The bunk bed was delivered and then we popped out to Overflow to see if they had any food covers for the party food (they did) so we picked up a few of them. Today I learned that "As Seen On TV" is trademarked, and so "Similar To As Seen On TV" is the trademark dodging thing to put on cheap knock-offs. As Overflow is two doors down from Petbarn, we stopped in there as well and grabbed some more kitty litter. One does not just pop into Petbarn with Zoe, so we spent some time there looking at the fish and assorting aquarium paraphernalia. They also had some hermit crabs now too.

On the way back home, we stopped in at (a different) Woolies to pick up the half slab of chocolate mudcake that I'd ordered for Zoe's birthday cake. I'd decided that the upright Minion cake I'd initially wanted to do was just way too adventurous for my abilities and not a good use of my time (and the quotes I'd sought for outsourcing it had come in at over $300). I scaled things back to just a flat slab Minion, which may still exceed my cake decorating abilities, but we'll find out tomorrow.

There'd been a miscommunication at Woolworths, and my half slab hadn't been boxed up and wasn't ready for my collection. All the bakery staff had already gone home, and I didn't really want to come back tomorrow, because I had this crazy idea of possibly starting on the cake tonight (not going to happen), so a couple of non-bakery staff had to find the cake and figure out how to extract a full slab from the baking tray and cut it in half and box it up. It provided some entertainment for Zoe and I.

We finally got home, and I rehashed some frozen leftovers for dinner. I decided to try something different for the bath time and bed time routine to see if it'd reduce procrastination. I got Zoe to pick out the three books she wanted to read at bed time before we got to story time, so we'd have something concrete to negotiate with. I also threw in the possibility of a "bonus story" if she didn't muck around. It seemed to work, and we had a fairly streamlined bath time. There's no doubt she was pretty tired today, and she went to bed without any fuss, so I'm hopeful that we'll have a good night tonight.

Categories: Elsewhere

Achieve Internet Blog: A Drupal Developers Guide to Responsive Web Design

Planet Drupal - Thu, 01/05/2014 - 05:36
The Achieve Internet Standard for RWD
Categories: Elsewhere

C.J. Adams-Collier: I think perhaps they mean “could join x86 in the server room”

Planet Debian - Thu, 01/05/2014 - 02:13

As much as I love PowerPC, and as great as it is that they’re doing this OpenPower thing, I don’t think that the first step should be to eliminate the competition. Perhaps they should put some effort in to taking back a large part of the market. Didn’t these guys read The Art of War?

The OpenPower Foundation, and how IBM and friends could oust x86 from the server room

I’d certainly take a look at a server if they sent me one; it looks like Debian still supports powerpc arch on wheezy. ;-)

Categories: Elsewhere


Subscribe to jfhovinne aggregator - Elsewhere