On Sat, 18 Jan 2025 at 17:18, Gilles Sadowski <gillese...@gmail.com> wrote: > > Le sam. 18 janv. 2025 à 17:22, Gary Gregory <garydgreg...@gmail.com> a écrit : > > > > On Sat, Jan 18, 2025 at 11:05 AM sebb <seb...@gmail.com> wrote: > > > > > > On Sat, 18 Jan 2025 at 15:03, Gilles Sadowski <gillese...@gmail.com> > > > wrote: > > > > > > > > > > TL;DR; Quite some time ago, INFRA offered the possibility to move > > > > > > the website(s) under "git" control. Is this related? > > > > > > If not, and there is a big change, should we reconsider the move? > > > > > > > > > > This is not related AFAICT. > > > > > > > > > > Moving the sites to git would not remove the need to use Subversion to > > > > > manage releasing components since there are other bits and pieces that > > > > > are in Subversion. > > > > > > > > > > For example, https://dist.apache.org/repos/dist/release/commons/ is > > > > > under Subversion > > > > > > > > I don't mind using subversion for this; it has nothing to do > > > > with moving to "git" for managing the web sites. > > > > > > Someone would need to work out how to migrate all the websites. > > > > > > Components don't have their own sites; they are subdirectories of the > > > main site. > > > > > > These all have to be merged together, which was quite tricky to set up. > > > > > > Changing this is not going to be easy. > > > > > > I don't know if it would be possible to migrate individual components, > > > or whether it would be necessary to do them all at once to avoid > > > breaking things. > > > > > > Is anyone offering to do this work? > > > And fix any issues that occur? > > > > What problem are we wanting to solve here? > > One problem is the mix of SVN (for the site itself) and > git (for the source code).
The site source is in Git in the same repos as the component. [Apart from the DORMANT and SANDBOX components.] At present the generated sites are committed to SVN. AIUI there is no technical reason why the generated output should not be in Git as well. It's obviously possible to merge multiple components into a single site in Git, as that is what Logging does. The issue here is how to migrate everything across. Can it be done piecemeal? > AFAIK the migration is supposedly a progress and will > perhaps be better supported by tools provided by INFRA. > A likely consequence could be a better separation of > contents and layout, and a website with a nicer look. That does not follow, unless the website is redesigned. > Just compare > https://logging.apache.org/ > with > https://commons.apache.org/ > There is no advantage that those sites look so different. ??? > It's not a priority task, for sure, but if someone can pull > it off, it would be great IMHO. > > > Especially considering > > Subversion is still needed to manage releases. > > That's not a reason for not migrating; otherwise, no > project would have done so. Agreed, that is irrelevant. > Regards, > Gilles > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
