BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.adass.org//adass2026//speaker//8MXX3M
BEGIN:VTIMEZONE
TZID:AWST
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1;UNTIL=20051231T160000Z
TZNAME:AWST
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:STANDARD
DTSTART:20070325T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:AWST
TZOFFSETFROM:+0900
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20071028T030000
RRULE:FREQ=YEARLY;BYDAY=4SU;BYMONTH=10;UNTIL=20081025T190000Z
TZNAME:AWDT
TZOFFSETFROM:+0800
TZOFFSETTO:+0900
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-adass2026-D8BZUJ@pretalx.adass.org
DTSTART;TZID=AWST:20261104T173000
DTEND;TZID=AWST:20261104T183000
DESCRIPTION:Astronomical software thrives on collaboration. Many collaborat
 ions\, however\, are created around funded projects and remain active only
  for as long as that funding continues. When the funding ends\, the collab
 oration often ends with it\, while the software and its users remain.\n\nT
 he consequences can be that software becomes unmaintained or former partne
 rs continue development independently\, creating diverging forks which cau
 ses duplicated effort and uncertainty for new users and contributors. At t
 he same time\, the cross-institutional networks built during these project
 s disappear\, networks that provide opportunities for discussion and groun
 ds for future collaboration.\n\nCommunity collaborations such as Astropy a
 nd the IVOA demonstrate that this is not inevitable. They show that sustai
 nable collaboration can be achieved through a variety of ways of working a
 nd funding. \n\nThis BoF will explore what makes such collaborations last 
 and why others fail. The session will be centered around a panel discussio
 n with a panel of experts and  the audience. We will explore questions inc
 luding: What enables a collaboration to survive? Which governance and main
 tenance models work in practice? How should responsibility be shared betwe
 en individuals and institutes? And which warning signs indicate that a col
 laboration is unlikely to remain sustainable?\n\nOur aim\, with this discu
 ssion\, is to identify commonalities between successful projects\, or what
  makes some initiatives less successful at remaining a long-lasting collab
 roration. If the outcome of the discussion permits\, we intend to summaris
 e those points and submit them as an entry in the proceedings\, as a refer
 ence.
DTSTAMP:20261116T153720Z
LOCATION:Seminar Room 4
SUMMARY:Beyond the grant: keeping astronomical collaborations alive - Yan G
 range\, Janneke de Boer\, Kim Hoogenberg
URL:https://pretalx.adass.org/adass2026/talk/D8BZUJ/
END:VEVENT
BEGIN:VEVENT
UID:pretalx-adass2026-WP89MK@pretalx.adass.org
DTSTART;TZID=AWST:20261104T173000
DTEND;TZID=AWST:20261104T183000
DESCRIPTION:Astronomy is entering an era in which several major facilities 
 are simultaneously operating\, or standing up\, science platforms designed
  to deliver petabyte-scale data and computing to their communities. As mis
 sions and observatories move from data collection to data delivery at scal
 e\, they are independently converging on similar architectural choices —
  and independently running into similar operational challenges — around 
 federated access\, compute-to-data\, authentication\, and long-term sustai
 nability. This BoF is proposed by confirmed panelists from Euclid/ESA Data
 labs\, Vera Rubin Observatory\, the SKA Regional Centre Network (SRCNet)\,
  Roman Telescope\, CADC/CANFAR\, NASA/Fornax and LOFAR. Other platforms ar
 e invited to join the discussion to compare architectures\, operational le
 ssons\, and user-facing services for large-scale science platforms and wor
 kflows.\n\nWith Euclid's Data Release 1 (DR1)\, a full year of Vera Rubin 
 Observatory operations\, the launch of the Roman Space Telescope\, and SKA
  Low's science verification getting underway next year\, the timing is ide
 al to take stock of what's working\, what isn't\, and where the community 
 could converge — on topics such as federated data access\, compute-to-da
 ta models\, interoperability standards\, and the balance between bespoke p
 latform development and shared infrastructure. Panellists will open the se
 ssion with a short position statement on how their platform is architected
  and operated today\, before the floor opens to a moderated discussion aim
 ed at surfacing common challenges and concrete opportunities for collabora
 tion across observatories.
DTSTAMP:20261116T153720Z
LOCATION:Seminar Room 1
SUMMARY:Science Platforms at Scale: Developing Data Services in the Petabyt
 e Era - Javier Ballester Arenas\, Yan Grange\, Marcos López-Caniego\, San
 dor Kruk\, Jesus Salgado\, William O Mullane\, Michele Delli Veneri\, Rosi
 e Bolton\, Brian Major\, Carmen Toribio\, Christophe Arviset
URL:https://pretalx.adass.org/adass2026/talk/WP89MK/
END:VEVENT
BEGIN:VEVENT
UID:pretalx-adass2026-WXU3NL@pretalx.adass.org
DTSTART;TZID=AWST:20261105T104800
DTEND;TZID=AWST:20261105T110000
DESCRIPTION:LOFAR is one of the largest radio interferometers in the world\
 , and the largest in the lower frequencies. In the first decade of its exi
 stance\, the development has focused on the instrumental capabilities\, wh
 ich over the years have led to many discoveries and sky surveys.\n\nThe cu
 rrent development focus is on the migration from the first generation of L
 OFAR to LOFAR 2.0\, which is planned to start observations in 2027. The LO
 FAR 2.0 development has two focal points. First of all\, improving the cap
 abilities of the instrument itself so that more instrumental modes can be 
 used to increase the scientific capabilities. The second focus\, which is 
 relevant for this contribution\, is making the output data and the end-use
 r facing services around the execution of the observational process more a
 ccessible\, to support the astronomy community at large making use of our 
 telescope.\n\nIn this contribution we will present how the different user-
 facing services are being built in an integrated way. We do this by applyi
 ng a uniform look-and-feel for the end user between proposal writing\, pro
 ject management\, up to the user ingest of processed data. On top of this\
 , we make sure the different services are also technically integrated\, so
  that a single action flow can be done from within the same interface\, an
 d use common services like Federated AAI infrastructure which supports use
 r authorisation across applications.
DTSTAMP:20261116T153720Z
LOCATION:Seminar Room 2
SUMMARY:Towards a unified data infastructure for LOFAR 2.0 - Yan Grange
URL:https://pretalx.adass.org/adass2026/talk/WXU3NL/
END:VEVENT
END:VCALENDAR
