License of binarized G-code specification?

Open
#24 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start with doc/specifications.md and review the licensing question alongside the linked CC0, OWFa, and Mozilla guidance. Done would require a project decision and a clearly recorded license for the specification, but the issue provides no settled choice or implementation steps.

Written by the indexing model from the issue text.

Description

What license is the binarized G-code specification released under?

The license of this project is AGPL but that isn't very suitable for a standard, especially not a standard that wants to achieve wide adoption.

Something like the CC0 + OWFa that Mozilla suggest, or a similar other alternative, would be preferable.

Dominant language
G-code
Stars
73
Forks
24
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 prusa3d/libbgcode

All issues in prusa3d/libbgcode

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.