BEGIN:VCALENDAR
VERSION:2.0
PRODID:https://github.com/derhansen/sf_event_mgt
METHOD:PUBLISH
BEGIN:VEVENT
UID:453-1123@news.typo3.com
CLASS: PUBLIC
SUMMARY:Inter-Project Documentation Rendering Code Sprint
DESCRIPTION:On 20 and 21 April 2023, members of at least four open-source p
 rojects will meet at the TYPO3 office in Düsseldorf, Germany, to bring PHP-
 based reStructuredText parsing forward.\n\nThe TYPO3 Core Documentation (Re
 ferences, Changelog, Guides, etc.), as well as the Documentation of many TY
 PO3 Extensions, is based on reStructuredText (reST) for more than ten years
 . \n\nMoving from Python to PHP and Joining Forces\n\nHowever the parsing a
 nd rendering of reST is still done in the Python-based tool Sphinx in the w
 orld of TYPO3 Documentation. This has several shortcomings: We are notoriou
 sly short on Python developers while we do have an abundance of PHP develop
 ers, being PHP based ourselves. The rendering has become slower and slower 
 with the years, as our rendering pipeline has historically grown. It needs 
 a makeover.\n\nBoth Symfony and Doctrine also base their documentation on r
 eST. They face similar challenges, like management of changes across versio
 ns, documentation for third-party packages, etc. \n\nAt the Symfony confere
 nce in Paris in October 2022, Ryan Weaver and Lina Wolf got the idea to kic
 kstart a closer cooperation on documentation infrastructure topics. Their d
 ocumentation is currently based on the doctrine/rst-parser package. Unfortu
 nately there has not been much contribution to their reST parser in the pas
 t years.\n\n“The world of documentors can be a lonely one! Being able to me
 et another team from a similar technology and compare strategies for code b
 locks, examples and maintenance is priceless.” —Ryan Weaver, Symfony\n\nMer
 ging the Fork\n\nThe phpDocumentor project are the ones who set the standar
 d for PHPDoc documentation (starting with /**) that we are using in TYPO3. 
 In 2020, they started working on a fork of the doctrine/rst-parser, and the
  two projects diverged. \n\nThe phpDocumentor reST-parser is integrated int
 o the complete phpDocumentor project that also renders API information for 
 PHP. It can also be run standalone, but it is still in the experimental sta
 ge. \n\nNow we want to bring everyone back together and work on a new and b
 etter version together.\n\n“Documentation is crucial for building maintaina
 ble code, and we're trying to set a new standard with phpDocumentor's reST 
 parser. Collaborating with other maintainers to learn about tooling require
 ments is an invaluable opportunity that I couldn't have imagined. I am exci
 ted to see how this open-source collaboration will shape the future of PHP 
 documentation.” —Jaap van Otterdijk, phpDocumentor\n\nJoin a Sprint With ph
 pDocumentor, Doctrine, Symfony, and TYPO3\n\nOn 20 and 21 April 2023, membe
 rs of the TYPO3, phpDocumentor, Doctrine and Symfony documentation teams wi
 ll meet in Düsseldorf. They will work on a new, stable version of the reST 
 parser and renderer that integrates both forks.\n\n“One of the major benefi
 ts of true Open Source projects is the collaboration between projects, maki
 ng better software and tools while getting to know new like-minded people. 
 It's truly a special experience I can highly recommend.”  —Benni Mack, TYPO
 3 Core Team Lead\n\nIf you are interested in joining the code sprint or the
  development in general, talk to Lina Wolf @linawolf or the #typo3-document
 ation channel in the TYPO3 Slack. You can also find Lina in the Doctrine, S
 ymfony and phpDocumentor Slack. You can also write an email to lina.wolf@ty
 po3.org. \n\nSprint participants must register with Lina Wolf no later than
  Wednesday 12 April 2023. The TYPO3 Documentation Team books hotel and cove
 rs travel costs, lodging, and food for registered participants during the s
 print according to the TYPO3 travel reimbursement regulations.
LOCATION:TYPO3 GmbH
DTSTAMP:20230326T205331Z
DTSTART:20230420T080000Z
DTEND:20230421T140000Z
END:VEVENT
END:VCALENDAR
