coderefinery / coderefinery.org Goto Github PK

It is not clear to users where these are operated and who maintains these.

Aalto case study:

• Two workshops at Aalto University so far. 45 signups and attendance of >35 for both. This is with limited advertisement, because they fill up too quickly.
• Second workshop fully invited at Aalto's initiative. Partner: Aalto Science-IT.
• Second workshop required minimal preparation: simply reviewing material the night before.
• Future plans include two workshops per year + integration with summer HPC training program.
• Aalto provides one instructor and catering
• Model extendable to other universities: invited workshops to key audiences. University possibly provides one instructor for second and later workshops, CR helps with training. Less traveling needed.

Text I got from Maiken:

The Nordugrid ARC software package recently migrated from the Apache Subversion
version control system to GitLab hosted by Coderefinery. Nordugrid ARC is a
software product which enables computing clusters around the world to connect
to the World Wide Large Hadron Collider Computing Grid (WLCG).

With GitLab we now not only have a version control system (git), but also a
very good platform for discussing changes to the source-code, performing
automatic build upon commits, and setting up a testing infrastructure. We are
using GitLab extensively now, and plan to expand the automatic deploy and
testing that GitLab offers in the near future.

We need something on the website.

I got the feedback that researchers browse our websites and conclude that this is not for them since they are not "developers" but "only" write scripts.

Motivate with use cases: "are you doing one of these things?"

This is to make it easier for people to move.

• Latitude/longitude should be part of the workshop metadata and the map autogenerated.
• Past/future workshops should have different color.

Also demonstrate distribution across disciplines.

On https://coderefinery.org/about/ the text for Bjørn and Max gets covered by the pictures of Stefan and Thor. Probably just need to increase vertical spacing

There is a lot of good stuff there. Just that we don't forget. @rkdarst

All the mugshot pictures have a manually set height:262.5px but fixed aspect ratio (just a max-width) so they can become narrower when the viewport is small.

Points we should mention (thanks to @rkdarst):

• why collected, types of data, who shared with (we probably say anonymous form only). Your data only comes from what you decide to provide to us. You will never be affected by this data except as given here.
• my own invention but likely matches with our philosophy: right to register anonymously.
• how long stored (x months after workshop, x years, 5 years?)
• if you believe something is wrong, let us know.
• if you want to be removed from announcement list, let us know. workshop registration can be canceled before and removed, otherwise we keep it for survey.
• We always keep affiliations and academic position long term for reporting
• right to lodge complaint with supervisory authority (way too complex for us, but OK)
• if you want access to your data or to be removed, email us from the address you have used for registration (also a bit complex for us, but OK)
• When attending a workshop, we use external services and guide you to register for accounts in them. We don't control this data, and this is not required to take part in the workshop.

GitLab pages now serve via *.pages.coderefinery.org. Currently only HTTP. TLS is in the works.

Not on any subdirectory.

http://coderefinery.org/repository/moving/

We should generalize and link to similar recipes that describe how to move from other GitLab/GitHub/etc repositories.

@Sabryr can you please list your presentation from May 12?

Say that at least say there will be one workshop in Helsinki region sponsored by Aalto science-IT at least every year.

• https://coderefinery.org/partners/
• https://coderefinery.org/

I've received a tip that it's confusing to clump together workshops and other types of events on the Workshops page. The sections now are "Upcoming events", "Planned workshops", and "Past workshops and events", so probably another section "Upcoming meetings" (or similar) should be added, and change "Past workshops and events" to "Past events"

@Jyrsa can you please add your presentation title for the talk you held at NORDUnet workshop, 12-15 September 2017, Copenhagen, here: http://coderefinery.org/outreach/

Thank you!

To explain more what we want to achieve, and how we plan to become sustainable.

I think both go together well.

For instance here we have a link "Python":
http://coderefinery.org/workshops/2018-06-12-oslo/

But somebody who has Python (2) already, will not click on it and not figure out that we need Python 3 or Sphinx or any of the other Python dependencies.

• Lund
• Oslo
• Tromsø
• DeiC conference
• NORDUnet conference
• Dalton meetings
• DIRAC meetings
• Metacenter meeting
• NorduGrid 2017 conference

the links for resources in https://coderefinery.github.io/documentation/01-motivation/ are corrupted.

what's the point of this section? It mostly describes what Computerome does...

So that the workshop page does not look like we are stopping operations.

Also show that it is possible to "save" a specific version by forking it and pushing a tiny change to it (to trigger build).

there's a lot of nice and useful stuff being said in answering the question "What else has changed in how you write code for your research after attending a CodeRefinery workshop?"

We could include quotes on the front page. Any comments on that? I can start working on it now

Very interesting initiative.

Hosting institutions can contact us if they wish to host a CodeRefinery workshop.

I will take care of that ...

And in which aspects we don't. It is a FAQ.

Seems to be a unexpected character or tab/space

This needs a clean-up, add relevant links, remove irrelevant ones.

To be added:

• http://wssspe.researchcomputing.org.uk
• https://bssw.io
• https://softdev4research.github.io/recommendations/

On company websites, staff is commonly listed under an "about" page. We should do the same i think

In workshop requirements we need to emphasize that the room needs space to walk between tables so that we can access participants with questions.

Looks like very good collection of best practices.

1. https://github.com/coderefinery/coderefinery.org/blob/gh-pages/_includes/js.html#L1-L2