Meet Your Developer: Will Panting

A Meet Your Developer double feature this week, as we introduce another instructor for the upcoming Islandora Conference: Will Panting. A Programmer/Analyst at discoverygarden, Inc., Will is a key member of the Committers Group and of one of the most stalwart defenders of best practices and backwards compatibility in Islandora. If you adopt a brand new module and it doesn't break anything, you may well have Will to thank.

Please tell us a little about yourself. What do you do when you’re not at work?

I went to UPEI and have a major in Comp Sci and a minor in Business. Before DGI I had a short stint at the University. As well as all the normal things like friends and family I spend my spare time developing some personal projects and brewing beer. I've been trying to get my brown recipe right for years now.

How long have you been working with Islandora? How did you get started?

More than four years that I've been with DGI. I had heard about the company through UPEI. I find working on Islandora very rewarding; I think this space is of some very real value.

Sum up your area of expertise in three words:

Complete Islandora Stack

What are you working on right now?

A complex migration from a custom application. It's a good one, using most of the techniques we've had to in the past.

What contribution to Islandora are you most proud of?

I've been in about just every corner of the code base and written tons of peripheral modules and customizations. I think the thing that I'm most proud of isn't a thing, but a consistent push for sustainable practice.

What new feature or improvement would you most like to see?

I'm divided between a viewer framework, an XSLT management component or the generic graph traversal hooks. All basic technology that would create greater consistency and speed development.

What’s the one tool/software/resource you cannot live without?

Box provisioning; absolutely crucial to our rate of development.

If you could leave the community with one message from reading this interview, what would it be?

Commit. Dive deep in the code, let it cut you up then stitch the wounds and do it again. It's great to see new committers.