Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd blog post on SC19 events #113
Conversation
@@ -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.
This comment has been minimized.
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.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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. |
This comment has been minimized.
This comment has been minimized.
Would be great to put the date before the link and title, and organize BOF/Panel/Tutorial (and other) via subheaders instead. |
This comment has been minimized.
This comment has been minimized.
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. ] |
This comment has been minimized.
This comment has been minimized.
I also think having this by date is more important than by type of event |
This comment has been minimized.
This comment has been minimized.
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! |
This comment has been minimized.
This comment has been minimized.
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. |
This comment has been minimized.
This comment has been minimized.
Hmm good point! For the order of bullets then, maybe sort by type, or in chronological order? |
This comment has been minimized.
This comment has been minimized.
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? |
This comment has been minimized.
This comment has been minimized.
That sounds |
This comment has been minimized.
This comment has been minimized.
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. |
This comment has been minimized.
This comment has been minimized.
Oops, the indentation didn't come out right for the date headers. Will fix... |
This comment has been minimized.
This comment has been minimized.
okay, so some questions:
|
This comment has been minimized.
This comment has been minimized.
Good catch on the mixed-up links. This would be so much easier if the links actually included the words from the title. |
This comment has been minimized.
This comment has been minimized.
@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. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I can't remember - are we requiring 1 or 2 approvals for blog posts? |
This comment has been minimized.
This comment has been minimized.
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! |
This comment has been minimized.
This comment has been minimized.
Sounds good. |
This comment has been minimized.
This comment has been minimized.
lgtm |
This comment has been minimized.
This comment has been minimized.
Thanks @danielskatz and @cferenba - merging. |
cferenba commentedOct 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'm assuming that new blog entries are not intended to have changelog entries - if not let.me know.
cc @usrse-maintainers