diff --git a/_activities-archive/analysisfacilitiesforum.md b/_activities-archive/analysisfacilitiesforum.md index b2a30d3ea..6425a3a1a 100644 --- a/_activities-archive/analysisfacilitiesforum.md +++ b/_activities-archive/analysisfacilitiesforum.md @@ -8,7 +8,7 @@ redirect_from: ## Overview -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. +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. 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. diff --git a/_activities/dataanalysis.md b/_activities/dataanalysis.md index 8315be522..0bcf55739 100644 --- a/_activities/dataanalysis.md +++ b/_activities/dataanalysis.md @@ -5,7 +5,7 @@ redirect_from: - /workinggroups/dataanalysis.html --- -Building on previous work, the Data Analysis Working Group aims to eliminate +Building on previous work, the Data Analysis Activity Area aims to eliminate the time spent by physicists working on monotonous and laborious tasks while performing physics analysis, and to make the publication of physics results efficient both in terms of human and computing resources. diff --git a/_activities/detsim.md b/_activities/detsim.md index 71294de37..f12ede7da 100644 --- a/_activities/detsim.md +++ b/_activities/detsim.md @@ -5,7 +5,7 @@ redirect_from: - /workinggroups/detsim.html --- -The Detector Simulation Working Group considers approaches to making +The Detector Simulation Activity Area considers approaches to making detector simulation faster and more accurate for HEP experiments. Simulation that produces a traditional digitised detector output, as well as more radical approaches to generate reconstruction or analysis @@ -16,7 +16,7 @@ adaption of simulation techniques to modern computing hardware (covering, e.g., multithreading, vectorisation and different accelerator technologies) are an important area of work. -[Mandate]({{ site.baseurl }}/organization/working-group-mandates.html). +[Mandate for Working Groups from 2018]({{ site.baseurl }}/organization/working-group-mandates.html). The group's meeting page is [in Indico](https://indico.cern.ch/category/10916/) and discussions are held on the [hsf-simulation](https://groups.google.com/g/hsf-simulation) list. diff --git a/_activities/generators.md b/_activities/generators.md index 2916c3267..4a271286a 100644 --- a/_activities/generators.md +++ b/_activities/generators.md @@ -5,7 +5,7 @@ redirect_from: - /workinggroups/generators.html --- -The Physics Generators Working Group is a common forum for discussion and +The Physics Generators Activity Area is a common forum for discussion and technical work on the physics event generators used by HEP experiments. It promotes the collaboration of experimental and theoretical physicists from different experiments and generator teams and of software and computing @@ -13,7 +13,7 @@ engineers, with the aim of having them work together on improving the current codes and production workflows and on making new theoretical advances easier to implement in a computationally efficient way. -The working group was set up as a follow-up of the Physics Event Generator +The group was set up as a follow-up of the Physics Event Generator Computing Workshop that was held at CERN in November 2018, during which an initial program of work in this area was identified. diff --git a/_activities/juliahep.md b/_activities/juliahep.md index a7479eebe..f759a9f05 100644 --- a/_activities/juliahep.md +++ b/_activities/juliahep.md @@ -5,7 +5,7 @@ redirect_from: - /workinggroups/juliahep.html --- -The JuliaHEP working group brings together a community of developers and users of [Julia](https://julialang.org) in Particle Physics, +The JuliaHEP Activity Area brings together a community of developers and users of [Julia](https://julialang.org) in Particle Physics, with the aim of improving the sharing of knowledge and expertise, as well as unify effort in developing Julia packages useful for the community. ## Conveners diff --git a/_activities/licensing.md b/_activities/licensing.md index 243d3cdc5..d5a10a27a 100644 --- a/_activities/licensing.md +++ b/_activities/licensing.md @@ -20,8 +20,8 @@ are compatible. This is a potential problem for the HSF as its goal is to create a software ecosystem where all packages can be combined to address the computing needs of our community. -In Spring 2015, A working group has been formed with people from the community -who had already some experiences with licensing issues. This working group, as +In Spring 2015, An Activity Area has been formed with people from the community +who had already some experiences with licensing issues. This group, as any in the HSF, is open to new participants and contributions. Most discussions so far took place in the HSF Technical Forum (). @@ -37,7 +37,7 @@ be released later if needed. # Forum Mailing List The [hsf-licensing-wg](https://groups.google.com/forum/#%21forum/hsf-licensing-wg) -is the discussion forum for the licensing working group - feel free to post +is the discussion forum for the licensing group - feel free to post any licensing related questions there. # Meetings diff --git a/_activities/pyhep.md b/_activities/pyhep.md index 078c5a579..e4ff380f1 100644 --- a/_activities/pyhep.md +++ b/_activities/pyhep.md @@ -5,7 +5,7 @@ redirect_from: - /workinggroups/pyhep.html --- -The PyHEP working group brings together a community of developers and users of Python in Particle Physics, with the aim of improving +The PyHEP Activity Area brings together a community of developers and users of Python in Particle Physics, with the aim of improving the sharing of knowledge and expertise. It embraces the broad community, from HEP to the Astroparticle and Intensity Frontier communities. # Conveners diff --git a/_activities/recotrigger.md b/_activities/recotrigger.md index 51da5be01..1ef6aa457 100644 --- a/_activities/recotrigger.md +++ b/_activities/recotrigger.md @@ -7,11 +7,11 @@ redirect_from: ## Mandate and Goals -The Reconstruction and Software Triggers Working Group considers +The Reconstruction and Software Triggers Activity Area considers approaches and solutions to common challenges across HEP in the area of event reconstruction and software triggering (e.g., algorithms and data structures designed for online and offline processing of raw detector -data). The working group targets challenges identified during the CWP +data). The group targets challenges identified during the CWP process as well as new ones arising as the state of R&D advances. This forum should foster collaboration on design and implementation challenges, the adoption of common approaches, and raise awareness of @@ -48,7 +48,7 @@ follow our mailing list on google groups [hsf-recotrigger](https://groups.google ## Details -[Mandate and link to other HSF working groups]({{ site.baseurl }}/organization/working-group-mandates.html). +[Mandate for Working Groups from 2018 and link to first HSF Working Groups]({{ site.baseurl }}/organization/working-group-mandates.html). ## Former Conveners - Giulia Casarosa (Belle II, Universita di Pisa), 2022-2023 diff --git a/_activities/toolsandpackaging.md b/_activities/toolsandpackaging.md index 1951d5fc8..21efd083d 100644 --- a/_activities/toolsandpackaging.md +++ b/_activities/toolsandpackaging.md @@ -11,18 +11,18 @@ redirect_from: ## Software Developer Tools -The Software Developer Tools Working Group aims to help the HEP community in developing the latest, modern feature-rich projects +The Software Developer Tools Activity Area aims to help the HEP community in developing the latest, modern feature-rich projects with the aid of software tools such as code editors, static/dynamic code analysers, compilers, debuggers, performance analysers and so on. The group plans to accomplish this by mainly serving as a forum where developers can share their experiences, discuss new/existing tools they utilise, and learn from each other. To that point, contributions from the entire community are strongly encouraged. ## Packaging -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* +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*. ### Packaging Goals -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 +The aim of this group is to foster communication and exchange among the experiments' librarians. We have identified various topics to work on, including 1. Common build recipes and tools 2. How to take most advantage of technologies like containers @@ -30,7 +30,8 @@ The aim of this working group is to foster communication and exchange among the ### Group Activities to Date -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. +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 +group agrees that this effort is being duplicated. We held [an initial series of meetings](https://indico.cern.ch/category/7975/) 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 ### Activities -- The Indico pages for the working group meetings can be found at +- The Indico pages for the group meetings can be found at - For all technical discussions please use (Tools) and (Packaging) ### Former Conveners diff --git a/_activities/training.md b/_activities/training.md index 1b78674f7..5c14a0900 100644 --- a/_activities/training.md +++ b/_activities/training.md @@ -11,7 +11,7 @@ excerpt: none -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. +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. 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. diff --git a/calendar.md b/calendar.md index aa661807d..fd79a722a 100644 --- a/calendar.md +++ b/calendar.md @@ -8,7 +8,7 @@ The HSF [Community Calendar](https://calendar.google.com/calendar/embed?src=e4v3 can be edited by people in the following Google Groups: - [HSF Steering Group](https://groups.google.com/forum/#!forum/hsf-steering) -- [HSF Working Group Conveners](https://groups.google.com/forum/#!forum/hsf-wg-conveners) +- [HSF Activity Area Conveners](https://groups.google.com/forum/#!forum/hsf-wg-conveners) - [HSF Calendar Editors Group](https://groups.google.com/forum/#!forum/hsf-calendar-editors) Google Groups. The most straight forward way to do this is to @@ -25,4 +25,4 @@ Then you will have the ability to view events in the community calendar and, if Please ask to join one of the editing groups if you would like to add events for your experiment or community. -Events in HSF working groups indico categories should be synced automatically. +Events in HSF Activity Area Indico categories should be synced automatically. diff --git a/forums.md b/forums.md index 086cef0a0..2a71bef58 100644 --- a/forums.md +++ b/forums.md @@ -30,20 +30,12 @@ The [hsf-tech-forum](https://groups.google.com/forum/#%21forum/hsf-tech-forum) i 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. -## Dedicated Activities and Working Groups +## Dedicated Activity Areas ----- -Each of the HSF Working groups maintains a dedicated page where contact +Each of the HSF Activity Areas maintains a dedicated page where contact information for that group can be found: - - -And for other HSF activities there are also dedicated pages: -
    {% for activity in site.activities %}
  • {{ activity.title }}
    • diff --git a/get_involved.md b/get_involved.md index cc6203686..0cb97508e 100644 --- a/get_involved.md +++ b/get_involved.md @@ -4,7 +4,7 @@ author: "Benedikt Hegner" layout: default --- -# How to get involved +## How to get involved Our goal is to make every effort going on as transparent and open as possible. Our official communication channel is the @@ -19,14 +19,14 @@ other existing discussion forums. ## Areas for contribution There are plenty of opportunities for you to contribute to the HSF, be it by -participation in technical discussions, by joining one of our working groups, or +participation in technical discussions, by joining one of our Activity Areas, or by joining the HSF with your software project: - * Participation in HSF [working groups]({{ site.baseurl }}/what_are_WGs.html) and [activity areas]({{ site.baseurl }}/what_are_activities.html) - * Participation in [HSF events and meetings]({{ site.baseurl }}/future-events.html) - * Taking advantage of the HSF by identifying your [software project]({{ site.baseurl }}/projects.html) with us - * Giving input to the [HSF Steering Group]({{ site.baseurl }}/organization/team.html) - * Contributing to this website +* Participation in HSF [Activity Areas]({{ site.baseurl }}/what_are_activities.html) +* Participation in [HSF events and meetings]({{ site.baseurl }}/future-events.html) +* Taking advantage of the HSF by identifying your [software project]({{ site.baseurl }}/projects.html) with us +* Giving input to the [HSF Steering Group]({{ site.baseurl }}/organization/team.html) +* Contributing to this website ## Meetings, Agendas and Video-Conferences Access @@ -36,7 +36,7 @@ etc. 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 to many of its services, if you do not have a full CERN account. -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. +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. ## Giving input to the HSF Steering Group diff --git a/howto-profile.md b/howto-profile.md index 9653f0f6c..ce111363b 100644 --- a/howto-profile.md +++ b/howto-profile.md @@ -33,7 +33,7 @@ Either * 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). * 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) -### Working group specific settings +### Activity Area specific settings * To be listed as "educator" on the [training community page]({{ site.baseurl }}/training/community.html) or the [educators page]({{ site.baseurl }}/training/educators.html): * 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). diff --git a/howto-website.md b/howto-website.md index 3b52efe1b..25bd381d5 100644 --- a/howto-website.md +++ b/howto-website.md @@ -61,14 +61,14 @@ HSF Coordination minutes are produced using the live notes approach described ab The only edit required is the replacement of the *front-matter* section by the one present in the previous meeting minutes in Jekyll, updating the title (meeting number and date). -### Adding a working group or activity +### Adding an Activity Area -*Before adding any new activity or proposing a new working group please discuss with the -[HSF Coordination Team]({{ site.baseurl }}/organization/team.html)! We will make sure it gets proposed -in an HSF meeting for approval.* +*Before adding any new activity or proposing a new Activity Area please discuss with the +[HSF Steering Group]({{ site.baseurl }}/organization/team.html)! +We will make sure it gets proposed in an HSF meeting for approval.* -Then, for the technical creation, add a new file in the `_workinggroups` or `_activities` directory. Follow the front-matter of the -other files in there. The `Working Groups` / `Activities` menu in the navigation bar will +Then, for the technical creation, add a new file in the `_activities` directory. Follow the front-matter of the +other files in there. The `Activities` menu in the navigation bar will be updated automatically: the menu entry text is the `title` attribute in the *front-matter* section. ### Adding an event @@ -79,7 +79,7 @@ in there. The [Events](http://hepsoftwarefoundation.org/events.html) page and th ### Adding a training event For *training events* we have a special handling that lists all of these together on the -[Training Working Group page]({{ site.baseurl }}/workinggroups/training.html). To create a new +[Training Activity Area page]({{ site.baseurl }}/workinggroups/training.html). To create a new entry you can either: 1. Run the interactive script ``scripts/add_training_event.py`` (recommended) @@ -128,7 +128,7 @@ As of writing, this website contains the following page templates for wider usag ### Menu bar and automatization The menu bar is defined in `_includes/navbar.ext`, from which all page layouts inherit. -The layout is somewhat hard-coded, but working groups and activities are generated +The layout is somewhat hard-coded, but activities are generated automatically. ### Main page diff --git a/organization/team.md b/organization/team.md index 8c79688bf..f21c8c62c 100644 --- a/organization/team.md +++ b/organization/team.md @@ -5,11 +5,11 @@ layout: plain The HEP Software Foundation Steering Group (SG) is a group of motivated individuals who take responsibility for promoting, guiding and monitoring the HSF’s activities in all areas. They have the role of preserving the HSF’s knowledge and engagement with the community over multiple years and over changes of working group conveners. -The SG takes responsibility for deciding on which working groups and activities that the HSF will engage in, with a view to making the HSF’s activities as beneficial for the HEP community as possible, whilst also respecting and nurturing the HSF’s “bottom-up” philosophy. Input from the Advisory Group is addressed. The SG will meet regularly, once a quarter. +The SG takes responsibility for deciding on which activities the HSF will engage in, with a view to making the HSF’s efforts as beneficial for the HEP community as possible, whilst also respecting and nurturing the HSF’s “bottom-up” philosophy. Input from the Advisory Group is addressed. The SG will meet regularly, at least once a quarter. -Each member of the SG will take responsibility for following at least one HSF activity, e.g., a particular working group, or a workshop or event organised by the HSF. To coordinate with the working groups and the rest of the HSF, SG members should attend HSF Coordination Group meetings. The SG liaisons will ensure that working groups remain active and cross coordinate with related activities; and that topical activities, such as workshops, should arrive at an agreed conclusion, where the outcome is clear, preserved for the future and that any follow-ups are acted on. +Each member of the SG will take responsibility for following at least one HSF activity, e.g., a particular activity, or a workshop or event organised by the HSF. To coordinate with the activities and the rest of the HSF, SG members should attend HSF Coordination Group meetings. The SG liaisons will ensure that activities remain engaged and cross coordinate with related activities; and that topical activities, such as workshops, should arrive at an agreed conclusion, where the outcome is clear, preserved for the future and that any follow-ups are acted on. -The SG will invite new members from amongst the active HSF members and working group conveners in order to ensure a healthy active SG group. When a SG member becomes inactive (e.g., ceases to meaningfully follow any HSF activities) in the HSF they will leave the SG. Normally HSF SG members should serve for about 5 years before stepping down to allow newer members to take over. +The SG will invite new members from amongst the active HSF members and activity conveners in order to ensure a healthy active SG group. When a SG member becomes inactive (e.g., ceases to meaningfully follow any HSF activities) in the HSF they will leave the SG. Normally HSF SG members should serve for about 5 years before stepping down to allow newer members to take over. The SG is convened by a chair, who is elected annually by the group (see below). The chair is responsible for organising the regular SG meetings and ensuring that all HSF activities are followed by members of the SG. The SG organises itself by seeking consensus. If the SG cannot agree on a particular issue, input will be solicited from the HSF Advisory Group and, if appropriate, the wider HSF community. In a last instance, the SG may hold a vote on a particular issue. The SG chair is also responsible for ensuring that SG members are actively fulfilling their role by contributing to the work of the SG (temporary breaks from SG activity in circumstances such as parental leave or illness are allowed). SG meeting minutes are made public, except where a confidential matter has been discussed. @@ -18,7 +18,7 @@ Following the concept of a do-ocracy active contributors to the HSF are invited * Caterina Doglioni - University of Manchester * Peter Elmer - Princeton University * Daniel Elvira - Fermilab -* Benedikt Hegner - CERN / Stony Brook University +* Benedikt Hegner - CERN * Michel Jouvin - IJCLab, CNRS/IN2P3 * David Lange - Princeton University * Paul Laycock - University of Geneva diff --git a/projects/affiliated.md b/projects/affiliated.md index 3980b1ac7..e93f3583b 100644 --- a/projects/affiliated.md +++ b/projects/affiliated.md @@ -23,7 +23,7 @@ Anyone is welcome to engage with the HSF in general and the [HSF Steering Group (SG)]({{ site.baseurl }}/organization/team.html), in particular to discuss the route towards making a software project or package an HSF Affiliated Project or Software. This can be an informal discussion initially. -Formal endorsement is provided by the HSF SG following a short evaluation period in consultation with the relevant HSF Working Group conveners and community experts. For transparency, these evaluations (start, scope and end) are advertised publicly via the HSF Forum, the HSF's main means of communication. +Formal endorsement is provided by the HSF SG following a short evaluation period in consultation with the relevant HSF Activity Area conveners and community experts. For transparency, these evaluations (start, scope and end) are advertised publicly via the HSF Forum, the HSF's main means of communication. The list of HSF Affiliated Projects and Software is hosted in a dedicated area on the HSF website, curated and maintained by the HSF SG. @@ -47,7 +47,7 @@ They are detailed in the document The HSF can organise informal reviews of community projects upon request. Such reviews bring together a group of experts from the community to assess all aspects of a project or software, from requirements to implementation: code, packaging, documentation, etc. -The reviews are organised by the HSF SG in consultation with relevant Working Group conveners. For transparency, these reviews (start, scope and end) are advertised publicly via the HSF Forum, the HSF's main means of communication, and the results are made public. +The reviews are organised by the HSF SG in consultation with relevant Activity Area conveners. For transparency, these reviews (start, scope and end) are advertised publicly via the HSF Forum, the HSF's main means of communication, and the results are made public. ## HSF Requirements and Reference Implementation diff --git a/services.md b/services.md index f82c34999..0e5b39fce 100644 --- a/services.md +++ b/services.md @@ -6,7 +6,7 @@ layout: default # Development Services -Both CERN and Fermilab have expressed willingness to support some development tools and services for the HSF community, once technical issues are worked out. For example, access to [TechLab](https://twiki.cern.ch/twiki/bin/viewauth/IT/TechLab) resources at CERN. In other areas the HSF may provide guidance, recommendations, templates etc. for the use of open source tools. This working group will plan and coordinate activities and service offerings in this area. +Both CERN and Fermilab have expressed willingness to support some development tools and services for the HSF community, once technical issues are worked out. For example, access to TechLab (link no longer available)resources at CERN. In other areas the HSF may provide guidance, recommendations, templates etc. for the use of open source tools. This group will plan and coordinate activities and service offerings in this area. ## TechLab @@ -28,4 +28,4 @@ Responders to the call for TechForum early adopters: ## Resources * [US HEP-FCE Working Group Report on Libraries and Tools]({{ site.baseurl }}/assets/fce-tools-wg-report.pdf) - * [CERN TechLab OpenPower8 and AArch64 Resources](http://lvalsan.web.cern.ch/lvalsan/processor_benchmarking/presentation/) + * CERN TechLab OpenPower8 and AArch64 Resources (link no longer available)