dimensionalOS / dimensionalOS/dimos

Policy decisions WRT obvious bot PRs and issues

Open
#1,650 0 comments 0 reactions 0 assignees View on GitHub

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:

  1. Contributors are responsible and held accountable for their contributions. Just submitting AI-generated content without reviewing themselves is absolutely unacceptable.
  2. The contributor must understand their contributed changes. They need to be able to answer questions from the reviewer about the changes.
  3. Contributors must responsibly disclose if a substantial portion of their contribution is AI-generated.
  4. Reviewers are empowered to decline reviewing/interacting contributions (including proposals and comments) that are primarily AI-generated.
  5. Submitting slop results in an immediate ban.
  6. 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

Open the contributing guide

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.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.