-
Notifications
You must be signed in to change notification settings - Fork 359
Home
Join: https://docs.google.com/forms/d/1WdCjXvWJ1tDSlZNJAroGWCWcqqDjRMAF2VNnZCfn14g/viewform
GitLab: https://gitlab.com/groups/rweekly
Admin: https://rssadmin.rweekly.org
Slack: https://rweekly.slack.com
rweekly-highlights: https://github.com/rweekly/rweekly-highlights
Validator: https://validator.w3.org/checklink
The draft post is in https://github.com/rweekly/rweekly.org/blob/gh-pages/draft.md
Put new updates to the draft post.
Separate each item with a blank line. This layout will have a better view on most RSS readers.
Doing is better than talking. If you find a bug which is easy to fix, just click the edit button.
+ [item one](link) - text
+ [item two](link) - text
For CRAN packages
+ <img class='emoji' src="https://link.rweekly.org/c" width='20' /> [pkg name](link) - text
For Bioconductor packages
+ <img class='emoji' src="https://link.rweekly.org/b" width='50' /> [pkg name](link) - text
For GitHub only packages
+ <img class='emoji' src="https://link.rweekly.org/g" width='20' /> [pkg name](link) - text
The draft post will be frozen on Sunday according to GMT+00:00, and the new items will be added to a new draft post. Editors of R Weekly can read and find bugs in the frozen post, which will be release on the next day.
Use https://validator.w3.org/checklink to check dead links. Release the frozen post as weekly update every Monday according to GMT+00:00.
Don't put images in the main repo, and this rule will keep the main repo size small and easy to clone.
R Weekly always uses HTTPS. To fix mixed content warning for images that are using HTTP, ask the copyright holder of the image for permission and put an copy of the image in rweekly/image repo.
Don't Use RawGit as CDN.
RawGit will no longer cache images. See https://twitter.com/rawgit/status/836744103190638592 .
For new images that will show in R Weekly issues, it is recommended to use https://raw.githubusercontent.com/ domain. And R Weekly Live only accepts https://raw.githubusercontent.com/ domain images.
Or do not use that image.
- Each weekly contains at most 3 highlight posts. When there are special events, eg. UseR!, we can have more highlight posts.
- Members of the R Weekly will vote for at most three posts on the R Weekly Slack channel every Saturday. If you do not want to recommend any post, you can skip the vote.
- There is a handy shiny widget rweekly/rweekly-highlights to generate poll for Slack.
If you want to be an R Weekly organization member, please take the survey.
A member will receive a notice about his/her inactive status for two months in the organization. A member will leave R Weekly organization if the inactive status passes 75 days.
Activities including GitHub, Slack, Google Group, and official Twitter account management.
In order to post more relevant content under each section, members/contributors are requested to follow the below rules to post content. Thank you!
Please post R tutorials for how to use certain packages and tools (usually code is embedded)
Please post articles that talks about R and data science in general(usually no code embedded)
Please post analyses that use R to analyze real-world data sets
Please post R use cases/events that showcase how organizations are utilizing or integrating to R
Please post R use cases that showcase how Academia is utilizing R
Please post Non-English R related content
Videos and Podcasts about R
Please post long posts, websites, books, slides, list, cheat sheets, or other learning resources in general that are more officially aggregated as a guide material
Please post R Jobs
Please post new packages and tools that are created or published in the past 2 weeks.
Please post new releases of tools and packages for R
Please post new R groups, communities or competitions here.
Please post at most three links about big events for the upcoming months. This section repeats every issue. If there are some big interesting events, we can also add more than three links.
Events can also be in Call for Participation section.