Desktop Research Manifest

1.  Field of Interest

Desktop issue definition

An issue is related to the desktop if it is : client side or end-user oriented workstation use. Basically, that's everything UI oriented, plus hardware management, installation problems as well as simple system management. Basically, if it is client side and doesn't use servers, it is our responsability.

Examples

setting internet/lan connection is desktop, but setting a ftp server is not. setting sound card, graphic card is desktop

2.  Problems Resolution

Exploration phase

GOAL : describe and decide

• throw a description here, verify validity
• preliminary discussion here and/or irc
• Optional : Prepare a prototype, testcase or a little code snippet to let everybody play
• talk with the devs that are the most concerned with the issue, get additional information, ask if there is a good reason not to handle it, inform them that plan to address a GLEP
• APPROVAL 1 : Is it worth pursuing this proposal? The result should be written to the mailing list and on the xml project page if we decide to handle the case.

Draft phase

GOAL : have a GLEP draft

• add new tasks : at least some time to research further (with a milestone), and some time to find a solution (with milestone)
• one of the task should be GLEP writing. Possibly one people should take care that the draft is conforming to GLEP standard
• assign people to the task, set up deadlines. People assigned should include as most as possible external devs that are concerned by the issue, so that the GLEP get discussed
• all this should be well written in the xml project pages, and should end with a new and shiny GLEP draft
• APPROVAL 2 : do we all (at desktop-research + involved devs) agree on the draft?

GLEP submission

• we submit the GLEP to the responsible entity, so that they approve it, or not

3.  Additional precisions

XML project pages precisions

Their main goal is to organize the work, and archive what's been done. They should be the canvas to the GLEP and development production. devs assigned to some task are responsible of it, and thus should maintain their task on the project pages.

GLEP precision

The GLEP should contain contain the key parts of the discussions from the discussion phase, problem identification (what is the problem), problem acceptation (is this really a problem), problem exploration (what are the causes and possible solutions to the problem) , proposed solution and the merits of this particular solution. The latter of course from later discussions.

Behaviour

We'll try to work together in a peacefull and friendly manner, so no use to be strict for every points. Nevertheless, rules are still usefull for extreme situations.

The contents of this document are licensed under the Creative Commons - Attribution / Share Alike license.