Re: [ovirt-devel] Lowering the bar for wiki contribution?
On Wed, Jan 4, 2017 at 9:57 AM, 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 > > +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. > 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. > > > > > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Lowering the bar for wiki contribution?
On 4 January 2017 at 11:06, Nir Soffer wrote: > On Wed, Jan 4, 2017 at 10:51 AM, Barak Korren wrote: > > On 4 January 2017 at 09:57, 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. > > > > Maybe we're using the wrong tool for the job? > > The site is intentionally not a wiki to allow OSAS some editorial > > control over what goes on the public site. > > > > I'm guessing that the scenario you are talking about here is a > > developer looking to create a preliminary design document for further > > discussion. Maybe we need a different tool and process for that? > > I agree, we are using the wrong tool for the job of putting initial design > for discussion. > > For publishing user documentation the site is ok. > > I miss the wiki we had, it was easier to use for development of feature > pages and developer documentation. > Who is our OSAS contact these days? > Nir > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Lowering the bar for wiki contribution?
On Wed, Jan 4, 2017 at 10:51 AM, Barak Korren wrote: > On 4 January 2017 at 09:57, 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. > > Maybe we're using the wrong tool for the job? > The site is intentionally not a wiki to allow OSAS some editorial > control over what goes on the public site. > > I'm guessing that the scenario you are talking about here is a > developer looking to create a preliminary design document for further > discussion. Maybe we need a different tool and process for that? I agree, we are using the wrong tool for the job of putting initial design for discussion. For publishing user documentation the site is ok. I miss the wiki we had, it was easier to use for development of feature pages and developer documentation. Nir ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Lowering the bar for wiki contribution?
On 4 January 2017 at 09:57, 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. Maybe we're using the wrong tool for the job? The site is intentionally not a wiki to allow OSAS some editorial control over what goes on the public site. I'm guessing that the scenario you are talking about here is a developer looking to create a preliminary design document for further discussion. Maybe we need a different tool and process for that? -- Barak Korren bkor...@redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/ ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Lowering the bar for wiki contribution?
On Wed, Jan 4, 2017 at 9:57 AM, 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. > 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? Y. > > Simple I think, and should work. > > > > > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Lowering the bar for wiki contribution?
On Wed, Jan 4, 2017 at 8:57 AM, 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. > > Sounds very good. +1 > > > > ___ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] 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 Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Lowering the bar for wiki contribution?
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. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
