architecture_decision_record VS oasis-core

I'm translating the Architecture Decision Record project to more languages. I'm seeking advice and guidance please: how are you all managing translations of git repos of content such as documentation and markdown files?

My experiments so far are here:

https://github.com/sixarm/locale-help

My work-in-progress is to create a top level directory `./locales`, then subdirectories per language using a ISO 639-1 two-letter language code, then content directories, for example:

./locales/en/hello/ (this is in English)

./locales/es/hola/ (this is in Español a.k.a. Spanish)

What do you use to track which content directories correspond to each other across languages?

The Architecture Decision Record repo is now mostly auto-translated into Spanish, French, Welsh, and Korean, in the top level directory `./locales`, using the program `slug-case` to help translate the markdown content file headlines into directory names:

https://github.com/joelparkerhenderson/architecture-decision-record

Link is https://github.com/joelparkerhenderson/architecture-decision...

Hi, article author here, we supplement our architecture diagrams with Architectural Decision Records (ADRs) https://github.com/joelparkerhenderson/architecture-decision... in the ADR we capture:

Architecture decision record by joelparkerhenderson

If anyone wants to see Polar in action on a GitHub issue, I'm experimenting with Polar on my Architecture Decision Record repo:

https://github.com/joelparkerhenderson/architecture-decision...

(I'm on the fence about the value of Polar for this kind of issue... see what you think)

This method is only slightly formalized as ADR (architecture decision record). What I personally like about templates that people share on the interned (https://github.com/joelparkerhenderson/architecture-decision-record) it that if force designed to actually consider cons of selected approach or honestly attempt to analyze alternatives.

The GitHub repo joelparkerhenderson/architecture-decision-record is a good source to get an overview of tools, articles and examples.

GitHub is prompting me to add a git successor to my open source repo, in case I die.

Do people here have advice about how to do this, or experience in doing it?

Any brainstorms about how to do it across all the related repos, orgs, etc., such as a will, or well-known file in the repo, that donates to a nonprofit, or foundation, etc.?

Here's the repo:

https://github.com/joelparkerhenderson/architecture-decision-record

Architecture Decision Records are a big help for teamwork. I have a bunch of notes and examples here, including from my time at ThoughtWorks with technology radars.

https://github.com/joelparkerhenderson/architecture-decision...

If you want to get started with ADR, I recommend looking at the repository, where you can find different ADR templates and examples of how to use them.

The way smart privacy solutions of Oasis are gaining traction thanks to the use of confidential smart contracts, this development was just waiting to happen. We already have seen a huge paradigm shift in DeFi (illumineX, CoinSender, Ocean Predictoor, Synthr, Celer cBridge, etc), web3 gaming (Pixudi), governance (Woo3), data storage (Crust Files), and cross-ecosystem (Oraichain) examples where privacy is the new normal of the new-gen web3. Now, with the NFTb (PixelRealm) partnership, Oasis is making its presence known in the NFT marketplace and will redefine web3 auctions by adding the element of confidentiality that no other protocol can provide.

I would recommend Oasis, as it is the only L1 protocol with confidential EVM in production (Sapphire) and can function as a cross-chain L2 (OPL) as well. Check out here, also the documentation, and GitHub. As the home of smart privacy, it is ideal for any web3 project. It can impact non-DeFi spaces like SocialFi, confidential voting in DAOs, confidential NFTs, confidential game logic in web3 gaming, etc, and also has applicability in account abstraction and responsible AI.

We have released Oasis Core 23.0.8 for MAINNET which includes additional signatures for the Eden upgrade genesis block (https://github.com/oasisprotocol/oasis-core/pull/5486/files) that will enable successful confidential ParaTime transition to the new chain. More details will be explained in detail shortly. All node operators on MAINNET please UPGRADE AND START YOUR NODES . For more information and links to releases see the updated MAINNET network parameters (https://docs.oasis.io/node/mainnet/). NOTE: DO NOT WIPE STATE and KEEP the SAME EDEN GENESIS FILE.

You can start with the fundamentals with a crash course into the space. Next, explore the value of using confidential smart contracts for web3 and know the various focus areas where you can build a net-gen, privacy-enabled dApp. When you are ready to build, you can start here.

The Oasis core team will participate in all these events and welcome enthusiastic developers to meet and network with them during these days. To brush up on Oasis technologies that enable smart privacy solutions in blockchain development, explore here as you learn how to build with Sapphire or integrate confidentiality with cross-chain OPL.

There are a lot of resources available out there. If you would like to get practical with a protocol, I can suggest going with Oasis Network and starting with documentation. They are the pioneers of implementing smart privacy solutions which mean developing and deploying smart contracts with customizable confidentiality settings so that end users can enjoy data sovereignty and security. Applicability is limitless, especially in boosting interoperability and ushering in account abstraction to ease the onboarding of web2 users onto the web3 ecosystem. Here is a whole range of tutorials/demos you can delve right into.

To stay updated on the Privacy4Web3 Hackathon and ensure you make the most of your virtual experience, you can keep checkin oasis' official blog, I'm sure they are gonna keep us up to date anyway!

Are you a Solidity developer or dApp builder trying to navigate the world of web3 and are bothered by the current scenario where lack of privacy is a big hurdle? Is there any chance that you will be attending the Ethereum Community Conference (EthCC) in July? Then heed this. Oasis Network will be present to share valuable insights on how to seamlessly add privacy to a web3 dApp on any EVM network. Not to be missed, right?

Join us for the upcoming Oasis Network Discord Community Call featuring a captivating discussion on Escrin, the secure decentralized computing network revolutionizing Web3 applications. Nick Hynes, founder at Enshrine Computing and Ecosystem Growth Advisor at Oasis Foundation, will share valuable insights during this must-attend event.

Oasis Network is a layer-1 blockchain protocol that prioritizes privacy and security while also enabling developers to build privacy-enabled applications. It goes beyond simple anonymity by incorporating features like confidential runtimes and cross-chain privacy tools. So, in the realm of privacy-focused blockchain projects, it definitely is worth keeping an eye on.