<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 4, 2017 at 8:57 AM, Roy Golan <span dir="ltr"><<a href="mailto:rgolan@redhat.com" target="_blank">rgolan@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>I'm getting the feeling I'm not alone in this, authoring and publishing a wiki page isn't as used to be for long time.<br><br>I want to suggest a bit lighter workflow: <br><br></div>1. Everyone can merge their page - (it's a wiki)<br></div> Same as with (public and open) code, no one has the motivation to publish a badly written<br></div> wiki page under their name. True, it can have an impact, but not as with broken code<br><br></div>2. Use Page-Status marker<br></div> The author first merges the draft. Its now out there and should be updated as time goes and its<br> status is DRAFT. Maintainers will come later and after review would change the status to<br> PUBLISH. That could be a header in on the page:<br> ---<br></div> page status: DRAFT/PUBLISH<br> ---<br><br></div><div> Simple I think, and should work.<br></div><br></div></blockquote><div><br></div><div>Sounds very good.</div><div><br></div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br><br></div></div>
<br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br></blockquote></div><br></div></div>