-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorporating native pipe in documentation #6
Comments
This could be a good topic for a dedicated sprint, or an activity in the upcoming Bug Barbecue at useR! (r-devel/rcwg#18). Alternatively (as it seems likely we will focus on other ideas for GSoD), this might be a good project for Google Summer of Code - might you be interested in co-mentoring such a project? |
A sprint is a good idea. I don't think it is enough of a code project for GSoC, that's why they created a separate documentation thing. |
Fair point. We'll keep in it mind for future activities then. |
Closing this issue as we went with #3 for GSoD 2022 and we have hired writers for this project - https://github.com/rstats-gsod/gsod2022/wiki/GSoD-2022-Writers If people would like to work on this issue on a voluntary basis or plan to make a proposal to another funding source, please reach out via one of the following:
This idea can also be proposed for GSoD 2023 when that repo is set up. |
Inspired by an exchange on Bugzilla, I think there is a good case to systematically incorporate the native pip (
|>
) examples across the help files. This would also provide a good opportunity to also improve examples and text in help files in general. In addition to https://bugs.r-project.org/buglist.cgi?bug_status=__open__&component=Documentation&list_id=19298&product=R which contains multiple issues about these files, many other issues are about undocumented behaviorsThe text was updated successfully, but these errors were encountered: