Development
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.
Mission Statement
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.
Building GParted
Briefly, the commands to build and install GParted into the default location of /usr/local are:
./configure make sudo make install
Full details of how to build GParted from source code, including a list of required dependencies and configuration options, can be found in the "Building from Source" section of the README file. Also included is a section on "Building using a Specific (lib)parted Version".
Source Code
Browse
the GParted git repository, hosted by GNOME.
Developing GParted using Git contains tips for
budding developers, including how to build GParted from git and how to
create your first GParted patch using git.
Communication
Issues and bugs are reported, discussed, and tracked using the GNOME bugzilla bug tracking system.
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 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.
Coding Style
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:
Artwork
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.
