<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 05/ 1/16 04:45 PM, Aurélien Larcher
wrote:<br>
</div>
<blockquote
cite="mid:CAHMq6q3mWYSTdQd6_ROaGw6fdKZFBf9rWvnR=EqLJ7P8o0QM9Q@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"> I
would like you have been doing this not alone, but
within Openindiana community and cooperation with
others, with announcing it here.<br>
</blockquote>
<div><br>
</div>
<div>Oh but this has been the opportunity of several
discussion on irc and by email.<br>
</div>
<div>I think the idea of a proof of concept before
involving more people is not a problem per se.<br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Involving more people in a process that results in something with
lower quality then we currently have , while not accepting OI's
documentation licensing does not qualify as OI's project.<br>
<br>
<br>
<blockquote
cite="mid:CAHMq6q3mWYSTdQd6_ROaGw6fdKZFBf9rWvnR=EqLJ7P8o0QM9Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div class="gmail_extra">
<div class="gmail_quote">
<div>In any case, the initial questions were:<br>
</div>
<div>- review existing documentation systems from BSD
and Linux distributions<br>
</div>
<div>- come up with a process lowering the barrier for
contributions<br>
</div>
<div>- allow conversion between different formats<br>
</div>
<div>- minimize the "man/hour" cost of deployment and
need for maintenance<br>
<br>
</div>
<div>IMHO Michael's solution satisfies all the
requirements.<br>
</div>
<div>When/If/As soon as the proposed solution is
considered technically, the considerations that you
raise (like migration to OI infrastructure) should be
addressed in a next stage but are orthogonal to
current proposal.<br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Next stage is almost always never. <br>
If documentation is not on OI's infrastructure it is not OI's
documentation.<br>
If it does not use Oi's documentation licensing, it's not OI
documentation. <br>
If it is not contributed with contribution agreement , it is not OI
documentation.<br>
If it is done without review and some plan of priorities, it's not
OI's documentation.<br>
<br>
- We are not BSD nor Linux and looking at them could help in some
extent in the future, but we have illumos and Opensolaris
documentation to maintain and extend, not to re-invent new wheels
here.<br>
- Lowering the involvement process should include people in the
community, and not supporting effort that goes against OI's
documentation principles. It also does not includes re-inventing the
wheels.<br>
(Reinventing the whell includes rewriting already existing docs,
instead of renewing existing one.)<br>
- Communication between formats it already done with XML and
exporting to html and PDF<br>
<br>
What we see here is Wiki reinvented and OI already has a Wiki!<br>
Please use Wiki if you think you have some great article to write
and you want it to be part of Openindiana. Sites like .ninja and
github web pages are not places for Openindiana docs, especially if
they are not licensed to be OI docs.<br>
- Minimizing man/hour requires accepting OI's documentation licenses
and there is no compromise about that.<br>
*You aether accept open documentation license including Contributor
agreement to OI or you contribute your time at somewhere else.*<br>
<br>
</body>
</html>