blob: e619a5b6bc3cc767f7cb7f88fd997b57529cc52c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,
<br>
<br>
I have started to document this tool : <br>
<h4 _path="/0/0/0/0" class="db_title db_section_title"><span
_path="/0/0/0/0/0" class="text-node">Set up a new network
interface (LAN, ISDN, ADSL, ...)</span></h4>
It is accessible in Calenco and visible soon here :
<br>
<a class="moz-txt-link-freetext"
href="http://docteam.mageia.nl/en/MCC/content/draksambashare.html">http://docteam.mageia.nl/en/MCC/content/drakconnect.html</a>
for
<br>
technically proofreading.
<br>
<br>
Some sections are not documented, besause it is necessary to have
the hardware connected to configure it:<br>
- Satellite connection (DVB)<br>
- Cable modem connection<br>
- GPRS/Edge/3G connection<br>
- Bluetoth Dial-Up Networking connection<br>
<br>
If you have such a hardware, you can provide to doc team screenshots
at each step of the configuration, or write the section.<br>
<br>
The technical proofreading means:
<br>
1/ Detect if some part of documentation is lacking, for example a
path for a wizard, or some window.
<br>
2/ Detect if what it is said is correct or not.
<br>
3/ Indicate if you feel that some part must be more detailed, for
example the implication of some options.
<br>
4/ Indicate if you feel that the actions done by the tool are not
enough described, for example which files are modified, which
service is restarted...
<br>
<br>
You can give your opinion even on one point and even if you do not
know how to complete/modify the documentation. You're welcome <span
class="moz-smiley-s1" title=":)"></span>
<br>
Papoteur
</body>
</html>
|
