Things new IRIS-HEP team members need to do

New IRIS-HEP team members need to do some number of things to get connected. This webpage documents the things that need to be done. If you find there are steps not mentioned here, or missing/unclear information, please contribute an improvement!

IRIS-HEP website

active: true
- <primary focus area(s), a list>
institution: <Your University>
name: <Your name>
photo: /assets/images/team/<First name>-<Last name>.jpg
shortname: <Your GitHub user ID>
title: <Can be blank - will show a title under your picture>
website: <Optional, your website>
  - title: How to make green eggs and ham
    date: 2018-09-10
    meeting: ROOT 2018 Users Workshop
    project: greeneggs
    focus-area: as
    location: Virtual
  • Add your GitHub username to the proper university file. Note that you will not show up in the full team page if you are not in a university file!


  • Have an existing team member add your email address to the IRIS-HEP Slack team.
  • Subscribe to the relevant Google mailing lists, at the very least “IRIS-HEP Full Team” and “IRIS-HEP Announcements”.


There is a section for presentations in the file you created above. We would like to keep track of the presentations made by IRIS-HEP team members, with the following criteria:

  • Only presentations related to IRIS-HEP itself should be included.
  • Any presentation in a “public” meeting should be included. This includes presentations made in experiment meetings, even if they are protected such that the presentation and meeting links are not world visible.
  • Presentations in the IRIS-HEP topical meetings should be included.
  • Minor presentations in internal “working” meetings of IRIS-HEP do not need to be added.
  • Presentations, lectures, etc. as part of training events should be included.
  • Posters at workshops and conferences can also be included. You can add “(poster)” at the end of the title. Include a link to a pdf of the poster.

The meaning of the fields is the following:

  • title - the title of the talk: you made need to place it in double quotes if certain characters like a colon space “: “ are included in the title.
  • date - the date on which the presentation was made, in the numeric format “YYYY-MM-DD”.
  • url - this should be a direct URL to the presentation or page containing the presentation. For Indico, link to the contribution, not the PDF or other links.
  • meeting - the name of the meeting.
  • meetingurl - the URL for the meeting in which the presentation was made.
  • location - optionally list the location of a meeting if it was a workshop or dedicated gathering. Meetings that are mostly in Vidyo can use “Virtual”.
  • focus-area - optionally list the relevant focus area for this presentation, using its short name, i.e. one of [ia,ssl,ssc,doma,as,osglhc,blueprint,core]. Can be a list, leave blank if none.
  • project - optionally list the relevant project for this presentation, using its short name, i.e. those found in the pages/projects/ area. Can be a list, leave blank if none.