]> git.ipfire.org Git - thirdparty/openssl.git/commitdiff
Update links in CONTRIBUTING.md
authorAndrew Dinh <andrewd@openssl.org>
Fri, 2 Aug 2024 13:58:13 +0000 (20:58 +0700)
committerNeil Horman <nhorman@openssl.org>
Wed, 7 Aug 2024 09:13:32 +0000 (05:13 -0400)
Reviewed-by: Neil Horman <nhorman@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/25073)

(cherry picked from commit ad3d57d27141c09fe07ef39c49af5afe69c59383)

CONTRIBUTING.md

index fec6616e21fe2ec0351796002a8472ee9b48219d..76ed5418d12021e898a3228c629bd7e16fbd8cd5 100644 (file)
@@ -3,7 +3,7 @@ HOW TO CONTRIBUTE TO OpenSSL
 
 Please visit our [Getting Started] page for other ideas about how to contribute.
 
-  [Getting Started]: <https://www.openssl.org/community/getting-started.html>
+  [Getting Started]: <https://openssl-library.org/community/getting-started/index.html>
 
 Development is done on GitHub in the [openssl/openssl] repository.
 
@@ -77,8 +77,8 @@ guidelines:
     Clean builds via GitHub Actions are required. They are started automatically
     whenever a PR is created or updated by committers.
 
-    [coding style]: https://www.openssl.org/policies/technical/coding-style.html
-    [documentation policy]: https://openssl.org/policies/technical/documentation-policy.html
+    [coding style]: https://openssl-library.org/policies/technical/coding-style/
+    [documentation policy]: https://openssl-library.org/policies/technical/documentation-policy/
 
  5. When at all possible, code contributions should include tests. These can
     either be added to an existing test, or completely new.  Please see