Who develops Anaconda ?

• The Red Hat installer team
  • Located mostly in Brno and Westford
• the community
  • fairly small amount of direct code contributions
  • but contributes A LOT by testing & filling of bug reports

The Anaconda Puzzle

The Anaconda Puzzle

• Anaconda is not a monolith (anymore)
• parts have been split to independent components where appropriate
  • to ease maintenance
  • to be more flexible
  • to make the pieces available for others

Storage

Storage

• the Blivet storage modeling library
• the libblockdev block device handling library
  • written in C with GObject Introspection support
• the libbytesize storage device size handling library
  • also written in C with GObject Introspection support
• pyparted Python bindings for parted

Image creation

• LORAX
  • tools for creating images, including the Anaconda boot.iso, live disk images, iso's, and filesystem images
• livecd-tools
  • tools for live CD creation

And the rest

• Initial Setup
  • a tool for final system re-/configuration after the installation
  • mostly just a thin wrapper around Anaconda spokes and modules
• Pocketlint
  • started as our Pylint config
  • then it became sentient and is now an independent component
• anaconda-user-help
  • holds content for the built-in help system
  • generated from the Installation Guide source code
• python-meh
  • a GUI & TUI exception handler
  • supports forwarding of tracebacks to libreport/Bugzilla

Use the source (code)

• everything is under the https://github.com/rhinstaller umbrella:
  • https://github.com/rhinstaller/anaconda
  • https://github.com/rhinstaller/pykickstart
  • https://github.com/rhinstaller/lorax
  • https://github.com/rhinstaller/blivet
  • https://github.com/rhinstaller/libblockdev
  • https://github.com/rhinstaller/libbytesize
  • https://github.com/rhinstaller/initial-setup
  • https://github.com/rhinstaller/python-meh
  • https://github.com/rhinstaller/pocketlint
  • etc.

How to contribute

• by sending patches/pull requests - of course :)
• by testing of Anaconda & co
  • and reporting the bugs you find so we can fix them
• by helping us to improve our documentation
• by translating Anaconda
  • https://fedora.zanata.org/project/view/anaconda
• by using some of our libraries in your project
  • rather than writing your own ;-)

Talk to us

• on the mailing list
• on IRC
  • #anaconda on Freenode
• here in person! ;-)