readme.io (again)

[Konstantin Boudnik-2]

I was looking at something in the Ignite docs and have noticed that the
content of the documentation is starting drifting all over the internet now.
The case in point is that the images are now hosted on something called
filepicker.io.

That brings back the whole discussion about not originating the documentation
of the project from from the ASF premises. In fact, the very issue we were
discussing multiple times during the incubation, but never got a closure with
it IIRC. Have we gotten any sort of the readme.io team to facilitate the
export/import documentation markup to/from their service into ASF git?

My concern here, is that if the current course is kept as it is then we are
going to see the content of the project spread thin all over the places. Which,
potentially, might have consequences we'll have to deal with. Thoughts?

--
Take care,
        Cos
2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
Cos' pubkey: http://people.apache.org/~cos/cos.asc

         ---- Wisdom of the hour ----

[dsetrakyan]

Cos, the readme team facilitates export to GIT (upon our request):
https://github.com/apacheignite/documentation

What would be the next step?

D.

On Mon, Mar 7, 2016 at 1:48 PM, Konstantin Boudnik <[hidden email]> wrote:

> I was looking at something in the Ignite docs and have noticed that the
> content of the documentation is starting drifting all over the internet
> now.
> The case in point is that the images are now hosted on something called
> filepicker.io.
>
> That brings back the whole discussion about not originating the
> documentation
> of the project from from the ASF premises. In fact, the very issue we were
> discussing multiple times during the incubation, but never got a closure
> with
> it IIRC. Have we gotten any sort of the readme.io team to facilitate the
> export/import documentation markup to/from their service into ASF git?
>
> My concern here, is that if the current course is kept as it is then we are
> going to see the content of the project spread thin all over the places.
> Which,
> potentially, might have consequences we'll have to deal with. Thoughts?
>
> --
> Take care,
>         Cos
> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
> Cos' pubkey: http://people.apache.org/~cos/cos.asc
>
>          ---- Wisdom of the hour ----
>
>

Hi:

https://apacheignite-fs.readme.io/docs
The above content is not synchronized?

在 16/3/8 10:43, Dmitriy Setrakyan 写道:
> Cos, the readme team facilitates export to GIT (upon our request):
> https://github.com/apacheignite/documentation
>
> What would be the next step?
>
> D

[dsetrakyan]

Hm… Let me check and get back to you tomorrow.

On Tue, Mar 8, 2016 at 3:43 AM, 李玉珏@163 <[hidden email]> wrote:

> Hi:
>
> https://apacheignite-fs.readme.io/docs
> The above content is not synchronized?
>
> 在 16/3/8 10:43, Dmitriy Setrakyan 写道:
>
> Cos, the readme team facilitates export to GIT (upon our request):
>> https://github.com/apacheignite/documentation
>>
>> What would be the next step?
>>
>> D
>>
>
>
>