You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* More on renaning WG to Activity Area
* More renaming
* Yet more renaming
* Yet more renaming
* Updated SG mandate to reflect activities rather than WGs
* Remove broken links
These links are no longer valid, so remove them and note that
they are not available
* Fix additional URLs
* A few final review changes
* Disable false positive link check failures
These are calendar URLs, so they don't work when checked as normal web
pages
---------
Co-authored-by: Graeme A Stewart <graeme.andrew.stewart@cern.ch>
Copy file name to clipboardExpand all lines: _activities-archive/analysisfacilitiesforum.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ redirect_from:
8
8
9
9
## Overview
10
10
11
-
The Analysis Facilities (AF) Forum provides a community platform for those interested in contributing to the development of analysis facilities for use by HEP experiments, serving as a space to develop and exchange ideas. We interpret “development” in the broad sense, including the contribution of ideas from potential end users for functionality to support the analysis of HEP data, specification and planning of the facilities themselves, and technical developments needed to realize AFs. HEP experiments have their own internal processes for developing and deploying AFs; this AF Forum is intended to support and strengthen those efforts by sharing amongst a broader community the key ideas and developments. The AF Forum also collaborates with related [HSF Working Groups]({{site.baseurl}}/what_are_WGs.html), such as the [Data Analysis Working Group]({{site.baseurl}}/workinggroups/dataanalysis.html) and the [PyHEP Working Group]({{site.baseurl}}/workinggroups/pyhep.html), and with [WLCG](https://wlcg.web.cern.ch) and [IRIS-HEP](https://iris-hep.org) projects.
11
+
The Analysis Facilities (AF) Forum provides a community platform for those interested in contributing to the development of analysis facilities for use by HEP experiments, serving as a space to develop and exchange ideas. We interpret “development” in the broad sense, including the contribution of ideas from potential end users for functionality to support the analysis of HEP data, specification and planning of the facilities themselves, and technical developments needed to realize AFs. HEP experiments have their own internal processes for developing and deploying AFs; this AF Forum is intended to support and strengthen those efforts by sharing amongst a broader community the key ideas and developments. The AF Forum also collaborates with related [HSF Activity Areas]({{ site.baseurl }}/what_are_activities.html), such as the [Data Analysis Activity Area]({{ site.baseurl }}/activities/dataanalysis.html) and the [PyHEP Activity Area]({{ site.baseurl }}/activities/pyhep.html), and with [WLCG](https://wlcg.web.cern.ch) and [IRIS-HEP](https://iris-hep.org) projects.
12
12
13
13
The development of future analysis facilities is of great interest to the HEP community, with considerable recent progress. There are numerous ongoing efforts to stand up AFs that utilize new tools and techniques to help make data analysis tasks easier, more performant, and more reproducible.
Copy file name to clipboardExpand all lines: _activities/recotrigger.md
+3-6
Original file line number
Diff line number
Diff line change
@@ -7,11 +7,11 @@ redirect_from:
7
7
8
8
## Mandate and Goals
9
9
10
-
The Reconstruction and Software Triggers Working Group considers
10
+
The Reconstruction and Software Triggers Activity Area considers
11
11
approaches and solutions to common challenges across HEP in the area of
12
12
event reconstruction and software triggering (e.g., algorithms and data
13
13
structures designed for online and offline processing of raw detector
14
-
data). The working group targets challenges identified during the CWP
14
+
data). The group targets challenges identified during the CWP
15
15
process as well as new ones arising as the state of R&D advances. This
16
16
forum should foster collaboration on design and implementation
17
17
challenges, the adoption of common approaches, and raise awareness of
@@ -46,11 +46,8 @@ follow our mailing list on google groups [hsf-recotrigger](https://groups.google
46
46
- Reconstruction+Trigger group meetings: [agendas](https://indico.cern.ch/category/10917/)
47
47
- Reconstruction+Trigger sessions at HOW2019 JLab include discussions on real-time analysis, reconstruction on accelerators, and more: [agenda](https://indico.cern.ch/event/759388/timetable/#20190320.detailed).
48
48
49
-
## Details
50
-
51
-
[Mandate and link to other HSF working groups]({{ site.baseurl }}/organization/working-group-mandates.html).
52
-
53
49
## Former Conveners
50
+
54
51
- Giulia Casarosa (Belle II, Universita di Pisa), 2022-2023
Copy file name to clipboardExpand all lines: _activities/toolsandpackaging.md
+6-5
Original file line number
Diff line number
Diff line change
@@ -11,26 +11,27 @@ redirect_from:
11
11
12
12
## Software Developer Tools
13
13
14
-
The Software Developer Tools Working Group aims to help the HEP community in developing the latest, modern feature-rich projects
14
+
The Software Developer Tools Activity Area aims to help the HEP community in developing the latest, modern feature-rich projects
15
15
with the aid of software tools such as code editors, static/dynamic code analysers, compilers, debuggers, performance analysers and so on.
16
16
The group plans to accomplish this by mainly serving as a forum where developers can share their experiences, discuss new/existing tools they utilise,
17
17
and learn from each other. To that point, contributions from the entire community are strongly encouraged.
18
18
19
19
## Packaging
20
20
21
-
The group has a particular focus also on solutions for building and deploying software stacks, through the evolution of the previous *HSF Packaging Working Group*
21
+
The group has a particular focus also on solutions for building and deploying software stacks, through the evolution of the previous *HSF Packaging Working Group*.
22
22
23
23
### Packaging Goals
24
24
25
-
The aim of this working group is to foster communication and exchange among the experiments' librarians. We have identified various topics to work on, including
25
+
The aim of is to foster communication and exchange among the experiments' librarians. We have identified various topics to work on, including
26
26
27
27
1. Common build recipes and tools
28
28
2. How to take most advantage of technologies like containers
29
29
3. Proper support for developers in our collaborations
30
30
31
31
### Group Activities to Date
32
32
33
-
Software development in high energy physics follows the paradigm of open source software (OSS). Experiments as well as the theory community heavily rely on software being developed outside of the field. Creating a consistent and working stack out of 100s of packages, on a variety of platforms is a non-trivial task. Within the field multiple technical solutions exist to configure and build those stacks. None of this work is experiment specific and our working group agrees that this effort is being duplicated.
33
+
Software development in high energy physics follows the paradigm of open source software (OSS). Experiments as well as the theory community heavily rely on software being developed outside of the field. Creating a consistent and working stack out of 100s of packages, on a variety of platforms is a non-trivial task. Within the field multiple technical solutions exist to configure and build those stacks. None of this work is experiment specific and our
34
+
group agrees that this effort is being duplicated.
34
35
35
36
We held [an initial series of meetings](https://indico.cern.ch/category/7975/)
36
37
to look at the existing build and packaging solutions, including the
@@ -72,7 +73,7 @@ All the coordinators can be reached [by email](mailto:gartung@fnal.gov,nbrei@jla
72
73
73
74
### Activities
74
75
75
-
- The Indico pages for the working group meetings can be found at <https://indico.cern.ch/category/7975/>
76
+
- The Indico pages for the group meetings can be found at <https://indico.cern.ch/category/7975/>
76
77
- For all technical discussions please use <hsf-tech-forum@googlegroups.com> (Tools) and <hsf-packaging-wg@googlegroups.com> (Packaging)
The HSF Training Working Group aims to help the research community to provide training in the computing skills needed for researchers to produce high quality and sustainable software. The group works with experiment training groups, HEP initiatives (such as [IRIS-HEP](https://iris-hep.org/) and [FIRST-HEP](https://first-hep.org/)) and organisations like [Software Carpentry](https://software-carpentry.org/) to coordinate training activities.
14
+
The HSF Training Activity Area aims to help the research community to provide training in the computing skills needed for researchers to produce high quality and sustainable software. The group works with experiment training groups, HEP initiatives (such as [IRIS-HEP](https://iris-hep.org/) and [FIRST-HEP](https://first-hep.org/)) and organisations like [Software Carpentry](https://software-carpentry.org/) to coordinate training activities.
15
15
16
16
The group aims to develop a training program that can be pursued by researchers to achieve the level of required knowledge. This ranges from basic core software skills needed by everyone to the advanced training required by specialists in software and computing.
Copy file name to clipboardExpand all lines: calendar.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -4,18 +4,18 @@ author: "Graeme Stewart"
4
4
layout: default
5
5
---
6
6
7
-
The HSF [Community Calendar](https://calendar.google.com/calendar/embed?src=e4v33e1a1drbncdle1n03ahpcs%40group.calendar.google.com){:target="_hsf_calendar"}
7
+
The HSF [Community Calendar](https://calendar.google.com/calendar/embed?src=e4v33e1a1drbncdle1n03ahpcs%40group.calendar.google.com){:target="_hsf_calendar"}<!-- markdown-link-check-disable-line -->
8
8
can be edited by people in the following Google Groups:
Copy file name to clipboardExpand all lines: forums.md
+2-10
Original file line number
Diff line number
Diff line change
@@ -30,20 +30,12 @@ The [hsf-tech-forum](https://groups.google.com/forum/#%21forum/hsf-tech-forum) i
30
30
This is not strictly an HSF mailing list. The [HEP S&C community mailing list](http://groups.google.com/d/forum/hep-sw-comp) is intended for occasional HEP software and computing community mailings. Everyone involved or interested in HEP S&C is encouraged to sign up to this list. It will be used for occasional mailings of community wide interest, such as announcements of HEP S&C conferences, workshops and schools not strictly related to the HSF.
31
31
32
32
33
-
## Dedicated Activities and Working Groups
33
+
## Dedicated Activity Areas
34
34
-----
35
35
36
-
Each of the HSF Working groups maintains a dedicated page where contact
36
+
Each of the HSF Activity Areas maintains a dedicated page where contact
Copy file name to clipboardExpand all lines: get_involved.md
+8-8
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ author: "Benedikt Hegner"
4
4
layout: default
5
5
---
6
6
7
-
# How to get involved
7
+
##How to get involved
8
8
9
9
Our goal is to make every effort going on as transparent and open as possible.
10
10
Our official communication channel is the
@@ -19,14 +19,14 @@ other existing discussion forums.
19
19
## Areas for contribution
20
20
21
21
There are plenty of opportunities for you to contribute to the HSF, be it by
22
-
participation in technical discussions, by joining one of our working groups, or
22
+
participation in technical discussions, by joining one of our Activity Areas, or
23
23
by joining the HSF with your software project:
24
24
25
-
*Participation in HSF [working groups]({{ site.baseurl }}/what_are_WGs.html) and [activity areas]({{ site.baseurl }}/what_are_activities.html)
26
-
* Participation in [HSF events and meetings]({{ site.baseurl }}/future-events.html)
27
-
* Taking advantage of the HSF by identifying your [software project]({{ site.baseurl }}/projects.html) with us
28
-
* Giving input to the [HSF Steering Group]({{ site.baseurl }}/organization/team.html)
29
-
* Contributing to this website
25
+
*Participation in HSF [Activity Areas]({{ site.baseurl }}/what_are_activities.html)
26
+
* Participation in [HSF events and meetings]({{ site.baseurl }}/future-events.html)
27
+
* Taking advantage of the HSF by identifying your [software project]({{ site.baseurl }}/projects.html) with us
28
+
* Giving input to the [HSF Steering Group]({{ site.baseurl }}/organization/team.html)
29
+
* Contributing to this website
30
30
31
31
## Meetings, Agendas and Video-Conferences Access
32
32
@@ -36,7 +36,7 @@ etc.
36
36
Meetings use the [CERN Indico system](http://indico.cern.ch/category/5816/) for agenda pages. The agenda pages are generally open to the world, and no CERN account is needed. To upload material to Indico you do need to be identified CERN now allows EduGain authentication
37
37
to many of its services, if you do not have a full CERN account.
38
38
39
-
The [Zoom](https://videoconference.web.cern.ch/t/about-the-zoom-cern-service/24) video conferencing system is used for almost all HSF meetings and anyone can participate in the meetings from any internet-connected location. Connection information for each specific Zoom meeting is on the corresponding Indico meeting agenda page.
39
+
The [Zoom](https://videoconference.docs.cern.ch/) video conferencing system is used for almost all HSF meetings and anyone can participate in the meetings from any internet-connected location. Connection information for each specific Zoom meeting is on the corresponding Indico meeting agenda page.
Copy file name to clipboardExpand all lines: howto-profile.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Either
33
33
* If you have specified your [gravatar](https://gravatar.com/) (a free service for global avatar synchornization), we will take your profile picture from there. Else, the profile picture will be taken from your [github](https://github.com) profile (if specified). If the latter is not specified either, you will have a blank profile picture showing an [octocat](https://en.wikipedia.org/wiki/GitHub#Mascot).
34
34
* If you don't know your gravatar email hash, you can [use this page](https://en.gravatar.com/site/check/) (or look [here](https://en.gravatar.com/site/implement/hash/) for more background information about the hashing)
35
35
36
-
### Working group specific settings
36
+
### Activity Area specific settings
37
37
38
38
* To be listed as "educator" on the [training community page]({{ site.baseurl }}/training/community.html) or the [educators page]({{ site.baseurl }}/training/educators.html):
39
39
* Set the `training_roles` field: Zero or more of `instructor`, `mentor`, `facilitator`, `author`. The first three ``training_roles`` are explained [here]({{ site.baseurl }}/training/educators.html). You are an `author` if you've made not-completely-trivial contributions to our training material. Valid examples: ``[]``, ``[instructor, mentor]``. **Invalid**: ``mentor`` (no brackets).
0 commit comments