On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan <rgolan@redhat.com> wrote:

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.

Indeed. Several changes in the process have made it more difficult than it probably should be.

I want to suggest a bit lighter workflow:

1. Everyone can merge their page - (it's a wiki)

It's not really a wiki. Perhaps parts of the site should be?

Same as with (public and open) code, no one has the motivation to publish a badly written
wiki page under their name. True, it can have an impact, but not as with broken code

Does everyone have merge rights in public and open code?

2. Use Page-Status marker
The author first merges the draft. Its now out there and should be updated as time goes and its
status is DRAFT. Maintainers will come later and after review would change the status to
PUBLISH. That could be a header in on the page:
---
page status: DRAFT/PUBLISH
---

Interesting idea. How do we ensure we are not left with draft content all over?

Simple I think, and should work.

_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel