0
I Use This!
Activity Not Available

Project Summary

We propose to develop a specification for syntax and semantic description files (SSDFs) in order to allow the user configure a GNU system using their prefered intuitive UI . This enables the development of unified configuration tools (similar to the old linuxconf or KDE Control panel).

Why do we need unified configuration?

One of the strengths of Free Software programs is that their configuration is specified in flat text files. This can easily be seen by examining the /etc directory of any Free UNIX or UNIX-like system (eg: GNU/Linux. The Hurd). Unfortunately the is also a usability weakness of Free Software, as each configuration file for each program may have a unique syntax. Thus the system administrator may have to learn n * i syntaxes for each i configuration files of n installed programs. This makes configuration of a Free Software system difficult and/or prone to error.

How to approach unified configuration:

To remove the advantage of flat text files would be preposterous, additionally the removal of the current distributed configuration storage methodology would introduce possible weaknesses into an currently robust system. In short we do not intend to represent system configuration files in binary format, nor do we intend to colate system configuration files into a single point of failure. We intend to devise a syntax description language. This will allow developers to use their current flat text configuration files and augment them with a sperate syntax description file. The syntax description file could be interpreted by arbitrary user interfaces in order to provide a single configuration tool for multiple applications.

A syntax description file should also allow a semantic description of entries in a configuration file. This should be either a formal semantic description of the effects a configuration change will have on the system (difficult but preferred) or simply a textual description of the effects of a configuration change.

Tags

No tags have been added

In a Nutshell, neo-LinuxConf...

 No code available to analyze

Open Hub computes statistics on FOSS projects by examining source code and commit history in source code management systems. This project has no code locations, and so Open Hub cannot perform this analysis

Is this project's source code hosted in a publicly available repository? Do you know the URL? If you do, click the button below and tell us so that Open Hub can generate statistics! It's fast and easy - try it and see!

Add a code location

GNU General Public License v2.0 or later
Permitted

Commercial Use

Modify

Distribute

Place Warranty

Forbidden

Sub-License

Hold Liable

Required

Include Copyright

Include License

Distribute Original

Disclose Source

State Changes

These details are provided for information only. No information here is legal advice and should not be used as such.

All Licenses

This Project has No vulnerabilities Reported Against it

Did You Know...

  • ...
    Black Duck offers a free trial so you can discover if there are open source vulnerabilities in your code
  • ...
    compare projects before you chose one to use
  • ...
    in 2016, 47% of companies did not have formal process in place to track OS code
  • ...
    you can embed statistics from Open Hub on your site

 No code available to analyze

Open Hub computes statistics on FOSS projects by examining source code and commit history in source code management systems. This project has no code locations, and so Open Hub cannot perform this analysis

Is this project's source code hosted in a publicly available repository? Do you know the URL? If you do, click the button below and tell us so that Open Hub can generate statistics! It's fast and easy - try it and see!

Add a code location

Community Rating

Be the first to rate this project
Click to add your rating
   Spinner
Review this Project!
Sample ohloh analysis