From Fedora Project Wiki
Line 28: Line 28:
There are several system configuration tools in Fedora which differs in terms of functionality, look and feel and quality. The aim of this project is to enhance this tools - unify look and feel, add better functionality and raise overall quality. Some of these tools are even obsoleted now.  
There are several system configuration tools in Fedora which differs in terms of functionality, look and feel and quality. The aim of this project is to enhance this tools - unify look and feel, add better functionality and raise overall quality. Some of these tools are even obsoleted now.  


=== Consistent look & feel
=== Consistent look & feel ===
** Follow Gnome Human Interface Guidelines http://library.gnome.org/devel/hig-book/stable/
** Follow Gnome Human Interface Guidelines http://library.gnome.org/devel/hig-book/stable/
** Consistently use dialog/application style  
** Consistently use dialog/application style  

Revision as of 14:29, 20 January 2009


Feature Name

System configuration tools cleanup - phase 1

Summary

Fedora includes several system configuration tools (system-config-*). Each of these configuration tools...

This effort includes:

  • GUI look & feel consistency
  • elimination of not used tools
  • better functionality

Owner

Current status

  • Targeted release: Fedora 42
  • Last updated: 2009-01-09
  • Percentage of completion: ?


Detailed Description

There are several system configuration tools in Fedora which differs in terms of functionality, look and feel and quality. The aim of this project is to enhance this tools - unify look and feel, add better functionality and raise overall quality. Some of these tools are even obsoleted now.

Consistent look & feel

Tools to eliminate

Functionality

Benefit to Fedora

System configuration tools are very visible parts of Fedora and high quality management tools could attract more users from competitor's operating systems. Also this project will help current Fedora users to maintain their systems in more efficient way.

Scope

How To Test

User Experience

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion