BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:Europe/Stockholm
X-LIC-LOCATION:Europe/Stockholm
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20190719T085745Z
LOCATION:HG E 1.1
DTSTART;TZID=Europe/Stockholm:20190614T143000
DTEND;TZID=Europe/Stockholm:20190614T150000
UID:submissions.pasc-conference.org_PASC19_sess155_msa236@linklings.com
SUMMARY:Continuous Documentation for Users, Developers and Maintainers
DESCRIPTION:Minisymposium\nComputer Science and Applied Mathematics, Engin
 eering\n\nContinuous Documentation for Users, Developers and Maintainers\n
 \nFrust\n\nThis talk covers the often neglected and “hated” as
 pect of software documentation that is indispensable in a sustainable rese
 arch software development process. A good, up-to-date and easily accessibl
 e software documentation lays the foundation for broader usage and collabo
 ration. Software documentation usually covers three different components: 
 user documentation, instructions how to modify and contribute to the softw
 are and a low-level API documentation. When starting developing a new rese
 arch software, the documentation should be considered from the very beginn
 ing. Maintaining an up-to-date software documentation with good coverage i
 n an exascale ready scientific software stack is only achievable, if the c
 ontribution process clearly includes a check for documentation adding or u
 pdates. This check can only be automated partially and usually requires a 
 manual review process. All contributions must be made with the understandi
 ng, that documentation is a key aspect of any contribution. Things get nev
 er cleaned up later. Recurrent tasks should be automated wherever possible
  to reduce the impact of manual errors, e.g. the deployment of software do
 cumentation. This talk provides a set of best practices for software docum
 entation in science combined with concrete examples from real-world scient
 ific software solutions.
END:VEVENT
END:VCALENDAR