On 21 April 2018 at 12:57, <j...@apache.org> wrote: > Hi. > > After having studied the solution proposed by Sebb, I have decided to add my > proposal again. > > My proposal has one outstanding TODO: > - add a .htaccess to projects that catches * and redirect to > attic.js?<project>
That needs testing to ensure it works properly. > - change attic.js to use project name instead of a number > Apart from that my solution is working, and seen from the outside the Attic > site is identical, responding to the same url as before. Apart from: The non-project HTML file resolution.html does not use the new list of projects The project/* files don't allow for additional info such as is present in some of the existing XML files The site does not work if a client does not support Javascript > The proposal from Sebb, involves new technology (Jekyll, YAML, bot) as well > as a markdown file pr project and are also working. > > Can we please have an open discussion to choose between these 2 variants and > if needed (which I hope we can avoid) a vote. > > — > My pow: > > JS is not the best solution I preferred PHP, but needed in order to have a > static server side. The JSON embedded in attic.js is valid json, and easy to > extract with a simple sed, should anybody need it. > > The solution from Sebb introduces a number of new technologies, and adds a > bot that runs and eat resources. > > As the one who have done the maintenance the last year, I look for a solution > where we update a single file, and avoid complications (like looking after a > build job). > > — > > Please add your comments and let aim at making a decision this month. > > Have a nice weekend > rgds > Jan I.
