Skip to content

beam-bots/proposals

Beam Bots Logo

Beam Bots Proposals

License: Apache 2.0 REUSE status

Feature proposals for the Beam Bots robotics framework.

Process

  1. Draft — Create a proposal using the template
  2. Discuss — Open a PR, gather feedback
  3. Accept — Merge when ready to implement
  4. Implement — Build it
  5. Close — Update status when done

That's it. No committees, no final comment periods, no bureaucracy.

Structure

proposals/
├── README.md
├── template.md
├── accepted/
│   └── 0001-feature-name.md
├── implemented/
│   └── ...
└── rejected/
    └── ...

Proposals start in accepted/ when merged. Move to implemented/ when the feature ships. Move to rejected/ if we change our minds (with a note explaining why).

Numbering

Proposals are numbered sequentially: 0001, 0002, etc. Use the next available number when opening a PR.

Template

See template.md for the proposal format.

Proposals

# Name Status Package
0001 bb_teleop Proposed bb_teleop
0002 bb_policy Proposed bb_policy
0003 bb_dataset Proposed bb_dataset
0004 bb_mcp Proposed bb_mcp
0005 bb_tui Proposed bb_tui
0006 bb_motion_planning Proposed bb_motion_planning

About

Feature proposals for Beam Bots

Resources

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Sponsor this project

 

Packages

No packages published