The linkedin link for Jim Pivarski on https://hepsoftwarefoundation.org/training/community isn't being generated correctly.

I assume something is wrong in https://github.com/HSF/hsf.github.io/blob/master/_educators/jim_pivarski.md
The only think I see is the "null" that perhaps should just be blank.

@klieret ?

hi,

it's more a meta-issue rather than an issue proper...

but could we always rebase a PR before merging it?
this would dramatically reduce the noise in the git history and its associated spaghettification:

$> git l
* a4d837c add first ATLAS proposal
* b1c635a Adding T. Bellembois to mentors
*   7947e13 Merge pull request #119 from sbinet-hsf/gsoc-go-interpreter
|\  
| * 45d5647 gsoc: add GoInterpreter project
* |   d4d4ccd Merge pull request #118 from sbinet-hsf/go-python-gopy
|\ \  
| |/  
|/|   
| * dc1d704 gsoc: add GoPy proposal and GoPython project
|/  
*   f3631fb Merge pull request #117 from oprojects/master
|\  
| * 7b7000c removed parenthesis for (no subscription needed)
| * 51a7bf3 added HSF GSoC mailing list
|/  
* cb6b5b8 Adding a few more mentors
*   03e1348 Merge pull request #115 from felicepantaleo/master
|\  
| * 52afcdb Update and rename proposal_CMSclustershape.md to proposal_CMSinference_code_generator.md
| * 07a2dc3 Update proposal_CMSclustershape.md
| * e9fc11a Create proposal_CMSclustershape.md
| * 6889c59 CUDA smart data structures
* |   832c803 Merge pull request #114 from etejedor/master
|\ \  
| * \   f1ebea5 Merge branch 'master' into master
| |\ \  
| |/ /  
|/| |   
* | |   25b8af7 Merge pull request #116 from oprojects/master
|\ \ \  
| * | | 475025b new line in the introduction
| * | | 9240a0b updated introduction and fixed some proposals with projects
|/ / /  
* | |   5d0930d Merge pull request #113 from etejedor/master
|\ \ \  
* \ \ \   4bf3cb7 Merge pull request #112 from etejedor/master
|\ \ \ \  
| |_|_|/  
|/| | |   
* | | |   5e6edc1 Merge pull request #111 from etejedor/master

that's quite unwieldly...

compare this situation to a (much more complex) repository (Go's), and you get:

$> git l
* e410d2a81e (HEAD -> master, origin/master, origin/HEAD) cmd/gofmt: clear pattern match map at the correct time
* 87ad863f35 runtime: use atomic ops for fwdSig, make sigtable immutable
* 14c2849c3e runtime: update android time_now call
* 48d7199072 cmd/go: clarify that tag lists are space-separated
* 3b84a3c9ac os: make Stdin.Stat() return ModeCharDevice if Stdin is console
* 3f7a35d91c encoding/json: add Valid for checking validity of input bytes
* 1f93ba66d6 math/big: add IsInt64/IsUint64 predicates
* 7bad00366b cmd/internal/obj: remove ATYPE
* 38cb9d28a9 runtime/pprof: document that profile names should not contain spaces.
* a833485828 cmd/compile: do not use statictmp for zeroing
* 8cf1766930 cmd/compile/internal/ssa: use *obj.LSym in ExternSymbol

Just to note we had a glitch on the last merge into the master branch https://github.com/HSF/hsf.github.io/runs/1783028603?check_suite_focus=true

Using markdown-link-check configuration file: .github/config/mdcheck.json
USE_QUIET_MODE: no
USE_VERBOSE_MODE: yes
FOLDER_PATH: .
MAX_DEPTH: -1
CHECK_MODIFIED_FILES: yes
FILE_EXTENSION: .md
FILE_PATH: 
BASE_BRANCH: master
remote: Not Found
fatal: repository 'https://github.com/HSF/hsf.github.io/' not found

Not a great start, sadly!

We want to add additional pages for the training working group. What's the best approach? I could

Option 1

change it so that we can have subpages in the workinggroups directory, i.e.

cd _workinggroups
mkdir training
mv  training.md training/index.md
touch training/something.md

and change the permalink of the workinggroups from /workinggroups/:title.html to /workinggroups/:path.html

Option 2

Have everything training related go to hepsoftwarefoundation/trainingdocs/.., i.e.

mkdir trainingdocs

and add it to _config.yml.

Option 3

Have everything training related (including the training home) in _training and set it up so that hepsoftwarefoundation.org/training goes to the index and hepsoftwarefoundation.org/training/something goes to the respective pages.
I'd add an additional redirect from hepsoftwarefoundation.org/workinggroups/training to hepsoftwarefoundation.org/training to not break any links.

Needs to be done after the renaming of the organization as the repo name must match the organization name. We also need to:

• Update hepsoftwarefoundation.org CNAME (owned/managed by Torre)
• Update the CNAME file in the repo
• Rename repo to hsf.github.io

Follow-up for #323

The last event in the HSF timeline is April 2015. Not fair for the work done in the last months! Need an update with the work, not always visible, to deliver/improve the first HSF services.

Reviewing the draft newsletter proposed by @hegner (https://github.com/HEP-SF/hep-sf.github.io/blob/master/_drafts/nodate-Newsletter-KB.md), I found these minor issues:

• I'd suggest the first part to have title like HSF Status as it is confusing to read things that have nothing to do with the main title (KB).
• Second §: hoping for instead of hoping fore. And there is sort of html comment in the paragraph that is displayed...
• Should the announcement of new versions of ROOT part of the HSF news? May be it would be good to have a section for this in our web site. IMO, this section should be more about "pure" HSF news (else what will be an eligible news from all the HSF-related projects). May be a more HSF-related news could be the started discussions/collaborations between ROOT and WikiToLearn around notebooks for training for example.
• Forthcoming events and job openings: may be add a URL

And we need to add the KB part! Thanks for bootstrapping this!

We are trying to enforce exernal link verification as part of the tests run on the web site. _gsocproposals/proposal_GoInterpreterWagon.md contains a reference to an invalid GitHub organization, https://github.com/gopherds (only gopherd exists but is an empty organization).

The exact error message from the test is:

- ./_site/gsoc/proposal_GoInterpreterWagon.html
  *  External link https://github.com/gopherds failed: 404 No error

@sbinet please, could you fix it or tell us what is the URL to use. This is a blocking issue for PR #133.

We agreed at the HSF coordination meeting that it would be good to implement the floating heads for the convenors of all the WGs, generalising what was done for the training group.

@klieret as the person who did the nice training implementaion can you see how to implement this easily?

I.e.

{% include list_of_selected_training_modules.html ids="unix,git,python,ssh,ml" %}

doesn't mean that the order of the modules in the curriculum is unix, git, python, ssh, ml.

Need to do something a bit more clever in the inclusion script

Currently we advise people to convert from Google Doc to Markdown to put things on the website. We should update this advice to recommend CodiMD for minute taking in the first place.

https://hepsoftwarefoundation.org/jekyll-beginners.html

As there's been a lot of discussion in many communities about the conotations of git's default master branch (which I don't want to repeat here), but I'd like to propose that we rename the development branch of hsf.github.io to main which is a very acceptable alternative.

It's rather easy to do, following instructions like this: https://github.com/github/renaming.

There are several files I've gone through that require grammatical corrections. Doing so would make the contents of the files clear, more readable to newcomers, and improve the delivery of the content.

I'm talking specifically of the tutorial files, which newcomers are likely to click on first when they enter HSF's GitHub.

As discussed in #183 with @hegner and @jouvin , we now have so many external URLs in the HSF website we observe a significant failure rate from

• Websites that are really in downtime for some ~hours
• Temporary timeouts

Immediate retries would help with the later. A nightly check might help with the former.

However, we should be aware that over complicating the infrastructure for doing this would not be a good solution.

Certificate checks against https://rucio.cern.ch have been failing for a while.

I have tracked this down to an old 'by hand' certificate that was installed in the HSF Jekyll container.

After a bit of experimentation I found that there is a problem with the Rucio cert as something in the certificate chain doesn't seem to be installed properly. So I did have to update this and to keep installing it manually in the docker container.

The new container was pushed and it does seem to work now: https://travis-ci.org/HSF/hsf.github.io/builds/499978452.

Currently the template for adding new training Schools looks like this:

---
title:  Alpaka Parallel Programming - Taster Session and Basic Tutorial
source: https://indico.cern.ch/event/858758/
date: 2020-04-27
end_date: 2020-04-27
author: Kilian Lieret
layout: event
categories: Schools
---
[Alpaka Parallel Programming - Taster Session and Basic Tutorial](https://indico.cern.ch/event/858758/)

so the body text is always [title](source).

I think we should automatize this (and not have any body text at all), i.e. only have

---
title:  Alpaka Parallel Programming - Taster Session and Basic Tutorial
source: https://indico.cern.ch/event/858758/
date: 2020-04-27
end_date: 2020-04-27
author: Kilian Lieret
layout: event
categories: Schools
---

because

1. this avoids copy-paste mistakes
2. this is more future proof, e.g. if we want to change the way the links are displayed consistently (add deadlines etc.)

@GuillermoFidalgo

We get consistent failures for a few weeks now with the Rucio website:

- ./_site/gsoc/2018/proposal_ATLASrucio.html
  *  External link https://rucio.cern.ch/ failed: response code 0 means something's wrong.
             It's possible libcurl couldn't connect to the server or perhaps the request timed out.
             Sometimes, making too many requests at once also breaks things.
             Either way, the return message (if any) from the server is: Peer certificate cannot be authenticated with given CA certificates

hi, the "Activities", "Communication" and "About" drop-down menus do not seem to work on iOS.
For some odd reason I -am- able to get the "Projects and Support" to open, but the others do not (AFAICT).

For being a text-heavy page (which we undoubtedly are), our base font size of 16px is unusually small. Most web design pages recommend 18px (or even larger) for such low-interaction websites.

Sources

• learnui.design
• w3-lab.com

I think this would also look much better on this kind of bleak, media deplete layout that most of our sub-pages have. Medium.com for example has even 21px!

We may want to review the team member list in organization/team.md (initially raised in #7).

The link: "discussions are held on the hsf-simulation list" does not work

Page: https://hepsoftwarefoundation.org/workinggroups/detsim.html

Travis is going almost fully commercial and will only offer limited support to open source projects in the future.

I have therefore disabled the Travis webhooks for hsf.github.io, which has disabled Travis runs. The reality is that the link checking became so unreliable (see #184 ) that it was practically useless. In addition, running Travis via webhook was deprecated anyway, in favour of GitHub Apps.

Moving to GitHub actions allows us to look again at how the URL checker runs and to try and improve it to be more reliable.

To avoid future name collisions (we may want to have how-to on other topics). Don't forget to update reference to this page.

We need to update the WG pages with the names of our new convenors for 2020.

QC and Visualisaion should be move (back) to Activities.

The https version of our website does not work, because the certificate is only valid for *github.io and *github.com.

Github have announced that they now support https for custom domain names:

https://blog.github.com/2018-05-01-github-pages-custom-domains-https/

So we should follow the procedure to enable this for HSF (maybe even disable the http version in time).

This might need @wenaus to update our DNS entry.

The calendar page doesn't mention who to contact or how to add an event in the calendar.

@graeme-a-stewart

Travis has been complaining about this for a while:

- ./_site/gsoc/2017/proposal_GoHEPFADS.html
  *  External link https://github.com/go-hep/fads failed: 404 No error
htmlproofer 3.9.1 | Error:  HTML-Proofer found 1 failure!

@sbinet - can you tell us the good URL now (or better, fix in a PR).

Thanks

Hi Mark

In commit 72afdf2 you added two CWP paper links, but you didn't actually add the PDFs to the HSF site, so these are broken links and make Travis look ill for everyone. Can you fix that please?

Thanks

Graeme

The link checker fails all links in recent PRs, see e.g. #1045 👍

All the link check failures seem to be the same kind as yesterday and all false positives. Maybe @klieret has an idea - it seems that {{site.baseurl}} is expanding to an empty string and then the URL checker is trying for an absolute path, instead of a relative one.

This is not strictly an HSF website issue, but...

At the moment adding quotidian HSF meetings (i.e., in Indico) into the HSF Google Calendar is done by hand. This is tedious and error prone.

It would be much nicer to sync this automatically, using the Indico APIs to harvest events and Google APIs to push them into the calendar.

Some care needs to be taken with the sync as we always need to add events into the calendar by hand (e.g., experiment weeks, major conferences and workshops). However, it would be useful if Indico events that update themselves or get cancelled would be reflected in the calendar.

There are a number of persistently failing links now for the link checker, which need to be addressed:

https://travis-ci.org/HSF/hsf.github.io?utm_medium=notification&utm_source=email

Some are real site breakages, others seem to be a certificate issue that needs patched in the docker image.

We have to have far too many manual steps right now for meetings:

• Create Indico.
• Add to community calendar.
• Do a PR to the website for a banner via an “announcement”.

This is tedious, tricky and error prone.

Indico offers (for ages) an export of events from an entire agenda section (e.g., https://indico.cern.ch/export/categ/5816.ics?from=-31d). So I propose that we use this as the “master” source of events. Then try to use a merged view between the classic community calendar and the HSF Indico events.

We should also extract the next 2-3 events for the front page of the website. This would be separare from the classic announcements mechanism, that we will still support.

Might be worth looking at FullCalendar (https://fullcalendar.io/), although that may be too heavy.

I noticed when adding a new redirect that there is an 'automatic' failure in the htmlproofer, because the redirect points to the absolute URL on http://hepsoftwarefoundation.org. Evidently this doesn't work as the PR has not yet been merged.

It may be possible to get jekyll-redirect-from to behave better (not clear from the docs how) or to use a different redirect plugin.

The link for Training roles is broken on the website.

If it's intended to point to Educators, #L138 in hsf.github.io/_workinggroups/training.md can be fixed by changing <a href="h/training/educators.html"> to <a href="educators.html">.

The colors on the training curriculum page are close together in intensity, and use a color scheme that is not very suitable to people with colorblindness. Although the same information is already present in the text (Status: Early development, Status: Beta testing), it may make sense to adopt a visual cue that is independent of color as well.

I played around a bit with repeating gradients to achieve this within the existing color scheme, and came up with this:

The additional modality is the fraction of the rectangle that is filled by foreground color. The 45 degree angled stripes are to hint at e.g. police caution tape.

Here is the relevant css (browser compatibility):

.tm-alpha {
  background-image: repeating-linear-gradient(-45deg, transparent, transparent 20px, #f9f2f4 20px, #f9f2f4 40px);
}
.tm-beta {
  background-image: repeating-linear-gradient(-45deg, transparent, transparent 10px, #f9f9f1 10px, #f9f9f1 40px);
}

I feel that this now distracts a bit too much, but I think a similar approach limited to the border of the rectangles could be effective without adding too much visual clutter.

http://www.hepsoftware.org has been down for ~1 week.

I know @wenaus looked at it already. We should discuss how to fix it here.

We approved having a Conditions DB activity in the coordination meeting of 9 Dec 2021 https://hepsoftwarefoundation.org/organization/2021/12/09/coordination.html. So now we need a page that describes the activity and gives contact information.

The continuous integration is consistenly failing due to this link:

https://nixcon2018.org/ in this post

The url works without https though.

Description of this repo still contains a reference to the old website name.

The HSF front page still lists April and May events:

Should this be updated automatically? There have been website builds since then which should have picked up more recent ical events.

@graeme-a-stewart

Based on the experience during GSoC 2017 project application phase, it would be nice to streamline a little bit more the management of projects and organizations. In particular, it would be nice to be able to add a project or organization without doing anything else than adding its MD page. Currently, it is still necessary to edit the main page to add it to the list. Also organizations have no description on the organization page, conversely to projects. All these flaws could be easily solved if the organizations and projects were turned into Jekyll collections (one for projects, one for organizations. Then it would be very easy to generate the list from the collection with a small Jekyll template (basically a for loop over the projects/organizations if we accept to sort them alphabetically).

Main things to be done are:

• Convert projects and organizations to Jekyll collections
• Generate the project/organization list on the main page with a Jekyll template: this includes adding in the project/organization front-matter an icon and a summary attribute.
• On the organization page, display before the project list either the description attribute if present or the summaryone (mandatory for the main page). Very similar to what is already done for project in _includes/gsoc_project.ext.
• To improve readability on mobile devices, turn into an item list the proposal list built in _includes/gsoc_project.ext and _includes/gsoc_proposal.ext (to be renamed _includes/gsoc_organization.ext).

I'd suggest that for latin words like forum, we say forums rather than fora when plural. One visible occurence is in the Activities menu.

The licensing working group page is a stub and needs extension.
@jouvin - I believe that could be something for you.

Hi-
I notice some 2019 vs 2020 errors on the recent HSF meeting minutes as shown on the hsf home page.. I don't think I have time to look in the next week so thought I would report it..

eg

It would be nice to have "next meeting" "previous meeting" links on the minutes, as navigating through them is right now a bit of a pain.

_activities/cwp.md has a few updates needed - simulation and reco, e.g.

In 2018, support for multiple GSoC years has been added to proposal management. It is based on a subdirectory per year in every GSoC-related collection/directory. One of the drawback is that year selection when building the proposal list per project or per organization is based on this directory structure, meaning that organizations and projects have to be redefined every year. In particular for organizations, this doesn't really make sense and result in file/information duplication. Suggested improvements are:

• support for organizations and projects that are not specific to one year. This requires a way to select the year we are interested to when asking the proposal related to a project/organization.
• Allow to list a multi-year list of proposals per project or organization, grouped by year

One possibility could be to create a project or organization page with all the projects for every year organized by section (year) with an anchor name which is the year and to add this anchor to the URL associated with the list of proposals in the main page so that the project/organization page is open directly at the relevant section.