···1+# Contributor Covenant Code of Conduct
2+3+## Our Pledge
4+5+We as members, contributors, and leaders pledge to make participation in our
6+community a harassment-free experience for everyone, regardless of age, body
7+size, visible or invisible disability, ethnicity, sex characteristics, gender
8+identity and expression, level of experience, education, socio-economic status,
9+nationality, personal appearance, race, caste, color, religion, or sexual
10+identity and orientation.
11+12+We pledge to act and interact in ways that contribute to an open, welcoming,
13+diverse, inclusive, and healthy community.
14+15+## Our Standards
16+17+Examples of behavior that contributes to a positive environment for our
18+community include:
19+20+- Demonstrating empathy and kindness toward other people
21+- Being respectful of differing opinions, viewpoints, and experiences
22+- Giving and gracefully accepting constructive feedback
23+- Accepting responsibility and apologizing to those affected by our mistakes,
24+ and learning from the experience
25+- Focusing on what is best not just for us as individuals, but for the overall
26+ community
27+28+Examples of unacceptable behavior include:
29+30+- The use of sexualized language or imagery, and sexual attention or advances of
31+ any kind
32+- Trolling, insulting or derogatory comments, and personal or political attacks
33+- Public or private harassment
34+- Publishing others' private information, such as a physical or email address,
35+ without their explicit permission
36+- Other conduct which could reasonably be considered inappropriate in a
37+ professional setting
38+39+## Enforcement Responsibilities
40+41+Community leaders are responsible for clarifying and enforcing our standards of
42+acceptable behavior and will take appropriate and fair corrective action in
43+response to any behavior that they deem inappropriate, threatening, offensive,
44+or harmful.
45+46+Community leaders have the right and responsibility to remove, edit, or reject
47+comments, commits, code, wiki edits, issues, and other contributions that are
48+not aligned to this Code of Conduct, and will communicate reasons for moderation
49+decisions when appropriate.
50+51+## Scope
52+53+This Code of Conduct applies within all community spaces, and also applies when
54+an individual is officially representing the community in public spaces.
55+Examples of representing our community include using an official e-mail address,
56+posting via an official social media account, or acting as an appointed
57+representative at an online or offline event.
58+59+## Enforcement
60+61+Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+reported to the community leaders responsible for enforcement at
63+[GitHub Issues](https://github.com/tsirysndr/oh-my-droid/issues). All
64+complaints will be reviewed and investigated promptly and fairly.
65+66+All community leaders are obligated to respect the privacy and security of the
67+reporter of any incident.
68+69+## Enforcement Guidelines
70+71+Community leaders will follow these Community Impact Guidelines in determining
72+the consequences for any action they deem in violation of this Code of Conduct:
73+74+### 1. Correction
75+76+**Community Impact**: Use of inappropriate language or other behavior deemed
77+unprofessional or unwelcome in the community.
78+79+**Consequence**: A private, written warning from community leaders, providing
80+clarity around the nature of the violation and an explanation of why the
81+behavior was inappropriate. A public apology may be requested.
82+83+### 2. Warning
84+85+**Community Impact**: A violation through a single incident or series of
86+actions.
87+88+**Consequence**: A warning with consequences for continued behavior. No
89+interaction with the people involved, including unsolicited interaction with
90+those enforcing the Code of Conduct, for a specified period of time. This
91+includes avoiding interactions in community spaces as well as external channels
92+like social media. Violating these terms may lead to a temporary or permanent
93+ban.
94+95+### 3. Temporary Ban
96+97+**Community Impact**: A serious violation of community standards, including
98+sustained inappropriate behavior.
99+100+**Consequence**: A temporary ban from any sort of interaction or public
101+communication with the community for a specified period of time. No public or
102+private interaction with the people involved, including unsolicited interaction
103+with those enforcing the Code of Conduct, is allowed during this period.
104+Violating these terms may lead to a permanent ban.
105+106+### 4. Permanent Ban
107+108+**Community Impact**: Demonstrating a pattern of violation of community
109+standards, including sustained inappropriate behavior, harassment of an
110+individual, or aggression toward or disparagement of classes of individuals.
111+112+**Consequence**: A permanent ban from any sort of public interaction within the
113+community.
114+115+## Attribution
116+117+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+version 2.1, available at
119+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+121+Community Impact Guidelines were inspired by
122+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+124+For answers to common questions about this code of conduct, see the FAQ at
125+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+[https://www.contributor-covenant.org/translations][translations].
127+128+[homepage]: https://www.contributor-covenant.org
129+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+[Mozilla CoC]: https://github.com/mozilla/diversity
131+[FAQ]: https://www.contributor-covenant.org/faq
132+[translations]: https://www.contributor-covenant.org/translations
···1+# Contributing Guidelines
2+3+Thank you for your interest in contributing to our project. Whether it's a bug
4+report, new feature, correction, or additional documentation, we greatly value
5+feedback and contributions from our community.
6+7+Please read through this document before submitting any issues or pull requests
8+to ensure we have all the necessary information to effectively respond to your
9+bug report or contribution.
10+11+## Reporting Bugs/Feature Requests
12+13+We welcome you to use the GitHub issue tracker to report bugs or suggest
14+features.
15+16+When filing an issue, please check existing open, or recently closed, issues to
17+make sure somebody else hasn't already reported the issue. Please try to include
18+as much information as you can. Details like these are incredibly useful:
19+20+- A reproducible test case or series of steps
21+- The version of our code being used
22+- Any modifications you've made relevant to the bug
23+- Anything unusual about your environment or deployment
24+25+## Contributing via Pull Requests
26+27+Contributions via pull requests are much appreciated. Before sending us a pull
28+request, please ensure that:
29+30+1. You are working against the latest source on the _master_ branch.
31+2. You check existing open, and recently merged, pull requests to make sure
32+ someone else hasn't addressed the problem already.
33+3. You open an issue to discuss any significant work - we would hate for your
34+ time to be wasted.
35+36+To send us a pull request, please:
37+38+1. Fork the repository.
39+2. Modify the source; please focus on the specific change you are contributing.
40+ If you also reformat all the code, it will be hard for us to focus on your
41+ change.
42+3. Ensure local tests pass.
43+4. Commit to your fork using clear commit messages.
44+5. Send us a pull request, answering any default questions in the pull request
45+ interface.
46+6. Pay attention to any automated CI failures reported in the pull request, and
47+ stay involved in the conversation.
48+49+GitHub provides additional document on
50+[forking a repository](https://help.github.com/articles/fork-a-repo/) and
51+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
52+53+## Finding contributions to work on
54+55+Looking at the existing issues is a great way to find something to contribute
56+on. As our projects, by default, use the default GitHub issue labels
57+(enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any
58+'help wanted' issues is a great place to start.
59+60+## Code of Conduct
61+62+This project has adopted the
63+[Contributor Covenant](https://www.contributor-covenant.org/), version 2.1,
64+available at
65+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
66+67+## Licensing
68+69+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to
70+confirm the licensing of your contribution.
+19
LICENSE
···0000000000000000000
···1+Copyright (c) 2025 Tsiry Sandratraina <tsiry.sndr@rocksky.app>
2+3+Permission is hereby granted, free of charge, to any person obtaining a copy
4+of this software and associated documentation files (the "Software"), to deal
5+in the Software without restriction, including without limitation the rights
6+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
7+copies of the Software, and to permit persons to whom the Software is
8+furnished to do so, subject to the following conditions:
9+10+The above copyright notice and this permission notice shall be included in all
11+copies or substantial portions of the Software.
12+13+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
14+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
15+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
16+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
17+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
18+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
19+SOFTWARE.
+17
README.md
···00000000000000000
···1+# oh-my-droid
2+3+Turn a fresh Android +15 Linux Terminal into a fully-configured, beautiful, and modern web development system by running a single command.
4+5+## Features
6+- Easy installation of essential development tools
7+- Pre-configured environment for web development
8+- Customizable settings for individual preferences
9+- Atuin integration for enhanced command history
10+- Zoxide integration for improved directory navigation
11+- ble.sh integration for a better terminal experience
12+- Pkgx package manager for easy software installation
13+- Mise integration for a modern command-line experience
14+- SSH support for secure remote access
15+- Pre-installed VS Code
16+- Oh My Posh integration for a beautiful prompt
17+- Alias setup for ls: `alias ls='eza -lh'`