code4lib / 2019.code4lib.org Goto Github PK

To be closed after Nov. 16th.

Date information: "Proposals can be submitted through Thursday, October 4, 2018 at midnight Pacific time. Voting will start on Tuesday, October 9, 2018 and continue
through Thursday, October 25, 2018 at midnight Pacific time. The committee
plans to announce selected proposals on Monday, October 29, 2018."

Submission link: https://docs.google.com/forms/d/e/1FAIpQLSeGNEkTAVyeUAhQViIrr-dE0WgUNPQ6s55EOqxj6T5KDKJqMw/viewform?c=0&w=1

Email text:

Code4Lib 2019 is soliciting proposals for poster sessions

Code4Lib 2019 is a loosely-structured conference that provides people
working at the intersection of libraries/archives/museums/cultural heritage
and technology with a chance to share ideas, be inspired, and forge
collaborations. For more information about the Code4Lib community, please
visit https://code4lib.org/about/.

The conference will be held at the San Jose DoubleTree by Hilton hotel,
from February 19-22, 2019. See https://2019.code4lib.org/ for more
information.

We are now calling for proposals for a 30-minute poster session at the
conference.

As with most things Code4Lib, the community will vote on posters that they
would like to see included in the program. The Program Committee will
curate the top voted proposals based on available presentation space and to
ensure diversity in program content.

Presenters whose posters are selected for inclusion in the program will
have conference registration slots held for them at the standard conference
rate (1 per poster).

Submit your poster proposal here! https://tinyurl.com/y9489rmc

Proposals can be submitted through November 12, 2018 at 11:59pm PST
(GMT−8). Voting will start on November 15, 2018 and continue through
November 29, 2018. The URL to submit votes will be announced on the
Code4Lib mailing list. The final list of posters will be announced in
December.

Thank you,
The Code4Lib 2019 Program Committee

To ensure the instructions are up to date.

Currently all of the assets are broken because we're using github.io links.

To be closed after voting ends on Friday, December 7, 2018 at 11:59 Eastern time.

Index Data is a gold sponsor, and MIT is bronze + a diversity scholarship sponsor.

As we frequently have open volunteer opportunities for the conference, it would be great to have a section for this on the homepage, similar to the sections for proposals and voting. The button could either link to a contact for the volunteering opportunity, or to the relevant wiki section.

Current open volunteer opportunities include duty officers and others on the wiki - https://wiki.code4lib.org/Code4Lib_2019_Conference_Committees

Each committee could have a conf section, with a true/false variable if they're looking for volunteers.

We've had the same ones since the very first conference site I think. They're defined in _data/testimonials.yml

Ideas for getting new ones:

• search Twitter/social media for statements, ask for permission
• ask former keynotes or speakers
• ask former diversity scholarship recipients

To be done after October 4 at midnight Pacific.

dates, hotel, hotel room rate, transportation (complimentary shuttle to airport)

Voting will end on Thursday, November 29, 2018 at 11:59:59 PM PT (GMT-8)

The sponsor registration form is currently buried at the bottom of the prospectus in the text. We need to make this stand out more, perhaps using a button or something similar.

Voting closes Oct. 25, 2019, at 11:59pm Pacific time.

The current colour scheme is making the prospectus text unreadable: https://2019.code4lib.org/prospectus/

We'll also need to improve the contrast in the childcare section.

Link: https://goo.gl/tM4JJq

Voting will end on Thursday, November 29, 2018 at 11:59:59 PM PT (GMT-8)

To be done after October 11, 5PM PST/8PM EST

See #98 — workshop posts have frontmatter, use the "presentation" layout, and a body which is HTML right now. But in the presentation layout their HTML {{content}} isn't parsed as markdown—URLs that people helpfully pasted into their workshop descriptions aren't converted to links. I've tried changing the template to {{ content | markdownify }} but it didn't do anything.

To be done after October 22, midnight Pacific

As noted by @phette23 here, there's an issue in Chrome with the hover text colour on the buttons.

URL: https://goo.gl/forms/DXyX8OGKBtHKkXzv1
Close date: October 11, 2018, 5PM PST/8PM EST
Contact: Kathleen Haley ([email protected])

The start of our audit currently lives here
https://docs.google.com/spreadsheets/d/1u8lQOUG964UJK2rUqKj4akJmHfKAnefkPTRdVB1KedU/edit?usp=sharing

Will be marking off these as completed and add anymore as we work.

To be closed after November 12, 2018 at 11:59pm PST.

see https://github.com/code4lib/2019.code4lib.org/wiki/Best-Practices-for-passing-data-to-the-Website-Working-Group

Looking for feedback from the group. Document goals:

• it's clear & understandable especially to people who a) are new to the Code4Lib conference structure, b) are unfamiliar with Jekyll & the conference site specifically
• it's fairly short (not much longer than the first draft)
• it contains concrete examples & links to relevant places
• it places a reasonable burden on other conference committees to deliver usable data to us in a timely manner

Date TBD but soon, probably this week (10/22).

Concentra donation form: https://mxmerchant.com/mxcustomer/d/27881511-a676-4fa5-80cb-9987204864c4/v3

Our content is at /general-info/angel-fund.html

We don't know the spreadsheet key for /assets/js/thermometer.js yet. I assume Concentra is updating a spreadsheet again this year but I haven't gotten any confirmation.

"LibTechWomen and Friends" is matching the first $4,000 donated. I'm going to try to find a logo for them but I think taking the one from http://libtechwomen.org is fine if we don't get sent one.

Close at midnight pacific time on November 16th or as close to it as feasible.

• add link to conference schedule when it's available
• add link to reception information
• add link to newcomer dinner when it's available
• add link to Quiet room when it's available

To be done after November 15, midnight EST

Currently some testimonials will break onto a new line depending on their length. We should fix the CSS/etc. so this doesn't happen.

should be more present in the jumbotron or elsewhere on the home page

A couple pieces of this (highlighted) still need to be confirmed but here's the prospectus for this year: https://docs.google.com/document/d/1V4PWR6kXTCxGAjXFsyjVoD52UyKNv1nGNabNaCEeFz0/edit?usp=sharing

Based on last year so there are relatively few edits to make.

We need to hide nav items that don't have content yet. This includes the duty officer schedule item in 'conduct & safety', and the 'quiet room' section under 'general info > accessibility'.

Technically we stop taking donations tonight (27th) at midnight but I'll close this tomorrow when we can see the updated totals.

On the speakers page at https://2019.code4lib.org/speakers/, there are colour contrast issues with many of the fonts.

See http://wave.webaim.org/report#/https://2019.code4lib.org/speakers/# (the contrast tab) for more details.

potential sources:

• Flickr https://www.flickr.com/search/?text=san%20jose&license=2%2C3%2C4%2C5%2C6%2C9
• Wikimedia Commons https://commons.wikimedia.org/wiki/San_Jose,_California

Proposal: Sharks colors https://teamcolorcodes.com/san-jose-sharks-color-codes/

Date: closes Oct. 22, 2018
Link: https://wiki.code4lib.org/2019_Keynote_Speakers_Nominations
Anonymous email: [email protected]

See full email on C4L list.

There's no way to go from an individual workshop page to the full list of them at /workshops/. I'm not saying we need breadcrumbs everywhere but I've found it a bit troublesome to navigate just as I'm testing the site.

their email announcement:

Code4Lib 2019 Diversity Scholarships


We would like to thank our sponsors for supporting the Code4Lib 2019 Diversity Scholarships! 


MIT Libraries 

Temple University

LibTech Women and Friends


As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our 2019 Diversity Scholarship program <http://2019.code4lib.org/general-info/scholarships>! The

Scholarship Committee hopes to award 15 Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1500 for travel costs, lodging, and conference fees for selected applicants to attend the 2019 Code4Lib Conference <http://2019.code4lib.org/> in San José, California. The deadline for applications is Friday, November 16, 2018 at 11:59 PM ET.


The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated.

Please contact [email protected] with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.


We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.


Code4Lib conference 2019: 


http://2019.code4lib.org


*About Code4Lib:*


Code4Lib (https://code4lib.org) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging CodeofConduct4Lib

<https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md>. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration. 


Diversity Scholarship Eligibility, Criteria, And Requirements


 - An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.


 - An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the About Code4Lib Page https://goo.gl/forms/WsqP717J90cINm7E3.


 - The scholarship recipients will be selected based upon their merit and financial needs.


Registration Details


Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.


How to Apply


Submit your application materials via the Code4Lib online form: https://docs.google.com/forms/d/e/1FAIpQLSetEMsBxZYXj_GGyxwWj_FnIxgxDRjxuZ-t16QqPtKuKKQ8Eg/viewform?usp=sf_link 

 

You will need to prepare:


 1. Your brief letter of interest, no more than 500 words, which:

-Identifies your eligibility for a diversity scholarship

-Describes how you see yourself benefiting from and participating in the Code4Lib 2019 conference and the general Code4Lib community


 2. Your current resume or CV


 3. Contact information for one reference who can speak to your professional goals and/or achievements



Please note: Your brief letter of interest and current CV/resume should be combined into a single pdf. Your file should follow a “Lastname-Firstname.pdf” naming convention. Please direct any questions to [email protected].


The application deadline is Friday, November 16, 2018 at 11:59 PM ET


The scholarship committee will notify all applicants by Wednesday, December 5, 2018, regardless of award results.

The local Emergency section with information like local hospitals, police, etc. needs to be updated for San Jose. It's present on the Conduct page: https://2019.code4lib.org/conduct/

We just need to research and write this section, no coding required really. See 2018 site for example of the info: https://2018.code4lib.org/conduct/#emergency

2018 site speakers page (Audrey's info expanded):

2019 site (Ophelia's expanded):

Seems like somewhere during the theme color or accessibility updates we made the .speaker-info background color the same as the page background.

These are being flagged as potential vulnerabilities - we need to test & upgrade the versions in the gemfile being used.

We need to use (at minimum):
rubyzip ~> 1.2.2
jekyll ~> 3.7.4

As discussed at today's meeting, let's add the first timer's guide sent out in emails to registrants to the website. Depending on the length, it could either be included on the 'attend' page, or as a sub-page.

Here's the email from last year (with apologies for the formatting):

 ---

We're in the last
few days before #c4l18 begins, and for a good number of you, this will be your first code4lib. Here is some information to help you navigate through the conference whirlwind next week:

• Schedule: We have
  a packed program with talks, preconferences, lightning talks, & breakout sessions. The full conference & pre-conference schedules are available on the main conference page [1]. The venue will provide lunch Wednesday and Thursday, as well as morning and afternoon
  break snacks Wednesday through Friday morning. Menus will be posted on the website soon. There will be caffeine.
• Social Activities
  [2]: There's a lot going on outside of the sessions, and this page has information about various gatherings, events, meals, etc. In addition, if you have any events that you’d like to organize, please feel free to add the event to the DIY Event Google Doc
  [3]!
  One activity I want
  to highlight is the Newcomer dinner [4] on Tuesday, February 13th. There are still a lot of great restaurants left on the list, and this is your chance to meet folks you might otherwise not get a chance to talk to at the conference. Read the guidelines and
  pick your restaurant (c4l veterans - this means you too!).
  Another event is
  Game Night on Wednesday, February 14th. While you do not need to bring something to participate, please let us know if you do plan to bring games [5]. Most importantly, bring yourself!
  Lastly, since this
  year’s conference falls on Ash Wednesday, the Social Activities Crew is compiling a list of Ash Wednesday services near the hotel [6].
• Volunteering: A
  round of applause for everyone who has helped to plan the conference! So much of what goes into making this event possible each year happens through the tireless efforts of our community members. The work isn't quite done yet, and we're still looking for
  volunteers for a few on-site tasks [7] - the Whatever Crew is always looking for more
  red shirts
  volunteers!
• IRC/Twitter/Slack.:
  Use the #c4l18 hashtag for conference related tweets, posts, pictures, and so on. The IRC channel [8] is #code4lib, and there will be volunteers at the conference who would be more than happy to help you with IRC. We also have a Slack [9] that volunteers can
  help you get set up at the conference. All channels are very active during the conference so check these channels often for announcements, information, etc.
• For my last item,
  give the following a read:
  -- CodeofConduct4lib
  [10]
  -- Related - Duty
  Officer information for the conference [11]
  If nothing else -
  if you have a question, ask! Ask the conference volunteers, folks who look like they know what they’re doing, folks who don’t exactly look like they know what they’re doing, the Slack channel, the Twitter/IRC streams - the choices are plentiful.
  Thanks and see you
  next week,
  Becky, on behalf
  of the (slow but steady) Welcome Wagon
  [email protected]
  [1]
  http://2018.code4lib.org/schedule/

[2]
http://wiki.code4lib.org/2018_Social_Activities
[3]
https://docs.google.com/document/d/1rwbYzsc70HWMZQlUfXJ9Z8YJ476CDY4FZI0zsW9aeBw/edit?usp=sharing

[4]
http://2018.code4lib.org/general-info/venues/#dinner
[5]
http://2018.code4lib.org/general-info/venues/#gaming
[6 ]
https://wiki.code4lib.org/2018_Social_Activities#Ash_Wednesday_Services
[7]
http://wiki.code4lib.org/2018_Conference_Volunteers

[8]
http://code4lib.org/irc
[9]
https://docs.google.com/forms/d/120Dw1JjLxPJB9VTGl0mUY7Ot6yg6YNY1RZUISJFzdwk/viewform?c=0&w=1

[10]
http://2018.code4lib.org/conduct/

[11]
http://2018.code4lib.org/conduct/#officers

I'm uploading speaker photos to this folder as I receive them. Anyone with a link should be able to edit.

https://drive.google.com/drive/folders/1Fr7HyW81G8AMo0-mI03pNQPREQIVe8NQ?usp=sharing

implemented with React of course

There are still some areas where we could probably be using variables in our data. Some that I've noticed are:

• the conference venue
• the conference city/state
• the date range
• the contact name/email for keynotes, workshops, and talks

Feel free to add others to this ticket!

In both _includes/workshops/card.html and _layouts/presentation.html we have some logic that keys off of the time value of a workshop (am, pm, or "full") to show the time range that the workshop runs. But this range changes year-over-year (was 9:30-5:30 in 2018, will be 9-5 this year) plus doesn't allow one-off exceptions such as workshops that run at unique times. Here's the logic for the record:

{% capture page_length %}
  {% if page.time == 'am' %}
    9:00-12:00
  {% elsif page.time == 'pm' %}
    2:00-5:00
  {% else %}
    9:00-5:00 (w/ lunch break)
  {% endif %}
{% endcapture %}

We should update both these templates to simply use {{page.startTime}} - {{page.endTime}} which is more flexible, more consistent with conference talks, and less likely to change year-over-year. Every workshop post will need to be updated with start/end times this year but it should be easy to populate them going forward as part of the preconference workshops workflow.

Link: goo.gl/xvQXyu
Closing: Voting will end on Thursday, October 25, 2018 at 11:59:59 PM PT (GMT-8)

See the C4L list for the full email.

• add Safiya Noble
• add "TBD" 2nd keynote speaker