Update bad links

2015-11-sc15-bof/bof-notes.md

@@ -34,7 +34,7 @@ _Special thanks to the note-takers: Neil Chue Hong, Mike Heroux, Lois Curfman Mc
 Book on software engineering for computational science and engineering due in 2016 (Jeff Carver, Neil Chue Hong, editors)
 * [WSSSPE](http://wssspe.researchcomputing.org.uk/) working group putting together best practices
 * [IEEE Software](http://www.computer.org/web/computingnow/software): Rajiv Ramnath, editor who is interested in SW papers
-* [Computing in Science and Engineering](http://www.computer.org/web/computingnow/cise) (CiSE) [Software Engineering Track](http://www.computer.org/cms/Computer.org/ComputingNow/docs/2016-software-engineering-track.pdf),  Jeff Carver and Damien Rouson editors (new)
+* [Computing in Science and Engineering](http://www.computer.org/web/computingnow/cise) (CiSE) [Software Engineering Track](https://www.computer.org/digital-library/magazines/cs/track-calls-for-papers#Software%20Engineering),  Jeff Carver and Damien Rouson editors (new)
 
 ### What about testing?
 

2016-11-sc16-bof/bof-notes.md

@@ -31,8 +31,7 @@ using math when everyone else isn’t”
 
 Formal Verification group at University of Utah:
 
-<http://formalverification.cs.utah.edu/new/> *→ A shorter link is*
-<http://www.cs.utah.edu/fv>
+~~formalverification.cs.utah.edu/new/~~
 
 *Archer tool for data race detection in OpenMP*
 
@@ -84,7 +83,7 @@ workshops with qualified instructors and helpers.
 Challenges: discoverability, Architecture-specific training, Evolving
 technologies, discipline-specific needs
 
-<https://github.com/hpccarpentry>
+~~github.com/hpccarpentry~~ --> <https://www.hpc-carpentry.org/>
 
 ### Jason Maassen, Netherlands eScience Center
 

2017-11-sc17-bof/bof-notes.md

@@ -41,7 +41,7 @@ excerpt: "SC17 BoF: Software Engineering and Reuse in Computational Science and
 * Info session will be on Dec 11. 2017
 
 
-#### NumFOCUS & Sustainable Software: <https://bit.ly/nf-sustainability> 
+#### NumFOCUS & Sustainable Software: ~~bit.ly/nf-sustainability~~
 * Funding a big factor, but not the only one
 * NumFocus sustainability program connecting people and projects and develop and provide training, common infrastructure
 * Strategic approach to funding across all projects rather than each project going out on their own.
@@ -89,16 +89,16 @@ excerpt: "SC17 BoF: Software Engineering and Reuse in Computational Science and
   - You can get a DOI for your code by depositing in Zenodo (can automatically do this if code in Github see: <https://guides.github.com/activities/citable-code/>)
   - Tools coming up like <http://citeas.org/> to make it easier for researchers to cite software
 * Places you can publish software
-  - <https://www.software.ac.uk/resources/guides/which-journals-should-i-publish-my-software>
-  - <https://bssw.io/resources/how-to-publish-cse-software>
+  - <https://www.software.ac.uk/top-tip/which-journals-should-i-publish-my-software>
+  - <https://bssw.io/items/where-and-how-to-publish-cse-software>
 * What should we learn from the experimental community? e.g. they don’t cite their equipment vendor. Also, how far down the rabbit do we go? However, there is a difference between providence and citation.
 * Is there a good enough approach to reproducibility?
 *	Value in knowing what you did and documenting it
 *	Reproducibility will never be perfect, will decay over time. What’s the sensible length of time? 
 * Software Heritage (softwareheritage.org) will be useful in future for when people want to cite software, but developers don’t want to get a DOI for software
 * Mantid software example of software which gives different DOI for each version, updates author list: <https://www.mantidproject.org/Main_Page>
 * Re-science journal: <http://rescience.github.io/>
-* Konrad Hinsen / software collapse: <http://blog.khinsen.net/posts/2017/01/13/sustainable-software-and-reproducible-research-dealing-with-software-collapse/>
+* Konrad Hinsen / software collapse: <https://blog.khinsen.net/posts/2017/01/13/sustainable-software-and-reproducible-research-dealing-with-software-collapse.html>
 
 How do you get user feedback? How do you know you are serving your audience?
 * FLASH created a database of publications created with FLASH code, created an easy way for people to submit their papers, make it easy to find out where it’s being used / find out those with vested interest to continue code
@@ -109,7 +109,7 @@ How do you get user feedback? How do you know you are serving your audience?
 How do you promote your software?
 * Need to go to where your users are, e.g. scientific conferences where they are presenting results, technical contacts in industry, people coming to your training course
 * What are people doing with respect to training? Of the audience some people offering training courses. Webinars were highlighted (not statistically significant but small number); tutorial offerings on Cloud+Jupyter.
-* Mozilla Foundation / Mozilla Science Lab runs open science training / guidance to make your projects more open: <https://science.mozilla.org/resources>
+* Mozilla Foundation / Mozilla Science Lab runs open science training / guidance to make your projects more open: <https://wiki.mozilla.org/ScienceLab>
 * FLASH experience: the more complexity needed, the more users you get
 * Ambassadors for the open source project to get out there and engage with the user community; build trust and continuity. Research in book ‘Diffusion of innovations” (Everett Rogers) backs this up. YouTube lecture by Everett Rogers also recommended: <https://www.youtube.com/watch?v=j1uc7yZH6eU>
 * Don’t want to release too early, as bad press can last a long time

2018-11-sc18-bof/bof-notes.md

@@ -9,7 +9,7 @@ excerpt: "SC18 BoF: Software Engineering and Reuse in Computational Science and
     *   Many initiatives need funding -- so it would be good to capture ROI from existing initiatives (UK SSI is the obvious, hoped for, source for this :-) )
 *   Conceptualizing a US Research Software Sustainability Institute (URSSI)
     *   Could community activities also include "collaborative community activities" such as code reviews, (a la Karthik Ram's BDSC initiative [I might have the name/acronym wrong])?
-        *   Yes, this is possible. Please suggest it on the [URSSI discuss board](https://discuss.urssi.us) or email (Dan)
+        *   Yes, this is possible. Please suggest it on the ~~URSSI discuss board~~ or email (Dan)
 *   HPC Carpentry: open source, hands-on HPC training
     *   Will the HPC Carpentry build on HPC University, or feed into the HPC Certification efforts?
     *   Will this be an intro to HPC, or will it also include (or grow to include) skills to use petascale and more advanced and specialized systems?

2021-11-sc21-bof/bof-notes.md

@@ -7,7 +7,7 @@ The organizers prepared a number of topics for possible discussion in breakout g
 
 ## Computational Science Ecosystems
 
-**Related Lightning Talk:** [Ecosystems are the Future!](https://betterscientificsoftware.github.io/swe-cse-bof/2021-11-sc21-bof/01-brown-ecosystems.pdf)
+**Related Lightning Talk:** [Ecosystems are the Future!](https://betterscientificsoftware.github.io/swe-cse-bof/assets/2021-11-sc21-bof/01-brown-ecosystems.pdf)
 
 **Participants:** Ben Brown, Mike Heroux, Saswata Hier-Majumder, Lois Curfman McInnes, Bill Miller
 
@@ -24,7 +24,7 @@ The organizers prepared a number of topics for possible discussion in breakout g
 
 ## Training Programs
 
-**Related Lightning Talk:** [The Internat. CSE Master Program at TUM](https://betterscientificsoftware.github.io/swe-cse-bof/2021-11-sc21-bof/03-bader-masterprogram.pdf)
+**Related Lightning Talk:** [The Internat. CSE Master Program at TUM](https://betterscientificsoftware.github.io/swe-cse-bof/assets/2021-11-sc21-bof/03-bader-masterprogram.pdf)
 
 **Participants:** Anshu Dubey, Nasir Eisty, Dan Katz, Marion Weinzierl
 
@@ -47,7 +47,7 @@ The organizers prepared a number of topics for possible discussion in breakout g
 
 ## FAIR4RS: Finability, Accessibility, Interoperability, and Reusability for Research Software
 
-**Related Lightning Talk:** [FAIR 4 Research Software (FAIR4RS)](https://betterscientificsoftware.github.io/swe-cse-bof/2021-11-sc21-bof/05-barker-fair4rs.pdf)
+**Related Lightning Talk:** [FAIR 4 Research Software (FAIR4RS)](https://betterscientificsoftware.github.io/swe-cse-bof/assets/2021-11-sc21-bof/05-barker-fair4rs.pdf)
 
 **Participants:** Michelle Barker, Rinku Gupta, Jean Sexton, Henri ?
 
@@ -74,7 +74,7 @@ The organizers prepared a number of topics for possible discussion in breakout g
 
 ## Reproducibility
 
-**Related Lightning Talk:** [Highlights from the IEEE CS Ad Hoc Committee on Open Science & Reproducibility](https://betterscientificsoftware.github.io/swe-cse-bof/2021-11-sc21-bof/06-parashar-openscience.pdf)
+**Related Lightning Talk:** [Highlights from the IEEE CS Ad Hoc Committee on Open Science & Reproducibility](https://betterscientificsoftware.github.io/swe-cse-bof/assets/2021-11-sc21-bof/06-parashar-openscience.pdf)
 
 **Participants:** Sandra Gesing, Pat Grubel, Axel Huebl, Ulf Schiller, Peter Vaillancourt