[
https://issues.apache.org/jira/browse/ARROW-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285498#comment-16285498
]
ASF GitHub Bot commented on ARROW-1911:
---------------------------------------
lmeyerov commented on issue #1412: ARROW-1911: [JS] Add Graphistry to Arrow JS
proof points
URL: https://github.com/apache/arrow/pull/1412#issuecomment-350618958
Great. Digging deeper, it seems we're pretty incomplete wrt JS inclusion.
Quick audit revealed the below. Ideally we can carve out a subset of the below
that's quick for JS at least. I bolded those that seem easy (I'm trying to rush
b/c some PR that'll be coming).
1. Main Arrow github README:
- **add JS to implementations list**
- **add Contributor & Powered By links**, and probably other main site
top-level content, as many readers will only look here.
2. Main Arrow website:
- add JS doc links to homepage
- add Powered By link to header
3. Powered By.md on github:
- **add GOAI to open source, and Graphistry to Companies**
4. JS README:
First, context: js community has norms for README top-level contents (~=
https://blog.nodejitsu.com/how-to-write-a-readme/ ), and evidence suggests this
will be the entry point README for JS users. Ex: quick Google search tests of
"apache arrow js" + "arrow nodejs" confirm the JS REAdME is a the top result.
So:
- **add Arrow top-level backlink to Related Projects**
- **add Powered By list here (small) + link to main Arrow Powered By**
- docs: none yet :(
1. As-is, JS users will likely miss this + other supposedly top-level
content. The js community norm for README top-level contents is increasingly
along the lines of https://blog.nodejitsu.com/how-to-write-a-readme/ . The JS
README was originally written to be largely complete wrt scanning for JS users,
and quick Google search tests ( "apache arrow js" + "arrow nodejs") confirm
that's the top result for JS users. Is it fine for me to make a pass
referencing top-level content?
Current thought:
See:
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add Graphistry to Arrow JS proof points
> ---------------------------------------
>
> Key: ARROW-1911
> URL: https://issues.apache.org/jira/browse/ARROW-1911
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Leo Meyerovich
> Labels: pull-request-available
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> As part of upcoming publicity to the JS project, we wanted to add the
> Graphistry enterprise-grade use case to the homepage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
