Update READMEs and SPDX id in UCD

[srl295]

# Unicode Character Database
# Date: 2023-08-28
# Copyright (c) 2023 Unicode, Inc.
# Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the U.S. and other countries.
# For terms of use, see https://www.unicode.org/terms_of_use.html

These should conform to other readmes per unicode-org/.github#6 and policy. Probably something closer to this project's README in https://github.com/unicode-org/unicodetools/tree/main#copyright--licenses

[markusicu]

@srl295 can you please provide the exact lines of text that we should use at the top of our data files?

@Ken-Whistler FYI

[srl295]

I probably need @annebright ’s input on it

The top level readme for this project has:

Copyright © 2001-2023 Unicode, Inc. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries.

The project is released under LICENSE

Perhaps LICENSE could be a link to https://www.unicode.org/license.txt

[markusicu]

The top level readme for this project has:

Do you mean https://github.com/unicode-org/unicodetools/blob/main/README.md ?

Copyright © 2001-2023 Unicode, Inc. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries.

The project is released under LICENSE

Perhaps LICENSE could be a link to https://www.unicode.org/license.txt

Well, it's a copy of that.

I actually assumed that you were talking about the published readmes like

• https://www.unicode.org/Public/15.1.0/ReadMe.txt
• https://www.unicode.org/Public/15.1.0/ucd/ReadMe.txt

We just need specific guidance on which files to say what.
I understand if you want to wait for Anne to return.

[srl295]

I understand, I just meant that the README.md has some already-approved wording. So it's likely to be close to that.

Yes, probably need to wait, and this will be targetting 16 anyway, right?

I see this is already assigned to me, as i assumed!

[markusicu]

Yes, probably need to wait, and this will be targetting 16 anyway, right?

The unicodetools README.md is just in the repo. It does not get copied into the www.unicode.org/Public/ files or anywhere else. We can change it whenever we have better text. And the repo is anyway open for 16.0 work, for files that do go up into Public/.

[annebright]

I've read this chain 3 times and I am still unsure which ReadMes the original question pertains to. But here is my best attempt at answering. If these answers are non-responsive, please clarify the question. If you are talking about any ReadMe in Github, these have ALL been defined in the spreadsheet summarizing the legal language for every Github repo. Please refer to that doc. If you are talking about a ReadMe in any of our directories on the website, we decided to wait until prep for 16.0 to change these, since I am not sure they all need the same language or even any language - I need to get more up to speed on the content of these directories and come up with a solution that is as standardized and simple as possible, not custom language for every file and subfile. Let me know if you have further Qs. I am checking in on work Mon-Wed this week from Zurich. Anne

…

On Thu, Sep 28, 2023 at 2:12 PM Steven R. Loomis ***@***.***> wrote: I probably need @annebright <https://github.com/annebright> ’s input on it The top level readme for this project has: Copyright © 2001-2023 Unicode, Inc. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries. The project is released under LICENSE Perhaps LICENSE could be a link to https://www.unicode.org/license.txt — Reply to this email directly, view it on GitHub <#541 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2S6UI2LEJAGLDEY7XICZWDX4XR3VANCNFSM6AAAAAA5DOKEOU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[annebright]

Whoops - realized I did not link to doc summarizing the legal language for every Github repo - it's here <https://docs.google.com/spreadsheets/d/1k2AOhTLEE1UtkJeawND-8ZdmDvPvbSH0lj5ai2B-QMo/edit#gid=2005994577> . On Sun, Oct 1, 2023 at 5:01 AM Anne Gundelfinger < ***@***.***> wrote:

…

I've read this chain 3 times and I am still unsure which ReadMes the original question pertains to. But here is my best attempt at answering. If these answers are non-responsive, please clarify the question. If you are talking about any ReadMe in Github, these have ALL been defined in the spreadsheet summarizing the legal language for every Github repo. Please refer to that doc. If you are talking about a ReadMe in any of our directories on the website, we decided to wait until prep for 16.0 to change these, since I am not sure they all need the same language or even any language - I need to get more up to speed on the content of these directories and come up with a solution that is as standardized and simple as possible, not custom language for every file and subfile. Let me know if you have further Qs. I am checking in on work Mon-Wed this week from Zurich. Anne On Thu, Sep 28, 2023 at 2:12 PM Steven R. Loomis ***@***.***> wrote: > I probably need @annebright <https://github.com/annebright> ’s input on > it > > The top level readme for this project has: > > Copyright © 2001-2023 Unicode, Inc. Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries. > > The project is released under LICENSE > > Perhaps LICENSE could be a link to https://www.unicode.org/license.txt > > — > Reply to this email directly, view it on GitHub > <#541 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A2S6UI2LEJAGLDEY7XICZWDX4XR3VANCNFSM6AAAAAA5DOKEOU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[markusicu]

@srl295 it sounds like this is about the Readme.md in the GitHub unicodetools repo. Therefore, I am taking it off of the PAG dashboard.

For resolution here, could you send a unicodetools pull request with specific changes?