I once tried to edit a broken link in current documentation and lost hope after 10 minutes of efforts.
Being a sysadmin, I understand the fear of unknown/untrusted people accessing stuff and performing uncontrolled changes, but generally speaking I believe the majority of this community is not driven by 10y old cracker attitudes: I trust that the additional value provided by people will greatly overcome a few typos and errors. +1 Cheers AG -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Martin Polednik Sent: Wednesday, January 4, 2017 9:01 AM To: Roy Golan <[email protected]> Cc: users <[email protected]>; devel <[email protected]> Subject: Re: [ovirt-users] Lowering the bar for wiki contribution? On 04/01/17 09:57 +0200, Roy Golan 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. > >I want to suggest a bit lighter workflow: > >1. Everyone can merge their page - (it's a wiki) > 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 > >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 > --- > > Simple I think, and should work. +1, github's contribution workflow is terrible and doesn't make any sense for wiki pages. >_______________________________________________ >Devel mailing list >[email protected] >http://lists.ovirt.org/mailman/listinfo/devel _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
