From fe1da712e3b6f3ea746567b208156a17c16d211c Mon Sep 17 00:00:00 2001 From: Christopher Allen Date: Tue, 27 Jul 2021 12:05:50 -0700 Subject: [PATCH] Clarified the commit for the CLA should be signed --- TRANSLATING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/TRANSLATING.md b/TRANSLATING.md index add7ffe..7fc8360 100644 --- a/TRANSLATING.md +++ b/TRANSLATING.md @@ -4,7 +4,7 @@ Thank you for your interest in translating Learning Bitcoin from the Command Lin 1. **Please Follow Our Normal Contributor Procedure.** * Read over [CONTRIBUTING.md](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/blob/master/CONTRIBUTING.md). - * Fill out a [Contributor License Agreement](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/blob/master/CLA.md) and submit it as a PR. + * Fill out a [Contributor License Agreement](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/blob/master/CLA.md), sign it with GPG, and submit it as a PR. 1. **Choose a Release.** * Choose a [Release](https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line/releases) as the basis of your translation. We generally suggest the latest release. This will ensure the consistency of all the files in your translation, will insulate you from any changes we make, and will make it easy to see what has changed when we create a new release. * If it looks like there hasn't been a new Release in a while, file an Issue saying you're interested in starting a new translation, and asking if it would make sense for there to be a new Release milestone before you do so. If there's been anything notable, and we're not in the middle of things, we'll likely create a new patch or minor version. If we're in the middle of things, we'll just suggest you use the previous Release.