[
https://issues.apache.org/jira/browse/ARROW-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529327#comment-16529327
]
Leo Meyerovich commented on ARROW-2777:
---------------------------------------
Great. I don't have a strong feeling over which synchronous comms channel is
preferred. I added Slack b/c I've been having synchronous education comms w/
various expert JS framework devs who are curious about Arrow but have
questions. Likewise, as basic compute fills out over next few months, I expect
more beginner q's to start, and an interim period before SO, tutorials, etc.
catch up. Slack appeared to be the most "in-the-open" sync comms channel being
actively used.
Maybe keep now, and if/when a decision is made + new path is established,
update?
Or clear enough decision that I should delete now, and if so, what should I put
instead?
Thanks!
> [JS] Friendlier onboarding readme
> ---------------------------------
>
> Key: ARROW-2777
> URL: https://issues.apache.org/jira/browse/ARROW-2777
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Leo Meyerovich
> Assignee: Leo Meyerovich
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Based on some recent community feedback, add to JS onboarding:
> -- Example of loading native JS values
> -- Pointer to Slack
> -- Links to tutorials and docs
> -- Ideally.. tutorial of loading -> map/filter/reduce -> emitting... but more
> core methods seem needed first.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
