yo-bj/how_to_c4l.md

## how_to_c4l.md

      
    Raw
  

              how_to_c4l.md
            
          
    how to code4lib v 2.0


v 1.0 "How to hack code4lib" by Declan Fleming, Director of IT, UCSD Libraries (BigD in channel), heavily edited by the community
v 2.0 sources: v 1.0 from Code4Lib; "Social Rules" and "Programmer Community Issues" from Write The Docs

Working draft for consideration by the community. This will eventually be placed in a pull request in the CodeOfConduct4Lib [CoC4Lib] repository. ~yo_bj
[todo - table of contents?]
Join the #code4lib Slack and IRC channels (Or get to the #code4lib IRC channel (and other discussions) via Slack) and listen for a while

The community back channel  is the most invaluable tool available to help you quickly get the feel for the community. As with any online forum, the level of discourse on in some of the channels is very similar to how a group of work friends would be talking in a relaxed office environment. The topics range from jokes about bacon and XML to esoteric explorations of the RDF expression of specific pieces of metadata. During conferences and meetings, the channels are also very useful for finding out where groups are going for lunch or dinner. You can find more information about IRC and Slack and how to get on it via the IRC and Slack pages on the main Code4Lib site.
Listen 90% of the time / Talk 10% of the time

code4lib is filled with folks who are passionate about some aspect of our profession. If you don't have a lot to share, don't worry! Ask a question or two then sit back and bask in the output. Don't worry, you'll have the chance to talk about what you are working on when your companion stops to take a break. Aim for participating when you can be constructive - just because you can make a comment, doesn’t mean you should. Try and be constructive in all that you do.
Don't be sexist/racist/*ist AKA follow the CodeOfConduct4Lib [CoC4Lib]

We are in a very interesting niche of the technology world. Librarianship is traditionally a female dominated profession, but library technology tends to be more white and cis-male. We have a wonderful opportunity to attract and promote equity in our part of the field and there's no reason to make an underrepresented group feel unwanted just to get a couple laughs from a joke - you know that you’re joking, but some people might take you seriously. Sarcasm and snark might be acceptable in more intimate group settings, but in public spaces those comments can be viewed as malicious or hurtful to those who are targeted by such comments.
If you encounter a questionable comment in the channels, you might ask the speaker to explain the comment, or if you uncomfortable asking or was the target of behavior that might violate the CoC4Lib:

IRC: the zoia command to list people designated as channel helpers is @helpers . There is at least one helper in the channel at most times.
Slack: [todo - reporting contact information]
Listserv: Contact list maintainer Eric Lease Morgan

If nothing else, follow the 90%/10% section above when in doubt.
Talking shop, the welcoming way

Library technology is not immune to various quirks of the general technology communities, and that includes talking about the tools that folks use on a daily basis. There is a lot of cross-over between our communities, so how do we make sure that we don’t fall into these same traps?

No Black Sheep - There may be tools that you don’t like. There is a good chance there is someone in the room who either helped create or likes to use that tool. Don’t make them feel bad, they are likely just in a different context.
Let Me Google That For You (LMGTFY) or Read The Friendly Manual (RTFM) - If people ask questions that are simple to answer on Google or in documenation, still answer them nicely.
Question Policing - Some people might ask incomplete questions that are hard to answer. Ask follow up questions and act in good faith to help them solve their issues.
My Tool Is Better Than Yours! - We don’t care if your tool is faster or better in some metric. Stealing from the Five Laws of Library Science, each tool their user, and each user their tool.

One group that gets a lot of attention in the channels is vendors. There's a healthy debate that comes and goes in the channels about whether it's good to have a place to vent, or if said venting limits their interaction in the community. One of the great strengths of the channels is that the norms are constantly in flux and openly discussed and debated.
Don't be intimidated by what looks like the "in crowd"

There is no in crowd. There are people who jump in and participate - both to the conversation and the ongoing work involved in promoting and supporting code4lib. You'll see them as the center of things until you actually get involved - a little at first to learn the social norms of the group, then more and more until you realize that new people are seeing you as part of the "in crowd." Now your job is to make the new people feel included.
Be ready to learn new stuff constantly

Listen to others' passions and see if any of it strikes a chord in you. There are times when you're listening to a presentation, or lurking in the various channels, and finding yourself searching for anything related to that topic to read up on later. You'll be doing a lot of this in the community, be it your first time in the channels or your tenth year in the community. We are always learning and always sharing what we learned with others.
Share your passion
[A testimonial from Declan, author of v 1.0] I never thought I'd stick around in libraries that long. I'm an IT professional, not a librarian. But I tell ya, being in this crowd for very long infects you with the depth and longevity of the problems that need to be addressed. Supporting a profession that has such a long tradition, and helping to bring it into the present and future is more satisfying than I ever thought possible. I have a passion for linked data and making things talk to other things in easy ways. I've shared this a few times in bar conversations and formal talks. Nothing got people talking to me more than this.
Attend your local or regional code4lib meeting

Chances are that you live relatively close to a local or regional code4lib group. These meetings are great places to get a taste of the code4lib community in the real world. Local and regional meetings are also great places to present and share your work and passions to a welcoming, interested audience. Finding like-minded folks in the area makes all the difference in feeling like part of a larger community.
Attend the annual code4lib conference

Of course attending an annual conference is a surefire way in getting immersed in the community. A few tips to help you navigate the whirlwind so you can do what you need to do to get the most out of the conference!

There will be things that go over your head. This is normal. This happens to everyone. No one is an expert in everything, so don't worry that you don't know every single thing that is mentioned in the presentations. You might feel guilty for spending work money and not understanding every presentation, breakout session, preconference workshop, etc. etc. etc. that you attend. The backchannels can compliment your experience by providing needed context or background information about the topic, as well as providing opportunities to explore a topic further.
You might have heard of the term "hallway track" in some conferences. The talks and sessions at code4lib lead to impromptu breakout sessions in the conference lobby, or in nearby pubs and restaurants. It's not uncommon for folks to start working on a project with a tool they just learned about at the conference, and have something up and running to show folks at a lightning talk the next day.
Take breaks. There will be A LOT of information thrown at you in a short period of time. You will be mentally exhausted before conference end. If you need to take a break, do so. Decompress outside the conference room, use the quiet room, or try a #nap4lib!

Come join us, wherever we are!

There are lots of places where things are happening, allowing you to choose the mediums of engagement you are most comfortable with and interested in. The main Code4Lib website has a lot of these places, including our listserv, Google Group, Slack, IRC, RSS Feeds of various library technology blogs, jobs site - and that's just only the list on the website. New Code4Lib places are popping up online and in the real world via new regional and local groups, so there are many opportunities for you to join us. Of course, if you don't see something in the community - a space on a new social media platform, or a local or regional group - go forth and create it! Just remember that all code4lib spaces - online and physical - are covered under the CoC4Lib.