[
https://issues.apache.org/jira/browse/FLINK-6038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021471#comment-16021471
]
David Anderson commented on FLINK-6038:
---------------------------------------
I'm thinking of linking to the github READMEs rather than the project's pages
-- so for example,
https://github.com/apache/bahir-flink/tree/master/flink-connector-redis rather
than http://bahir.apache.org/docs/flink/current/flink-streaming-redis/. The
content is identical, but I find the github versions more readable. More
importantly, Bahir has yet to make a release, so to use these connectors you
have to go to github and clone the repo, so it seems more helpful to link
directly there.
[~tzulitai] Is this a bad idea?
> Add deep links to Apache Bahir Flink streaming connector documentations
> -----------------------------------------------------------------------
>
> Key: FLINK-6038
> URL: https://issues.apache.org/jira/browse/FLINK-6038
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, Streaming Connectors
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: David Anderson
>
> Recently, the Bahir documentation for Flink streaming connectors in Bahir was
> added to Bahir's website: BAHIR-90.
> We should add deep links to the individual Bahir connector dos under
> {{/dev/connectors/overview}}, instead of just shallow links to the source
> {{README.md}} s in the community ecosystem page.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
