Activities menu and HSF Seminars (#1582)

* Add seminar description Add HSF Seminars to our list of meetings and advertise the first topic * Reorganise activities Drop the distinction between working groups and activities - now everything is an activity Reorganise menus to group activities together and add an archived area for activities which are no longer working * Fix a few dead links Caught by the link checker. Commit missing change to add convener guide to menu. * No unnecessary abbreviation * Add redirects from old page locations * Fix links and spelling * Update activity-coordination.md Co-authored-by: Eduardo Rodrigues <[email protected]> * Apply Eduardo's suggestions from code review Co-authored-by: Eduardo Rodrigues <[email protected]> * Use plural Co-authored-by: Eduardo Rodrigues <[email protected]> --------- Co-authored-by: hegner <[email protected]> Co-authored-by: Eduardo Rodrigues <[email protected]>
HSF · Sep 9, 2024 · 2e39fb8 · 2e39fb8
1 parent c55aa22
commit 2e39fb8
Show file tree

Hide file tree

Showing 22 changed files with 348 additions and 43 deletions.
diff --git a/_activities/analysisfacilitiesforum.md → ...vities-archive/analysisfacilitiesforum.md b/_activities/analysisfacilitiesforum.md → ...vities-archive/analysisfacilitiesforum.md
@@ -2,6 +2,8 @@
 title: Analysis Facilities Forum
 author: Mark Neubauer
 layout: plain
+redirect_from: 
+  - /activities/analysisfacilitiesforum.html
 ---
 
 ## Overview

diff --git a/_activities/conditionsdb.md → _activities-archive/conditionsdb.md b/_activities/conditionsdb.md → _activities-archive/conditionsdb.md
@@ -2,6 +2,8 @@
 title: "Conditions Databases"
 author: "Paul James Laycock"
 layout: plain
+redirect_from: 
+  - /activities/conditionsdb.html
 ---
 
 Discussions between Conditions Database experts across several HEP experiments took place as part of the HSF Community White Paper process in 2016/2017, producing a white paper describing best practice for a Conditions Database schema design: HSF-CWP-2017-03 [(arXiv)](https://arxiv.org/abs/1901.05429). That document provides a starting point for continuing cross-experiment discussions.  The level of consensus across the experiments on guiding principles was very encouraging, with agreement that good design features include:

diff --git a/_activities/differentiablecomputing.md → ...vities-archive/differentiablecomputing.md b/_activities/differentiablecomputing.md → ...vities-archive/differentiablecomputing.md
@@ -2,6 +2,8 @@
 title: Differentiable Computing
 author: Nathan Simpson
 layout: plain
+redirect_from: 
+  - /activities/differentiablecomputing.html
 ---
 
 ## Why make things differentiable?

diff --git a/_workinggroups/frameworks.md → _activities-archive/frameworks.md b/_workinggroups/frameworks.md → _activities-archive/frameworks.md
@@ -1,7 +1,9 @@
 ---
 title: "Frameworks"
 layout: plain
-redirect_from: activities/frameworks.html
+redirect_from: 
+  - /activities/frameworks.html
+  - /workinggroups/frameworks.html
 ---
 
 ## Mandate

diff --git a/_activities/visualization.md → _activities-archive/visualization.md b/_activities/visualization.md → _activities-archive/visualization.md
@@ -5,6 +5,7 @@ layout: plain
 redirect_from: 
   - /workinggroups/Visualisation.html
   - /workinggroups/visualisation.html
+  - /activities/visualization.html
 ---
 
 The Visualisation Activity Area gathers experts, developers, users and all people from the Particle Physics community interested in interactive data visualisation and event displays. 

diff --git a/_workinggroups/dataanalysis.md → _activities/dataanalysis.md b/_workinggroups/dataanalysis.md → _activities/dataanalysis.md
@@ -1,6 +1,8 @@
 ---
 title: Data Analysis
 layout: plain
+redirect_from: 
+  - /workinggroups/dataanalysis.html
 ---
 
 Building on previous work, the Data Analysis Working Group aims to eliminate

diff --git a/_workinggroups/detsim.md → _activities/detsim.md b/_workinggroups/detsim.md → _activities/detsim.md
@@ -1,6 +1,8 @@
 ---
 title: "Detector Simulation"
 layout: plain
+redirect_from:
+  - /workinggroups/detsim.html
 ---
 
 The Detector Simulation Working Group considers approaches to making

diff --git a/_workinggroups/generators.md → _activities/generators.md b/_workinggroups/generators.md → _activities/generators.md
@@ -1,6 +1,8 @@
 ---
 title: "Physics Generators"
 layout: plain
+redirect_from:
+  - /workinggroups/generators.html
 ---
 
 The Physics Generators Working Group is a common forum for discussion and

diff --git a/_workinggroups/juliahep.md → _activities/juliahep.md b/_workinggroups/juliahep.md → _activities/juliahep.md
@@ -2,7 +2,7 @@
 title: JuliaHEP - Julia in HEP
 layout: plain
 redirect_from:
-  - /activities/juliahep.html
+  - /workinggroups/juliahep.html
 ---
 
 The JuliaHEP working group brings together a community of developers and users of [Julia](https://julialang.org) in Particle Physics, 

diff --git a/_workinggroups/pyhep.md → _activities/pyhep.md b/_workinggroups/pyhep.md → _activities/pyhep.md
@@ -2,7 +2,7 @@
 title: PyHEP - Python in HEP
 layout: plain
 redirect_from:
-  - /activities/pyhep.html
+  - /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

diff --git a/_workinggroups/recotrigger.md → _activities/recotrigger.md b/_workinggroups/recotrigger.md → _activities/recotrigger.md
@@ -1,6 +1,8 @@
 ---
 title: "Reconstruction and Software Triggers"
 layout: plain
+redirect_from:
+  - /workinggroups/recotrigger.html
 ---
 
 ## Mandate and Goals

diff --git a/_workinggroups/toolsandpackaging.md → _activities/toolsandpackaging.md b/_workinggroups/toolsandpackaging.md → _activities/toolsandpackaging.md
@@ -6,6 +6,7 @@ redirect_from:
   - /activities/packaging.html
   - /workinggroups/packaging.html
   - /workinggroups/softwaredevelopertools.html
+  - /workinggroups/toolsandpackaging.html
 ---
 
 ## Software Developer Tools

diff --git a/_workinggroups/training.md → _activities/training.md b/_workinggroups/training.md → _activities/training.md
diff --git a/_config.yml b/_config.yml
@@ -15,6 +15,9 @@ collections:
   activities:
     output: true
     permalink: /activities/:title.html
+  activities-archive:
+    output: true
+    permalink: /activities-archive/:title.html
   gsocorgs:
     output: true
     permalink: /gsoc/organizations/:path.html
@@ -42,9 +45,6 @@ collections:
   meetings:
     output: true
     permalink: /meetings/:title.html
-  workinggroups:
-    output: true
-    permalink: /workinggroups/:title.html
   training:
     output: true
     permalink: /training/:path.html

diff --git a/_includes/navbar.ext b/_includes/navbar.ext
@@ -11,16 +11,6 @@
         </div>
         <div class="navbar-collapse collapse" id="navbar-main">
           <ul class="nav navbar-nav navbar-center">
-            <li class="dropdown">
-              <a class="dropdown-toggle" data-toggle="dropdown" href="{{ site.baseurl }}/index.html" id="wg_menu"><span class="glyphicon glyphicon-briefcase"></span>&nbsp;&nbsp;Working Groups<span class="caret"></span></a>
-                <ul class="dropdown-menu" aria-labelledby="activities_menu">
-                  <li><a href="{{site.baseurl}}/what_are_WGs.html">What are HSF working groups?</a></li>
-                  <li class="divider"></li>
-                  {% for workinggroup in site.workinggroups %}
-                    <li><a href="{{ workinggroup.url }}">{{ workinggroup.title }}</a></li>
-                  {% endfor %}
-               </ul>
-            </li>
             <li class="dropdown">
               <a class="dropdown-toggle" data-toggle="dropdown" href="{{ site.baseurl }}/index.html" id="activities_menu"><span class="glyphicon glyphicon-briefcase"></span>&nbsp;&nbsp;Activities<span class="caret"></span></a>
                 <ul class="dropdown-menu" aria-labelledby="activities_menu">
@@ -29,6 +19,9 @@
                  {% for activity in site.activities %}
                    <li><a href="{{ activity.url }}">{{ activity.title }}</a></li>
                  {% endfor %}
+                 <li class="divider"></li>
+                 <li><a href="{{ site.baseurl }}/what_are_activities.html#archive">Archived Activities</a></li>
+                 <li><a href="{{ site.baseurl }}/activity-coordination.html">Convener Guide</a></li>
                </ul>
             </li>
             <li class="dropdown">

diff --git a/_layouts/main.html b/_layouts/main.html
@@ -48,7 +48,7 @@ <h2>Meetings</h2>
     <p>
       The HSF holds <a href="{{ '/future-events.html' | relative_url }}" target="_hsf_indico">regular meetings</a>
       in its activity areas and has bi-weekly coordination meetings as well.
-      All of our meetings are open for everyone to join.
+      All are welcome to join these public meetings and other HSF activities.
     </p>
     <ul class="list list-simple">
 {% assign pagedate = site.time | date: "%Y-%m-%d"   %}
@@ -78,6 +78,16 @@ <h2>JuliaHEP 2024</h2>
       the event with this <a
       href="https://cernbox.cern.ch/s/utykrPvfhl2wUk5">poster.</a>
     </p>
+    <p>
+      As part of the JuliaHEP event we will also have the very first <a
+      href="{{site.baseurl}}/meetings/hsf-seminars.html">HSF Seminar</a>, where Uwe Acosta will
+      present <a href="https://indico.cern.ch/event/1452314/"><em>Julia in
+      high-energy physics: a paradigm shift or just another tool?</em></a>
+    </p>
+    <p style="display: block; text-align: center">
+      <img src="{{ '/images/HSF-logo/hsf-logo-seminar.svg' | relative_url }}"
+      alt="HSF seminar logo" style="width:40%; margin-left: auto; margin-right: auto;">
+    </p>
   </div>
 
 

diff --git a/_meetings/hsf-seminars.md b/_meetings/hsf-seminars.md
@@ -0,0 +1,26 @@
+---
+title: "HSF Seminars"
+author: "Graeme Stewart"
+layout: plain
+---
+
+HEP Software Foundation Seminars are a regular series of monthly meetings for
+the field (usually held on the last Wednesday of a month). The HSF Seminars are
+focused longer form meetings and allow plenty of time for discussion on the
+subject material.
+
+Of particular interest are domain areas in HEP, e.g., event generators,
+simulation, reconstruction and analysis. However, all interesting topics are
+eligible!
+
+The schedule for past and future meetings is published in
+[Indico](https://indico.cern.ch/category/18810/).
+
+You can contact the [HSF Steering Group](mailto:[email protected])
+or any of our [activity area]({{ site.baseurl }}/) coordinators to suggest or
+volunteer any topics that you would like to see in future meetings.
+
+<p align=center>
+<img src="{{ '/images/HSF-logo/hsf-logo-seminar.svg' | relative_url }}"
+  alt="HSF-logo" style="display: inline-block; width:20%; margin:3%">
+</p>
diff --git a/activity-coordination.md b/activity-coordination.md
@@ -0,0 +1,91 @@
+---
+title: "Coordinating an Activity Area"
+author: "Graeme Stewart"
+layout: default
+---
+
+## Being an Activity Convener
+
+The HSF is extremely grateful to members of the community who take on the role
+of convener in our activity areas - *thank you*. Each group engages
+with a different subset of the developer and physics community and thus the
+exact pattern of activities that are organised can vary. It is delegated to the
+conveners to decide the way to organise so that it best serves the needs in
+HEP software and computing as required.
+
+### Meetings
+
+#### Activity Topical Events
+
+That said, organising semi-regular events is very important to keep up momentum
+in a topic and sometimes a series of related events might happen bunched
+together more tightly, e.g., looking at one specific topic from the point of
+view of several experiments.
+
+HSF activity meetings in general should try to:
+
+- be there to help encourage the exchange of ideas and techniques
+- do not need to focus on "finished" items, but rather can be there
+  to provide a community forum for unsolved problems
+- should ensure there is plenty of time for discussion
+- should take notes or minutes for important discussion points (attaching these
+  to Indico is recommended)
+
+#### HSF Seminars and Cross Interest Meetings
+
+Another route for a group is that instead of group specific meetings, organise
+contributors to the [HSF Seminar Series]({{ site.baseurl
+}}/meetings/hsf-seminars.html). These meetings have a regular cadence and would
+usually attract many people who are not particularly experts on the topic, so
+the subjects should be accessible to a general scientific audience.
+
+One other focus that we encourage is to organise events together with other
+groups, e.g., a special session at a workshop, a joint meeting with a software
+development project, a cross-cutting topic that bridges more than one HSF
+activity (our groups are not intended to be silos). These meetings are excellent
+for bringing together people that might not normally talk or know each other.
+They might also fit into a seminar session.
+
+#### Recording Meetings and Minutes
+
+In general, recording *is appropriate* for HSF meetings, which are there to
+foster discussion and collaboration, so *we do recommend it*. There are a lot of
+meetings and we have a worldwide community, so not everyone who is interested
+can join a meeting and recordings can help people to catch-up.
+
+However, you need to make it very clear with the speakers and to participants that:
+
+- The meeting is being recorded and will be made public;
+- And where the video will be posted ([YouTube]({{ site.baseurl }}/organization/youtube.html), [CDS](http://cds.cern.ch/record/2289430), etc.);
+  - Note that it is strongly recommended not to add video files directly into Indico, instead post a link to CDS.
+
+In any case, *please also make sure that meetings are minuted in a concise way*
+(it’s not always the case that people have the time to watch the 60 minute
+video and they need a shorter summary). Minutes can be posted directly onto
+Indico (easy) or to the [HSF website]({{ site.baseurl }}/howto-website.html) (via a PR).
+
+### HSF Affiliated Projects
+
+We strongly encourage the use of common software in the HSF and opportunities
+for common development and sharing should be seized when they exist. The HSF
+exists as a [GitHub organisation](https://github.com/HSF) and is happy
+to host projects to help them grow. This can include things like common
+datasets used in development as well as actual code.
+
+### Coordinator Responsibilities
+
+Our activity conveners should usually dedicate between 5% and 10% of their
+time to running the activity area. More than 10% is great, but we recognise
+that people are busy with many other tasks. Less than 5% and the activity area
+can fall into an inactive state. Conveners should meet at least once a month to
+plan. The HSF Steering Group is always happy to attend to give feedback
+and suggestions.
+
+At least one of the activity conveners should attend the bi-weekly
+[HSF Coordination Meetings](https://indico.cern.ch/category/7970/) and
+give a short update on the group's recent and forthcoming activities.
+
+When the HSF organises [workshops](https://indico.cern.ch/category/7971/)
+activity conveners can give input to the organising team. If there
+will be a session dedicated to matters of relevance to an activity area then
+conveners will be asked to co-organise it.
diff --git a/announcements/_posts/2024/2024-10-01-JuliaSeminar.md b/announcements/_posts/2024/2024-10-01-JuliaSeminar.md
@@ -0,0 +1,12 @@
+---
+title: "Julia in high-energy physics: a paradigm shift or just another tool?, 1 October 2024"
+author: Graeme Stewart
+layout: newsletter
+symbol: glyphicon-calendar
+link: https://indico.cern.ch/event/1452314/
+until: 2024-10-01
+---
+
+On Tuesday 1 October at 16h30, in the very first HSF Seminar, Uwe Hernandez
+Acosta of HZDR will present *Julia in high-energy physics: a paradigm shift or
+just another tool?*.
diff --git a/howto-website.md b/howto-website.md
@@ -84,7 +84,7 @@ entry you can either:
 
 1. Run the interactive script ``scripts/add_training_event.py`` (recommended)
 2. Directly edit the ``_data/trainning-schools.yml`` file and add another entry following the structure of the existing entries (note that events are sorted chronologically by starting date)
-    - There is one very rare thing you may need to do if the URL for the training event 
+    - There is one very rare thing you may need to do if the URL for the training event
       will not validate in the link checker, which is to add the tag `url_proof_ignore: true`
       to the YAML file (an example is a school that used a web technology that insists
       on setting cookies and issues continual redirects without this)
@@ -118,28 +118,29 @@ selected profiles into a page.
 
 As of writing, this website contains the following page templates for wider usage:
 
- * default - every page inherits from this
- * event - to be used for events
- * newsletter - to be used for news items and announcements
- * plain - to be used for standard contents
- * main - the main page w/ boxes
- * minutes - used for meeting minutes (the template adds
-   forward / backward navigation links)
+- default - every page inherits from this
+- event - to be used for events
+- newsletter - to be used for news items and announcements
+- plain - to be used for standard contents
+- main - the main page w/ boxes
+- minutes - used for meeting minutes (the template adds forward / backward navigation links)
 
 ### 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
 automatically.
 
 ### Main page
+
 The main page contains three blocks, mostly hard-coded:
 
-  * A *meetings* block, with links to the minutes of the last three meetings
+- A *meetings* block, with links to the minutes of the last three meetings
     auto-generated
-  * A news item that holds a small snippet of current important information
+- A news item that holds a small snippet of current important information
     (currently this is hard-coded, but it would be better if it were more
       dynamic)
-  * An *activities* block, that serves as an entry point to the main sections
+- An *activities* block, that serves as an entry point to the main sections
     of the website
 
 They are filled with *[Liquid](https://github.com/Shopify/liquid/wiki)* snippets.