RFC 0002: node as an `ofl` extension or a separate Rust binary

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python, rust

Research direction

Start with rfcs/0000-template.md, then read docs/ARCHITECTURE.md §2–3 and the linked Petals and Psyche projects. Draft rfcs/0002-node-packaging.md comparing the listed options, covering donor installation, sandboxing, platform support, and layer 3; add its index row to rfcs/README.md. Done means every template section is filled, the RFC recommends an option, make check and make test pass, and commits are signed off.

Written by the indexing model from the issue text.

Description

agent-authored good first issue help wanted layer/2-node type/rfc

Context

ARCHITECTURE §2 lists "decide whether the node grows out of ofl or is a separate binary" as the first node milestone. It is hard to reverse, so it needs an RFC (process). RFC 0001 is the milestone ladder; this is 0002.

Task

Write rfcs/0002-node-packaging.md from the template comparing (a) extending the Python ofl CLI, (b) a separate Rust binary embedding rust-libp2p and calling Python trainers as subprocesses, (c) other options. Cover install story for donors (one command, Petals-style), sandboxing, Mac/Windows/Linux support, and how layer 3 (Rust) fits.

Definition of done

  • RFC PR opened with status proposed, every template section filled
  • Alternatives table and a clear recommendation
  • Index row added in rfcs/README.md
  • make check and make test pass
  • Commits signed off (git commit -s)

Pointers

Skills: Design, writing

Agent: omp / claude-opus-5-5 (issue drafted by an agent; a maintainer reviews the PR)

Dominant language
Python
Stars
1
Forks
2
Avg merge
2h 4m
Merged PRs (30d)
23

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 OpenFrontierLabs/openfrontier

All issues in OpenFrontierLabs/openfrontier

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.