Skip to content

Commit 7baeed1

Browse files
authored
Merge pull request #1 from Dartvauder/dev
ALPHA-RELEASE
2 parents ce169a7 + 6e2591a commit 7baeed1

33 files changed

+1261
-1
lines changed

.gitattributes

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
*.py linguist-language=Python
2+
*.sh linguist-language=Shell
3+
*.bat linguist-language=Batchfile

.github/CODE_OF_CONDUCT.md

Lines changed: 130 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,130 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
![3](https://github.com/Dartvauder/NeuroChatWebUI/assets/140557322/87397844-0add-4f59-a278-cf10578c0037)
4+
5+
## Our Pledge
6+
7+
We as members, contributors, and leaders pledge to make participation in our
8+
community a harassment-free experience for everyone, regardless of age, body
9+
size, visible or invisible disability, ethnicity, sex characteristics, gender
10+
identity and expression, level of experience, education, socio-economic status,
11+
nationality, personal appearance, race, religion, or sexual identity
12+
and orientation.
13+
14+
We pledge to act and interact in ways that contribute to an open, welcoming,
15+
diverse, inclusive, and healthy community.
16+
17+
## Our Standards
18+
19+
Examples of behavior that contributes to a positive environment for our
20+
community include:
21+
22+
* Demonstrating empathy and kindness toward other people
23+
* Being respectful of differing opinions, viewpoints, and experiences
24+
* Giving and gracefully accepting constructive feedback
25+
* Accepting responsibility and apologizing to those affected by our mistakes,
26+
and learning from the experience
27+
* Focusing on what is best not just for us as individuals, but for the
28+
overall community
29+
30+
Examples of unacceptable behavior include:
31+
32+
* The use of sexualized language or imagery, and sexual attention or
33+
advances of any kind
34+
* Trolling, insulting or derogatory comments, and personal or political attacks
35+
* Public or private harassment
36+
* Publishing others' private information, such as a physical or email
37+
address, without their explicit permission
38+
* Other conduct which could reasonably be considered inappropriate in a
39+
professional setting
40+
41+
## Enforcement Responsibilities
42+
43+
Community leaders are responsible for clarifying and enforcing our standards of
44+
acceptable behavior and will take appropriate and fair corrective action in
45+
response to any behavior that they deem inappropriate, threatening, offensive,
46+
or harmful.
47+
48+
Community leaders have the right and responsibility to remove, edit, or reject
49+
comments, commits, code, wiki edits, issues, and other contributions that are
50+
not aligned to this Code of Conduct, and will communicate reasons for moderation
51+
decisions when appropriate.
52+
53+
## Scope
54+
55+
This Code of Conduct applies within all community spaces, and also applies when
56+
an individual is officially representing the community in public spaces.
57+
Examples of representing our community include using an official e-mail address,
58+
posting via an official social media account, or acting as an appointed
59+
representative at an online or offline event.
60+
61+
## Enforcement
62+
63+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
64+
reported to the community leaders responsible for enforcement at
65+
Dartvauder007@protonmail.com.
66+
All complaints will be reviewed and investigated promptly and fairly.
67+
68+
All community leaders are obligated to respect the privacy and security of the
69+
reporter of any incident.
70+
71+
## Enforcement Guidelines
72+
73+
Community leaders will follow these Community Impact Guidelines in determining
74+
the consequences for any action they deem in violation of this Code of Conduct:
75+
76+
### 1. Correction
77+
78+
**Community Impact**: Use of inappropriate language or other behavior deemed
79+
unprofessional or unwelcome in the community.
80+
81+
**Consequence**: A private, written warning from community leaders, providing
82+
clarity around the nature of the violation and an explanation of why the
83+
behavior was inappropriate. A public apology may be requested.
84+
85+
### 2. Warning
86+
87+
**Community Impact**: A violation through a single incident or series
88+
of actions.
89+
90+
**Consequence**: A warning with consequences for continued behavior. No
91+
interaction with the people involved, including unsolicited interaction with
92+
those enforcing the Code of Conduct, for a specified period of time. This
93+
includes avoiding interactions in community spaces as well as external channels
94+
like social media. Violating these terms may lead to a temporary or
95+
permanent ban.
96+
97+
### 3. Temporary Ban
98+
99+
**Community Impact**: A serious violation of community standards, including
100+
sustained inappropriate behavior.
101+
102+
**Consequence**: A temporary ban from any sort of interaction or public
103+
communication with the community for a specified period of time. No public or
104+
private interaction with the people involved, including unsolicited interaction
105+
with those enforcing the Code of Conduct, is allowed during this period.
106+
Violating these terms may lead to a permanent ban.
107+
108+
### 4. Permanent Ban
109+
110+
**Community Impact**: Demonstrating a pattern of violation of community
111+
standards, including sustained inappropriate behavior, harassment of an
112+
individual, or aggression toward or disparagement of classes of individuals.
113+
114+
**Consequence**: A permanent ban from any sort of public interaction within
115+
the community.
116+
117+
## Attribution
118+
119+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
120+
version 2.0, available at
121+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
122+
123+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
124+
enforcement ladder](https://github.com/mozilla/diversity).
125+
126+
[homepage]: https://www.contributor-covenant.org
127+
128+
For answers to common questions about this code of conduct, see the FAQ at
129+
https://www.contributor-covenant.org/faq. Translations are available at
130+
https://www.contributor-covenant.org/translations.

.github/CONTRIBUTING.md

Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
# Contributing to NeuroChatWebUI
2+
3+
![2 (1)](https://github.com/Dartvauder/NeuroChatWebUI/assets/140557322/18c44d3c-e030-4c5a-b179-034a06c5948a)
4+
5+
First off, thanks for taking the time to contribute! ❤️
6+
7+
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
8+
9+
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
10+
> - Star the project
11+
> - Tweet about it
12+
> - Refer this project in your project's readme
13+
> - Mention the project at local meetups and tell your friends/colleagues
14+
15+
## Table of Contents
16+
17+
- [I Have a Question](#i-have-a-question)
18+
- [I Want To Contribute](#i-want-to-contribute)
19+
- [Reporting Bugs](#reporting-bugs)
20+
- [Suggesting Enhancements](#suggesting-enhancements)
21+
- [Your First Code Contribution](#your-first-code-contribution)
22+
- [Join The Project Team](#join-the-project-team)
23+
24+
## I Have a Question
25+
26+
> If you want to ask a question, we assume that you have read the available [Documentation]().
27+
28+
Before you ask a question, it is best to search for existing [Issues](https://github.com/Dartvauder/NeuroChatWebUI/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
29+
30+
If you then still feel the need to ask a question and need clarification, we recommend the following:
31+
32+
- Open an [Issue](https://github.com/Dartvauder/NeuroChatWebUI/issues/new).
33+
- Provide as much context as you can about what you're running into.
34+
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
35+
36+
We will then take care of the issue as soon as possible.
37+
38+
## I Want To Contribute
39+
40+
> ### Legal Notice
41+
> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
42+
43+
### Reporting Bugs
44+
45+
#### Before Submitting a Bug Report
46+
47+
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
48+
49+
- Make sure that you are using the latest version.
50+
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/Dartvauder/NeuroChatWebUI/discussions/10).
51+
- Also make sure to search the internet to see if users outside of the GitHub community have discussed the issue.
52+
- Collect information about the bug:
53+
- Stack trace (Traceback)
54+
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
55+
- Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
56+
- Possibly your input and the output
57+
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
58+
59+
#### How Do I Submit a Good Bug Report?
60+
61+
> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <>.
62+
63+
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
64+
65+
- Open an [Issue](https://github.com/Dartvauder/NeuroChatWebUI/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
66+
- Explain the behavior you would expect and the actual behavior.
67+
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
68+
- Provide the information you collected in the previous section.
69+
70+
Once it's filed:
71+
72+
- The project team will check and label the issue, and try to fix it in the near future
73+
74+
### Suggesting Enhancements
75+
76+
This section guides you through submitting an enhancement suggestion for NeuroChatWebUI, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
77+
78+
#### Before Submitting an Enhancement
79+
80+
- Make sure that you are using the latest version.
81+
- Read the [features](https://github.com/Dartvauder/NeuroChatWebUI/tree/main#Features) carefully and find out if the functionality is already covered, maybe by an individual configuration.
82+
- Perform a [search](https://github.com/Dartvauder/NeuroChatWebUI/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
83+
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
84+
85+
#### How Do I Submit a Good Enhancement Suggestion?
86+
87+
Enhancement suggestions are tracked as [GitHub issues](https://github.com/Dartvauder/NeuroChatWebUI/issues).
88+
89+
- Use a **clear and descriptive title** for the issue to identify the suggestion.
90+
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
91+
- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
92+
- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to.
93+
- **Explain why this enhancement would be useful** to most NeuroChatWebUI users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
94+
95+
### Your First Code Contribution
96+
97+
## Join The Project Team
98+
99+
- Mail me to dartvauder007@protonmail.com

.github/ISSUE_TEMPLATE/bug_report.yml

Lines changed: 91 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,91 @@
1+
name: "🐛 Bug Report"
2+
description: "Create a new ticket for a bug."
3+
title: "🐛 [BUG] - <title>"
4+
labels: [
5+
"bug"
6+
]
7+
body:
8+
- type: textarea
9+
id: description
10+
attributes:
11+
label: "Description"
12+
description: "Please describe the issue in detail."
13+
placeholder: "Provide a detailed description of the issue..."
14+
validations:
15+
required: true
16+
17+
- type: textarea
18+
id: expected_behavior
19+
attributes:
20+
label: "Expected Behavior"
21+
description: "Please describe what you expected to happen."
22+
placeholder: "Expected result..."
23+
validations:
24+
required: true
25+
26+
- type: textarea
27+
id: reprod
28+
attributes:
29+
label: "Reproduction Steps"
30+
description: "Please list the steps to reproduce the issue, one step per line."
31+
placeholder: "1. Open app\n2. Go to settings\n3. Observe error"
32+
validations:
33+
required: true
34+
35+
- type: textarea
36+
id: screenshot
37+
attributes:
38+
label: "Screenshots"
39+
description: "If applicable, add screenshots to help explain your problem."
40+
placeholder: "Attach screenshots here..."
41+
validations:
42+
required: false
43+
44+
- type: textarea
45+
id: logs
46+
attributes:
47+
label: "Logs"
48+
description: "Please copy and paste any relevant log output."
49+
validations:
50+
required: false
51+
52+
- type: dropdown
53+
id: browsers
54+
attributes:
55+
label: "Browsers"
56+
description: "What browsers are you seeing the problem on?"
57+
multiple: true
58+
options:
59+
- Firefox
60+
- Chrome
61+
- Safari
62+
- Microsoft Edge
63+
- Opera
64+
validations:
65+
required: false
66+
67+
- type: dropdown
68+
id: os
69+
attributes:
70+
label: "OS"
71+
description: "What is the impacted environment?"
72+
multiple: true
73+
options:
74+
- Windows
75+
- Linux
76+
- Mac
77+
validations:
78+
required: false
79+
80+
- type: dropdown
81+
id: priority
82+
attributes:
83+
label: "Priority"
84+
description: "How critical is this issue?"
85+
options:
86+
- Low
87+
- Medium
88+
- High
89+
- Critical
90+
validations:
91+
required: true
Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
name: "🎨 Design Feedback"
2+
description: Provide feedback on UI/UX design
3+
title: "🎨 [Design] - <title>"
4+
labels: [
5+
"design"
6+
]
7+
body:
8+
- type: textarea
9+
id: description
10+
validations:
11+
required: true
12+
attributes:
13+
label: Feedback Description
14+
description: |
15+
Provide details about the design aspect you are giving feedback on.
16+
17+
- type: textarea
18+
id: suggestion
19+
validations:
20+
required: false
21+
attributes:
22+
label: Suggested Improvements
23+
description: |
24+
Suggest any changes or improvements you think would enhance the design.
25+
26+
- type: dropdown
27+
id: feedback-type
28+
validations:
29+
required: true
30+
attributes:
31+
label: Feedback Type
32+
description: |
33+
Select the type of feedback.
34+
options:
35+
- Usability
36+
- Visual Design
37+
- Accessibility
38+
- Responsiveness

0 commit comments

Comments
 (0)