blob: f73b8fe7f8361b4f85340d08cc4de85e3f1b42d9 (
plain)
1
2
3
4
5
6
|
<div>My question is basically revolved around the fact that mdk / mdv has always been a pretty active community around the documentation, and in all the languages I think it does. On the other, as you point out there were clear and well defined process for creating official documentation.</div>
<div><br></div><div>On the wiki, we have all seen change so diverse content by language. This is a sign of wealth but may be unfortunate because we lost by lack of unification.</div><div>The other defect of the wiki is the feeling of unfinished work forever. (When you do not implement the same procedures as in Gentoo or Fedora). Which, by experience one realizes, is part of a source of confusion for readers, and other corporate sources of exhaustion for writers, because of criticism due to the first point.</div>
<div><br></div><div>The process you describe, and that you report to want to keep extending it, the process is professional, professional quality.</div><div><br></div><div>And I want to ask you some questions about how best to:</div>
<div>1. not frustrate the contributors to the wiki, they can participate</div><div>2. not repeat the mistakes of a wiki giving the impression of never finished (not good for users, not as nice returns for writers)</div><div>
3. not to lose local skills when they are not able to have a minimum technical English despite having all the qualities and willingness to participate</div><div><br></div><div>Hence the idea (but certainly not the best) can also enhance the professional quality documentation with translations, certainly rare in the sense other languages -> English. And not just in one direction.</div>
<div><br></div><div>Regards</div><div><br></div>
|
