diff --git a/_activities/analysisfacilitiesforum.md b/_activities-archive/analysisfacilitiesforum.md similarity index 98% rename from _activities/analysisfacilitiesforum.md rename to _activities-archive/analysisfacilitiesforum.md index 1b4bfc101..b2a30d3ea 100644 --- a/_activities/analysisfacilitiesforum.md +++ b/_activities-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 b/_activities-archive/conditionsdb.md similarity index 97% rename from _activities/conditionsdb.md rename to _activities-archive/conditionsdb.md index 282ccc76e..31541a2cc 100644 --- a/_activities/conditionsdb.md +++ b/_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 b/_activities-archive/differentiablecomputing.md similarity index 98% rename from _activities/differentiablecomputing.md rename to _activities-archive/differentiablecomputing.md index d7ddf8256..e23872e71 100644 --- a/_activities/differentiablecomputing.md +++ b/_activities-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 b/_activities-archive/frameworks.md similarity index 96% rename from _workinggroups/frameworks.md rename to _activities-archive/frameworks.md index 92a280cc8..954cb9846 100644 --- a/_workinggroups/frameworks.md +++ b/_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 b/_activities-archive/visualization.md similarity index 99% rename from _activities/visualization.md rename to _activities-archive/visualization.md index d89d8156c..d6e46e904 100644 --- a/_activities/visualization.md +++ b/_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 b/_activities/dataanalysis.md similarity index 97% rename from _workinggroups/dataanalysis.md rename to _activities/dataanalysis.md index 53ac07841..8315be522 100644 --- a/_workinggroups/dataanalysis.md +++ b/_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 b/_activities/detsim.md similarity index 97% rename from _workinggroups/detsim.md rename to _activities/detsim.md index 846430337..71294de37 100644 --- a/_workinggroups/detsim.md +++ b/_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 b/_activities/generators.md similarity index 98% rename from _workinggroups/generators.md rename to _activities/generators.md index cbd95ed16..2916c3267 100644 --- a/_workinggroups/generators.md +++ b/_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 b/_activities/juliahep.md similarity index 97% rename from _workinggroups/juliahep.md rename to _activities/juliahep.md index bdf8ab25c..a7479eebe 100644 --- a/_workinggroups/juliahep.md +++ b/_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 b/_activities/pyhep.md similarity index 99% rename from _workinggroups/pyhep.md rename to _activities/pyhep.md index 42dcda9e5..078c5a579 100644 --- a/_workinggroups/pyhep.md +++ b/_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 b/_activities/recotrigger.md similarity index 98% rename from _workinggroups/recotrigger.md rename to _activities/recotrigger.md index 02caf27e0..51da5be01 100644 --- a/_workinggroups/recotrigger.md +++ b/_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 b/_activities/toolsandpackaging.md similarity index 99% rename from _workinggroups/toolsandpackaging.md rename to _activities/toolsandpackaging.md index 8f17792a2..1951d5fc8 100644 --- a/_workinggroups/toolsandpackaging.md +++ b/_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 b/_activities/training.md similarity index 100% rename from _workinggroups/training.md rename to _activities/training.md diff --git a/_config.yml b/_config.yml index baff84f53..745c0a836 100644 --- 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 index a04ad9971..ab49fc999 100644 --- a/_includes/navbar.ext +++ b/_includes/navbar.ext @@ -11,16 +11,6 @@ diff --git a/_meetings/hsf-seminars.md b/_meetings/hsf-seminars.md new file mode 100644 index 000000000..8348ba522 --- /dev/null +++ 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:hsf-steering@googlegroups.com) +or any of our [activity area]({{ site.baseurl }}/) coordinators to suggest or +volunteer any topics that you would like to see in future meetings. + +

+HSF-logo +

diff --git a/activity-coordination.md b/activity-coordination.md new file mode 100644 index 000000000..59dea0163 --- /dev/null +++ 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 new file mode 100644 index 000000000..b0f9b0094 --- /dev/null +++ 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 index f06f66500..3b52efe1b 100644 --- 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. diff --git a/images/HSF-logo/hsf-logo-seminar.svg b/images/HSF-logo/hsf-logo-seminar.svg new file mode 100644 index 000000000..4970df0b8 --- /dev/null +++ b/images/HSF-logo/hsf-logo-seminar.svg @@ -0,0 +1,135 @@ + + + + + + + + + + + + + + H + F + + + + HEP Software Foundation + Seminar + + diff --git a/what_are_activities.md b/what_are_activities.md index 7ecd3b445..6d7ecc93b 100644 --- a/what_are_activities.md +++ b/what_are_activities.md @@ -2,29 +2,48 @@ title: "What are activity areas?" author: "Graeme Stewart" layout: default +redirect_from: + - /what_are_WGs.html --- -# Activity Areas and Interest Groups +# HSF Activities -HSF Activity Areas and Interest Groups are led by enthusiasts and -advocates for a particular area of work or of technology -interest and provide a focal point for organising discussions -in the HEP community. They can also cover engagement with -external projects, like Google's Summer of Code. +HSF activities are focused mainly on community led groups that organise around +particular domains with the aim of increasing communication between developers, +providing a platform for discussion of interesting problems and novel solutions +developments, and fostering the adoption of common software between different +communities. -They are less formal, in the HSF, than [working groups]({{ site.baseurl }}/what_are_WGs.html) -and any relevant and reasonable activity for HEP can spawn -an interest group. If you want to put some community-wide -activity under the umbrella of the HSF as an activity areas or interest group -just contact the -[HSF Steering Group](mailto:hsf-steering@googlegroups.com). +Activity areas have multiple conveners (typically three), to help share the +workload, and are appointed by the HSF (via an open nomination process and a +search committee) to serve for one year, with renewal possible by mutual +agreement. We have a [guide]({{ site.baseurl }}/activity-coordination.html) for +conveners about how to organise activities. -Activity areas are added to the website of the HSF, with -description and contact information and will have a dedicated mailing list -and, if appropriate, an Indico category. +We strive for a diverse representation amongst the conveners and a broad +representation of experiments. + +If you want to put some community-wide activity under the umbrella of the HSF, +just contact the [HSF Steering Group](mailto:hsf-steering@googlegroups.com) with +your proposal. + +Activities are added to the website of the HSF, with description and contact +information, and their own [Indico +category](https://indico.cern.ch/category/7972/). + +## Archive + +The HSF has had a number of activities in the past which are no longer active, +but are kept for reference: + +