Hi. Le mer. 22 janv. 2025 à 12:57, Maxim Solodovnik <solomax...@gmail.com> a écrit : > > Please NOTE 1.27 from here: https://summerofcode.withgoogle.com/rules :)
Thanks for this reminder. In the other thread[1], Piotr mentioned > 1. Moving from SVN to Git should be easy. > 2. Converting from a variety of formats to Asciidoc can also be done > almost automatically. > 3. Replacing `maven-site-plugin` with Antora can reuse the work done in > Log4j. > 4. Proofreading and expanding the documentation is the part that really > takes time. So point 4 is clearly off limits. But what about the others? Also, Gary mentioned: > Also, if someone is thinking about doing this, they better be ready to > take on updating and testing our Maven Commons Release Plugin which > checks in the site and deliverables to Subversion. Is this provision sufficient for this to be a valid GSoC project? [IIRC (?), the plugin is coded in Java.] Clearly, there will also be work with "git", "svn" and "maven" (for updating the website management). How to make sure that moving around the documentation is not misconstrued as a "documentation" project? Gilles [1] https://lists.apache.org/thread/jocfdbnzbb9hfx1cx2dxtmcsbbbsffpo --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
