Becoming a Drupal Core Mentor

t's finally time to start doing something I should have done long ago: mentoring new core contributors! I've spent a small chunk of time as a mentee, setting up my own development environment (dev env), finding issues in the mentoring queue and on Drupal.org (d.o), and interacting with other core contributors. While writing documentation and doing rerolls has been a great way to learn Drupal, the real rewards have come from working with other contributors. It's been a great comfort to know that I can ask for help on IRC, and can always find a mentor online during the core mentoring office hours.

And the bonus is that teaching others is the best way (for me) to learn things! So I went to YesCT for some advice on where to start. Here are a few resources she pointed me to (in addition to this big page o' mentor resources):

First of all, the most important thing to remember for everyone in the Drupal community is that "we are all mentors." This blog post from YesCT is pretty much what I was trying to say in para #1, but she says it better. Being friendly is the best way to encourage new contributors to come back! See also: WebChick's comic about her first encounter on IRC with "the Drupal Community on a Bad Day."

Next we have a key component of being a mentor: reviewing new contributor's work. This requires knowing how to review the contributor's work, and how to review a patch itself (to check that it was done correctly). Sticking with the theme of constructive criticism, gentle reminders, helpful pointers and other supportive input here. Teaching contributors how to interact and communicate with others is a great way to keep everyone positive and engaged.

As a side project, I'd like to help update dm.o and d.o to merge issue task instructions with the regular issue queue, essentially add functionality to the d.o issue queue. Todo for me: read through these related core mentoring on d.o issues. I had just recently noted that having contributor task instructions linked on d.o as they are on dm.o would be much easier than googling them every time I start work on a new issue. Turns out there's an issue for that! (there's also a google doc I won't link to here, but, note to self...)

Then we've got resources for planning a sprint, which I'd really like to do at a Drupalcon in the near future, but am currently lacking a topic to sprint on. If anyone needs a sprint co-leader, I'm happy to help!

Part of sprinting of contributing is going to be getting everyone set up with a local environment to work with. At an event like Drupalcon, or even something on a smaller scale, this can become problematic if everyone is downloading new software etc at the same time. So here are the Drupal Community Tools Download Instructions (dctdi. Tech is almost as bad as gov't with the acronyms). We've also got an Austin specific Core Mentoring page here and of course the perennial dev env setup page here.

Phew. So far I've had a look at most of those pages, but I need to go back and read the issues for dm.o->d.o as well as go through the mentor resources links thoroughly. It's just really great to have a specific goal and project to work on! I enjoy contributing on issues, but with the current D8 beta push it's been hard to find anywhere I fit in lately. Tallyho.

Drupalcon Prague notes

s one might expect, my lofty goal of watching the 20 or so DrupalCon Prague sessions I would have attended in person didn't quite work out... But here are some brief notes on the sessions I've looked at so far:


Frontend development; dancing on the tip of a hurtling rocket

This is almost verbatim why I wanted to be a librarian, and how I came to web development: "What we do as developers is provide content and provide access to that content. That is essentially the value we provide as professionals: There's information out there; we're making it possible for individuals out in the world to get to that content." -Jesse Beach

It's fascinating to think about how accessibility goals can be translated into more general applications later on. With proper DOM semantics and metadata the entire web could be twice as useful and useable.

From Not-Invented-Here to Proudly-Found-Elsewhere: A Drupal 8 Story
Alex Pott- This was marked beginner! I get the general gist, but the code examples were a bit over my head. Recommended reading on PHP- good, something helpful, recommended, up to date.

Drush Optimizations for Your Development Workflow & Drush- Do I Really Have To Use It?
Two sessions on Drush from Prague- One was all about convincing people to use Drush (already there, though not entirely clear on how it actually works with a drupal site... should, again, read the basic docs), and the other was adding Drush functionality to your contrib modules (so too advanced). Had I been in Prague, the "Getting Drush Installed" BOF would have been perfect.

Lisa Welchman Keynote: The Paradox of Open Growth
"Governance is about stewardship. It's about taking care of something." "It seems like it's really just for people who are developers. You could be more inclusive and welcoming" (slight paraphrase). Given that I know people try really hard with mentoring and so on, that seems unfortunate.

And then she brings up shape-note music as a standards practice! Crazy cross-over with my singing experience and hearing from my friend Lynn recently that she had just adapted (with her group) a traditional Chinese piece into shape note.

TBC...

Mobile:Library:Toy:CIL2010

I... am a lazy, lazy blogger.

Back in early April, I attended* the Computers in Libraries conference in Crystal City, took extensive notes, and then sat on them for the last few weeks. (Bad blogger, no cookie.) So, now that we've all had sufficient time to process, here's a quick run through of my thoughts from those two days.

CIL2010 was my first conference of any kind, and I admit that I was a bit starry eyed and excited about the whole business. I did not, however, feel out of the loop during the sessions, or as if I didn't fit in with the crowd (although the librarians who have been to a lot of these are a bit clique-ish). There were more sessions than I could manage to attend all at once (where's a time-turner when I need it?), but I got to one in every time block while I was there. In all honesty, the subject matter was a bit disappointing. I was hoping for more cutting edge stuff I'd never heard about, and instead I got... "cool blue alien hot stuff" and way too much hype about smartphones and ipads. In some ways, the conference solidified my desire to be some sort of special or academic librarian, not a public librarian. I'll try to reserve judgment on a lot of the conference on the grounds that it was my first and I don't know the presenters or the insider drama very well.

On to my notes!

The first session I went to was a presentation of a fancy, interactive, online, visual collection exploration application that was entirely fake. The Smithsonian Commons is this big idea for a way to get visitors into the collections from outside the physical museum, allowing them to develop personal collections and so on. But it's only a prototype! It's a huge project, oodles of effort and money spent on something that doesn't exist. Argh. Plus I disagree with the concept of an online version of the collection in the first place, but I'm just kind of elitist about museums and keeping things proper.

Which brings me to a question I had a lot: do people really want all this change, all this web 2.0, ebooks, mobile devices... or do they want Classic Library? It's certainly true that librarians are a bunch of geeks, and think that all this 2.0 stuff could be useful/cool/blue, but are they also forcing it down people's throats? I heard a lot about how books are dead. Well guys, personally, I can't afford a smartphone, or an ipad, I dislike reading on a screen, and I love collecting hard copies on my shelves. I'm not the only one (even if I can't find a supporting study right this second).

The counter argument is that librarians are "complacent," and are saying "we're great, why change?"

I also made long lists of things to research and understand better in the future: Drupal and OCLC, par example. I signed up for Google Analytics right away, and now I can collect ridiculous amounts of data on traffic to this very website. I'm a sucker for pretty charts and information visualizations, especially if it live-updates! Watson Library created a spiffy "dashboard" that does this kind of thing. Another neat tool I heard mentioned was the Google Public Data Explorer. (Further exploration and maybe a post on the Google tools later).

I just realised that this post will be epically long and dull if I don't cut it into bits. Consider this Part I.

*It should be noted that a very kind co-worker/mentor loaned me his conference pass for two of the three days, for which I am very grateful.

Classic library image from Trinity College Library, Dublin, by Candida Hofer.

Modern library image from Francis Martin Library, a branch of the NYPL. Design by 1100 Architect.

ps. Some of the random links in this are well-worth clicking...

EDIT/PPS: at some point the formatting got all screwy on some of my archived posts. Sorry about that, maybe I'll fix it all in the future... [9.7.2012]