On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan <firstname.lastname@example.org> wrote:wiki page under their name. True, it can have an impact, but not as with broken codeSame as with (public and open) code, no one has the motivation to publish a badly writtenI'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.1. Everyone can merge their page - (it's a wiki)
I want to suggest a bit lighter workflow:
+1.Moreover, I think we shouldn't block any merging. Instead, wiki maintainers could act afterwards and revert when needed (Wikipedia style). Another issue is that (sadly) unlike mediawiki, we need to wait for wiki publish after a change. So I'd suggest to build and publish the wiki at least once a day. Any way, I think we should make the workflow much more intuitive and pleasant like the previous wiki - i.e. much less restrictive than manipulating a code base.
page status: DRAFT/PUBLISH2. Use Page-Status markerThe 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:
---Simple I think, and should work.
Users mailing list