CLDR-14010 Bulk replace http -> https

[KOLANICH]

CLDR-14010

Bulk replace http -> https for the websites known supporting it using HTTPSEverywhere ruleset.

Was applied using https://github.com/KOLANICH-tools/https-everywhere-py/tree/bulk_replace tool (as a byproduct of debugging the tool).

Some human reviewing was done and some dead links were replaced with more alive analogues and some sites known to have https but that are not in the rulesets were also fixed in some places. Also for some files the changes have been reverted, mostly for the ones copyed from external sources.

CLA won't be signed, but you can consider the contribution as the one in public domain. Also it is likely that it is below the threshold of originality since it is a result of just applying the software and some mechanistic procedures.

Anyway, if you don't want to accept the PR, you can use the tool linked to make a your own PR.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[srl295]

@KOLANICH Interesting and good work! Comments:

• we'll ned a bug for the PR title and commit message
• Some files are external, automatically generated, etc. so may need to be excluded.

[srl295]

CLA won't be signed, but you can consider the contribution as the one in public domain. Also it is likely that it is below the threshold of originality since it is a result of just applying the software and some mechanistic procedures.

Please consider signing the CLA so we can evaluate this contribution.

[KOLANICH]

we'll ned a bug for the PR title and commit message

Could you create it for me?

Some files are external, automatically generated, etc. so may need to be excluded.

I have tried to avoid them in manual checking phase. If you see the files in which fixes need to be reverted, please name them.

[srl295]

we'll ned a bug for the PR title and commit message

Could you create it for me?

https://unicode-org.atlassian.net/browse/CLDR-14010

(you can just write CLDR-14010 within the repo, it's linked)

Some files are external, automatically generated, etc. so may need to be excluded.

I have tried to avoid them in manual checking phase. If you see the files in which fixes need to be reverted, please name them.

/docs/rfc is an IETF RFC and shouldn't be changed here

anything in the /data/ subdirectory is mostly external data sources and should be left alone.

[KOLANICH]

https://unicode-org.atlassian.net/browse/CLDR-14010 (you can just write CLDR-14010 within the repo, it's linked)

Thanks. I have edited the head post.

/docs/rfc is an IETF RFC and shouldn't be changed here anything in the /data/ subdirectory is mostly external data sources and should be left alone.

Thanks, I will fix that when I have time.

[jira-pull-request-webhook[bot]]

Notice: the branch changed across the force-push!

• docs/rfc/draft-davis-u-langtag-ext-00.txt is no longer changed in the branch
• docs/rfc/draft-davis-u-langtag-ext-00.xml is no longer changed in the branch
• docs/rfc/rfc2629.xslt is no longer changed in the branch
• tools/cldr-code/src/main/resources/org/unicode/cldr/util/data/asia is no longer changed in the branch
• tools/cldr-code/src/main/resources/org/unicode/cldr/util/data/country_language_population_raw.txt is no longer changed in the branch
• tools/cldr-code/src/main/resources/org/unicode/cldr/util/data/europe is no longer changed in the branch
• tools/cldr-code/src/main/resources/org/unicode/cldr/util/data/external/other_country_data.txt is no longer changed in the branch
• tools/cldr-code/src/main/resources/org/unicode/cldr/util/data/st_sysmsg.html is no longer changed in the branch
• tools/cldr-code/src/main/resources/org/unicode/cldr/util/data/test_help_messages.html is no longer changed in the branch

View Diff Across Force-Push

~ Your Friendly Jira-GitHub PR Checker Bot

[srl295]

https://unicode-org.atlassian.net/browse/CLDR-14010 (you can just write CLDR-14010 within the repo, it's linked)

Thanks. I have edited the head post.

/docs/rfc is an IETF RFC and shouldn't be changed here anything in the /data/ subdirectory is mostly external data sources and should be left alone.

Thanks, I will fix that when I have time.

https://unicode-org.atlassian.net/browse/CLDR-14010 (you can just write CLDR-14010 within the repo, it's linked)

Thanks. I have edited the head post.

commit message needs to match

/docs/rfc is an IETF RFC and shouldn't be changed here anything in the /data/ subdirectory is mostly external data sources and should be left alone.

Thanks, I will fix that when I have time.

thanks… also the CLA

[KOLANICH]

also the CLA

The quote from the top message in this issue:

CLA won't be signed, but you can consider the contribution as the one in public domain. Also it is likely that it is below the threshold of originality since it is a result of just applying the software and some mechanistic procedures.

I don't sign any legally binding aggreements when it is not really benefiting me. Here it is me who donates the contribution to the project. I have said "public domain", and that must be enough for you to accept the content without legal risks.

CLA-bots (a third-party webapp requiring me to sign into their website using my GH acc), CLAs in PSF-fashion, when one has to fax a scan of govt-issued ID, DCOs, requiring people use their legal names and all of this KYC-stuff is just destroying free open-source software movement. The foundation of FOSS movement is that just a file called License.md + knowledge which content is covered by it should be enough to use that content for everyone. Then some overparanoid lawyers said "not enough intimidating; let's also collect personal data, oathes, etc, etc, etc...." I feel it is not very far from the times when collection of biometric data as a "proof" that the person who has sent the DCO is the one having that legal name would become the standard approach to the matter. What would be required next, a certificate from a psychiatrist, narcologist and proctologist?! I refuse to play such games.

Anyway, if you don't want to accept the PR, you can use the tool linked to make a your own PR.

[srl295]

@KOLANICH The only agreement here is the exact text of the license. And it only needs GitHub login to do so.

[KOLANICH]

The only agreement here is the exact text of the license. And it only needs GitHub login to do so.

https://docs.github.com/en/github/site-policy/github-terms-of-service#6-contributions-under-repository-license

Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms.

So, in this case the CLA bot is unnecessary.

[macchiati]

I'm sorry, but we simply cannot accept contributions without a signed CLA.

[KOLANICH]

I have expected that it can be the response. Quite some corporate repos have rejected my contributions on that basis.

Fortunately, you can close the PR and use the tool to redo the changes from a user that has the CLA signed, and send a PR from that user.

[srl295]

superseded by #2396