dimensionalOS / dimensionalOS/dimos
Policy decisions WRT obvious bot PRs and issues
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
for example https://github.com/dimensionalOS/dimos/issues/1648
I think cheap solution to this is to assume broader OSS community posture which will get crystalized soon if it hasn't already.
For example I find Rust community notes reasonable thoughtful and measured
https://nikomatsakis.github.io/rust-project-perspectives-on-ai/feb27-summary.html
This is one of the maintainers proposal (not a community as whole) but looks like a good starting point to me we could adapt immediately if people agree:
- Contributors are responsible and held accountable for their contributions. Just submitting AI-generated content without reviewing themselves is absolutely unacceptable.
- The contributor must understand their contributed changes. They need to be able to answer questions from the reviewer about the changes.
- Contributors must responsibly disclose if a substantial portion of their contribution is AI-generated.
- Reviewers are empowered to decline reviewing/interacting contributions (including proposals and comments) that are primarily AI-generated.
- Submitting slop results in an immediate ban.
- Piping reviewer/maintainer questions into an LLM then posting the LLM’s response verbatim is an immediate ban.
if banning or refusing contribution we can also have a snippet of text to link as to why
Synced from DIM-736 by summer
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue 1648 and the linked Rust project perspectives summary, then compare the proposed rules with the project's needs. Done would mean reaching a documented decision on contribution policy and, if banning or refusing contributions is included, providing a reusable explanation snippet.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100