This organization is a place for any Cycle.js project that welcomes collaboration. We welcome all types of projects, from drivers to games to documentation to art.

The official cyclejs organization contains the code for Cycle.js itself and the core libraries developers might use. (HTTP, DOM, etc). We're here for all of the cool stuff the community makes.

We are a welcoming, collaborative community. We believe that contributions should be encouraged and celebrated. We especially welcome those who feel like they might not be welcome, or able to help. Come one, come all.

We do not tolerate behaviour that makes other contributors feel harassed or unwelcome. Please see the code of conduct.

In short, don't be a dick and consider how others will perceive your actions. If you experience any negative interactions, please contact either @tylors or @widdershin and we will do our best to help. If in doubt, get in touch.

We welcome contributors of all levels of experience and from all different backgrounds.

We are liberal about membership. If you want to be a member, please open an issue on this repository and we will add you. 😄

As a member, you are welcome to create repositories in this community and to transfer your existing repos. The only criteria is that they're related to Cycle.js and that collaboration is welcomed.

The most straightforward way to contribute to a repository is to open a pull request. We ask that repositories in our community follow Github flow as using pull requests allows for more review, discussion and learning to take place.

When one of your pull requests is merged, you will be added as a collaborator to the repository. This allows for easier collaboration (as collaborators can work together on pull requests).

Being a collaborator means:

• You can push to the repo, and to branches.
• With the permission of the other collaborators, you can merge pull requests.
• You get to have a say in the development of the project.
• You have no obligation to contribute, but any work you do is very appreciated.
• You still work with pull requests, but now you work on the repo itself, not your fork. This makes it easier to collaborate.

Here is an automagically generated list of open, unassigned issues with a "Help Wanted" label. If you want to contribute but you're unsure what to work on, take a look at these issues and comment on any you're interested in.

cyclic-router

• #124 - Question: its possible to make a Link component?
• #95 - Component runs twice, isolated child components lose scope/namespace
• #32 - Provide a param observable instead of value

cycle-canvas

• #28 - Add more examples
• #16 - How to handle click events?

README

• #10 - Present to a JavaScript meetup in Edmonton, Canada

cycle-svg-pan-and-zoom

• #3 - Support touch events for panning and zooming
• #2 - Support other stream libraries
• #1 - Write tests

cycle-regl

• #1 - Clean up DOM when using container option upon re-running or Cycle .dispose() being called