Dedicated readme.io documentation for Ignite integrations

[dmagda]

Igniters,

Ignite can already boast about a number of integrations it has with a other products and technologies. Up to this point all the integrations were documented on our main readme.io <http://readme.io/> making the overall documentation a bit messy.

I’ve decoupled the integrations from the core modules by moving them to a new documentation domain “Apache Ignite Integrations” <https://apacheignite-mix.readme.io/docs>. As a result integrations as Cassandra CacheStore, OSGi support, Zeppelin and bunch of the streamers reside there.

Dmitriy, looks like we have to upgrade readme.io subscription to “Developer Hub” for the new documentation domain because now there is now way to change the appearance. Appearance themes settings are poor. Could you handle this?

—
Denis

[dsetrakyan]

Denis, do you think RDBMS integrations should be there as well?

On Wed, Nov 30, 2016 at 4:22 AM, Denis Magda <[hidden email]> wrote:

> Igniters,
>
> Ignite can already boast about a number of integrations it has with a
> other products and technologies. Up to this point all the integrations were
> documented on our main readme.io <http://readme.io/> making the overall
> documentation a bit messy.
>
> I’ve decoupled the integrations from the core modules by moving them to a
> new documentation domain “Apache Ignite Integrations” <
> https://apacheignite-mix.readme.io/docs>. As a result integrations as
> Cassandra CacheStore, OSGi support, Zeppelin and bunch of the streamers
> reside there.
>
> Dmitriy, looks like we have to upgrade readme.io subscription to
> “Developer Hub” for the new documentation domain because now there is now
> way to change the appearance. Appearance themes settings are poor. Could
> you handle this?
>
> —
> Denis

[dmagda]

Dmitriy,

Agree. The documentation is already there.
https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence <https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence>

However, the documentation is presently based on the legacy schema-import tool. It’s reasonable to refine the documentation relying on a similar Web Console capability. The question is do we want to keep maintaining the schema-import’s documentation at least for some time or this tool has to be fully discontinued in favor of Web Console?

Also, Dmitriy please take a look at the following. The integrations’ documentation style is absolutely different from the ones we have for other documentations domains
>> Dmitriy, looks like we have to upgrade readme.io subscription to
>> “Developer Hub” for the new documentation domain because now there is now
>> way to change the appearance. Could
>> you handle this?


—
Denis

> On Nov 29, 2016, at 10:01 PM, Dmitriy Setrakyan <[hidden email]> wrote:
>
> Denis, do you think RDBMS integrations should be there as well?
>
> On Wed, Nov 30, 2016 at 4:22 AM, Denis Magda <[hidden email]> wrote:
>
>> Igniters,
>>
>> Ignite can already boast about a number of integrations it has with a
>> other products and technologies. Up to this point all the integrations were
>> documented on our main readme.io <http://readme.io/> making the overall
>> documentation a bit messy.
>>
>> I’ve decoupled the integrations from the core modules by moving them to a
>> new documentation domain “Apache Ignite Integrations” <
>> https://apacheignite-mix.readme.io/docs>. As a result integrations as
>> Cassandra CacheStore, OSGi support, Zeppelin and bunch of the streamers
>> reside there.
>>
>> Dmitriy, looks like we have to upgrade readme.io subscription to
>> “Developer Hub” for the new documentation domain because now there is now
>> way to change the appearance. Appearance themes settings are poor. Could
>> you handle this?
>>
>> —
>> Denis

[dsetrakyan]

Do we even have this tool still? I would update the documentation to use
the Web Console.

On Thu, Dec 1, 2016 at 4:36 AM, Denis Magda <[hidden email]> wrote:

> Dmitriy,
>
> Agree. The documentation is already there.
> https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence <
> https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence>
>
> However, the documentation is presently based on the legacy schema-import
> tool. It’s reasonable to refine the documentation relying on a similar Web
> Console capability. The question is do we want to keep maintaining the
> schema-import’s documentation at least for some time or this tool has to be
> fully discontinued in favor of Web Console?
>
> Also, Dmitriy please take a look at the following. The integrations’
> documentation style is absolutely different from the ones we have for other
> documentations domains
> >> Dmitriy, looks like we have to upgrade readme.io subscription to
> >> “Developer Hub” for the new documentation domain because now there is
> now
> >> way to change the appearance. Could
> >> you handle this?
>
>
> —
> Denis
>
> > On Nov 29, 2016, at 10:01 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
> >
> > Denis, do you think RDBMS integrations should be there as well?
> >
> > On Wed, Nov 30, 2016 at 4:22 AM, Denis Magda <[hidden email]> wrote:
> >
> >> Igniters,
> >>
> >> Ignite can already boast about a number of integrations it has with a
> >> other products and technologies. Up to this point all the integrations
> were
> >> documented on our main readme.io <http://readme.io/> making the overall
> >> documentation a bit messy.
> >>
> >> I’ve decoupled the integrations from the core modules by moving them to
> a
> >> new documentation domain “Apache Ignite Integrations” <
> >> https://apacheignite-mix.readme.io/docs>. As a result integrations as
> >> Cassandra CacheStore, OSGi support, Zeppelin and bunch of the streamers
> >> reside there.
> >>
> >> Dmitriy, looks like we have to upgrade readme.io subscription to
> >> “Developer Hub” for the new documentation domain because now there is
> now
> >> way to change the appearance. Appearance themes settings are poor. Could
> >> you handle this?
> >>
> >> —
> >> Denis
>
>

[dmagda]

Yes, sure, the schema-import utility is still being used and maintained.

I would create a separate page for Web Console for now and discontinue the schema-import utility only when Web Console is no longer  in the beta state
https://issues.apache.org/jira/browse/IGNITE-4348 <https://issues.apache.org/jira/browse/IGNITE-4348>

—
Denis

> On Nov 30, 2016, at 8:14 PM, Dmitriy Setrakyan <[hidden email]> wrote:
>
> Do we even have this tool still? I would update the documentation to use
> the Web Console.
>
> On Thu, Dec 1, 2016 at 4:36 AM, Denis Magda <[hidden email]> wrote:
>
>> Dmitriy,
>>
>> Agree. The documentation is already there.
>> https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence <
>> https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence>
>>
>> However, the documentation is presently based on the legacy schema-import
>> tool. It’s reasonable to refine the documentation relying on a similar Web
>> Console capability. The question is do we want to keep maintaining the
>> schema-import’s documentation at least for some time or this tool has to be
>> fully discontinued in favor of Web Console?
>>
>> Also, Dmitriy please take a look at the following. The integrations’
>> documentation style is absolutely different from the ones we have for other
>> documentations domains
>>>> Dmitriy, looks like we have to upgrade readme.io subscription to
>>>> “Developer Hub” for the new documentation domain because now there is
>> now
>>>> way to change the appearance. Could
>>>> you handle this?
>>
>>
>> —
>> Denis
>>
>>> On Nov 29, 2016, at 10:01 PM, Dmitriy Setrakyan <[hidden email]>
>> wrote:
>>>
>>> Denis, do you think RDBMS integrations should be there as well?
>>>
>>> On Wed, Nov 30, 2016 at 4:22 AM, Denis Magda <[hidden email]> wrote:
>>>
>>>> Igniters,
>>>>
>>>> Ignite can already boast about a number of integrations it has with a
>>>> other products and technologies. Up to this point all the integrations
>> were
>>>> documented on our main readme.io <http://readme.io/> making the overall
>>>> documentation a bit messy.
>>>>
>>>> I’ve decoupled the integrations from the core modules by moving them to
>> a
>>>> new documentation domain “Apache Ignite Integrations” <
>>>> https://apacheignite-mix.readme.io/docs>. As a result integrations as
>>>> Cassandra CacheStore, OSGi support, Zeppelin and bunch of the streamers
>>>> reside there.
>>>>
>>>> Dmitriy, looks like we have to upgrade readme.io subscription to
>>>> “Developer Hub” for the new documentation domain because now there is
>> now
>>>> way to change the appearance. Appearance themes settings are poor. Could
>>>> you handle this?
>>>>
>>>> —
>>>> Denis
>>
>>

[dsetrakyan]

On Thu, Dec 1, 2016 at 8:10 AM, Denis Magda <[hidden email]> wrote:

> Yes, sure, the schema-import utility is still being used and maintained.
>

Why do we need it?


>
> I would create a separate page for Web Console for now and discontinue the
> schema-import utility only when Web Console is no longer  in the beta state
> https://issues.apache.org/jira/browse/IGNITE-4348 <
> https://issues.apache.org/jira/browse/IGNITE-4348>
>

Agree that we need a page demonstrating RDBMS integration from the
web-console.

I also think that our Web Console is pretty stable right now. Definitely
stable enough to use it for the RDBMS integration. I would discontinue the
legacy import tool because we want to drive more users to the web-console,
which has a lot more functionality.

>
> —
> Denis
>
> > On Nov 30, 2016, at 8:14 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
> >
> > Do we even have this tool still? I would update the documentation to use
> > the Web Console.
> >
> > On Thu, Dec 1, 2016 at 4:36 AM, Denis Magda <[hidden email]> wrote:
> >
> >> Dmitriy,
> >>
> >> Agree. The documentation is already there.
> >> https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence <
> >> https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence>
> >>
> >> However, the documentation is presently based on the legacy
> schema-import
> >> tool. It’s reasonable to refine the documentation relying on a similar
> Web
> >> Console capability. The question is do we want to keep maintaining the
> >> schema-import’s documentation at least for some time or this tool has
> to be
> >> fully discontinued in favor of Web Console?
> >>
> >> Also, Dmitriy please take a look at the following. The integrations’
> >> documentation style is absolutely different from the ones we have for
> other
> >> documentations domains
> >>>> Dmitriy, looks like we have to upgrade readme.io subscription to
> >>>> “Developer Hub” for the new documentation domain because now there is
> >> now
> >>>> way to change the appearance. Could
> >>>> you handle this?
> >>
> >>
> >> —
> >> Denis
> >>
> >>> On Nov 29, 2016, at 10:01 PM, Dmitriy Setrakyan <[hidden email]
> >
> >> wrote:
> >>>
> >>> Denis, do you think RDBMS integrations should be there as well?
> >>>
> >>> On Wed, Nov 30, 2016 at 4:22 AM, Denis Magda <[hidden email]>
> wrote:
> >>>
> >>>> Igniters,
> >>>>
> >>>> Ignite can already boast about a number of integrations it has with a
> >>>> other products and technologies. Up to this point all the integrations
> >> were
> >>>> documented on our main readme.io <http://readme.io/> making the
> overall
> >>>> documentation a bit messy.
> >>>>
> >>>> I’ve decoupled the integrations from the core modules by moving them
> to
> >> a
> >>>> new documentation domain “Apache Ignite Integrations” <
> >>>> https://apacheignite-mix.readme.io/docs>. As a result integrations as
> >>>> Cassandra CacheStore, OSGi support, Zeppelin and bunch of the
> streamers
> >>>> reside there.
> >>>>
> >>>> Dmitriy, looks like we have to upgrade readme.io subscription to
> >>>> “Developer Hub” for the new documentation domain because now there is
> >> now
> >>>> way to change the appearance. Appearance themes settings are poor.
> Could
> >>>> you handle this?
> >>>>
> >>>> —
> >>>> Denis
> >>
> >>
>
>

[Sergey Kozlov]

Hi

+1 for removing of schema import.

On Thu, Dec 1, 2016 at 8:51 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> On Thu, Dec 1, 2016 at 8:10 AM, Denis Magda <[hidden email]> wrote:
>
> > Yes, sure, the schema-import utility is still being used and maintained.
> >
>
> Why do we need it?
>
>
> >
> > I would create a separate page for Web Console for now and discontinue
> the
> > schema-import utility only when Web Console is no longer  in the beta
> state
> > https://issues.apache.org/jira/browse/IGNITE-4348 <
> > https://issues.apache.org/jira/browse/IGNITE-4348>
> >
>
> Agree that we need a page demonstrating RDBMS integration from the
> web-console.
>
> I also think that our Web Console is pretty stable right now. Definitely
> stable enough to use it for the RDBMS integration. I would discontinue the
> legacy import tool because we want to drive more users to the web-console,
> which has a lot more functionality.
>
>
> >
> > —
> > Denis
> >
> > > On Nov 30, 2016, at 8:14 PM, Dmitriy Setrakyan <[hidden email]>
> > wrote:
> > >
> > > Do we even have this tool still? I would update the documentation to
> use
> > > the Web Console.
> > >
> > > On Thu, Dec 1, 2016 at 4:36 AM, Denis Magda <[hidden email]> wrote:
> > >
> > >> Dmitriy,
> > >>
> > >> Agree. The documentation is already there.
> > >> https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence <
> > >> https://apacheignite-mix.readme.io/v1.7/docs/automatic-persistence>
> > >>
> > >> However, the documentation is presently based on the legacy
> > schema-import
> > >> tool. It’s reasonable to refine the documentation relying on a similar
> > Web
> > >> Console capability. The question is do we want to keep maintaining the
> > >> schema-import’s documentation at least for some time or this tool has
> > to be
> > >> fully discontinued in favor of Web Console?
> > >>
> > >> Also, Dmitriy please take a look at the following. The integrations’
> > >> documentation style is absolutely different from the ones we have for
> > other
> > >> documentations domains
> > >>>> Dmitriy, looks like we have to upgrade readme.io subscription to
> > >>>> “Developer Hub” for the new documentation domain because now there
> is
> > >> now
> > >>>> way to change the appearance. Could
> > >>>> you handle this?
> > >>
> > >>
> > >> —
> > >> Denis
> > >>
> > >>> On Nov 29, 2016, at 10:01 PM, Dmitriy Setrakyan <
> [hidden email]
> > >
> > >> wrote:
> > >>>
> > >>> Denis, do you think RDBMS integrations should be there as well?
> > >>>
> > >>> On Wed, Nov 30, 2016 at 4:22 AM, Denis Magda <[hidden email]>
> > wrote:
> > >>>
> > >>>> Igniters,
> > >>>>
> > >>>> Ignite can already boast about a number of integrations it has with
> a
> > >>>> other products and technologies. Up to this point all the
> integrations
> > >> were
> > >>>> documented on our main readme.io <http://readme.io/> making the
> > overall
> > >>>> documentation a bit messy.
> > >>>>
> > >>>> I’ve decoupled the integrations from the core modules by moving them
> > to
> > >> a
> > >>>> new documentation domain “Apache Ignite Integrations” <
> > >>>> https://apacheignite-mix.readme.io/docs>. As a result integrations
> as
> > >>>> Cassandra CacheStore, OSGi support, Zeppelin and bunch of the
> > streamers
> > >>>> reside there.
> > >>>>
> > >>>> Dmitriy, looks like we have to upgrade readme.io subscription to
> > >>>> “Developer Hub” for the new documentation domain because now there
> is
> > >> now
> > >>>> way to change the appearance. Appearance themes settings are poor.
> > Could
> > >>>> you handle this?
> > >>>>
> > >>>> —
> > >>>> Denis
> > >>
> > >>
> >
> >
>

--
Sergey Kozlov
GridGain Systems
www.gridgain.com

[dmagda]

I don't say we need it but rather mean that it’s still being delivered as a part of the distribution.

Let’s sweep it out once the Web Console based approach is documented
https://issues.apache.org/jira/browse/IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349>

—
Denis

> On Nov 30, 2016, at 9:51 PM, Dmitriy Setrakyan <[hidden email]> wrote:
>
>>
>> Yes, sure, the schema-import utility is still being used and maintained.
>>
>
> Why do we need it?

[dsetrakyan]

On Thu, Dec 1, 2016 at 10:28 AM, Denis Magda <[hidden email]> wrote:

> I don't say we need it but rather mean that it’s still being delivered as
> a part of the distribution.
>
> Let’s sweep it out once the Web Console based approach is documented
> https://issues.apache.org/jira/browse/IGNITE-4349 <
> https://issues.apache.org/jira/browse/IGNITE-4349>
>

Sounds good, thanks!

>
> —
> Denis
>
> > On Nov 30, 2016, at 9:51 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
> >
> >>
> >> Yes, sure, the schema-import utility is still being used and maintained.
> >>
> >
> > Why do we need it?
>
>

[Roman Shtykh]

Denis,

Can you please set permissions for me to edit
https://apacheignite-mix.readme.io/docs?

-Roman



On Thursday, December 1, 2016 4:38 PM, Dmitriy Setrakyan <[hidden email]> wrote:
On Thu, Dec 1, 2016 at 10:28 AM, Denis Magda <[hidden email]> wrote:

> I don't say we need it but rather mean that it’s still being delivered as
> a part of the distribution.
>
> Let’s sweep it out once the Web Console based approach is documented
> https://issues.apache.org/jira/browse/IGNITE-4349 <
> https://issues.apache.org/jira/browse/IGNITE-4349>
>

Sounds good, thanks!

>
> —
> Denis
>
> > On Nov 30, 2016, at 9:51 PM, Dmitriy Setrakyan <[hidden email]>
> wrote:
> >
> >>
> >> Yes, sure, the schema-import utility is still being used and maintained.
> >>
> >
> > Why do we need it?
>
>

[Denis Magda]

Roman,

The access is granted.

—
Denis

> On Dec 4, 2016, at 6:37 PM, Roman Shtykh <[hidden email]> wrote:
>
> Denis,
>
> Can you please set permissions for me to edit
> https://apacheignite-mix.readme.io/docs?
>
> -Roman
>
>
>
> On Thursday, December 1, 2016 4:38 PM, Dmitriy Setrakyan <[hidden email]> wrote:
> On Thu, Dec 1, 2016 at 10:28 AM, Denis Magda <[hidden email]> wrote:
>
>> I don't say we need it but rather mean that it’s still being delivered as
>> a part of the distribution.
>>
>> Let’s sweep it out once the Web Console based approach is documented
>> https://issues.apache.org/jira/browse/IGNITE-4349 <
>> https://issues.apache.org/jira/browse/IGNITE-4349>
>>
>
> Sounds good, thanks!
>
>
>
>>
>> —
>> Denis
>>
>>> On Nov 30, 2016, at 9:51 PM, Dmitriy Setrakyan <[hidden email]>
>> wrote:
>>>
>>>>
>>>> Yes, sure, the schema-import utility is still being used and maintained.
>>>>
>>>
>>> Why do we need it?
>>
>>

[Roman Shtykh]

Thank you, Denis!




On Tuesday, December 6, 2016 2:32 AM, Denis Magda <[hidden email]> wrote:
Roman,

The access is granted.

—
Denis

> On Dec 4, 2016, at 6:37 PM, Roman Shtykh <[hidden email]> wrote:
>
> Denis,
>
> Can you please set permissions for me to edit
> https://apacheignite-mix.readme.io/docs?
>
> -Roman
>
>
>
> On Thursday, December 1, 2016 4:38 PM, Dmitriy Setrakyan <[hidden email]> wrote:
> On Thu, Dec 1, 2016 at 10:28 AM, Denis Magda <[hidden email]> wrote:
>
>> I don't say we need it but rather mean that it’s still being delivered as
>> a part of the distribution.
>>
>> Let’s sweep it out once the Web Console based approach is documented
>> https://issues.apache.org/jira/browse/IGNITE-4349 <
>> https://issues.apache.org/jira/browse/IGNITE-4349>
>>
>
> Sounds good, thanks!
>
>
>
>>
>> —
>> Denis
>>
>>> On Nov 30, 2016, at 9:51 PM, Dmitriy Setrakyan <[hidden email]>
>> wrote:
>>>
>>>>
>>>> Yes, sure, the schema-import utility is still being used and maintained.
>>>>
>>>
>>> Why do we need it?
>>
>>