Skip to content

Development tree for Marlin firmware. See MarlinFirmware/Marlin for releases.

License

Notifications You must be signed in to change notification settings

eboston/MarlinDev

 
 

Repository files navigation

Marlin 3D Printer Firmware

Documentation has moved to [marlinfirmware.org](http://www.marlinfirmware.org).

Development Only

Not for production use – use with caution!

The dev branch contains the most up-to-date Marlin code. When reporting any issues, please check to see if they are resolved in this branch first. But let us know if issues exist in tagged releases so that we can document and patch them.

Testing

The RC branch will contain the latest pre-release candidate.

Submitting Patches

Development patches should be submitted as a Pull Request against the master branch

For the latest tagged version of Marlin (currently 1.0.2 – January 2015) you should switch to the Release Repository.

Current Status: Bug Fixing

Marlin development is being accelerated to catch up with a long list of issues. Check the Issues and Pull Requests links on the right to to see what we are currently working on.

Coverity Scan Build Status Travis Build Status

Contact

Google Hangout: . Hangout We have a hangout every 2 weeks. Search the issue list for "Hangout" and you will see what time and date the next event is going on.

Credits

The current Marlin dev team consists of:

  • Scott Lahteine [@thinkyhead] - English
  • Andreas Hardtung [@AnHardt] - Deutsch, English
  • [@Wurstnase] - Deutsch, English
  • F. Malpartida [@fmalpartida] - English, Spanish
  • [@CONSULitAS] - Deutsch, English
  • [@maverikou]
  • Chris Palmer [@nophead]
  • [@paclema]
  • [@epatel]
  • Erik van der Zalm [@ErikZalm]
  • David Braam [@daid]
  • Bernhard Kubicek [@bkubicek]
  • Richard Wackerbarth [@Wackerbarth] - English
  • Roxanne Neufeld [@Roxy-3DPrintBoard] - English

More features have been added by:

  • Alberto Cotronei [@MagoKimbra]
  • Lampmaker,
  • Bradley Feldman,
  • and others...

License

Marlin is published under the GPL license because we believe in open development. The GPL comes with both rights and obligations. Whether you use Marlin firmware as the driver for your open or closed-source product, you must keep Marlin open, and you must provide your compatible Marlin source code to end users upon request. The most straightforward way to comply with the Marlin license is to make a fork of Marlin on Github, perform your modifications, and direct users to your modified fork.

While we can't prevent the use of this code in products (3D printers, CNC, etc.) that are closed source or crippled by a patent, we would prefer that you choose another firmware or, better yet, make your own.

Flattr this git repo

About

Development tree for Marlin firmware. See MarlinFirmware/Marlin for releases.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C 71.3%
  • C++ 14.0%
  • Eagle 10.8%
  • Other 2.3%
  • Processing 0.8%
  • JavaScript 0.3%
  • Other 0.5%