Karl Berry wrote:
> not to dynamically emit the current year in the copyright statement?
> ...
> Of course that is different from the Copyright statement on the source
> code for web sites.
>
> As far as I can recall, the FSF (rms) had legal advice to have the
> physical text
not to dynamically emit the current year in the copyright statement?
...
Of course that is different from the Copyright statement on the source
code for web sites.
As far as I can recall, the FSF (rms) had legal advice to have the
physical text "2022" appear in some file that is
For a dynamically created web site such as these is there any reason
not to dynamically emit the current year in the copyright statement?
I have often wondered if there is a reason that web sites don't do
that just as a matter of routine. That would eliminate the need to
update those files every
/etc/savane/content/gnu-content/README says,
Whoops. It did not even occur to me to look :(.
"This repository is obsolete; use the 'frontend/site-specific' directory
of Savane."
That's fine but, just to mention, insufficient in practice. If I had
seen it, it would have taken me
[off-tracker]
On Sat, Jan 01, 2022 at 11:17:37AM -0500, Karl Berry wrote:
>
> The copyright year at the bottom of https://savannah.gnu.org/ (and nongnu) is
> 2019.
>
> It used to be that this was controlled by the files page_header.txt and
> page_footer.txt in content/gnu-content under the
