community guidlines

Open
#53 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

No file, test, or entry point is named. Review the repository structure and any existing contributor or support material first, then define where the guidelines belong and ensure they address contributing, reporting problems, and seeking support.

Written by the indexing model from the issue text.

Description

There should be clear guidelines for third-parties wishing to:

Contribute to the software
Report issues or problems with the software
Seek support
Dominant language
Python
Stars
7
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FireDynamics/LEDSmokeAnalysis

All issues in FireDynamics/LEDSmokeAnalysis

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.