Den fre 4 juli 2025 kl 02:11 skrev Nathan Hartman <hartman.nat...@gmail.com >:
> On Thu, Jul 3, 2025 at 3:28 PM Daniel Sahlberg < > daniel.l.sahlb...@gmail.com> wrote: > >> Den tors 3 juli 2025 kl 21:04 skrev Nathan Hartman < >> hartman.nat...@gmail.com>: >> >>> > >>> ============================================================================== >>> > --- serf/site/publish/doap.rdf (original) >>> > +++ serf/site/publish/doap.rdf Thu Jul 3 18:45:08 2025 >>> > @@ -13,7 +13,7 @@ >>> > (the "License"); you may not use this file except in compliance >>> with >>> > the License. You may obtain a copy of the License at >>> > >>> > - http://www.apache.org/licenses/LICENSE-2.0 >>> > + https://www.apache.org/licenses/LICENSE-2.0 >>> > >>> > >>> Hi, >>> >>> There might be an error here: the approved text for the license header >>> [1] >>> uses http://, not https://. Perhaps we should ask the board to consider >>> approving using https:// and document it as such at [1], but until >>> then... >>> we have to be careful with search-and-replace. :-) >>> >>> [1] https://www.apache.org/licenses/LICENSE-2.0#apply >>> >>> The rest looks good to me... >>> >> >> That is a good catch! I'm aware of it and I should probably have been >> more clear about this in the commit message. >> >> This is actual content of the output of the DOAP generation tool linked >> by Dave in a recent thread on members@: >> https://projects.apache.org/create.html >> >> I don't think there was any way I could have caused this myself, thus, I >> committed the file as-is. >> >> Cheers, >> Daniel >> > > > Thanks for clarifying. So, I guess we should request an update to the > official license header text. Then we can update all http to https, here > and in Subversion, and not have to worry about accidental replacements in > the license headers. WDYT? > That would probably be good - or if the DOAP generation tool is wrong, ComDev should revert it to http. Can you take care of this? I'm focusing on building/testing ATM. Cheers, Daniel
