Code4Lib - User contributions [en]

2019 Keynote Speakers Nominations

2018-10-04T15:05:18Z

ShiraPeltzman: Nominated Mark Matienzo

Nominations for invited speakers/keynotes for Code4Lib 2019 in San José, CA will run until '''October 22, 2018'''.

Please include a description and any relevant links and try to keep the list in alphabetical order.

The criteria for nominating a candidate to act as keynote are below:
*Speaker’s name (First Name, Last Name)
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information of candidate (email address)

''We strongly encourage you to nominate speakers who are local to the San José area.''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

[[Link(s) with contact information for nominee]]

</pre>

__TOC__

==Jane Doe (example)==

Jane works at ________, doing _______.

Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.

==Tara Robertson ==

Tara works at Mozilla as the Diversity & Inclusion Strategic Partner. She is tasked with ensuring one of the darlings of the technology industry to be more inclusive, diverse and open. Tara has been championing open communities, open source, open access, and open education prior to her affiliation with Mozilla for over a decade. As the Code4lib community continues to wrestle with these very issues, it is a timely opportunity to invite her to speak to us since we are on the left coast this year.

More on [https://tararobertson.ca Tara].

[https://tararobertson.ca/2016/lita-keynote/ Not all information wants to be free,] LITA Closing Keynote, 2016.

==Mark Matienzo==

Mark works at Stanford as the Collaboration & Interoperability Architect for Digital Library Systems and Services.

Mark has worked at the intersection of technology, libraries, and systems for over a decade, serving as a technologist, advocate, and facilitator for cross-institutional projects. Prior to joining Stanford, Mark worked as an archivist, technologist, and strategist specializing in born-digital materials and metadata management, at institutions including the Digital Public Library of America, Yale University Library, The New York Public Library, and the American Institute of Physics. Mark would be an excellent keynote speaker because his long track record of involvement in cross-disciplinary and intra-institutional initiatives has given him a unique exposure to projects that touch on all aspects of library systems and tools. In addition, he is an outspoken advocate on a wide range of issues including labor, the environment, and leadership in libraries.

More on [https://matienzo.org/ Mark].

[[Category:Code4Lib2019]]

[[Category:Code4Lib2019]]

2017 Code4Lib T-Shirt Design Competition

2016-10-14T19:15:56Z

ShiraPeltzman: Moved the deadline text farther down

Starting Monday October 17th, 2016, we are issuing a month-long open call for a logo design that will be featured on the front of the Code4Lib 2017 Conference t-shirt. The winning logo will be based on a popular vote, which will commence after the submission process closes.

'''DESIGNS ARE DUE BY FRIDAY, NOVEMBER 18, 2016 at 5 PM Pacific Standard Time'''

Please submit your high-quality image to the [[#Submissions|Submissions]] section of this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. Be sure to include your name and email address!

== Details ==

* Along with your image, name, and email address, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design when voting begins.
* Place a horizontal rule (----) on a separate line after your submission.
* Original art only, please!
* The screen-printers generally need vector art files (ai, .cdr, .eps & .pdf). If you need help converting your design to one of these file formats, email Shira.

The t-shirt color will (probably) be black, but we can look into changing the color depending on the design that is ultimately selected. If the winning design's assumed color is something other than the traditional black, we will try to get the t-shirts in the requested color. If that color is not feasible, the logo will default to white or gray, depending on the requested design contrast, on a black t-shirt.

(Please stick to a color scheme that folks who are colorblind will be able to see.)

==Sample Submission==
Joe Ouroboros, joe@loopback.edu :

[[Image:Reset-200.png]]

This is my awesome design. It'll win one of these years.
-----
Not sure how to submit your image? Check out https://www.mediawiki.org/wiki/Help:Editing_pages for more information about editing a page! Here's a template for what the wikitext should look like when you submit your image:
Name, email address :
<nowiki>[[Image:Name of image file you uploaded]]</nowiki>
Explanatory text
<nowiki>-----</nowiki>
== Submissions ==

2017 Code4Lib T-Shirt Design Competition

2016-10-14T17:51:37Z

ShiraPeltzman: Reformatted/reorganized Details section and intro

Starting Monday October 17th, 2016, we are issuing a month-long open call for a logo design that will be featured on the front of the Code4Lib 2017 Conference t-shirt. The winning logo will be based on a popular vote, which will commence after the submission process closes.

Please submit your high-quality image to the [[#Submissions|Submissions]] section of this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. Be sure to include your name and email address!

'''DESIGNS ARE DUE BY FRIDAY, NOVEMBER 18, 2016 at 5 PM Pacific Standard Time'''

== Details ==

* Along with your image, name, and email address, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design when voting begins.
* Place a horizontal rule (----) on a separate line after your submission.
* Original art only, please!
* The screen-printers generally need vector art files (ai, .cdr, .eps & .pdf). If you need help converting your design to one of these file formats, email Shira.

The t-shirt color will (probably) be black, but we can look into changing the color depending on the design that is ultimately selected. If the winning design's assumed color is something other than the traditional black, we will try to get the t-shirts in the requested color. If that color is not feasible, the logo will default to white or gray, depending on the requested design contrast, on a black t-shirt.

(Please stick to a color scheme that folks who are colorblind will be able to see.)

==Sample Submission==
Joe Ouroboros, joe@loopback.edu :

[[Image:Reset-200.png]]

This is my awesome design. It'll win one of these years.
-----
Not sure how to submit your image? Check out https://www.mediawiki.org/wiki/Help:Editing_pages for more information about editing a page! Here's a template for what the wikitext should look like when you submit your image:
Name, email address :
<nowiki>[[Image:Name of image file you uploaded]]</nowiki>
Explanatory text
<nowiki>-----</nowiki>
== Submissions ==

2017 Code4Lib T-Shirt Design Competition

2016-10-14T17:11:06Z

ShiraPeltzman:

It’s that time of year again… the annual 2017 Code4Lib t-shirt logo design competition! For those who are new or for those who need a refresher, here’s how it works: starting Monday October 17th, 2016, we are issuing a month-long open call for a logo design that will be featured on the front of the Code4Lib 2017 Conference t-shirt. The winning logo will be based on a popular vote, which will commence after the submission process closes.

== Details ==

'''DESIGNS ARE DUE BY FRIDAY, NOVEMBER 18, 2016 at 5 PM Pacific Standard Time'''

Please submit your high-quality image to the [[#Submissions|Submissions]] section of this wiki page:

* Post an image file of your print-ready proposal by editing this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. If your print-ready document is different from your displayed image, include a link to the print-ready file.
* Include your name and email address with your proposal.
* If you want, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design when voting begins.
* Place a horizontal rule (----) on a separate line after your submission.
* Original art only, please!
* The screen-printers generally need vector art files (ai, .cdr, .eps & .pdf). If you need help converting your design to one of these file formats, email Shira.

The t-shirt color will (probably) be black, but we can look into changing the assumed t-shirt color depending on the design that is ultimately selected. If the assumed color of the winning design is something other than the traditional black, we will try to get the t-shirts in the requested color. If that color is not feasible, the logo will default to white or gray, depending on the requested design contrast, on a black t-shirt. (Please stick to a color scheme that folks who are colorblind will be able to see.)

==Sample Submission==
Joe Ouroboros, joe@loopback.edu :

[[Image:Reset-200.png]]

This is my awesome design. It'll win one of these years.
-----
Not sure how to submit your image? Check out https://www.mediawiki.org/wiki/Help:Editing_pages for more information about editing a page! Here's a template for what the wikitext should look like when you submit your image:
Name, email address :
<nowiki>[[Image:Name of image file you uploaded]]</nowiki>
Explanatory text
<nowiki>-----</nowiki>
== Submissions ==

2017 Code4Lib T-Shirt Design Competition

2016-10-14T17:09:28Z

ShiraPeltzman: Minor edit to sample submission/submission help

It’s that time of year again… the annual 2017 Code4Lib t-shirt logo design competition! For those who are new or for those who need a refresher, here’s how it works: starting Monday October 17th, 2016, we are issuing a month-long open call for a logo design that will be featured on the front of the Code4Lib 2017 Conference t-shirt. The winning logo will be based on a popular vote, which will commence after the submission process closes.

== Details ==

'''DESIGNS ARE DUE BY FRIDAY, NOVEMBER 18, 2016 at 5 PM Pacific Standard Time'''

Please submit your high-quality image to the [[#Submissions|Submissions]] section of this wiki page:

* Post an image file of your print-ready proposal by editing this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. If your print-ready document is different from your displayed image, include a link to the print-ready file.
* Include your name and email address with your proposal.
* If you want, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design when voting begins.
* Place a horizontal rule (----) on a separate line after your submission.
* Original art only, please!
* The screen-printers generally need vector art files (ai, .cdr, .eps & .pdf). If you need help converting your design to one of these file formats, email Shira.

The t-shirt color will (probably) be black, but we can look into changing the assumed t-shirt color depending on the design that is ultimately selected. If the assumed color of the winning design is something other than the traditional black, we will try to get the t-shirts in the requested color. If that color is not feasible, the logo will default to white or gray, depending on the requested design contrast, on a black t-shirt. (Please stick to a color scheme that folks who are colorblind will be able to see.)

==Sample Submission==
Joe Ouroboros, joe@loopback.edu :

[[Image:Reset-200.png]]

This is my awesome design. It'll win one of these years.
-----
Not sure how to submit your image? Check out https://www.mediawiki.org/wiki/Help:Editing_pages for more information about editing a page! Here's an template for what the wikitext should look like when you submit your image:
Name, email address :
<nowiki>[[Image:Name of image file you uploaded]]</nowiki>
Explanatory text
<nowiki>-----</nowiki>
== Submissions ==

2017 Code4Lib T-Shirt Design Competition

2016-10-14T16:54:22Z

ShiraPeltzman: Added more details on submitting images

It’s that time of year again… the annual 2017 Code4Lib t-shirt logo design competition! For those who are new or for those who need a refresher, here’s how it works: starting Monday October 17th, 2016, we are issuing a month-long open call for a logo design that will be featured on the front of the Code4Lib 2017 Conference t-shirt. The winning logo will be based on a popular vote, which will commence after the submission process closes.

== Details ==

'''DESIGNS ARE DUE BY FRIDAY, NOVEMBER 18, 2016 at 5 PM Pacific Standard Time'''

Please submit your high-quality image to the [[#Submissions|Submissions]] section of this wiki page:

* Post an image file of your print-ready proposal by editing this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. If your print-ready document is different from your displayed image, include a link to the print-ready file.
* Include your name and email address with your proposal.
* If you want, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design when voting begins.
* Place a horizontal rule (----) on a separate line after your submission.
* Original art only, please!
* The screen-printers generally need vector art files (ai, .cdr, .eps & .pdf). If you need help converting your design to one of these file formats, email Shira.

The t-shirt color will (probably) be black, but we can look into changing the assumed t-shirt color depending on the design that is ultimately selected. If the assumed color of the winning design is something other than the traditional black, we will try to get the t-shirts in the requested color. If that color is not feasible, the logo will default to white or gray, depending on the requested design contrast, on a black t-shirt. (Please stick to a color scheme that folks who are colorblind will be able to see.)

==Sample Submission==
Joe Ouroboros, joe@loopback.edu :

[[Image:Reset-200.png]]

This is my awesome design. It'll win one of these years.
-----
Not sure how to submit your image? Check out https://www.mediawiki.org/wiki/Help:Editing_pages for more information about editing a page! Here's an example of what the wikitext should look like when you submit your image:
Name, email address :
<nowiki>[[Image:Name of image file you uploaded]]</nowiki>
Explanatory text
<nowiki>-----</nowiki>
== Submissions ==

2017 Code4Lib T-Shirt Design Competition

2016-10-14T16:39:32Z

ShiraPeltzman: Added design competition details and sample submission

Main Page

2016-10-14T14:44:15Z

ShiraPeltzman: /* Code4Lib 2017 Conference */ Added "2017 Code4Lib T-Shirt Logo Design Competition" sub-page

{| id="mp-topbanner" style="width:100%; background:#f9f9f9; margin:1.2em 0 6px 0; border:1px solid #ddd;"
| style="width:54%; color:#000;" |

{| style="width:280px; border:none; background:none;"
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the Code4lib wiki</div>
|}


__NOTOC__
| style="width:20%; font-size:95%;vertical-align:top; " |
* [[#About Code4Lib|About Code4Lib]]
* [[#Software Usage and Documentation|Software Usage and Documentation]]
* [[#Current topics|Current topics]]
* [[#Other Code4Lib Sites|Other Code4Lib Sites]]
| style="width:13%; font-size:95%;" |
* [[#Code4Lib 2016 Conference|2016 Conference]]
* [[#Local / Regional Groups|Local / Regional Groups]]
* [[#Interest Groups|Interest Groups]]
* [[#Earlier Conferences and events|Earlier Conferences and events]]
|}


{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"

| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"
|-

== About Code4Lib ==

* [[About Code4Lib]] - Background and history of the community
* [[A Guide for the Perplexed]] - Building skills for working with library technologies
* [[How to hack code4lib]] - For those newer to the community
* [https://docs.google.com/document/d/1m-9VtL7L_fUxl2hTF_YZSdFRfucaLtmHvLSzom6XPVM/edit?pli=1 Code4Lib Indoctrination] (This is a Google doc open to all including anonymous feedback.)
**"How do we make code4lib a more inclusive place for newcomers? <br/> Or, how do we quickly indoctrinate newbies to our values and ways of doing things?"
**Suggestions, ideas, and follow-up actions solicited.
* [[One recommended tool/resource for n00bs]] - For new coding librarians/library Coders
* [[Mentorship Program]]
* [[Skill Sharing Clubs]] - Find people with similar interests in your field.
* [[Zoia or the Code4Lib IRC bot]]
|-

== Software Usage and Documentation ==

* [[Umlaut]] - OpenURL link resolving middleware
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking.
* [[ILS Documentation]]
* [[OSS Directory]]
* [[Working with MARC]]
* [[Rogue]] - principles for standards creation
* [[ProjectManagement]] - list of project management and issue tracking software that are frequently mentioned on the Code4Lib mailinglist
|-

== Current topics ==

* [[Code4Lib Regional Meeting Streaming]]
* [[Code4Lib Website Update]]
* [[OCLC Policy Change]]
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]
* [[Parsing Library Data]]
* [[Robots Are Our Friends]]
* [[Libraries Sharing Code]]
* [[Code4Lib Tagline brainstorm]]
|-

== Other Code4Lib Sites ==

* [http://www.code4lib.org/ code4lib.org]
* [http://planet.code4lib.org planet.code4lib.org]
* [http://journal.code4lib.org journal.code4lib.org]
|-

== Code4Lib Journal ==

* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents

|}
| style="border:1px solid transparent;" |
| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|

{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"
==Code4Lib 2017 Conference==
{{:Category:Code4Lib2017}}
* [[2017_Code4Lib_T-Shirt_Design_Competition|2017 Code4Lib T-Shirt Logo Design Competition]]
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"

==Code4Lib 2016 Conference==
{{:Category:Code4Lib2016}}
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]
* [[2016_Conference_Volunteers|Volunteer for the 2016 Code4Lib Conference]]
* [[2016_Social_Activities|Social Activities for 2016]]
|-

== Local / Regional Groups ==

=== United States ===
* [[NEC4L|New England Code4lib]] - New England
* [[NYC|Code4LibNYC]] - NYC and surrounding areas
* [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area
* [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas
* [[Southeast|Code4LibSE]] - North Carolina, South Carolina, Georgia, Virginia, Well, you get the idea
* [[Midwest|Code4Lib Midwest]] - Wherever that is...
* [[Code4Lib_Chicago|Chicago]] - Chicago is a city in the Midwest
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest
* [[Western|Code4Lib West]] - California North and South

=== Canada ===

* [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces
* [[North|code4lib North]] - Ontario and surrounding areas
* [[Edmonton|Code4LibYEG]] - Edmonton, Alberta ''(also new in 2013)''
* [[BC|Code4Lib BC]] - British Columbia ''(new in 2013)''

=== Europe ===
* [[NL|Code4Bib]] - Dutch Code4Bib
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers

=== Asia/Pacific ===
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.
|-

== Interest Groups ==

* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries
* [[Fiscal_Continuity|Fiscal Continuity]] - A group exploring whether and how to make long-term fiscal arrangements for conferences (and perhaps other activities)
|-

|}
|}

== Earlier Conferences and events ==
* [[:Category:Code4Lib2016|Code4Lib 2016]] Philadelphia, PA
* [[:Category:Code4Lib2015|Code4Lib 2015]] Portland, OR
* [[:Category:Code4Lib2014|Code4Lib 2014]] Raleigh, NC
* [[:Category:Code4Lib2013|Code4Lib 2013]] Chicago, IL
* [[:Category:Code4Lib2012|Code4Lib 2012]] Seattle, WA
* [[:Category:Code4Lib2011|Code4Lib 2011]] Bloomington, IL
* [[:Category:Code4Lib2010|Code4Lib 2010]] Asheville, NC
* [[:Category:Code4Lib2009|Code4Lib 2009]] Providence, RI
* [[:Category:Code4Lib2008|Code4Lib 2008]] Portland, OR
* [[:Category:Code4Lib2007|Code4Lib 2007]] Athens, GA
* [[:Category:Code4Lib2006|Code4Lib 2006]] Corvallis, OR
[[Conference Financial History At A Glance]]

=== Older Conference T-Shirt Designs ===
* [http://www.code4lib.org/node/235 2008 (Portland, Oregon)] - [http://code4lib.org/files/code4lib08.gif winning design]
* [http://code4lib.org/node/146 2007 (Athens, Georgia)] - [http://code4lib.org/files/code4lib2007-7.jpg winning design]
* [http://code4lib.org/tshirts 2006 (Corvalis, Oregon)] - [http://code4lib.org/files/t-shirt.png winning design]

=== Other workshops ===
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010

== Archived topics ==

* [[Logo Design Process]]

[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites