Following is a high level view of how development is guided and
managed on the GParted project.
Work on the GParted application is managed by Curtis Gedak.
Work on the GParted Live image is managed by Steven Shiau.
The goal of GParted is to provide an easy way to graphically manage disk device partitions, without unintended loss of data, through the use of GNU libparted and other free software file system tools.
Source Code Repository
The source code for GParted is managed under the GNOME git repository.
See the GParted git page for more information.
A list of dependencies required to build GParted from source code can be found in the "Building from Source" section of the README file.
Plans for new releases of GParted can be found in
We strive to create new releases of GParted about every 2 months. Having said that, we will create a new release in a much shorter time frame, especially if needed to fix critical bugs.
Application Development Guidelines
GParted is written
in C++ and uses
gtkmm for the Graphical
User Interface (GUI).
GParted uses GNU libparted to detect and manipulate devices and partition tables. Several optional file system tools provide support for file systems not included in libparted.
The general approach is to keep the GUI as simple as possible. We strive to conform to the GNOME Human Interface Guidelines. We try to keep the source code as maintainable as is reasonably possible. We seek to stay true to the GParted mission statement.
We try to ensure that the GParted will compile and run on the currently supported versions of many major GNU/Linux distributions (distros). Distros we often include in our testing include: Centos/RHEL, Debian, Fedora, openSUSE, and Ubuntu.
To help guide graphical interface design, we use 800x600 as our target minimum screen resolution.
There are no hard and fast coding standards for GParted. For now we
prefer code enhancements to match the surrounding coding style.
Having said that, the existing code base contains a mixture of indentation and alignment schemes which use various combinations of tabs and spaces. This is messy.
For patches and for new code we prefer to use tabs for indentation and spaces for alignment. For details on this "smart tab" alignment scheme, please refer to the following links:
Creative designs can be found on the artwork page.
Other Ways to Help
There are many ways to contribute to the GParted project that do not involve developing code. See the how to help page.