On 2025/04/07 21:55:06 sebb wrote: > On Mon, 7 Apr 2025 at 22:15, Hervé Boutemy <hbout...@apache.org> wrote: > > > > Le dimanche 6 avril 2025, 00:17:19 CEST sebb a écrit : > > > > > > If we just change the build script to get its source from such Git > > > > > > branch > > > > > > and commit output to existing svn: > > > > > > https://svn.apache.org/repos/asf/attic/site/docs/ > > > > > > and https://svn.apache.org/repos/asf/attic/site/cwiki_retired/ > > > > > > See else thread. cwiki_retired. > > yes, this was cited, unless there is something I did not understand > > > > > > I don't get what this all means: the concept is that nothing changes in > > > > svn as a result of the build, isn't it? > > > Infra tooling makes use of both source and generated output. > > I suppose this is another way to say the same > > - https://svn.apache.org/repos/asf/attic/site/docs/ > > - https://svn.apache.org/repos/asf/attic/site/cwiki_retired/ > > > > > The reference to SVN is to the SOURCE, which is being proposed for change. > > just call cwiki_retired in svn "output", as a copy of a source somewhere, > > and nothing changes > > > > > > we can also update cwiki_retired to be maintained like flagged: > > - source in https://svn.apache.org/repos/asf/attic/site/xdocs/ > > - output in https://svn.apache.org/repos/asf/attic/site/docs/ > > with copy from source to output done in build.sh > > then we'll have something consistent between the 2 types of flags > > Of course you can move cwiki_retired but then you will have to change > Puppet to use the new location, and make sure there is a smooth > changeover. > You don't appear to have considered that.
of course I considered, please consider I'm reasonable as you are > > Equally, one could move flagged. > If anything is to be moved, I think that would make more sense, as > flagged does not really need to be part of the Attic website, it just > needs to be available to the web server somewhere. > But again this would mean changes to Puppet and planning for a smooth > changeover. I'll do it: having consistent approach will clarify maintenance over time, so it's important for future maintenance by the whole team > > > > > > > There needs to be a plan to ensure that Infra tooling relating to > > > Attic banners can still access the files it needs, and if any of its > > > sources are changed, that there is a plan for how to migrate without > > > breaking anything. > > > > > > I don't know if there are any other references to Attic data files > > > apart from the ones used for adding banners. > > > > > > Have you had a look in the sources for the various Infra tools? > > > I think these are all now in Git repos. > > > > > > Should be easy enough, as there is currently only one Attic repo > > > (though you may need to allow for http(s) and alternate hosts such as > > > svn-master.a.o). > > > > yes, searching for "attic/" gives a good feeling we have everything > > > > https://github.com/search?q=repo%3Aapache%2Finfrastructure-p6+attic%2F&type=code > > No, it does not. > That only searches Puppet code. > What about all the other Infra tools? > Are there any other references? ok, extending the search to the whole org https://github.com/search?q=org%253Aapache+attic%252F&type=code and reviewing: found one interesting additional case: Whimsy with 2 matches: - https://github.com/apache/whimsy/blob/2a48953dbeb6350f5aaccae14873318daffa58a7/repository.yml#L37 - https://github.com/apache/whimsy/blob/2a48953dbeb6350f5aaccae14873318daffa58a7/lib/spec/lib/svn_wunderbar_spec.rb#L85 > > > > > > > > > > Regards, > > > > > > > > > > > > Hervé > > > > > > >
