├── .github
    └── ISSUE_TEMPLATE
    │   ├── config.yml
    │   ├── 01-bug-report.yml
    │   └── 02-package-request.yml
└── README.md


/.github/ISSUE_TEMPLATE/config.yml:
--------------------------------------------------------------------------------
1 | blank_issues_enabled: true
2 | contact_links:
3 |   - name: Want to ask questions about the project?
4 |     url: https://github.com/termux-play-store/termux-issues/discussions
5 |     about: Join GitHub Discussions
6 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # termux-issues
2 | Issues for the Google Play build of Termux.
3 | 
4 | If you have installed Termux from Google Play, please report issues [here](https://github.com/termux-play-store/termux-issues/issues/new/choose) and nowhere else.
5 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/01-bug-report.yml:
--------------------------------------------------------------------------------
 1 | name: "Bug report"
 2 | description: "Create a report to help us improve"
 3 | title: "[Bug]: "
 4 | labels: [untriaged, "bug report"]
 5 | body:
 6 |   - type: markdown
 7 |     attributes:
 8 |       value: |
 9 |         This is a bug tracker of the Termux packages for the Google Play build of Termux. Please do not report issues of third-party software there, but ask in [GitHub Discussions](https://github.com/termux-play-store/termux-issues/discussions) instead. Use search to check whether your issue has been already reported and perhaps solved.
10 | 
11 |         To submit a bug report, fill the form below. Provide as much as possible information about the encountered issue. We may request extended information such as `strace` logs if considered necessary. This will help package maintainers to understand the problem correctly and provide a solution. Make sure that your logs do not leak sensitive information (passwords, API keys, etc). Be patient, do not expect that issue could get resolved immediately.
12 |   - type: textarea
13 |     attributes:
14 |       label: Problem description
15 |       description: |
16 |         A clear and concise description of what the problem is. You may attach the logs, screenshots, screen video recording and whatever else that will help to understand the issue.
17 | 
18 |         Issues without proper description will be closed without solution.
19 |     validations:
20 |       required: true
21 |   - type: textarea
22 |     attributes:
23 |       label: What steps will reproduce the bug?
24 |     validations:
25 |       required: true
26 |   - type: textarea
27 |     attributes:
28 |       label: What is the expected behavior?
29 |   - type: textarea
30 |     attributes:
31 |       label: System information
32 |       description: Provide output of the command `termux-info`.
33 |       render: shell
34 |     validations:
35 |       required: true
36 | 


--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/02-package-request.yml:
--------------------------------------------------------------------------------
 1 | name: "Package request"
 2 | description: "Request a new package"
 3 | title: "[Package]: "
 4 | labels: ["package request"]
 5 | body:
 6 |   - type: markdown
 7 |     attributes:
 8 |       value: |
 9 |         Use search (`pkg search <name>`) to check whether package is already available. If package does not exist in our repositories, fill the form below to request it.
10 | 
11 |         Package requests are recommendational and are served at low priority. There no guarantee that package will be added at all.
12 |   - type: textarea
13 |     attributes:
14 |       label: Why is it worth to add this package?
15 |       description: Provide us a detailed explanation how do you plan to use the requested package and why it would be a nice addition to the Termux repository.
16 |     validations:
17 |       required: true
18 |   - type: input
19 |     attributes:
20 |       label: Home page URL
21 |   - type: input
22 |     attributes:
23 |       label: Source code URL
24 |       placeholder: Link to Git or source archive
25 |     validations:
26 |       required: true
27 | 
28 |   - type: checkboxes
29 |     attributes:
30 |       label: Packaging policy acknowledgement
31 |       description: |
32 |         Please provide additional information about the desired package.
33 |       options:
34 |         - label: The project is actively developed.
35 |             ###### We prefer packaging actively maintained projects
36 |           required: false
37 |         - label: The project has [existing packages](https://repology.org/projects) and is "well known".
38 |             ###### We prefer packaging projects with [existing packages on other distributions](https://repology.org/projects).
39 |           required: false
40 |         - label: Licensed under an [open source license](https://spdx.org/licenses/).
41 |           required: true
42 |         - label: |
43 |             Not available through a language package manager: pip, npm, cpan, cargo, etc.
44 |         ###### We do not package modules for Ruby, Lua, Python, NodeJS, etc.
45 |         ###### Unless they require specific tweaks in order to work on Termux, in which case the rest of the packaging policy still applies.
46 |           required: true
47 |         - label: Not taking up too much disk space (< 100MiB per architecture, exceptions can be made)
48 |             ###### All packages are usually built across 4 architectures, and our resources are limited.
49 |             ###### We generally restrict package size to 100MiB (per architecture).
50 |           required: false
51 |         - label: Not duplicating the functionality of existing packages.
52 |             ###### Every package requires a baseline of maintenance, as such we generally prefer packaging projects offering distinct functionality from existing packages.
53 |           required: false
54 |         - label: Not serving hacking, malware, phishing, spamming, spying, ddos functionality.
55 |             ###### We do not accept packages which serve solely destructive or privacy violation purposes, including but not limited to pentesting, phishing, bruteforce, sms/call bombing, DDoS attaks, OSINT.
56 |           required: true
57 | 
58 |   - type: textarea
59 |     attributes:
60 |       label: Additional information
61 |       description: |
62 |         Have you tried to compile it on device? If it did not work then provide the error you ran into. Otherwise please share build steps and any patches that you had to apply.
63 | 
64 |         Does your package have special device requirements such as root permissions, custom kernel or even additional hardware? If yes, then list all details here.
65 | 


--------------------------------------------------------------------------------