contributor_covenant VS Visual Studio Code

While you are free to write your own or adopt one from another repository, project, or organization you respect, there exists a code of conduct written and maintained by the community known as the Contributor Covenant.

Many Open Source projects have adopted the Contributor Covenant as their code of conduct. Check this page to see a list of adopters.

https://www.contributor-covenant.org/ is (was?) the most widely adopted code of conduct in FOSS, initially drafted by a Ruby contributor, who also happens to be transgender if that's pertinent information to you. It's the genesis seed from which all this code of conduct madness stems from. Personally I'd stick with "be excellent to each other" or "say what you want, just don't insult other contributors" or something vague, ambiguous and universally understood as that. I'm not really a fan of rigorous social rules, so my view on this starts from that position.

You can adapt the guidelines provided by https://www.contributor-covenant.org/ to create your guideline.

The Contributor Covenant that the maintainer removed to "reclaim polymc from the leftoids" was added in February: https://github.com/PolyMC/PolyMC/pull/178. You can view a list of other communities that have adopted the covenant on their website.

For reference, the Code of Conduct they used is basically the same as this one: https://www.contributor-covenant.org/

Please follow the Contributor Covenant

As your audience grows, it is vital that you define clear rules to create a safe environment for everyone to participate. A common way of doing this is to define a code of conduct (CoC), which sets some basic guidelines on what kind of community interaction will not be tolerated. We decided to stick to well-established frameworks and based our CoC on the Contributor Covenant.

Those aren't the only ways I could see things happen, but that represents a few points on the spectrum. Having been participating in the English Wikipedia community since the early days, I know that collaborative writing on a worldwide scale is hard, and leads to misunderstandings and hurt feelings. Hence the reason why things like the Contributor Covenant came out, and why Linus Torvalds took such a long time accepting something. Note, things labeled "Code of Conduct" and "Contributor Covenant" are one small slice of governance. Dealing with things like the ideal public transit system create a massive extra layer of complexity. Governance, in general, is difficult.

A code editor (VS Code is my go-to IDE), but feel free to use any code editor you're comfortable with.

First, grab your favorite command-line tool, Terminal or Warp, and a code editor, preferably VS Code and let’s begin.

C# is very good as a language, have developed in it for 5+ years. The problem is the gap between what MSFT promises to management and actually delivers to developers. You really really need to fully read the fine print, think of the omissions in documentation and implement a proof-of-concept that almost implements the full solution to find out the hidden gotchas.

For example, even probably their best product VS Code only got reasonable multiple screens support last year: https://github.com/microsoft/vscode/issues/10121#issuecommen...

And then, on the other end of the spectrum, you have Teams.

Hey fellow amazing developers, we got you Essential VS Code Extensions for 2024 (these are especially important for web developers) recommended by our developers at evotik, we wont talk about ESlint nor Prettier which all of you already know.

Visual Studio Code (VS Code): Developed by Microsoft, VS Code is a lightweight yet powerful IDE with extensive support for Python development through extensions. It offers features like IntelliSense, debugging, and built-in Git integration.

In VSCode for example this can be easily done by adding the following .vscode/launch.json file:

I had a near-identical experience. I looked into switching in 2019 and ran into this 2016 bug which was a showstopper for me. Fixed it myself, grand total 4 line diff. https://github.com/microsoft/vscode/issues/10643

When working in Visual Studio Code (VS Code), always create a new Python file for your project.

Code Editor: Choose a code editor like Visual Studio Code that offers good support for web technologies and extensions for PWA development.

When working in Visual Studio Code (VS Code), create a new Python file for our music player project. It's helpful to have separate files for different parts of your project.