fuel-dev team mailing list archive

[Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>]

Regarding docs: as Ivan mentioned, we have nailgun Python generated docs
from there.
If we move dev docs to fuel-docs, it will be impossible to generate our
Nailgun Python documentation.



On Tue, Dec 17, 2013 at 3:11 PM, Ivan Kolodyazhny <ikolodyazhny@xxxxxxxxxxxx
> wrote:

> Dmitry,
> I'm partially agree with you. You touched more general problem, that
> nailgun docs. Actually, there are a lot not web-related code in a fuel-web
> repo. E.g. it will be good to move out at least fuel menu and fuel client
> to separate repositories.
>
>
> On Tue, Dec 17, 2013 at 5:28 AM, Paul Reiber <reiber@xxxxxxxxx> wrote:
>
>> +N.
>> Kind regards,
>> -Paul Reiber
>> Phone: (210)854-8253
>> Email: paul@xxxxxxxxxx
>> Web: http://bit.ly/reiber
>>
>>
>> On Mon, Dec 16, 2013 at 5:26 PM, Andrew Woodward <xarses@xxxxxxxxx>
>> wrote:
>> >
>> >
>> >
>> > On Mon, Dec 16, 2013 at 2:49 PM, Dmitry Borodaenko
>> > <dborodaenko@xxxxxxxxxxxx> wrote:
>> >>
>> >> All,
>> >>
>> >> I think it's worth considering moving the fuel-dev docs from fuel-web
>> >> to fuel-docs repository. The development docs are relevant for all our
>> >> repositories, not just fuel-web, and it, given the similarities
>> >> between fuel-docs and fuel-web/docs, will be easier to maintain a
>> >> single set of CI scripts instead of maintaining two slightly different
>> >> copies.
>> >>
>> > +1
>> >
>> >>
>> >> My 2c,
>> >> -Dmitry
>> >>
>> >> On Mon, Dec 16, 2013 at 2:43 PM, Ivan Kolodyazhny
>> >> <ikolodyazhny@xxxxxxxxxxxx> wrote:
>> >> > Thanks Dmitry, it was my typo.
>> >> >
>> >> > Example of CI checks and docs preview:
>> >> > Here is build for review request #6187
>> >> >
>> https://fuel-jenkins.mirantis.com/job/stackforge-verify-fuel-docs/46/.
>> >> > "Fuel
>> >> > Docs build results" link navigates you to a docs preview.
>> >> >
>> >> > We've got development documentation(docs.mirantis.com/fuel-dev/) in
>> a
>> >> > fuel-web repository. We have no any development docs checks or
>> preview
>> >> > for
>> >> > review requests but we are working on it.
>> >> >
>> >> >
>> >> > On Tue, Dec 17, 2013 at 12:38 AM, Dmitry Borodaenko
>> >> > <dborodaenko@xxxxxxxxxxxx> wrote:
>> >> >>
>> >> >> On Mon, Dec 16, 2013 at 2:23 PM, Ivan Kolodyazhny
>> >> >> <ikolodyazhny@xxxxxxxxxxxx> wrote:
>> >> >> > As was announced earlier, we moved our user and administration
>> guide
>> >> >> > to
>> >> >> > StackForge: https://github.com/stackforge/fuel-web.
>> >> >>
>> >> >> Actual link: https://github.com/stackforge/fuel-docs
>> >> >>
>> >> >> (fuel-web is our repository for Fuel UI, not the documentation)
>> >> >>
>> >> >> --
>> >> >> Dmitry Borodaenko
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Regards,
>> >> > Ivan "e0ne" Kolodyazhny,
>> >> > Software Engineer, Mirantis, Inc.
>> >>
>> >>
>> >>
>> >> --
>> >> Dmitry Borodaenko
>> >>
>> >> --
>> >> Mailing list: https://launchpad.net/~fuel-dev
>> >> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> >> Unsubscribe : https://launchpad.net/~fuel-dev
>> >> More help   : https://help.launchpad.net/ListHelp
>> >
>> >
>> >
>> >
>> > --
>> > If google has done it, Google did it right!
>> >
>> > --
>> > Mailing list: https://launchpad.net/~fuel-dev
>> > Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~fuel-dev
>> > More help   : https://help.launchpad.net/ListHelp
>> >
>>
>
>
>
> --
> Regards,
> Ivan Kolodyazhny,
> Software Engineer, Mirantis, Inc.
>
> --
> Mailing list: https://launchpad.net/~fuel-dev
> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~fuel-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Mike Scherbakov
#mihgen