To login to Connect now, click "Login" in upper right.
There is currently 1 user online.
A big happy welcome to the 33 of you who have joined so far!
So: we've reserved meeting space at 1:30-3:30 on Saturday at Annual. What do you think we should do with it?
My first thoughts for topics are:
We probably wouldn't have time to get into all of these, but thoughts? Priorities? Discuss amongst yourselves.
I would very much like to talk about what we've accomplished, so far, and what we're getting out of the program.
In addition to that, though, perhaps we should meet and do some serious talking about what we're going to do NEXT year?
What does this IG look like, past the end of 2012? I'd love to talk about that.
I second that emotion, as the song goes! Let's definitely talk about keeping the momentum going, especially as some of us (cough, me, cough) might not get through all the code year lessons by the end of 2012. And I doubt they remove the lessons now that they're existing and online.
Yes. This. And everything else Marliese and Coral said. :)
I second Marlise on sharing what we have done with our new Code A Year skills in our libraries. It's too early for me to tell how I might be able to apply this locally.
Erica Findley, MLS www.ericafindley.com
I would also be very interested to hear whether any libraries are working with patrons who are participating in Code Year (i.e., providing space for a meetup group, organizing sessions for participants, providing supplemental classes, etc.) and, if so, whether that has been successful.
So looking at this, I see three basic possibilities emerging:
1) Talk about what people have been doing with code. This could be a lot of things: ways you've been applying code in your work life, ways your library has been working with CodeYear, things you've learned while learning code, etc. Maybe we could get a range of perspectives by getting a half-dozen people or so to do some Ignite-style talks?
2) Brainstorming session on what we want the group to be doing after Annual.
3) Hackathon/time to work on lessons, catch up, mentor, etc.
I think in a 2-hour slot we have time for at most 2 of these, and my preference would be the first 2. But I've also been thinking it would be really fun to have some Google Hangouts or similar before Annual to do some focused conversations and keep the momentum going. We could totally use those to check in/work on CodeYear lessons. Could also use them to talk about how we're using code in our lines of work (I could demo some of my jquery, e.g.), tools we've found for learning, et cetera.
LITA Board of Directors, 2013-2016http://andromedayelton.com@ThatAndromeda
#3 also sounds nice but I don't know, an unstructured hackfest might not go anywhere. Perhaps if we could agree upon some projects beforehand that would help?
California College of the Arts
Several years ago (2007?!) at EMA (the Endeavor Mid-Atlantic Users Group meeting) we had an almost completely unstrucured hackfest.
I came in with the desire to hack a way to be able to one-click add item records to del.icio.us - nobody else had any burning desires about this, so we hacked a way around teh systems constraints and made it happen. See: "Tag Item (Beta)" in this catalog record.
Long story short, if someone has a burning desire to buiild something specific a hackfest is a great collaborative effort.
"Always remember everyone is working to make the organization better in their own way." -Eli Mina, ALA Parliamentarian