Change all references to HEP-SF to HSF (HSF#323)

* Change all references to HEP-SF to HSF
* Remove or mask dead/unreliable URLs

Author: graeme-a-stewart

_activities/packaging.md

@@ -49,14 +49,14 @@ The summary of our initial findings is found in the [Technical note on Build Too
 
   * [cet-is](https://cdcvs.fnal.gov/redmine/projects/build-framework/repository)
   * [cmsdist recipes](https://github.com/cmsbuild/cmsdist)
-  * [HEP-SPACK recipes](https://github.com/HEP-SF/hep-spack)
+  * [HEP-SPACK recipes](https://github.com/HSF/hep-spack)
   * [conda recipes by Daniela Remenska ](https://github.com/remenska/root-conda-recipes)
   * [conda recipes by Brett Viren](https://github.com/brettviren/lbne-conda) (deprecated)
   * [aliDist recipes](https://github.com/alisw/alidist)
   * [LCGCMake recipes](https://gitlab.cern.ch/sft/lcgcmake)
 
 # Other resources
 
-  * [HSF Organization on GitHub](https://github.com/HEP-SF)
-  * [HSF cmaketools package ](https://github.com/HEP-SF/cmaketools)
+  * [HSF Organization on GitHub](https://github.com/HSF)
+  * [HSF cmaketools package ](https://github.com/HSF/cmaketools)
   * [Draft Technical Note on Platform Naming Conventions](/technical_notes.html)

_config.yml

@@ -26,5 +26,5 @@ collections:
     permalink: /gsoc/:path.html
 
 docs:
-  url: https://github.com/HEP-SF/documents/blob/master
-  cwp201711: https://github.com/HEP-SF/documents/blob/master/CWP/papers/2017-11
+  url: https://github.com/HSF/documents/blob/master
+  cwp201711: https://github.com/HSF/documents/blob/master/CWP/papers/2017-11

_drafts/nodate-Newsletter-Share.md

@@ -14,7 +14,7 @@ open source licenses.
 or TN in short, are a possibility to share ideas, concepts, or results of discussions.
 They are meant to be informal and inclusive. And can contain any topic you may find relevant
 for the HSF community. The very first HSF TN explains this in detail: 
-[HSF Technical Notes policy](https://github.com/HEP-SF/documents/tree/master/HSF-TN/2015-01).
+[HSF Technical Notes policy](https://github.com/HSF/documents/tree/master/HSF-TN/2015-01).
 
 ## Open Source Licenses
 One of the complex, and always postponed questions is - what license should I use for my software?

_includes/sidebar.ext

@@ -37,7 +37,7 @@ See also <a href='http://hepsoftware.org/?popupmode=Events&popupstate=events'>HE
       <li><a href="http://feeds.feedburner.com/HepSoftwareFoundationNewsletter">RSS feed</a></li>
       <li><a href="http://hepsoftware.org">HEP Knowledge Base</a></li>
       <li><a href="http://it.wikitolearn.org/Main_HSF_Page">HSF on WikiToLearn</a></li>
-      <li><a href="https://github.com/hep-sf">HSF on GitHub</a></li>
+      <li><a href="https://github.com/HSF">HSF on GitHub</a></li>
 
     </ol>
   </div>

cwp-whitepapers.md

@@ -113,9 +113,9 @@ If you have a white paper which you would like to contribute to the CWP process,
 
   * DOE - [High Energy Physics Forum for Computational Excellence: Working Group Reports (I. Applications Software II. Software Libraries and Tools III. Systems)](http://arxiv.org/abs/1510.08545)
 
-<!---  * [HEP-FCE Working Group on Libraries and Tools](http://arxiv.org/abs/1506.01309) --->
-
-  * US Particle Physics Project Prioritization Panel (P5) report: [Building for Discovery: Strategic Plan for U.S. Particle Physics in the Global Context](http://science.energy.gov/~/media/hep/hepap/pdf/May-2014/FINAL_P5_Report_Interactive_060214.pdf)
+<!--- P5 is quite an unreliable URL, perhaps as the download is so huge, so don't check it --->
+  * US Particle Physics Project Prioritization Panel (P5) report: [Building for Discovery: Strategic Plan for U.S. Particle Physics in the Global Context](http://science.energy.gov/~/media/hep/hepap/pdf/May-2014/FINAL_P5_Report_Interactive_060214.pdf){:data-proofer-ignore=""}
+  
 
   * US Snowmass process:
 

cwp/cwp-wg-papers.md

@@ -27,14 +27,14 @@ recommended.
       may find that text is inside a spurious `quote` environment and that some
       odd non-breaking spaces appear. Just delete these.
 1. Adopt the JHEP preprint style, using the template in the
-   [software development paper](https://github.com/HEP-SF/documents/tree/master/CWP/papers/HSF-CWP-2017-13_soft-dev/latex/).
+   [software development paper](https://github.com/HSF/documents/tree/master/CWP/papers/HSF-CWP-2017-13_soft-dev/latex/).
     - Copy the `jheppub.sty` file into your latex area as it is needed for arXiv side compilation.
 1. The paper title should be `HEP Software Foundation Community White Paper Working Group \-- *My Working Group*`.
 1. You will need to add an abstract for arXiv.
 1. Add a copyright and license statement as a comment - we strongly recommend <br>`% Copyright (C) 2018, The HSF Community White Paper authors, licence CC-BY-4.0.`
 1. When finalised/finalising add the document sources to the
   HSF documents github repo,
-  [https://github.com/HEP-SF/documents](https://github.com/HEP-SF/documents), following the
+  [https://github.com/HSF/documents](https://github.com/HSF/documents), following the
   usual pull request workflow. You can ask `hegner`, `eduardo-rodrigues`, `graeme-a-stewart`
   or `jouvin` for a review (best to pick at least two).
     -  Your paper should go into 

events/_posts/2015-04-17-CHEP.md

@@ -135,7 +135,7 @@ Phase 1: requirements and specification, define the problem space well
  * Collect technical input
  * See if defining a common build protocol is doable
 
-Discussion started on GitHub HEP-SF/packaging as issues
+Discussion started on GitHub HSF/packaging as issues
 
  * Can be subscribed/unsubscribed on an issue basis: if subscribed, an email sent for every contribution to the issue
  * Need broader participation!

github-beginners.md

@@ -15,7 +15,7 @@ This pages is a GitHub and Git survival kit for people not familiar with these t
 
 At a first glance, GitHub (and Git) may look complex with their "workflows". But they are not so much in fact. What makes these tools great is that they allow a clear separation between your personal work and what you decide to show or export. Your personal work, unlike with tools like SVN, can be versionned and you can work on different things in parallel (branches) very easily.
 
-In the HSF web site context, what is shared is what is in the project repository called, [hep-sf.github.io](https://github.com/HEP-SF/hep-sf.github.io). Your personal environment is made of 2 parts:
+In the HSF web site context, what is shared is what is in the project repository called, [hep-sf.github.io](https://github.com/HSF/hep-sf.github.io). Your personal environment is made of 2 parts:
 
 * One personal repository on GitHub, called a *fork*. It is typically created using the GitHub web interface, click on the `Fork` button when you are in the project repository. Despite this is a Git repository, you cannot access it directly from you local computer with Git commands (for example, you cannot `git commit` changes made on your local computer to it).
 * One (or several) clone of your personal repository on GitHub. This is where you'll make/develop your changes, using the full versionning capabilities of Git. And until you publish (`git push`) your changes to your personal repository (fork) on GitHub, they are not visible by anybody else. Once in your personal repository, it is potentially visible but you control when you want to submit these changes to the project repository creating a `pull request`: at this point people can review/comment your changes and people with the appropriate permissions can `merge` your changes in the project repository.
@@ -24,7 +24,7 @@ With this *GitHub workflow*, the only repository you need to have write access t
 
 For simple things, there is an alternative to creating a clone on your local computer: you can use the GitHub editor in the web interface. When you save your changes, this commits your changes and you are asked for *commit message*. Note that this is really limited to situations where your contribution is limited to only one file as you cannot edit several files and commit them togheter this way. Apart from the management of the Git clone, there workflow for pushing your changes to the project repository remains the same, using *pull request*.
 
-Sections below give more details on the main steps involved. Examples are based on the HSF web site [repository](https://github.com/HEP-SF/hep-sf.github.io). Note that there is a help available for each Git command that can be displayed with:
+Sections below give more details on the main steps involved. Examples are based on the HSF web site [repository](https://github.com/HSF/hep-sf.github.io). Note that there is a help available for each Git command that can be displayed with:
 
 ```bash
 git help
@@ -43,7 +43,7 @@ Once you have an account, if you want to use the full workflow with a clone of t
 
 As explained in the introduction, this involves 2 steps:
 
-* Creating your personal fork: with your browser, open the HSF web site [repository](https://github.com/HEP-SF/hep-sf.github.io) and click on the `Fork` button at the top-right of page.
+* Creating your personal fork: with your browser, open the HSF web site [repository](https://github.com/HSF/hep-sf.github.io) and click on the `Fork` button at the top-right of page.
 * Creating your local clone of your personal fork (assuming your name is `dupont`: 
 
   ```bash
@@ -58,7 +58,7 @@ As explained in the introduction, this involves 2 steps:
 
   ```bash
   # Later to refer to the project repository, we'll use the remote called upstream
-  git remote add upstream [email protected]:HEP-SF/hep-sf.github.io.git
+  git remote add upstream [email protected]:HSF/hep-sf.github.io.git
   ```
 
 Note that adding a remote adds no information to the repository itself.

gsoc/guideline.md

@@ -10,7 +10,7 @@ layout: default
 
  * Option A: email GSoC administrators: [Sergei Gleyzer](mailto:[email protected]), [Enric Tejedor Saavedra](mailto:[email protected]) and [Antoine Perus](mailto:[email protected]) 
  * Option B (via git): 
-   * fork [git repository](https://github.com/HEP-SF/hep-sf.github.io) 
+   * fork [git repository](https://github.com/HSF/hep-sf.github.io) 
    * add `_gsocproposals/YEAR/proposal_YOURPROJECTyourproposal.md` (for example `proposal_ROOTspark.md`)
    * add a front matter as given in this
    [example](https://raw.githubusercontent.com/hep-sf/hep-sf.github.io/master/_gsocprojects/2018/project_ROOT.md)
@@ -23,7 +23,7 @@ layout: default
 
 Proposals are attached to aproject (e.g. ROOT, CMS...). If you want to add a project for your proposal, you need to create 
 a MD file describing your project in `_gsocprojects/2018` directory (must start with `project_`,
-look at [ROOT project](https://raw.githubusercontent.com/HEP-SF/hep-sf.github.io/master/_gsocprojects/2018/project_ROOT.md) for an example).
+look at [ROOT project](https://raw.githubusercontent.com/HSF/hep-sf.github.io/master/_gsocprojects/2018/project_ROOT.md) for an example).
 This is a very simple file, containing only a *front matter* section that defines the attributes of
 your organization. The 2 mandatory attributes are `project` (your project name) and `layout` (which must be `default`).
 In addition you can use 2 optional attributes:

howto-website.md

@@ -6,7 +6,7 @@ layout: default
 
 ## About the HSF website
 
-This site is maintained by the HSF GitHub [contributors](https://github.com/orgs/HEP-SF/people). If you're interested to become one contact the HSF startup team or any team member. It was set up by Torre Wenaus and Benedikt Hegner.
+This site is maintained by the HSF GitHub [contributors](https://github.com/orgs/HSF/people). If you're interested to become one contact the HSF startup team or any team member. It was set up by Torre Wenaus and Benedikt Hegner.
 
 ## Implementation
 
@@ -19,7 +19,7 @@ A [HSF documentation](/jekyll-beginners.html) provides some useful hints to make
 
 For adding information to this page or improving it, we follow the *[pull request](https://help.github.com/articles/using-pull-requests/)* workflow in GitHub.
 
-Just fork our HSF [website repository](https://github.com/HEP-SF/hep-sf.github.io), edit the
+Just fork our HSF [website repository](https://github.com/HSF/hep-sf.github.io), edit the
 files you want to edit, push them to your fork, and open a pull request.
 
 If you wish (and it is recommended) you can easily set up a local instance of the newsletter site in order to preview your submissions. See the [documentation](https://help.github.com/articles/using-jekyll-with-pages/)