Skip to content

Commit f2f7ad9

Browse files
Add code of conduct and contributing files
1 parent 1fcb8bc commit f2f7ad9

2 files changed

Lines changed: 80 additions & 0 deletions

File tree

CODE_OF_CONDUCT.md

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# Agentic starter kits Code of Conduct
2+
3+
Like the technical community as a whole, the agentic starter kits team and community is made up of a mixture of professionals and volunteers from all over the world, working on every aspect of the mission - including mentorship, teaching, and connecting people.
4+
5+
Diversity is one of our huge strengths, but it can also lead to communication issues and unhappiness. To that end, we have a few ground rules that we ask people to adhere to. This code applies equally to founders, mentors and those seeking help and guidance.
6+
7+
This isn't an exhaustive list of things that you can't do. Rather, take it in the spirit in which it's intended - a guide to make it easier to enrich all of us and the technical communities in which we participate.
8+
9+
This code of conduct applies to all spaces managed by the agentic starter kits project or red-hat-data-services. This includes IRC, the mailing lists, the issue tracker, DSF events, and any other forums created by the project team which the community uses for communication. In addition, violations of this code outside these spaces may affect a person's ability to participate within them.
10+
11+
If you believe someone is violating the code of conduct, we ask that you report it by emailing [wrebisz@redhat.com](mailto:wrebisz@redhat.com) or [tguzik@redhat.com](mailto:tguzik@redhat.com).
12+
13+
- **Be friendly and patient.**
14+
- **Be welcoming.** We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.
15+
- **Be considerate.** Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we're a world-wide community, so you might not be communicating in someone else's primary language.
16+
- **Be respectful.** Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the agentic starter kits community should be respectful when dealing with other members as well as with people outside the agentic starter kits community.
17+
- **Be careful in the words that you choose.** We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behavior aren't acceptable. This includes, but is not limited to:
18+
- Violent threats or language directed against another person.
19+
- Discriminatory jokes and language.
20+
- Posting sexually explicit or violent material.
21+
- Posting (or threatening to post) other people's personally identifying information ("doxing").
22+
- Personal insults, especially those using racist or sexist terms.
23+
- Unwelcome sexual attention.
24+
- Advocating for, or encouraging, any of the above behavior.
25+
- Repeated harassment of others. In general, if someone asks you to stop, then stop.
26+
- **When we disagree, try to understand why.** Disagreements, both social and technical, happen all the time and agentic starter kits is no exception. It is important that we resolve disagreements and differing views constructively. Remember that we're different. The strength of agentic starter kits comes from its varied community, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn't mean that they're wrong. Don't forget that it is human to err and blaming each other doesn't get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.
27+
28+
Original text courtesy of the [Speak Up! project](http://web.archive.org/web/20141109123859/http://speakup.io/coc.html).
29+
30+
## Questions?
31+
32+
If you have questions, please see the project [README](README.md) or open an issue. If that doesn't answer your questions, feel free to [wrebisz@redhat.com](mailto:wrebisz@redhat.com) or [tguzik@redhat.com](mailto:tguzik@redhat.com). For contribution guidelines and commit conventions, see [CONTRIBUTING.md](CONTRIBUTING.md).

CONTRIBUTING.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Contributing to Agentic starter kits
2+
3+
Thank you for your interest in contributing. This document gives a short overview of how to get involved.
4+
5+
## How to contribute
6+
7+
- **Report bugs or suggest features** – Open an [issue](https://github.com/red-hat-data-services/agentic-starter-kits/issues) and describe the problem or idea. Check existing issues first to avoid duplicates.
8+
9+
- **Submit code changes** – Create a branch (in your fork or directly in this repo if you have access), make your changes, and open a pull request (PR). You don’t need to fork if you can push branches here. Keep PRs focused; one feature or fix per PR is easier to review.
10+
11+
- **Improve documentation** – Fixes and clarifications in the README, agent docs, or code comments are always welcome. Use the `docs:` prefix in your commit (see below).
12+
13+
- **Add or fix tests** – If you add or change behavior, consider adding or updating tests and use the `test:` prefix in commits.
14+
15+
Before submitting, please read our [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you agree to uphold it.
16+
17+
## Commit message conventions
18+
19+
We encourage [Conventional Commits](https://www.conventionalcommits.org/) so that history and release notes stay clear.
20+
21+
Use one of these prefixes at the start of your commit message:
22+
23+
| Prefix | Meaning |
24+
| --------- | -------- |
25+
| **feat:** | A new feature |
26+
| **fix:** | A bug fix |
27+
| **perf:** | A change that improves performance |
28+
| **chore:**| Maintenance (deps, tooling, config) |
29+
| **docs:** | Documentation only |
30+
| **test:** | Adding or updating tests |
31+
32+
You can optionally add a scope (e.g. the agent or module name) in parentheses after the type.
33+
34+
### Examples
35+
36+
```
37+
feat: add health check endpoint to autogen_agent
38+
fix: correct env var name in deployment in langgraph_react_agent
39+
docs: update README with OpenShift deploy steps
40+
test: add tests for tool registration
41+
chore: bump python-dotenv in requirements
42+
```
43+
44+
This is optional but appreciated; maintainers may ask you to reword commits when preparing a release.
45+
46+
## Questions?
47+
48+
See the main [README](README.md) or open an issue. You can also contact [wrebisz@redhat.com](mailto:wrebisz@redhat.com) or [tguzik@redhat.com](mailto:tguzik@redhat.com).

0 commit comments

Comments
 (0)