# Community Guidelines

### **Do's**&#x20;

#### 👏  |  Be constructive&#x20;

Constructive feedback consists of three elements: what went right or wrong, why it was or wasn’t effective, and what can be improved to make it better. It's great to say, "your project is excellent," but you have more effect when saying, "I liked \[feature] of your project because \[reason why]. I suggest looking into \[improvement] to make it even better".

#### 💪  |  Play to your strengths

You don’t need to give feedback on every aspect of a submission. If you can review the code, go straight to the GitHub repo. If you’re a product person, check out the “Products and Services” section. If business plans are your thing, look at the revenue model, competitive analysis, or marketing and sales proposal. Many submitters are new to Stellar and could use your specific insight and experience to scale their projects.

#### 🙌   |  Be kind and supportive, even to your competitors

We’re working together to build a community, and a welcoming environment increases participation and drives development.

### Don'ts

#### ❌   |  Don't wait

Building a business in this industry requires fast-paced development, so when you notice something about a project, say it immediately and don't wait. The sooner you tell them, the more time they have to incorporate your feedback into their project before voting begins.

#### ❌   |  Don't assume someone is wrong

Ask substantive questions that give contestants a chance to clarify or explain their project. When possible, suggest a change rather than merely pointing out a flaw.

#### ❌   |  Don't end it there

Following up after giving feedback indicates you're genuinely interested in seeing a project grow and increases the chance to see real change. If you're available and interested, let them know you're open to discussing things and supporting them where possible.

