grantmcdermott commented on PR #44033:
URL: https://github.com/apache/arrow/pull/44033#issuecomment-2342356033

   Thanks for the feedback all. I've actioned the requested changes (modulo the 
uppercase suggestion). Let me know if you want changes to the wording.
   
   Some other points/thoughts:
   
   - I didn't mention anything about R-universe potentially guaranteeing a 
richer feature set because of CRAN restrictions (e.g., like we've experienced 
on MacOS with certain releases in the past w.r.t. S3 access etc.) I feel that 
this is a potentially important point that users should know about. But you all 
have better visibility to this stuff on the dev side.
   - Looking over the README, I feel like there's quite a bit of unnecessary 
repetition, made worse by inconsistent referencing the the upstream C++ docs 
and the R package website. For example...
     > To learn more about the Apache Arrow project, see the parent 
documentation of the [Arrow Project](https://arrow.apache.org/). The Arrow 
project provides functionality for a wide range of data analysis tasks to 
store, process and move data fast. See the [read/write 
article](https://arrow.apache.org/docs/r/articles/read_write.html) to learn 
about reading and writing data files, [data 
wrangling](https://arrow.apache.org/docs/r/articles/data_wrangling.html) to 
learn how to use dplyr syntax with arrow objects, and the [function 
documentation](https://arrow.apache.org/docs/r/reference/acero.html) for a full 
list of supported functions within dplyr queries.
   
     (note the mixed links the  upstream docs and the individual R vignettes) 
... is followed by a dedicated `"What can the arrow package do?"` do only a few 
paragraphs later. Better IMO to consolidate this information in one place and 
generally prioritize the R package documentation/website above the upstream 
docs. I'm happy to take a crack at consolidation as part of this PR, but I 
imagine that you would prefer a separate PR. LMK.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to