Merge branch 'dev' into dev-stable

Author: Hayao0819

channels/i3/airootfs.any/etc/skel/.config/i3/config

@@ -52,7 +52,7 @@ for_window [class="pavucontrol"] floating enable
 set $mod Mod4
 
 # start calamares (installer)
-bindsym $mod+i exec --no-startup-id sudo calamares
+bindsym $mod+i exec --no-startup-id sudo -E calamares
 
 # start a terminal
 bindsym $mod+Return exec --no-startup-id sakura

docs/CODE_OF_CONDUCT.md

@@ -3,9 +3,9 @@
 ## Our Pledge
 
 In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
+contributors and maintainers pledge to make participation in our project and
 our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
+size, disability, ethnicity, sex characteristics, gender identity, and expression,
 level of experience, education, socio-economic status, nationality, personal
 appearance, race, religion, or sexual identity and orientation.
 
@@ -23,13 +23,13 @@ include:
 Examples of unacceptable behavior by participants include:
 
 * The use of sexualized language or imagery and unwelcome sexual attention or
- advances
+  advances
 * Trolling, insulting/derogatory comments, and personal or political attacks
 * Public or private harassment
 * Publishing others' private information, such as a physical or electronic
- address, without explicit permission
+  address, without explicit permission
 * Other conduct which could reasonably be considered inappropriate in a
- professional setting
+  professional setting
 
 ## Our Responsibilities
 
@@ -54,7 +54,7 @@ further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
+Instances of abusive, harassing or otherwise unacceptable behavior may be
 reported by contacting the project team at serenelinux.dev@gmail.com. All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is

docs/CONTRIBUTING.md

@@ -3,20 +3,24 @@
 ## コーディング規約
 
 ### 全体
+
 - なるべく`bash`のビルドインコマンドを使用する
 - 外部コマンドを使用する場合は依存パッケージを追加する（極力使用しないでください）
 
 ### 出力
+
 - エラーメッセージは全て`STDERR`に出力する
 - メッセージ用の関数がある場合はその関数を使用する
 - 最小限の出力とし、冗長な出力は引数で有効化された場合のみに許可する
 
 ### 見た目
+
 - インデントはスペース4つとする
 - 引数の多いコマンド（`xorriso`など）やパイプを多用する場合は`\`で改行する
 - コードにTodoを書く場合は日付とユーザー名を書く
 
 ### 変数や関数
+
 - 全ての関数に概要や使い方にコメントを書く
 - 関数の定義は`function`を付けず、`my_func () {}`を使用する
 - 全ての変数は`${hoge}`のように括弧を使用する
@@ -25,11 +29,13 @@
 - 算術式展開は`$(( m + n ))`を使用する
 
 ### if、for、test、case、while
+
 - `test`コマンドは必ず`[[`を使用する
 - `do`や`then`などは`while`、`for`、`if`と同じ行に書く
 - `case`の際はなるべくインデントを揃える
 
 ### 例
+
 ```bash
 # Usage: test_hoge <str>
 test_hoge () {
@@ -44,21 +50,25 @@ test_hoge () {
 }
 ```
 
-
 ### その他
+
 - 極力相対パスを使用しない
 - ファイルパスは必ず`""`で囲む
 
 ## Issues
+
 Issueを送る際は以下の情報を記述して下さい。
+
 - インストールに使用したイメージファイルへのURL
 - 問題が発生した環境
 - どのようなことを行ったか
 - スクリーンショットやログ等
 - ビルドに問題が発生した際は作業ディレクトリにある`build_options`
 
 ## プルリクエスト
+
 日本語もしくは英語で内容を書いて下さい。内容とは具体的に以下のものを指します。
+
 - どのような機能を追加するか（問題を修正するのか）
 - 現在確認されている問題（その対処方法も書ければ）
 - 参考にした文献について
@@ -71,20 +81,24 @@ Issueを送る際は以下の情報を記述して下さい。
 ## Coding Conventions
 
 ### General
+
 - Use the `bash` build-in command if possible
 - Add a dependency package if you use an external command (please try not to use it as much as possible)
 
 ### Output
+
 - Output all error messages to `STDERR`
 - If you have a function for messages, use that function
 - Minimize output and redundant output only allow when enabled by the argument
 
 ### Looks
+
 - Indent should be four spaces
-- The line break with `\` when use a lot of command with many arguments (`xorriso`, etc.) or a lot of pipes
+- The line break with `\` when using a lot of commands with many arguments (`xorriso`, etc.) or a lot of pipes
 - If you write a Todo in your code, write the date and user name
 
 ### Variables and functions
+
 - Write comments on all functions in summary and usage
 - The function definition does not use a `function` but uses `my_func () {}`
 - All variables use brackets like `${hoge}`
@@ -93,11 +107,13 @@ Issueを送る際は以下の情報を記述して下さい。
 - Arithmetic expansion uses `$(( m + n ))`
 
 ### if, for, test, case, while
+
 - The `test` command must use `[[`
 - `do`, `then`, etc. write on the same line as `while`, `for` and `if`
 - Align indents on `cases` as much as possible
 
 ### Example
+
 ```bash
 # Usage: test_hoge <str>
 test_hoge () {
@@ -112,21 +128,25 @@ test_hoge () {
 }
 ```
 
-
 ### Other
+
 - Use as few relative paths as possible.
 - Make sure to enclose the file path in `""`.
 
 ## Issues
+
 When you send the issue, please include the following information.
+
 - The URL to the image file used for the installation
 - The environment in which the problem occurred
 - What did we do
 - Screenshots, logs, etc.
-- If a problem happen when you building, Please attach the file `build_options` in the working directory
+- If a problem happens when you're building, Please attach the file `build_options` in the working directory
 
 ## Pull Request
+
 Please write content in either Japanese or English. Specifically, the content refers to the following
+
 - What features you are going to add (or fix the problem)
 - Known issues (and how to deal with them if you can write about them)
 - About the references