Checklist for event registrations
The event registration tool allows people to easily add their events to our website. On the backend side, this requires a person checking the entries and adding the to our website and the wiki manually.
The process currently looks like the following:
- A person registers an event with the website
A mail containing basic information and two attachments is sent to the Events queue in OTRS, and to the person who registered the event
The first attachment is for the website, e.g. event-20190101-01.en.xml. It is supposed to be uploaded to the directory events/20XX/ in the website.
- The second attachment is for the wiki
In order to make the addition of an event to the website as smooth and flawless as possible, the checklist below will help you to avoid typical mistakes:
- Is the filename correct?
The script names them depending on the given start date, but it could be that there already is an event on the same date with the same file name. In this case, exchange the -01 with -02.
Also, the language of the file is normally set correctly, but check whether (for example) the .en. matches with the language of title and description.
The script automatically adds the front-page tag (<tag>front-page</tag>). Please delete this if the event file is not existent in English. Make sure to check whether a person registered the same event in English in another mail.
Obvious: Check whether the XML syntax is correct. Refer to the automatic syntax check for more information.
- If users put two or more languages into the same registration request, separate them and upload them individually with their corresponding language-tag.
Curate the content
Many users are lazy and they simply copy and paste information from somewhere else. However, we like our events-page to be interesting and easy for our readers to read. To achieve this goal, always check our content policies:
- Only events that are run by or involve the FSFE. For example someone giving a talk at a conference, a booth or a local meeting.
- If the FSFE runs an event (e.g. a community meeting, web-a-thon or similar), do not forget to briefly explain to our readers what the event is about.
- If the FSFE is involved in an event (e.g. someone giving a talk, having a booth etc) we concentrate on what the FSFE is doing at this event. It is ok to explain in one or two sentences what the event is about but the rest is only about our engagement in this event (have a booth, new merchandise, like to talk to people etc)
- Only links to an FSFE activity (e.g. a talk by someone, the local meeting etc like www.conference.com/speakers/talk.html) but not a general link to a conference where we have the booth (like www.conference.com). People will find it in the internet if they are curious and it only leads our readers away from our content.