Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add blog post on SC19 events #113

Merged
merged 6 commits into from Oct 5, 2019

Conversation

@cferenba
Copy link
Member

commented Oct 4, 2019

Description

Adds a blog post with information on SC19 RSE events.

Motivation and Context

There have been several questions about SC, so we wanted to gather all the information in one location.

Checklist:

  • I have posted the link for the PR in the usrse slack (#website) to ask for reviewers
  • I have previewed changes locally
  • I have updated the CHANGELOG and (if necessary) the README.md

I'm assuming that new blog entries are not intended to have changelog entries - if not let.me know.

cc @usrse-maintainers

_posts/2019-10-04-SC19.md Outdated Show resolved Hide resolved
@@ -28,4 +28,4 @@ Several additional sessions may be of interest to RSEs:

Finally, we're also planning to arrange an informal RSE gathering (or more than one?) during the conference - details are TBA. We hope to see you there!

(See the [SC19 website](https://sc19.supercomputing.org/) for more details. Note that schedules are subject to last-minute changes. Thanks to Sandra Gesing and Dan Katz; their URSSI newsletter article provided several of the items on this list.)
(See the [SC19 website](https://sc19.supercomputing.org/) for more details. Note that schedules are subject to last-minute changes. Thanks to Sandra Gesing and Dan Katz; their [URSSI newsletter](https://mailchi.mp/9ff12a24ee11/urssi-september-2019-newsletter) article provided several of the items on this list.)

This comment has been minimized.

Copy link
@danielskatz

danielskatz Oct 4, 2019

Collaborator

(See the [SC19 website](https://sc19.supercomputing.org/) for more details. Note that schedules are subject to last-minute changes. Thanks to the [URSSI newsletter](https://mailchi.mp/9ff12a24ee11/urssi-september-2019-newsletter) for providing several of the items on this list.)

- Workshop: [3nd International Workshop on Software Correctness for HPC Applications (Correctness 2019)](https://sc19.supercomputing.org/?post_type=page&p=3480&sess=sess118), Monday, Nov. 18
- Students@SC: [Modern Software Design, Tools, and Practices](https://sc19.supercomputing.org/?post_type=page&p=3479&id=pec109&sess=sess410), Monday, Nov. 18
- BOF: [Extreme-Scale Scientific Software Stack (E4S)](https://sc19.supercomputing.org/?post_type=page&p=3480&sess=sess269), Tuesday, Nov. 19
- BOF: [Ask.CI, the Q&A Platform for Research Computing - Recent Developments](https://sc19.supercomputing.org/session/?sess=sess274), Tuesday, Nov. 19

This comment has been minimized.

Copy link
@vsoch

vsoch Oct 4, 2019

Member

hooray!

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 4, 2019

If you take a look at the preview: https://265-120906408-gh.circle-artifacts.com/0/usrse.github.io/2019-10-04-SC19/index.html

I want to suggest (so the spacing is cleaner) to have each of the bullets in the format:

That way, there is some consistent lining up of the elements - right now since the title is second (and date at the end) my eyes are jumping and rolling around a bit.

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 4, 2019

Also, instead of having a small header per entry, why not have sub headings? E.g., instead of:

Do like

Panels

Birds of a Feature

And you could do italic or bold, depending on your preference! It's a little cleaner to look at, and easier to digest (because there is a lot of content on that page!)

@vsoch vsoch self-requested a review Oct 4, 2019
Copy link
Member

left a comment

Would be great to put the date before the link and title, and organize BOF/Panel/Tutorial (and other) via subheaders instead.

@cferenba

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2019

I like your idea of moving the dates first - will do.

I'm hesitant to do subheaders in the way you suggest, for a couple of reasons: it loses chronological order, and it overshadows my grouping of directly-RSE vs. of-interest-to-RSE events. But how about something like this:

Research Software Engineering sessions

[ etc. ]

Other sessions of interest to RSEs

[ etc. ]

@danielskatz

This comment has been minimized.

Copy link
Collaborator

commented Oct 4, 2019

I also think having this by date is more important than by type of event

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 4, 2019

I think you could still do it by date, and then by type of event. Imagine that someone is opening up their phone to check the page - they would first want to see quickly the date (the top heading) but then they would want it to be cleanly grouped by the type of event (at least I would). I see no reason we can't take advantage of the ability to have multiple levels of headers, and support both of these needs!

@cferenba

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2019

There are few enough events on each individual day that I don't think two levels of sorting would add much value. But adding a section for each date should be fine.

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 4, 2019

Hmm good point! For the order of bullets then, maybe sort by type, or in chronological order?

@cferenba

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2019

So what I'm thinking is, sections for directly-RSE events vs. related events; subsections by date; then bullets sorted in chronological order within each subsection, with the event type in italic or bold. How does that sound?

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 4, 2019

That sounds 👌

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 4, 2019

Oh wow this looks so much better! https://266-120906408-gh.circle-artifacts.com/0/usrse.github.io/2019-10-04-SC19/index.html

Let me go through and check all the links, then I should be good to approve.

@cferenba

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2019

Oops, the indentation didn't come out right for the date headers. Will fix...

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 4, 2019

okay, so some questions:

  • I think the link to "Developing and Managing Research Software in Universities and National Labs" might be wrong - it goes to a session page with a different title.
  • I just noticed the indentation too :)
  • " Getting Scientific Software Installed" links to the other one I think!
@cferenba

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2019

Good catch on the mixed-up links. This would be so much easier if the links actually included the words from the title. 🙁

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 4, 2019

@cferenba it's done robot style! The web robots can just read the titles from the cached pages in the browser - us lowly humans have to actually navigate to visually see them.

@vsoch
vsoch approved these changes Oct 4, 2019
@cferenba

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2019

I can't remember - are we requiring 1 or 2 approvals for blog posts?

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 4, 2019

We could probably do 1, but since @danielskatz already has commented let's wait for him to look it over again (and give approval). We want to make sure his concerns are fully addressed so we don't have to do another PR!

@cferenba

This comment has been minimized.

Copy link
Member Author

commented Oct 4, 2019

Sounds good.

@danielskatz

This comment has been minimized.

Copy link
Collaborator

commented Oct 5, 2019

lgtm

@vsoch

This comment has been minimized.

Copy link
Member

commented Oct 5, 2019

Thanks @danielskatz and @cferenba - merging.

@vsoch vsoch merged commit 50aed56 into USRSE:master Oct 5, 2019
3 checks passed
3 checks passed
greeting
Details
ci/circleci: build-site Your tests passed on CircleCI!
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.