[jira] [Updated] (IGNITE-12951) Update documents for migrated extensions
[
https://issues.apache.org/jira/browse/IGNITE-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis A. Magda updated IGNITE-12951:
Description:
# Update README for migrated extensions.The newly migrated extensions modules
have suffix -ext in the artifact name.Review and update extensions README docs
to correct artifact name. An example for correct artifact name would be
ignite-flink-ext
# We need to update some sections (maven artifacts name, a paragraph about
the extensions repository) in existing docs before the extension is released:
https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
#
{quote}{{As for the extensions web page, I see its structure as follows. It
goeswith a header introducing the extensions repository and covering types
ofcontributions that are welcomed there. Then down below in the body we listall
the available extensions - it can be a simple table with an extensionname,
description, URL or a bit more advanced interface with a grid layoutlike on
this page [1]. With the grid layout, we can add logos of theprojects Ignite is
integrated with in addition to the name/description/URL.Let me know what you
think.[1] [https://ignite.apache.org/screencasts.html]}}{quote}
{{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
was:
# Update README for migrated extensions.The newly migrated extensions modules
have suffix -ext in the artifact name.Review and update extensions README docs
to correct artifact name. An example for correct artifact name would be
ignite-flink-ext
# We need to update some sections (maven artifacts name, a paragraph about
the extensions repository) in existing docs before the extension is released:
[https://apacheignite-mix.readme.io/docs/twitter-streamer]
#
{quote}{{As for the extensions web page, I see its structure as follows. It
goeswith a header introducing the extensions repository and covering types
ofcontributions that are welcomed there. Then down below in the body we listall
the available extensions - it can be a simple table with an extensionname,
description, URL or a bit more advanced interface with a grid layoutlike on
this page [1]. With the grid layout, we can add logos of theprojects Ignite is
integrated with in addition to the name/description/URL.Let me know what you
think.[1] [https://ignite.apache.org/screencasts.html]}}{quote}
{{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
> Update documents for migrated extensions
>
>
> Key: IGNITE-12951
> URL: https://issues.apache.org/jira/browse/IGNITE-12951
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Priority: Major
>
> # Update README for migrated extensions.The newly migrated extensions modules
> have suffix -ext in the artifact name.Review and update extensions README
> docs to correct artifact name. An example for correct artifact name would be
> ignite-flink-ext
> # We need to update some sections (maven artifacts name, a paragraph about
> the extensions repository) in existing docs before the extension is released:
> https://github.com/apache/ignite/tree/master/docs/_docs/extensions-and-integrations
> #
> {quote}{{As for the extensions web page, I see its structure as follows. It
> goeswith a header introducing the extensions repository and covering types
> ofcontributions that are welcomed there. Then down below in the body we
> listall the available extensions - it can be a simple table with an
> extensionname, description, URL or a bit more advanced interface with a grid
> layoutlike on this page [1]. With the grid layout, we can add logos of
> theprojects Ignite is integrated with in addition to the
> name/description/URL.Let me know what you think.[1]
> [https://ignite.apache.org/screencasts.html]}}{quote}
>
> {{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12951) Update documents for migrated extensions
[
https://issues.apache.org/jira/browse/IGNITE-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saikat Maitra updated IGNITE-12951:
---
Description:
# Update README for migrated extensions.The newly migrated extensions modules
have suffix -ext in the artifact name.Review and update extensions README docs
to correct artifact name. An example for correct artifact name would be
ignite-flink-ext
# We need to update some sections (maven artifacts name, a paragraph about
the extensions repository) in existing docs before the extension is released:
[https://apacheignite-mix.readme.io/docs/twitter-streamer]
#
{quote}{{As for the extensions web page, I see its structure as follows. It
goeswith a header introducing the extensions repository and covering types
ofcontributions that are welcomed there. Then down below in the body we listall
the available extensions - it can be a simple table with an extensionname,
description, URL or a bit more advanced interface with a grid layoutlike on
this page [1]. With the grid layout, we can add logos of theprojects Ignite is
integrated with in addition to the name/description/URL.Let me know what you
think.[1] [https://ignite.apache.org/screencasts.html]}}{quote}
{{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
was:
Update README for migrated extensions.
The newly migrated extensions modules have suffix -ext in the artifact name.
Review and update extensions README docs to correct artifact name.
An example for correct artifact name would be ignite-flink-ext
> Update documents for migrated extensions
>
>
> Key: IGNITE-12951
> URL: https://issues.apache.org/jira/browse/IGNITE-12951
> Project: Ignite
> Issue Type: Sub-task
> Components: streaming
>Reporter: Saikat Maitra
>Priority: Major
>
> # Update README for migrated extensions.The newly migrated extensions modules
> have suffix -ext in the artifact name.Review and update extensions README
> docs to correct artifact name. An example for correct artifact name would be
> ignite-flink-ext
> # We need to update some sections (maven artifacts name, a paragraph about
> the extensions repository) in existing docs before the extension is released:
> [https://apacheignite-mix.readme.io/docs/twitter-streamer]
> #
> {quote}{{As for the extensions web page, I see its structure as follows. It
> goeswith a header introducing the extensions repository and covering types
> ofcontributions that are welcomed there. Then down below in the body we
> listall the available extensions - it can be a simple table with an
> extensionname, description, URL or a bit more advanced interface with a grid
> layoutlike on this page [1]. With the grid layout, we can add logos of
> theprojects Ignite is integrated with in addition to the
> name/description/URL.Let me know what you think.[1]
> [https://ignite.apache.org/screencasts.html]}}{quote}
>
> {{[http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html#a46863]}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12951) Update documents for migrated extensions
[ https://issues.apache.org/jira/browse/IGNITE-12951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Saikat Maitra updated IGNITE-12951: --- Summary: Update documents for migrated extensions (was: Update README for migrated extensions) > Update documents for migrated extensions > > > Key: IGNITE-12951 > URL: https://issues.apache.org/jira/browse/IGNITE-12951 > Project: Ignite > Issue Type: Sub-task > Components: streaming >Reporter: Saikat Maitra >Priority: Major > > Update README for migrated extensions. > The newly migrated extensions modules have suffix -ext in the artifact name. > Review and update extensions README docs to correct artifact name. > An example for correct artifact name would be ignite-flink-ext -- This message was sent by Atlassian Jira (v8.3.4#803005)
