Add open-source project scaffolding: contributor docs, issue/PR templates, and lint CI

.editorconfig

@@ -0,0 +1,37 @@
+# https://editorconfig.org
+#
+# Matched to the conventions already present in the tree (4-space indent across
+# both shell and Python) so existing files are not reformatted wholesale.
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 4
+
+# Ecosystem convention is 2 spaces for these; fighting it just creates churn.
+[*.{yml,yaml,json,jsonc,kdl,toml}]
+indent_size = 2
+
+[*.{js,mjs,ts,css}]
+indent_size = 2
+
+# Markdown: two trailing spaces is a hard line break, so trimming corrupts prose.
+[*.md]
+trim_trailing_whitespace = false
+
+# The Obsidian vault is authored in Obsidian, not in an editor honouring this
+# file. Leave it entirely alone.
+[Documents/**]
+trim_trailing_whitespace = false
+insert_final_newline = false
+
+[Makefile]
+indent_style = tab
+
+[*.{png,jpg,jpeg,webp,gif,ico,mp3,wav,ogg,ttf,otf,woff,woff2,so}]
+insert_final_newline = false
+trim_trailing_whitespace = false

.gitattributes

@@ -0,0 +1,91 @@
+# ─────────────────────────────────────────────────────────────────────────────
+#  Line endings — this is load-bearing, do not remove.
+#
+#  Dusky is deployed onto Arch Linux with `git checkout -f` straight into $HOME.
+#  A shell script that lands with CRLF endings does not "look slightly wrong",
+#  it hard-fails at exec time:
+#
+#      /usr/bin/env: 'bash\r': No such file or directory
+#
+#  Contributors on Windows or WSL frequently have `core.autocrlf=true`, which
+#  would otherwise commit CRLF into the repo. Pin the behaviour here rather than
+#  trusting every contributor's local git config.
+# ─────────────────────────────────────────────────────────────────────────────
+* text=auto eol=lf
+
+# Executables and code — always LF, no exceptions.
+*.sh        text eol=lf
+*.bash      text eol=lf
+*.zsh       text eol=lf
+.zshrc      text eol=lf
+.zprofile   text eol=lf
+*.py        text eol=lf
+*.lua       text eol=lf
+*.js        text eol=lf
+*.mjs       text eol=lf
+*.ts        text eol=lf
+
+# Config formats consumed by daemons that are not CRLF-tolerant.
+*.conf      text eol=lf
+*.ini       text eol=lf
+*.toml      text eol=lf
+*.json      text eol=lf
+*.jsonc     text eol=lf
+*.kdl       text eol=lf
+*.yml       text eol=lf
+*.yaml      text eol=lf
+*.css       text eol=lf
+*.rasi      text eol=lf
+*.desktop   text eol=lf
+*.service   text eol=lf
+*.timer     text eol=lf
+*.rules     text eol=lf
+*.glsl      text eol=lf
+*.frag      text eol=lf
+*.vert      text eol=lf
+*.md        text eol=lf
+*.txt       text eol=lf
+
+# ─────────────────────────────────────────────────────────────────────────────
+#  Binary — never normalised, never diffed as text.
+# ─────────────────────────────────────────────────────────────────────────────
+*.png       binary
+*.jpg       binary
+*.jpeg      binary
+*.webp      binary
+*.gif       binary
+*.ico       binary
+*.svg       text eol=lf
+*.mp3       binary
+*.wav       binary
+*.ogg       binary
+*.opus      binary
+*.mp4       binary
+*.ttf       binary
+*.otf       binary
+*.woff      binary
+*.woff2     binary
+*.so        binary
+*.o         binary
+*.zip       binary
+*.xpi       binary
+*.gz        binary
+*.xz        binary
+*.zst       binary
+
+# ─────────────────────────────────────────────────────────────────────────────
+#  GitHub Linguist — keep the language bar honest.
+#
+#  `Documents/` is a ~400-file Obsidian notes vault and `Pictures/` is image
+#  assets. Neither is source code, and without these hints GitHub reports this
+#  as a prose repository rather than the shell/python project it actually is.
+# ─────────────────────────────────────────────────────────────────────────────
+Documents/**                linguist-documentation
+Pictures/**                 linguist-vendored
+*.md                        linguist-documentation
+
+# Vendored/derived third-party code — excluded from language stats and from
+# "lines changed" noise in PR review.
+.config/sddm/**             linguist-vendored
+**/hyprland-focus-grab-v1-client-protocol.c    linguist-generated
+**/hyprland-focus-grab-v1-client-protocol.h    linguist-generated

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,138 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a
+harassment-free experience for everyone, regardless of age, body size, visible or
+invisible disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal appearance,
+race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse,
+inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community
+include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and
+  learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without
+  their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional
+  setting
+
+### A note specific to this project
+
+Dusky attracts people at wildly different levels of Linux experience — some arriving from
+Windows and installing Arch for the first time, some who have been ricing for a decade.
+
+**"Just read the wiki" is not an answer here.** Beginners asking basic questions are
+welcome and expected. Condescension toward someone who does not yet know what a
+compositor is, or gatekeeping about what makes someone a "real" Linux user, is a Code of
+Conduct issue, not a personality quirk.
+
+Equally: disagreement about technical direction is fine and useful. Argue about the
+approach, not the person proposing it.
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in response to
+any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments,
+commits, code, wiki edits, issues, and other contributions that are not aligned to this
+Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an
+individual is officially representing the community in public spaces. Examples of
+representing our community include using an official email address, posting via an
+official social media account, or acting as an appointed representative at an online or
+offline event.
+
+For this project, community spaces include the GitHub repository (issues, pull requests,
+discussions) and the [Dusky Discord server](https://discord.gg/Nv2a7yTBQS).
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to
+the community leaders responsible for enforcement by direct message to the maintainer on
+the [Dusky Discord server](https://discord.gg/Nv2a7yTBQS), or by opening a
+[private report on GitHub](https://github.com/dusklinux/dusky/security/advisories/new).
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter
+of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the
+consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity
+around the nature of the violation and an explanation of why the behavior was
+inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with
+the people involved, including unsolicited interaction with those enforcing the Code of
+Conduct, for a specified period of time. This includes avoiding interactions in community
+spaces as well as external channels like social media. Violating these terms may lead to
+a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained
+inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication
+with the community for a specified period of time. No public or private interaction with
+the people involved, including unsolicited interaction with those enforcing the Code of
+Conduct, is allowed during this period. Violating these terms may lead to a permanent
+ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards,
+including sustained inappropriate behavior, harassment of an individual, or aggression
+toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1,
+available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/inclusion).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.