Coder Social home page Coder Social logo

sorse / sorse.github.io Goto Github PK

View Code? Open in Web Editor NEW
4.0 10.0 14.0 61.01 MB

Website of the SORSE20 conference

Home Page: https://sorse.github.io

License: Creative Commons Attribution 4.0 International

Ruby 1.66% HTML 61.02% Python 18.81% Shell 1.81% JavaScript 5.40% SCSS 11.30%

sorse.github.io's Introduction

SORSE Website repository

This repository contains the source code for the Series of Online Research Software Events (SORSE). It is based on the Minimal Mistakes Jekyll theme and hosted with Github Pages. The static website is build automatically on Github but you can also build it locally.

The documentation how to contribute is in the Wiki of this repository. There you find, how to add new members, new national chapters, how to assign someone to a specific team, etc.

How to contribute

Unless you know exactly what you are doing, please always

  • do not push directly to the master branch (usually you are anyway not allowed to do so). You must contribute via pull request
  • we always require a review from another person (the four eyes principle)
  • assign issues and pull request to applicable milestones, labels and projects.
  • if you're working on an issue or PR, assign it to yourself! If you are not working on it anymore, remove your assignment from the PR, either because you are finished or because you don't have the time to do more, unassign yourself and ideally leave a message that someone else should take over.

New to GitHub? Don't worry, you'll figure it out fast and it's no problem if it does not immediately work. If you have a problem, ask in slack or create an issue. You should have a look into the Projects tab (see above), that gives you an overview on the current tasks.

Important facts

  • if you are lacking a link and nevertheless want to add the text as a placeholder, mark it with {: .missing}. The link will then be highlighted in red (example: [some important document](){: .missing})

  • when referencing an internal link, e.g. {{ site.data.committee.national_chapters.deRSE.internal }}, use prepend it with a {{ site.baseurl }}, otherwise it will not resolve correctly on GitHub. In other words

    • [Software demos]({{ site.data.committee.programme_teams.software-demos.internal }}) 👎 😠
    • [Software demos]({% include fix-link.html link=site.data.committee.programme_teams.software-demos.internal %} 👍 💚

Local installation

As we cannot host one version of this site with GitHub Pages (generated from the master branch), you should build the website locally and test the implemented changes (or the reviewer in the pull request does it, this is fine as well). To build this site locally, you need to use the command line:

  1. Install ruby for your platform
  2. Install bundle via gem install bundler
  3. cd to the clone of this repository
  4. Run bundle install
  5. Serve the site locally via bundle exec jekyll serve
  6. Visit the site in the browser via http://localhost:4000

Preview the Site on CircleCI

We use CircleCI to preview the site for pull requests, and this is controlled by the files in the .circleci folder. To use CircleCI, you will need to make sure you are logged in to the service and following the repository. When you select a build associated with a pull request, click on the "Artifacts" tab, and select a static file to open and preview in your browser.

Testing the installation

We use the html-proofer to test for broken links, etc. To run the tests locally, you need to install it (see Local installation) and run the tests via executing bundle exec rake

License

The contents of the SORSE website and its source code repository is published under the Creative Commons Attribution 4.0 International Public License (CC BY 4.0). See the LICENSE file for more details.

Copyright (c) 2020, the SORSE committee.

The original software for creating this website, the Minimal Mistakes Jekyll Theme, is distributed under the MIT license, see https://github.com/mmistakes/minimal-mistakes#license.

The MIT license also applies for the _includes and _layouts folder in this repository.

The [academicons][ci/academicons.ttf] font is redistributed from the latex package academicons, which has been published under the SIL Open Font License.

sorse.github.io's People

Contributors

chilipp avatar eileen-kuehn avatar teriforey avatar catsmith avatar sdruskat avatar vsoch avatar cc-a avatar stephanjanosch avatar trallard avatar andrewgait avatar rainsworth avatar jcohen02 avatar johanphilips avatar bast avatar maccradar avatar imgbotapp avatar alisonrclarke avatar juanfrh avatar danielskatz avatar marionbweinzierl avatar mkuzak avatar tscheypidi avatar aniabrown avatar github-actions[bot] avatar

Stargazers

avatar avatar avatar Florian Thiery avatar

Watchers

Frank Löffler avatar James Cloos avatar Ben van Werkhoven avatar avatar Florian Thiery avatar avatar avatar avatar Claire Wyatt avatar Kim Martin avatar

Forkers

mdolling-gfz johanphilips mkuzak teriforey chilipp marionbweinzierl andrewgait cc-a jcohen02 tscheypidi aniabrown alisonrclarke stephanjanosch annalenalamprecht

sorse.github.io's Issues

Enable CircleCI for RSE-leaders

We use CircleCI to render static previews of the website in Pull requests. Therefore, CircleCI needs to be granted access to the RSE-leaders repository (public repositories only). If you are not familiar with CircleCI @alysbrett, you could make me a regular member of the RSE-leaders organization, and I will make the request.

Create page for Programme Committee

Eventually by listing all members grouped into subteams? (Would be straight-forward and automatic)

  • #9 closed
  • page/section created
    - [ ] listed in _data/navigation.yml Won't do that as all are on the same page (see #21)
  • internal link added to _data/committee/committees.yml

Add national RSE chapters

They should be listed in _data/committee/national_chapters.yml. Shall we make a Excel file and put it in the google drive and the people can fill it with content?

Add logos for the website

We need a logo for the SORSE20 webpage

  • favicon added (for the window title)
  • logo added (for the navigation menu bar at the top)

Remove grouping members by national membership

Currently the international conference committee members are grouped by their national membership - and are therefore not shown if they don't belong to a national group. I propose removing this constraint, and to perhaps show all members alphabetically, as some people may not be part of a national group like deRSE.

preview for website?

hey @sdruskat and @Chilipp - I think it might be really useful to have static previews of the site, to make reviewing of the PRs easier. What do you think? If you want to connect the repository to circle, I can take a shot at adding a build that saves static files for preview (we do it for usrse).

Code of Conduct

Please could this go on the website , linked from the landing page across the top menu?

Code of Conduct

We value the participation of each stakeholder and want all participants to have an enjoyable and fulfilling experience. Accordingly, all participants are expected to show respect and courtesy to other participants throughout the events and through all communication channels, including but not limited to the zoom room, zoom webinar, youtube channel, discord platform and the slack channel.

To make clear what is expected, all participants, speakers, exhibitors, organisers and volunteers involved in SORSE are required to conform to the following Code of Conduct. Organisers will enforce this code.

Summary

SORSE organisers are dedicated to providing a harassment-free experience for everyone. We do not tolerate harassment of participants in any form. All communication should be appropriate for a professional audience including people of many different backgrounds.

Be kind to others. Do not insult or put down other attendees.

Behave professionally. Remember that harassment and exclusionary jokes are not appropriate. Do not send any unprofessional messages to other participants, including but not limited to private messages in Slack, Zoom and Discord.

Participants violating these rules may be asked to leave the event at the sole discretion of the SORSE organisers.

Thank you for helping make this a welcoming, friendly event for all.

Clarifications

Harassment includes offensive communication related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.

Participants asked to stop any harassing behaviour are expected to comply immediately.

Be careful in the words that you choose. Remember that words can be offensive to those around you. Offensive jokes are not acceptable at the SORSE events. Excessive swearing is not appropriate.

If a participant engages in behaviour that violates this code of conduct, the SORSE organisers may take any action they deem appropriate, including warning the offender or expulsion from the event and it may affect the offenders' ability to join future events.

Contact Information

If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact any member of the Code of Conduct team:

Claire Wyatt, Software Sustainability Institute, RSE Community Manager, [email protected]

Marion Weinzierl, Durham University,

The Code of Conduct team is happy to assist those experiencing harassment to feel safe for the duration of the event. We value your participation.

Procedure for Reporting Harassment

You can find the Attendee Procedure For Reporting Harassment here.

Acknowledgement

This Code of Conduct was adapted from the example policy for the CW20 and also from the Geek Feminism wiki, created by the Ada Initiative and other volunteers, which is under a Creative Commons Zero license.

(New page - linked from the sentence above "You can find the Attendee Procedure For Reporting Harassment here."

Attendee Procedure For Reporting Harassment

Please contact either member of the Code of Conduct (CoC) team:

Claire Wyatt, Software Sustainability Institute, RSE Community Manager, [email protected]

Marion Weinzierl, Durham University, [email protected]

The CoC team is prepared to handle the incident. Both of our team members are informed of the Code of Conduct policy and guide for handling harassment at the workshop. There will be a mandatory CoC Committee meeting just prior to the series launch when this will be reiterated as well.

Report the harassment incident via private message in Slack or as an email to a member of the CoC team. All reports are confidential.

When reporting the event to a CoC team member, try to gather as much information as available, but do not interview people about the incident. The CoC team member will assist you in writing the report/collecting information.

The important information we need consists of:

    Identifying information (name) of the participant doing the harassing

    The behaviour that was in violation

    The approximate time of the behaviour (if different than the time the report was made)

    The circumstances surrounding the incident

    Other people involved in the incident

The CoC team is well informed on how to deal with the incident and how to further proceed with the situation.

Even though this is an online workshop if at any time you feel that your personal safety is in jeopardy then contact your local Police / law enforcement service.

Acknowledgement

This procedure has been adopted from the Ada Initiative's guide titled "workshop anti-harassment/Responding to Reports”.

Test for CircleCI

I chat with the minimal mistakes maintainer(?) and the suggested approach was to try:

baseurl: /0/SORSE
url: https://8-267395254-gh.circle-artifacts.com

so we should do that.

Create page for Organization Committee

  • #9 closed
  • page/section created
    - [ ] listed in _data/navigation.yml Won't do that as all are on the same page
  • internal link added to _data/committee/committees.yml

Bumping tags and contents in cards view

The hover transition of cards for team members sometimes create a very unappealing effect in terms of break tags, words and layouts.

An example can be seen when hovering over the card of Philipp. I checked this in Safari and Firefox.

This might be an issue with the effect defined in CSS but might also be fixed by adapting contents being rendered.

Where should the committee pages live?

Should we create separate pages such as for the programme subteams? Or should we list them in the contact space, such as the national chapters? Or should we show them at all?

Events - need a calendar/sorted list

Not sure on the best format for this, but we should start the conversation.

We need to list the upcoming events, possibly as a calendar. They should be sorted by date, those that are in the past should be hidden, and it needs to be easy to edit so we can add new events. We'd probably want to advertise the next one or two events on the main page, as well as make it easy to share the events via all the various channels (twitter, email etc).

Anyone got any experience doing something like this within github pages?

Code of Conduct missing

from slack by @ClaireWyatt:

Hello!, we should have a Code of Conduct for our event and on the website (as reminded to me by @sdruskat yesterday) so here is a link to the CoC from the CW20 online workshop earlier this year. Is there a volunteer who has a bit of time to amend this slightly? It really isn't very long and I would do it myself but I'm creating sponsorship packages at the moment and doing research on that. https://www.software.ac.uk/cw20/code-conduct

Volunteers welcomed =)

Add the organization committee members to the website

Don't know how we should do this. Shall we create an Excel table and put it in the google drive and create a folder, where the people can upload their images?

We need to track somehow within this issue (or the excel file), how has already inserted his credentials and who hasn't

Add an Impressum

Should we add an impress to the site? @rainsworth, I remember that you said during the OC call that you have experience with this, right? What should we add for such an international online event?

Create page for website committee

  • #9 closed
  • page/section created
    - [ ] listed in _data/navigation.yml Won't do that as all are on the same page (see #21)
  • internal link added to _data/committee/committees.yml

Create event framework

As a followup on #15, we need to setup a structure for the content of events (see the second PR in #15 (comment)).

We need to add events to the front page, which should show closest the upcoming events, and we need to add a page that shows all events.

@vsoch suggested to use a combination of fullcalendar.io and a collection, where each contribution get's one markdown page (see #37 (comment))). As no one opposed this idea and it also matches what the people talked about today during the programme team call, I think we are good to go @vsoch 😃

shall I come up with some draft PR that contains an events collection with some dummy events and you setup the calendar thing? We are not really in a hurry with this as we do not have submissions, yet

Panel abstract FAQ

I got the following text sent to me from the panels team.

"Please describe your topic, how its is relevant to the RSE community right now, how the topic of the session aligns with the topic of the conference in general, and what is the added advantage of discussing it with the broader audience. For panel discussions, please also mention how the expertises of your plenary speakers will shed light on different aspects of the topic. For open discussion, please list subtopics that can be discussed in breakout groups."

This will need adding into the panel page/FAQ

Wishlist - needs adding as a separate link

Currently if people wish to suggest topics/speakers they're invited to do so within the topic bazaar - but this isn't really the best place for it.

I suggest we create a gwdg pad where we can list suggested speakers and topics, people can then add whatever they like to it. As I'm on the bazaar team, and we said we're happy to look this over every now and then to make sure it's not been defaced/deleted.

I've not created a gwdg pad before so not sure what the best way of doing this is, but I'm happy to do it, if we agree this is a good way forward.

Shorten home nav

I suggest to shorten the home nav item to just "SORSE20", as it takes to much space in the menu.

Should we remove the Google spreadsheet of the organizers?

I am talking about the organizers spreadsheet on the google drive. The deadline to edit it was last Thursday, however some changes have been made since then (see #38).

Shall we remove this Excel spreadsheet? Or update the yml file for the website when there have been changes to the document on google drive (you can configure the document such that you get notified when someone makes changes to it)?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.