Update Hack Day page

Author: sdruskat

_sass/minimal-mistakes/_buttons.scss

@@ -91,6 +91,100 @@
     font-size: $type-size-5;
   }
 
+  /* small button */
+  &--small {
+    font-size: $type-size-7;
+  }
+}
+
+/*
+   Left-aligned button with linebreak after it
+   ========================================================================== */
+
+.btn--break {
+  /* default */
+  margin-bottom: 0.25em;
+  padding: 0.5em 1em;
+  font-family: $sans-serif;
+  font-size: $type-size-6;
+  font-weight: bold;
+  text-align: left;
+  text-decoration: none;
+  border-width: 0;
+  border-radius: $border-radius;
+  cursor: pointer;
+
+  .icon {
+    margin-right: 0.5em;
+  }
+
+  .icon + .hidden {
+    margin-left: -0.5em; /* override for hidden text*/
+  }
+
+  /* button colors */
+  $buttoncolors:
+  (primary, $primary-color),
+  (inverse, #fff),
+  (light-outline, transparent),
+  (success, $success-color),
+  (warning, $warning-color),
+  (danger, $danger-color),
+  (info, $info-color),
+  (facebook, $facebook-color),
+  (twitter, $twitter-color),
+  (google-plus, $google-plus-color),
+  (linkedin, $linkedin-color);
+
+  @each $buttoncolor, $color in $buttoncolors {
+    &--#{$buttoncolor} {
+      @include yiq-contrasted($color);
+      @if ($buttoncolor == inverse) {
+        border: 1px solid $border-color;
+      }
+      @if ($buttoncolor == light-outline) {
+        border: 1px solid #fff;
+      }
+
+      &:hover {
+        @include yiq-contrasted(mix(#000, $color, 20%));
+      }
+
+      &:visited {
+        @include yiq-contrasted($color);
+      }
+    }
+  }
+
+  /* fills width of parent container */
+  &--block {
+    display: block;
+    width: 100%;
+
+    + .btn--block {
+      margin-top: 0.25em;
+    }
+  }
+
+  /* disabled */
+  &--disabled {
+    pointer-events: none;
+    cursor: not-allowed;
+    filter: alpha(opacity=65);
+    box-shadow: none;
+    opacity: 0.65;
+  }
+
+  /* extra large button */
+  &--x-large {
+    font-size: $type-size-4;
+  }
+
+  /* large button */
+  &--large {
+    font-size: $type-size-5;
+  }
+
   /* small button */
   &--small {
     font-size: $type-size-7;

_sass/minimal-mistakes/_notices.scss

@@ -15,7 +15,7 @@
   padding: 1em;
   color: $dark-gray;
   font-family: $global-font-family;
-  font-size: $type-size-6 !important;
+  /*font-size: $type-size-6 !important;*/
   text-indent: initial; /* override*/
   background-color: mix(#fff, $notice-color, 90%);
   border-radius: $border-radius;

assets/images/zenodo.1405679.svg

@@ -0,0 +1,68 @@
+---
+title: Citation File Format - Code of Conduct for events
+---
+
+Citation File Format events are community events organized by the Citation File
+Format community or the project maintainers. They are intended for collaboration and learning.
+We value the participation of every member of the community and want all attendees to have an 
+enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and 
+courtesy to other attendees throughout the event and in interactions online associated with the event.
+
+The event organizers are dedicated to providing a harassment-free experience for everyone, 
+regardless of gender, gender identity and expression, age, sexual orientation, disability, 
+physical appearance, body size, race, ethnicity, religion (or lack thereof), technology choices, 
+or other group status.
+
+To make clear what is expected, everyone taking part in Citation File Format events and discussions — 
+speakers, helpers, organizers, and participants — is required to conform to the following Code of Conduct.
+
+All participants are expected to follow this code throughout the event, and you may also contact 
+the person or team responsible for the Code of Conduct (CoC) directly by email at 
+cff-coc@sdruskat.net. All communication will be treated as confidential.
+
+To that end, we ask all attendees to adhere to the following guidance:
+
+- Communicate appropriately for a professional audience including people of many different backgrounds. Sexual language and imagery are not appropriate for any event.
+- Be kind to others. Do not insult or put down other attendees. Be mindful of jargon, which can sometimes exclude others from engaging in the discussion.
+- Behave professionally. Remember that harassment and sexist, racist, ageist, or exclusionary behavior are not appropriate.
+
+Note that we take a community approach to ensuring the safety and comfort of all attendees. Everyone is responsible for assisting in any circumstances where anyone appears to not follow the Code of Conduct.
+
+## Conflict Resolution
+
+If someone makes you or anyone else feel unsafe or unwelcome, please report it as soon as possible to the event organizer(s) if you are hesitant about addressing the person yourself. At any time, you can reach them either in person or via email (see contact information below). 
+The event organizers are committed to address and resolve the issue in question to the best of their abilities.
+
+Harassment and other Code of Conduct violations reduce the value of our event for everyone. We want you to be happy at our event. A harassment-free environment makes our event more conducive to research creativity and productivity.
+
+You can make a report either personally or anonymously.
+
+## Sanctions
+
+Participants asked to stop any behavior that makes others uncomfortable are expected to comply immediately. If a participant engages in harassing behavior, organizers will take any action they deem appropriate, including warning the person in question, removing the harasser from the event, banning the offender from a mailing list or other online means of communication.
+
+Specific actions may include but are not limited to:
+
+- warning the person to cease their behavior and that any further reports will result in other sanctions
+- requiring that the person avoid any interaction with, and physical proximity to, their victim for the remainder of the event
+- early termination of a talk or presentation that violates the policy
+- not publishing the video or slides of a talk that violated the policy
+- not allowing a speaker who violated the policy to give (further) talks or presentations at the event
+- immediately ending any event volunteer responsibilities, and privileges the harasser holds and requiring that the person to not volunteer for future events (either indefinitely or for a certain time period)
+- requiring that the person immediately leave the event and not return
+- banning the person from future events (either indefinitely or for a certain time period)
+- publishing an account of the harassment
+
+Citation File Format event organizers can be identified by their name badges, and will help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the event.
+
+If an incident occurs, please use the following contact information:
+
+Resonsible for the Code of Conduct (CoC):
+
+    Stephan Druskat: cff-coc@sdruskat.net
+
+We expect participants to follow these rules at all event venues, event-related social events, community gatherings, and online communication channels.
+
+Thank you for your participation in the CFF community, and your efforts to keep CFF events a safe and friendly space for all participants!
+
+(Based on the [WSSSPE5.1 Code of Conduct](http://wssspe.researchcomputing.org.uk/wssspe5-1/wssspe5-1-code-of-conduct/), which was based on the [FORCE11 Code of Conduct](https://www.force11.org/meetings/force2016/code-conduct), which was based on the Code4Lib Code Of Conduct, inspired by the ADA Initiative)

events/coc.md

@@ -1,43 +1,135 @@
 ---
 title: Citation File Format Hack Day @ RSE18
+toc: true
 ---
 
+{% include toc %}
+
 The [Citation File Format (CFF)](https://citation-file-format.github.io/) is a human-centric, machine-readable format for software citation metadata. It is developed to provide an easy way for RSEs, and other developers of software in academia, to ensure that they can receive credit for their work; Likewise, it provides researchers with access to the necessary metadata for references to the software they use in their research. The Citation File Format follows the [Software Citation Principles](https://peerj.com/articles/cs-86/), and is compatible with the [CodeMeta](http://codemeta.github.io/) JSON-LD exchange format for software metadata. It is being developed in the context of the [FORCE11 Software Citation Implementation Working Group](https://www.force11.org/group/software-citation-implementation-working-group) and a wider community of stakeholders, including the [Netherlands eScience Center](https://www.esciencecenter.nl/). Recently, CFF has been adopted by [CiteAs.org](http://citeas.org/) as a source format, and its tools infrastructure is growing.
 
-During a dedicated **Hack Day on Wednesday, 5 September** - co-locating with the [3rd Conference of Research Software Engineers (RSE18)](http://rse.ac.uk/conf2018/) in Birmingham - we want to *a)* give an overview of - and discuss - the Citation File Format, its tooling and workflows; *b)* discuss what tools would be necessary to facilitate, e.g., better usability, optimized workflows, or integration with other tools in the software citation workflow (reference managers, repositories, other formats, etc.); *c)* do some actual work around existing and new tools, as well as the Citation File Format itself and its documentation.
+## Hack Day at the 3rd Conference of Research Software Engineers
 
-**Participation is free and open to everyone**, regardless of their skill set and experience.
+During a dedicated **Hack Day on Wednesday, 5 September** - co-locating with the [3rd Conference of Research Software Engineers (RSE18)](http://rse.ac.uk/conf2018/) in Birmingham - we want to 
 
-**Registration** has been possible through the [registration form for #RSE18](https://store.southampton.ac.uk/conferences-and-events/physical-sciences-and-engineering/physics-astronomy/events/third-conference-of-research-software-engineers). If you don't attend the main
-conference but want to participate in the hack day, please let me know per email at
-*stephan* [dot] *druskat* [at] *hu-berlin* [dot] *de*.
+- *a)* give an overview of - and discuss - the Citation File Format, its tooling and workflows; 
+- *b)* discuss what tools would be necessary to facilitate, e.g., better usability, optimized workflows, or integration with other tools in the software citation workflow (reference managers, repositories, other formats, etc.); 
+- *c)* do some actual work around existing and new tools, as well as the Citation File Format itself and its documentation.
 
-**PLEASE NOTE THAT THE HACK DAY IS NOW FULLY BOOKED!**
-If you have confirmed your attendance per email, you're on board.
-If you have registered, but have not yet confirmed your attendance per email, 
-you can still do so and will be added to the waiting list for the event.
+**The hack day is now fully booked!** If you have re-confirmed your participation
+via email to Stephan Druskat, you will have received a confirmation email and preliminary infos
+about the hack day, and have a place.  
+Please confirm your wish to participate via email to *stephan* [dot] *druskat* 
+[at] *hu-berlin* [dot] *de* to be added to the waiting list. If space becomes available for you,
+you will be notified via email.
+{: .notice--danger}
 
-**Participation is limited to 30 attendees**, and participants will be
-selected on a first come first serve basis. You will be notified about your participation per
-email at the beginning of August (i.e., once registration is closed) at the latest.
-Please also consider this with regard to booking your accommodation and travel.
+## Location
 
-**Accommodation** for participants is available at Chamberlain Halls and can be booked through the
-main [accommodation booking form](https://rse.ac.uk/conf2018/accommodation/). Note that
-accommodation for Wednesday night (5 September) is also available through this form for 
-participants who do not travel after the end of the hack day on Wednesday.
+The hack day will take place in the **Murray Learning Centre**, R28,
+University of Birmingham, Birmingham B15 2FG
+([Google Maps](https://goo.gl/maps/UDPocWznNW52), [Walking Map](walking-map.pdf): marked as "Learning Centre" on p.2 
+below the legend), room tbc.
 
-Please **get in touch** with any questions and comments via email to
-*stephan* [dot] *druskat* [at] *hu-berlin* [dot] *de*.
+The international morning
+meeting and the Tier-2/HPC workshop will also take place there, so that
+you can meet delegates from the other events during lunch and coffee breaks.
+
+### Pre-Hack Day Social 
+On the evening before the hack day, if you want to get to know your fellow 
+hackers in advance, there will be an **informal get-together**, and you're invited 
+to come along for a drink and a chat. We'll meet at the [Arco Lounge](https://thelounges.co.uk/arco/)
+(147 High Street, Harborne, Birmingham, B17 9NP - [Google Maps](https://goo.gl/maps/YkDAuqYszWF2))
+from around 18:00 on Tuesday, 4 September. They have food as well (including quite a few vegan options).
+
+## Agenda
+
+### Tuesday, 4 September 2018
+
+**RSE Talk:** Tuesday, 4 September 2018, [13:30, parallel session 4, Track B](https://rse.ac.uk/conf2018/programme/) -    
+S. Druskat: *"YOU HAVE 0 CREDIT – PLEASE INSERT C̶O̶I̶N̶ FILE": The Citation File Format*
+
+**Pre-Hack Day Social:** Tuesday, 4 September 2018, from ca. 18:00, [Arco Lounge](https://thelounges.co.uk/arco/)
+{: .btn--break .btn--info}
+
+<i class="fa fa-fw fa-twitter" aria-hidden="true"></i> If you want to tweet about the hack day, please use the hashtag **#cffhackday**.
+{: .notice--info}
+
+### Wednesday, 5 September 2018, 09:00 - 17:00
+
+**09:00** - *Registration: Coffee and Tea*
+{: .btn--break .btn--info}
+
+**09:15** - Introductions  
+**09:30** - **Talk:** "Brief introduction to the Citation File Format" (S. Druskat)  
+**09:50** - **Talk:** "The Citation File Format at the Netherlands eScience Center" (J. Spaaks)  
+**10:15** - **Hack idea pitches & group formation** (<http://bit.ly/cff-hack-ideas>)
+{: .btn--break .btn--warning}
+
+**10:45** - *Coffee and Tea break*
+{: .btn--break .btn--info}
+
+<br/>**11:00** - **Hacking in groups**<br/><br/>
+{: .btn--break .btn--success}  
+
+**12:00** - *Lunch*
+{: .btn--break .btn--info}
 
-## Dates & agenda
+**12:30** - **Hacking updates** (plenary)
+{: .btn--break .btn--warning}
 
-- **Hack day**: Wednesday 5 September 2018, 9:00-17:00
-- **Venue**: University of Birmingham, exact location tba
-- **Agenda**: tba
+<br/>**12:45** - **Hacking in groups**<br/><br/>
+{: .btn--break .btn--success}
+
+**14:30** - *Coffee and Tea break*
+{: .btn--break .btn--info}
+  
+<br/>**14:45** - **Hacking in groups**<br/><br/>
+{: .btn--break .btn--success}
+
+**16:00** - **Hacking reports & Wrap-up**
+{: .btn--break .btn--warning}
+
+**17:00** - *End*
+{: .btn--break .btn--info}
+
+## Hack ideas
+
+If you have an idea how the Citation File Format, its tooling, its
+documentation, or its integration in the software citation workflow could be 
+improved, you **please register your hack idea** in the 
+Hack Ideas Spreadsheet at <http://bit.ly/cff-hack-ideas>.  
+If you register a hack idea, please be prepared to present a very short
+pitch of the idea during the hack day.
+
+
+## Code of Conduct
+
+I want to make sure that the hack day is welcoming and friendly to everyone.
+Therefore, **please read Code of Conduct. You are expected to adhere to it.**
+It can be read here: <https://citation-file-format.github.io/events/coc>.
+
+## Resources
+
+- The main resource for the Citation File Format itself is the [**project
+website**](https://citation-file-format.github.io). Some basic info can
+also be found at <https://cite.research-software.org>.
+- <i class="fa fa-fw fa-slack" aria-hidden="true"></i> **Slack channel:** I've set up a Slack channel for the hack day. Please join it, 
+using this link: <http://bit.ly/cff-hack-day-slack-invite>! If you haven't used Slack
+before, some info on getting started can be found at <https://get.slack.help/hc/en-us/categories/360000049043>
+- <i class="fa fa-fw fa-github" aria-hidden="true"></i> **GitHub:** The suggested code platform to use for any hacktivities
+during the hack day. Please create an account on GitHub if you haven't
+got one yet. Some info to get you started can be found at <https://guides.github.com/activities/hello-world/>.
+- <i class="fa fa-fw fa-twitter" aria-hidden="true"></i> If you want to tweet about the hack day, please use the hashtag **#cffhackday**.
+
+## Contact
+
+Please **get in touch** with any questions and comments via email to
+*stephan* [dot] *druskat* [at] *hu-berlin* [dot] *de*.
 
 ---
 
+## Thanks
+
 I'd like to thank the following for their great help and support in organizing this hack day:
 
 - [#RSE18 organizing committee](https://rse.ac.uk/conf2018/contacts/), especially Louise Brown,