--- tags: '@badging/tooling' --- # Windows Subsystem for Linux 2 ## Getting Started ### Using `WSL2` with Visual Studio Code - Steps 1. Install the [`Remote development Extension pack on VS Code`](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack) 2. Once you install the extension, you will see a Remote Development extension icon at the bottom left corner of the VS Code editor.Click on the icon, you will get a pop up with a list of options. Click on the first option "Remote-WSL: New Window" for the default distro or select the "Remote-WSL: New Window using Distro" for a specific distro. 3. Once installed, the VS Code of your Windows machine/desktop will communicate with VS Code server on the Linux side. ## Troubleshooting ## Troubleshooting `docker-compose` - Steps taken to fix `WSL` 1. Install latest Windows updates 2. Install `WSL2` following the [docs](https://docs.microsoft.com/en-us/windows/wsl/install-win10#update-to-wsl-2) - Steps taken to use `docker-compose` in `WSL` 1. Uninstalled and reinstalled docker desktop on windows 10 2. Enable the `WSL2` based engine in the settings on docker desktop. 3. Enable integration with additional distributions under `Resources` on docker desktop. ## Troubleshooting `npm` Based on [Fiqri Ismail's Medium article](https://medium.com/@fiqriismail/setup-wsl-on-windows-10-for-your-javascript-development-with-visual-studio-code-f63f75841e5f): 1. Use the `nodesource` distribution installer: ```sh curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash - ``` > Find other versions in [@nodesource/distributions/deb/](https://github.com/nodesource/distributions/tree/master/deb) 2. Use `apt-get` to install `nodejs`: ```sh sudo apt-get install -y nodejs ``` 3. Verify that `node` is working: ```sh node --version ``` ## Troubleshooting `PATH` #### If you hit this: ``` bash: /mnt/c/Program Files/nodejs/npm: /bin/sh^M: bad interpreter: No such file or directory ``` #### First try this: If you find your `pwd` starts with `/mnt/c/…` and you should `cd ~/` which will take you to your home folder inside `WSL` which you want to be using instead when hacking on code. #### Then try this: You are likely hitting a problem with importing your Windows `PATH` environment variable into `WSL2`. See https://github.com/microsoft/WSL/issues/1890. > **Important Notice**: Refer to [@microsoft/WSL #1890](https://github.com/microsoft/WSL/issues/1890#issuecomment-423692567) before making the following changes. 1. Open `~/.bashrc` in your editor: ``` code ~/.bashrc ``` 2. Append the following line in the end: ```sh PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') # strip out problematic Windows %PATH% ``` 3. If you still run into the problem with some commands you might wan to consider this approach: ```sh ### remove unnecessary Win PATHs # This can prevent extension-less commands from bleeding into BASH. # (eg. "ng" would execute the Win bin if "@angular/cli" wasn't installed on Linux.) # function path_remove { # Delete path by parts so we can never accidentally remove sub paths PATH=${PATH//":$1:"/":"} # delete any instances in the middle PATH=${PATH/#"$1:"/} # delete any instance at the beginning PATH=${PATH/%":$1"/} # delete any instance in the at the end } path_remove '/mnt/c/Users/me/AppData/Roaming/npm' path_remove '/mnt/c/Users/me/AppData/Local/Yarn/bin' path_remove '/mnt/c/Program Files (x86)/Yarn/bin' path_remove '/mnt/c/Program Files/Git' path_remove '/mnt/c/Program Files/Git/cmd' path_remove '/mnt/c/Program Files/nodejs' path_remove '/mnt/c/OpenSSL-Win32/bin' path_remove '/mnt/c/Program Files (x86)/Python27' ``` > See this [comment](https://github.com/microsoft/WSL/issues/1890#issuecomment-318802876).
Last changed by  
 
badging
9490

Read more

Diversity & Inclusion Event Badging Form

Thank you for showing interest in D&I Badging for your event! The Event Badging section of CHAOSS Badging is about measuring inclusivity of different technical events through human reviews. The goal of the Diversity & Inclusion Badging Program is to encourage projects and events to obtain D&I badges for reasons of pride, leadership, self-reflection, and self-improvement on issues critical to building the Internet as a social good. Motivation to Apply The primary motivation to apply for a CHAOSS D&I Badge is the badge itself! The awarded event can show the open source community that they foster healthy D&I practices with a CHAOSS badge. Applying for a badge supports the open source community as a whole by showing the open source community that your event is willing to improve. This ultimately affects D&I practices in your event and even outside of your project space. Before You Start

9/2/2020
Badging by CHAOSS

May11 GSoD Exploration May20 D&I Update Jun09 GSoD Application Start Jun30 GitLab Checkpoint Jul09 GSoD Application Due Jul31 GSoD Selection Aug16 GSoD Announcement

7/20/2020
What the Markdown!

Triage Topics Indents References Markdown https://en.wikipedia.org/wiki/Markdown

7/20/2020
Locize Translation View

This is an Overview Illustration of the proces involved in Localization of a Service using Locize Login into your Locize Dashboard. When logged into your dashboard, a Demo project is being created for you to work with called Demo Project You can also add a new project by pressing the + sign close to ADD A NEW PROJECT. After that fill in the Project information for your Project After Creating your new Project, you could Import/Export your files with the supported formats here After Creating your Project, Specify the reference language, youcan also add new languages that will be used for translating your files. Creating Namespaces enables you to separate translations that get loaded into multiple files.

7/18/2020
Read more from badging
Published on HackMD