BurningForge Community Rules

BurningForge should feel like a serious workshop: open, practical, curious, and respectful.

These rules are here to protect that atmosphere without turning the forum into a bureaucratic space.

1. Respect the Work and the People

People come here to learn, build, share, and ask for help.

Treat others with respect, especially when:

  • they are new

  • they are wrong

  • they are still learning

  • they built something imperfect

  • they documented a failed experiment

Good engineering communities grow when people can show unfinished work without being mocked for it.

2. Be Honest and Constructive

Technical criticism is welcome.

Dismissive behavior is not.

If you disagree, explain:

  • what you think is wrong

  • why it may be a problem

  • what evidence or experience supports your view

  • what better direction you would suggest

The goal is to improve the work, not to win an argument.

3. No Toxicity, No Meaningless Noise

Do not fill discussions with:

  • insults

  • personal attacks

  • baiting

  • ego contests

  • repetitive low-value posting

  • pointless arguments that add no technical or community value

A little humor is fine. Repeated noise that makes useful discussion harder is not.

4. No Fraud, Scams, or Deceptive Behavior

Do not use the forum to:

  • mislead people

  • impersonate others

  • sell fake services

  • post dishonest offers

  • request money or access through manipulation

  • promote fraudulent schemes

Trust is hard to build and easy to destroy.

5. Be Careful With Dangerous Experiments

Many community topics may involve:

  • high temperatures

  • tools

  • rotating machinery

  • batteries

  • power electronics

  • chemicals

  • pressure

  • lasers

  • sharp tools

Do not encourage reckless behavior.

When sharing risky processes:

  • mention relevant hazards

  • describe safety constraints clearly

  • avoid presenting dangerous steps as harmless

  • do not pressure others into unsafe testing

BurningForge should help people build boldly, not carelessly.

6. Be Responsible for the Instructions You Publish

If you post a guide, tutorial, or technical walkthrough, do your best to make it:

  • understandable

  • accurate

  • honest about limitations

  • clear about assumptions

  • clear about what you have actually tested

It is acceptable to post work in progress.

It is not acceptable to present guesses as proven instructions without warning.

7. Respect Copyright, Licensing, and Attribution

If you use someone else’s work, respect:

  • licenses

  • attribution requirements

  • reuse conditions

  • authorship

Do not repost paid files, stolen documentation, or proprietary material that you do not have the right to share.

If you are unsure, say so and ask.

8. Future Project Posting Rules

As project publishing becomes more structured, we will likely ask members to keep project topics reasonably documented.

That may include:

  • a clear project goal

  • current status

  • components or tools used

  • logs, photos, or diagrams where relevant

  • known problems

  • licensing or usage notes where applicable

The point is not perfection. The point is making topics useful to others.

9. Help Moderation Early

If you see a problem:

  • flag it through forum tools when available

  • contact moderators or admins if needed

  • provide context, not drama

When reporting a moderation issue, try to include:

  • a link to the topic or post

  • what happened

  • why it may be a problem

  • whether safety, fraud, harassment, or spam is involved

Do not start public fights when a quiet report will solve the issue better.

10. Build the Kind of Community You Want to Return To

BurningForge is still early.

That means the tone we establish now matters a lot.

If you want a community where people document real work, share hard-earned lessons, and help each other build unusual things, act in a way that makes that possible.

What Next

If you are not sure whether something belongs on the forum, ask openly and in good faith. It is better to clarify early than to create avoidable friction later.