You are here

Drupal

An amazing year as part of Montréal's software community

As 2011 wraps up I look back in awe at all that has changed. A year ago I moved my business from Vancouver to Montréal and things have been steadily changing since I arrived. Really good things. When I arrived last year I knew only a few people in Montréal. One thing Montréal is great for is meetups. There are tons of software meetups, every night of the week! So I put my hiking shoes on and started going to a lot of events.

I took to the streets

For awhile I got involved with DevLab and for a few weeks I did Blitzweekend events. The former was great French practice for me, I learned all about git, and then I took that knowledge to Blitzweekend where I coded my first code release Drupal projects. Then I became an approved maintainer on Drupal.org. Progress!

I also connected with Montréal's Drupal association. The association has grown over the years and 2011 marks the start of the group as a registered society under Québec's non-profit system. We also planned out a Drupal Camp (and I learned a lot - not having done this sort of thing before). Some of us are discussing running an "actual camping" event in the summer. Would you like to help? Let me know.

A new company was born

This was also the year that I channeled all of this good energy into rebranding my company. From 2008-2010 I had run under the name "Granola Systems" which was registered in British Columbia. It is a suitably apt name for a company out west, but doesn't carry the same meaning in eastern North America. For much of 2011 I reverted back to billing as Ryan Weal until our incorporation documents were complete.

In the fourth quarter of 2011 I officially relaunched as Kafei Interactive Inc. / Kafei Interactif Inc. We're registered nationally, so as long as we're based in Canada we will always have the same name. In case you're wondering, kāfēi is how you say the word "coffee" ( 咖啡 ) in Chinese. We drink a lot of coffee at our studio.

We scaled up a bit

As I launched Kafei Interactive, the new business opened up to include many more people in our production process. It was really a huge step up that has been needing to happen for awhile.

This year we brought in many more people to our nimble shop. We had one person loading content on a couple projects, a translator, at least three types of designers, a database guru, a support guy. The list goes on. In total, there are probably about ten different people we work with now.

New invoicing system

To handle the increased capacity this year we opted for a new banking and invoicing arrangement. We now invoice with our time tracking system and clients can pay online. For clients who pay by credit card, you can now collect travel points with your card. We also started accepting Interac e-Transfers.

These changes reduced the number of trips to the bank and also has the advantage of taking the post man out of the equation for collecting payments. Canada Post was on strike for a few months this year. It was a frustrating experience.

We also began a new effort to quote more accurately on our projects. This one is tough, and it has certainly taken a bite from our paycheques in the past. Estimating software is hard to do is a pretty accurate statement. In the new year we will be linking our work orders with our invoices so clients will have a complete overview of all account activities.

Lastly on the infrastructure front, we maintained a brick and mortar office for most of the year. Though looking back it seems counter to all of the "virtualization" of our business practices. At the end of the year we decided to consolidate our shared apartment situation and our office into one private studio in the heart of Montréal. We're now located in central Villeray!

Our business has changed

This one was planned but it is always interesting to see how it plays out in real life. We took on a lot more coding this year. In fact, most of what we do now is strictly programming.

We also do brochure websites, theming, and internationalization of websites.

That is a pretty wide variety of stuff, which is why we use a narrow set of tools to get things done. The coding stuff is really enjoyable and we hope to be doing more and more of it in the future.

The great give

While taking on additional coding projects we started to release our work on drupal.org. This week I finally published a variety of modules which have been in development at different points in the year.

Unfortunately our module work has been focused on Drupal 6 because that is the API we were really "steeped" in and it had the body of supporting modules we needed for our clients. We plan on releasing D7 versions of anything we post on drupal.org, but much of it will come in the new year.

What's next for Kafei Interactive

The new year is all about Drupal 7 for us. We're full time coders, so if there is anything lacking in D7 we're equipped to take on those little bits and pieces. While we're at it we're going to push ourselves closer to the current development of Drupal... that is to say, we're also going to be chasing Drupal 8 but we will be using Drupal 7 for all projects until it is declared stable and meets our needs.

Category: 

Announcing Kafei Interactive Inc.

Today I am pleased to announce the formation of my new company, Kafei Interactive Inc.. The new company continues the work that I was doing as Granola Systems (BC) and takes on some of my work for Groupe Rutagi (NS/QC). I look forward to continuing my work with the Drupal community under this new banner from my new office in Montréal.

Category: 

So many ways to lose your domain at 1&1

This posting will hopefully serve some people well in the future. I have had a very frustrating time with 1&1 and I wish to share my story.

There are countless stories out there that are like this. You can find them in threads around the Internet.

My client started their web presence with 1&1 Internet, a cheap hosting provider that lures buyers in with a free year of domain registration.

When we migrated my client's site to a new host the troubles began. When it came time to renew the domain we approached things a few days early just in case there were any hassles.

Our initial plan was to transfer registrars. We settled on a one year renewal.

When we logged in to the account, however, nothing was there. During our transfer we had the hosting account closed and that took the domain registration account away with it.

We asked 1&1 to reactivate the account so we could manage the domain. We were willing to pay the extra year with 1&1 to do an update, that was a non issue.

Then the first cost hit us: $X reactivate the account because apparently we were behind payment (curiously, no notification about this prior).

Things take a long time in the queue though, so in that time that things were processing 1&1 let our domain registration lapse. So now the domain was in the redemption period.

Not their fault apparently.

Second cost: fee from redemption $X. Wtf, we had contacted them days before the domain was set to expire.

That goes on awhile and finally the domain is reactivated. 1&1 had setup a new account to provision us and somehow wired the domain up manually. Everything seems fine.

Days later a DNS update is made but we are not made aware of the change.

About a month later we received letters from 1&1 notifying us that the account was in arrears. Again? Didn't we like *just* pay 2x that fee to renew and redeem ourselves from their domain lapse?

Months go by and everything is fine. We gave up on dealing with 1&1 to transfer the domain. We figured since we renewed with them let's not rock the boat. It was such a hassle going through the previous issues I did not want to do it again.

As far as I know the disputed payment issue had been resolved (I spoke to billing first assuming such, but they quickly pointed me to tech support). I'll probably touch base with my client on this when we debrief.

So here we are with a functioning, renewed domain. Then out of the blue I get this webform request.

I thought it was a scam:

Web developer writes to let me know that our domain is listed in HIS 1&1 domain account and wants it out of there ASAP. Does not want to pay for it.

Says he contacted my client (no response). I'm thinking total scam. Then I run a whois. Sure enough, he owns it. I login to my client's account and sure enough it is missing.

Initially I responded to the developer to try to get an idea of what was going on with the file and he very clearly stated he just wanted it gone. I reassured him we had just renewed it so one would assume he's not incurring any charges on the account.

So here we are with an empty domain name management account and a pissed off guy that doesn't want our domain. Who is this guy? None of us know. He just wants us to have it back.

Still feels like a scam though.

We thought the logical thing to do would be to let 1&1 know about the issue. I wrote them a support ticket and neither myself nor my client received any response. I let this simmer for a bit as I was busy with another project and obviously in for a very complicated discussion.

I finally call their support desk and try to explain the situation. This was a closed-then-reactivated account and somehow provisioning (re)allocated our file to someone else.

It should be obvious. They have support records documenting all of what went on above. The domain was renewed by us just months prior.

The domain records have been set to LOCKED just as it was at the start of our issue. In other words, the *whole* time.

How did the domain get transfered then?

How?

If this person had acquired the domain on purpose, why does it still point to us? Why did they contact us?

It should be obvious that they re-provisioned our domain to someone else.

What does 1&1 say?

Why don't you give that guy a call and work it out.

I sent the guy an email to let him know we've made no progress with 1&1 and provided instructions on unlocking the domain so that we can begin the transfer process.

That guy seems to be offline. Great.

I went to internic and filed my first complaint ever. It said there was already a complaint against our domain after my first attempt would not validate. Hours later I realized that the other developer may be in the middle of a complaint process also. We shall hopefully find out soon.

First Drupal code release - Node Tasklist

Yesterday marks my first public foray into developing contrib modules for the Drupal project. I applied for project maintainer status for my new module, Node Tasklist.

From the description of the project:

Each time you visit the page or block created by this module you are presented with the edit form of the most recent node of that content type. When you save your changes, you are returned to the same page so you can perform another update to the node.

Read the description of Node Tasklist in my Drupal.org sandbox.

I made a demo of the module at the end of Montréal's Blitzweekend, where I put the final touches on the code.  You can see the module in action here: http://weal.ca/tl/blitz

I really love doing work that has a time component.  I have in the past written shell scripts and scheduling systems.  I also have a time tracker I developed in-house with Drupal and much more.  I hope to release all three of those as community projects once the Node Tasklist module is fully polished.

Pages