Rules · Read before applying
Community rules
The rules every member of the KDU Developer Community agrees to: behaviour, taking part, crediting work, use of the platforms, and how breaches are handled.
Working version
This is the current version. The leadership team will confirm the final wording before the community opens to a wider group. If something reads wrong to you, say so — that is easier to fix now than later.
The point of having rules is not to make the community strict. It is to avoid confusion later, so everyone knows what is expected of them and what they can expect from everyone else. Applying to join means agreeing to these.
1. General behaviour
- Treat every member with respect, in every channel and every meeting.
- No harassment, no discrimination, no abuse. This one is not negotiable.
- Disagree with the argument, not the person.
- Keep communication professional and appropriate.
2. Taking part
- Respect meetings and activities. Turn up when you said you would, and say early when you cannot.
- Do not spam the channels.
- Keep discussion relevant to the channel it is in.
- Ask questions freely. Nobody here is judged for not knowing something.
3. Projects and credit
- Respect the work other members have done.
- Credit what you use — code, designs, writing, data, anything.
- Never present work that is not yours as your own.
- Agree who is responsible for what at the start of a group project.
4. Communication platforms
- Use each channel for what it is for.
- Keep announcements, discussion, project work and casual conversation separate.
- Post appropriate content only.
- What a member shares inside the community stays inside it, unless they say otherwise.
5. Leadership and decisions
- The leadership team is responsible for the rules, the platforms, the activities and the organisation.
- Decisions are made by the leadership team, and explained when a member asks.
- Any member can propose an improvement, and proposals are answered either way.
- Bring problems to the leadership team early rather than letting them grow.
6. If a rule is broken
Most problems are misunderstandings, so the first step is always a conversation. Beyond that:
- A private conversation with someone on the leadership team.
- A formal warning if it continues.
- Removal from the community for serious or repeated breaches.
- Harassment, discrimination, or passing off work that is not yours can mean removal without the earlier steps.
7. Changes to these rules
These are not permanent. As the community grows the leadership team will review them and improve them where necessary. Members can propose changes at any time, and anything material will be announced on the community platform before it takes effect.