We should also have a link to the project website.

Perhaps better to just link the website, in case we move off github in the future?

@gmaxwell agreed. The website address should be more permanent than the source repository which may or may not change in the future.

@btcdrak @gmaxwell I still think it is useful to have a link directly to the GitHub repo. I think there are no plans to move away from GitHub in the near future. Though, we may switch to the bitcoin-core organization some time...

Also, I have added two links to the website.

utACK

I think listing both the source code and the project website is a good idea.

fine, but my personal preference would just link to "https://bitcoincore.org" rather than a specific page.

Yes, just one link please. It would be also nice to not have About windows scrollable because of lot of texts.

utACK fa6565d

ACK fa6565d

When you are in this file, can you change the http:// to https:// in the MIT link?

@paveljanik Please mention this in #8192 (I can't change already translated strings as part of this pull anymore, as we are freezing translations tomorrow)

@MarcoFalke ? You have just added the string "Please contribute if you..". So?

@paveljanik The problem is with already translated strings. Currently we have 161 project languages (27 without translators) and not even the German translations for 0.12 are fully done.

If you change a translated string, people would need to go through the about ~80 languages where it is already translated and apply the difference. This may or may not happen.

To sum up:

• Having no translation is better than having no link to our websites at all.
• Having a slightly outdated translation (e.g. a http link) is better than no translation at all.

Sure, but in the case of http -> https, we can simply postprocess the transifex files.

Please squash.
ACK fa6565d2fc9c4cd8eac57915dc8b0aef8176b39c

@jonasschnelli: Squashed fa6565d into fa58e5e

Perhaps better to just link the website, in case we move off github in the future?

In that case we'll just update the software.

Sure, but in the case of http -> https, we can simply postprocess the transifex files.

Unfortunately, no, we can't do that. Postprocessing the ts files is simple, but getting the data back to Transifex without breaking all their metadata is not.

utACK fa58e5e, this seems the best solution for 0.13 as we don't want to break translation strings.