+ 1
It would be better, if we have a kind of FAQ. Then we can help our user's
troubleshooting : )

On Fri, Jan 29, 2016 at 5:36 PM, Hyung Sung Shim <[email protected]> wrote:

> +1
>
> 2016년 1월 29일 금요일, Victor Manuel Garcia<[email protected]>님이 작성한 메시지:
>
> > +1
> > El 29/1/2016 6:53, "DuyHai Doan" <[email protected] <javascript:;>>
> > escribió:
> >
> > > +1
> > >
> > > On Fri, Jan 29, 2016 at 3:39 AM, moon soo Lee <[email protected]
> > <javascript:;>> wrote:
> > >
> > > > Hi,
> > > >
> > > > I think documentation is not the strongest part of the project at the
> > > > moment.
> > > >
> > > > There're some undocumented features, out dated informations.
> > > > And i think more examples, tips and tutorials would be necessary.
> > > >
> > > > Also building guide lines for the doc and improving (font, font-size,
> > > > spaces, etc) would help making better, readable documentation.
> > > >
> > > > How about we figure out the list of tasks we need to do and create an
> > > > umbrella issue for it? Then it's more easier to take and resolve one
> by
> > > > one.
> > > >
> > > > What do you think?
> > > >
> > > > Thanks,
> > > > moon
> > > >
> > >
> >
>

Reply via email to