Hi PyBricks maintainers,
URML (urml.dev) is a small open language for describing robot intent. A user writes "drive forward 30 cm, then beep"; URML translates that to move_to and play_sound primitives, validates against the hub's manifest, then dispatches. URML's edu-runtime already ships a LEGO SPIKE Prime adapter, and the natural next step is to declare PyBricks specifically as a substrate the manifest can target. Apache-2.0 on URML's side, no change to PyBricks proposed, nothing for you to maintain.
Two short questions, both light. First: the pybricks-micropython repo currently shows "Other" as its license; could you confirm the OSI license, or point at the LICENSE file that should be authoritative? URML's downstream packaging depends on knowing whether this is MIT, BSD, or something else. Second: is pybricks/support the right place to keep that conversation, or do you prefer the forum at pybricks.com for design-shape questions like this?
Full write-up if useful: https://github.com/URML-MARS/URML/blob/rfc/move18-batches-2to4-complete/docs/rfcs/0235-pybricks-outreach.md
Thanks for keeping Pybricks the cleanest path off the LEGO default firmware.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.
Hi PyBricks maintainers,
URML (urml.dev) is a small open language for describing robot intent. A user writes "drive forward 30 cm, then beep"; URML translates that to
move_toandplay_soundprimitives, validates against the hub's manifest, then dispatches. URML's edu-runtime already ships a LEGO SPIKE Prime adapter, and the natural next step is to declare PyBricks specifically as a substrate the manifest can target. Apache-2.0 on URML's side, no change to PyBricks proposed, nothing for you to maintain.Two short questions, both light. First: the pybricks-micropython repo currently shows "Other" as its license; could you confirm the OSI license, or point at the LICENSE file that should be authoritative? URML's downstream packaging depends on knowing whether this is MIT, BSD, or something else. Second: is pybricks/support the right place to keep that conversation, or do you prefer the forum at pybricks.com for design-shape questions like this?
Full write-up if useful: https://github.com/URML-MARS/URML/blob/rfc/move18-batches-2to4-complete/docs/rfcs/0235-pybricks-outreach.md
Thanks for keeping Pybricks the cleanest path off the LEGO default firmware.
Ido Yahalomi (URML, greenvh@gmail.com)
AI-assisted prose, maintainer-reviewed before posting (see VIBE.md). Human-only correspondence available on request.