On Wed, Mar 04, 2015 at 11:55PM, Branko Čibej wrote: > On 04.03.2015 23:47, Konstantin Boudnik wrote: > > On Wed, Mar 04, 2015 at 11:41PM, Branko Čibej wrote: > >> On 04.03.2015 23:33, Konstantin Boudnik wrote: > >>> On Wed, Mar 04, 2015 at 02:22PM, Dmitriy Setrakyan wrote: > >>>> On Wed, Mar 4, 2015 at 2:20 PM, Konstantin Boudnik <[email protected]> > >>>> wrote: > >>>> > >>>>> On Wed, Mar 04, 2015 at 02:18PM, Dmitriy Setrakyan wrote: > >>>>>> readme.io is a very cool documentation platform which gives free web > >>>>>> hosting, versioning, and sexy looks to open source projects, including > >>>>>> Apache projects. It stores documentation in a regular markdown format, > >>>>> and > >>>>>> I will add the MD files to the GIT tree before doing the next release. > >>>>> This > >>>>>> way readme.io will be the copy of the documentation stored in github. I > >>>>> You meant 'stored in Apache git", didn't you? > >>>>> > >>>> Yes, the Apache git. > >>> It seems to be satisfactory solutio as far as we keep the original docs > >>> source > >>> in Apache, no? > >> There are a couple open questions here: > >> > >> * While all committers can update the docs, all committers should also > >> be able to manage the readme.io site. AFAIK there's no automated way > >> to achieve that, and no documented way for adding site > >> administrators. That's kind of a bad start. > > if readme.io would only be a "mirror" of real docs that issue will sorta go > > away, right? As no one would need to manage or change the site? > > But that's not the case. Docs in git != online docs, so it's not a > mirror, it's the only online source.
True, unless there's a way to transpose the docs from source code to something like (c)wiki we might have a problem. > Tecnically, you can view the docs with 'cat | less' and use your > imagination to interpret the CSS and markup ... My imagination works better than that - I can open a disk file in my FF ;) And let it do the rest. Cos
