[Rosetta-7] Improve CONTRIBUTING, conduct, support

Open
#871 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@roshankumar0036singh is already working on this.

Since Sep 11, 2026.

  • #877 by @mmaher32 — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
c, cmake, cpp

Research direction

Start with .github/CONTRIBUTING.md, the existing conduct file in .github/, the PR template, SECURITY.md, and ROADMAP.md. Verify the documented CMake, build, and ctest commands against the repository, then check that the acceptance points are met: no placeholders, a newcomer can run one test, and conduct and support paths are discoverable from the root.

Written by the indexing model from the issue text.

Description

documentation
Goal

Make first contribution easy. Fix stubs.

Tasks
  • Fill .github/CONTRIBUTING.md PR process now holding 1. ... 2. ....
  • Add build flows:
    • cmake -S . -B build
    • cmake --build build --target install
    • Loader flags example cmake -DOPTION_BUILD_LOADERS_PY=On -DOPTION_BUILD_LOADERS_NODE=On ..
    • Single test ctest -VV -R metacall-python-test
    • Full ctest, memcheck, ASan, TSan, clang-format.
  • Add style rules: C23 and C++23 default, -Wall -Wextra -Werror -fsanitize=address,undefined, clang-format, no dead code.
  • Add issue templates guide and review SLA.
  • Add AI-use disclosure field for PRs.
  • Add or link root CODE_OF_CONDUCT.md, SUPPORT.md. Current conduct lives only in .github/ with personal contact. Update contact or add team alias.
  • Fix PR template broken link to debugging section.
  • Link SECURITY.md and ROADMAP.md.
Acceptance
  • New contributor can build and run one test from doc alone.
  • No placeholder steps remain.
  • Conduct and support paths are discoverable from root.
Dominant language
C
Stars
1.8k
Forks
266
Avg merge
2d 16h
Merged PRs (30d)
14

Getting set up

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 metacall/core

All issues in metacall/core

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.