cloudyr / cloudyr/cloudyr.github.io

CloudyR Slack

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
29
Forks
3
PR merge metrics
No merged PRs in 30d

Description

We have a reserved Slack channel at cloudyr.slack.com - should we open it up to the package developers to foster collaboration and help make decisions now Thomas has stepped back?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with issue #27 and the reserved cloudyr.slack.com channel mentioned there. Determine whether opening the channel to package developers is desired and what collaboration or decision-making scope would be needed; done means a recorded decision and clearly defined follow-up work.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.