On 6 May 2018 at 09:58, sebb <seb...@gmail.com> wrote: > On 6 May 2018 at 09:06, Hervé BOUTEMY <herve.bout...@free.fr> wrote: >> Le samedi 5 mai 2018, 17:38:21 CEST Hervé BOUTEMY a écrit : >>> Le samedi 5 mai 2018, 17:24:09 CEST sebb a écrit : >>> > On 5 May 2018 at 16:15, Hervé BOUTEMY <herve.bout...@free.fr> wrote: >>> > > Honestly, who knows or uses the .us and .eu DNS names? >>> > > the requirement seems quite theoretical to me: is not worth making site >>> > > maintenance harder >>> > >>> > I am only suggesting doing it for oltu. >>> >>> honestly, doing it or not just for this one is not critical >>> -0 >> sorry, was angry yesterday: that's human life :) >> >> +1 >> AFAIK, adding 3 DNS entries banner flag files instead of only one won't wreak >> havoc and will improve completeness of the solution >> >> let's do it and continue to move forward > > OK, thanks. > > I'll wait a couple more days in case there are other comments.
No objections so will add the directories. They can be removed later if necessary, e.g. if a better solution is found. >> Regards, >> >> Hervé >> >>> >>> > > but I had a little idea on the flag file creation that could do the job, >>> > > while even simplifying site maintenance = what it is more about >>> > >>> > Automation is for later. >>> >>> when automation adds a big change, yes >>> the idea here is so simple that no need to wait >>> >>> I tested it in my asf-attic.github.io for oltu: >>> https://github.com/asf-attic/asf-attic.github.io/tree/source >>> >>> works like a charm with just a few lines of shell script >>> >>> I didn't take time to create a branch for review here, since this repo is >>> not a real shared repo (and I was lazy) >>> but in normal situation, this would be in a branch so we can discuss if we >>> want to merge the commit, or change it >>> (and now I regret not having created that branch, since it would have been a >>> good demo of discussing before merging... >>> >>> > > since what we need is just to create flag file, why not code the >>> > > creation >>> > > basically in build.sh, in basic shell >>> > > >>> > > with a basic convention like adding XML comments in projects/*.xml: >>> > > <!-- >>> > > retired flag: oltu >>> > > --> >>> > > >>> > > >>> > > build.sh could basically do: >>> > > >>> > > for retired in `grep 'retired flag:' xdocs/projects/*.xml | awk '{ print >>> > > $3 }'` do >>> > > >>> > > for d in $retired $retired.us $retired.eu >>> > > do >>> > > >>> > > mkdir docs/flagged/$d.apache.org >>> > > touch docs/flagged/$d.apache.org/$d.apache.org >>> > > >>> > > done >>> > > >>> > > done >>> > > >>> > > >>> > > I know, I know, that's not very elegant... >>> > > >>> > > But it would ease maintenance just now, isn't it? and as a side effect, >>> > > treat the .us and .eu DNS names... >>> > > (and nobody will cry when reimplementing the feature with a new build >>> > > tool) >>> > > >>> > > Regards, >>> > > >>> > > Hervé >>> > > >>> > > Le samedi 5 mai 2018, 14:39:14 CEST sebb a écrit : >>> > >> The Attic banners are currently added to pages oltu.apache.org >>> > >> However they are not added to oltu.us.apache.org and oltu.eu.apache.org >>> > >> This could be confusing. >>> > >> >>> > >> A simple solution would be to create the directories: >>> > >> >>> > >> xdocs/oltu.eu.apache.org >>> > >> xdocs/oltu.us.apache.org >>> > >> >>> > >> This is not ideal long-term, but at least in the meantime the banner >>> > >> prefixing would work. >>> > >> A better solution can be sorted out later. >>> > >> >>> > >> Are there any objections to creating those directories? >>> > >> >>> > >> S. >> >>
