-
Your folder structure follows community standards! It's recommended that you group everything related together, so that means putting your css file into a folder called css, and also putting all your …
-
(Broader context at the end).
This issue is to discuss a potential PHEP to replace the "documentation" portion of the existing PyHC standards: to lay out what looks like the current standards, and …
-
Technically, there isn't anything wrong with this, but your folder structure doesn't quite follow community standards. It's recommended that you group everything related together, so that means puttin…
-
Your Folder structure follows community standards! It's recommended that you group everything related together, so that means putting your css file into a folder called css, and also putting all your …
-
There is no clear definition of what firmly belongs to the Nix ecosystem, what is "official" or merely "associated", and what is considered third-party.
## Tasks
- decide on criteria
- define pro…
-
# README.md
- [ ] the description of the project.
- [ ] why the project is useful.
- [ ] link to contributing.md
# CONTRIBUTING.md
- [ ] the different ways contributors can contribute to the project…
-
Your Folder structure follows community standards! It's recommended that you group everything related together, so that means putting your css file into a folder called css, and also putting all your …
-
All related work to prepare the repository for further development.
Follow [community recommended standards](https://opensource.guide/)
## Scope:
- [x] .gitignore
- [x] README.md
- [x] Repo…
-
Having tried to use a few serverless plugins lately, to be respectful I won't name them as I appreciate the effort of contributors, it would be good to see some community standards before they are acc…
-
Your Folder structure follows community standards! It's recommended that you group everything related together, so that means putting your css file into a folder called css, and also putting all your …