Please add me as a member. Thanks!

For example, the rackt community has an excellent set of principles. If you haven't read it, I highly recommend it.

I think we have a different goal as a community, more centered around collaboration and creativity, but maintenance and ownership are definitely things to consider.

Does anyone else know of similar documents we can absorb and discuss?

I'm not sure if this is the place to do this, so just close this issue if it's not, however I couldn't think of a better way to get the attention of this awesome community and try to find a Cycle.js contributor that might be willing to come speak at our JavaScript meetup. We're working on getting a budget to fly people in, but in the maintime we're focused on using Hangouts to bring people in remotely.

If you're interested, we're looking for a 30 minute presentation, including time for questions. Usually it works in the range of 15-20 minutes a talk, with the remainder for questions. We meetup the first Thursday of every month of 18:30 MST (12:30 AM UTC).

Thanks, and thanks to all the hard work you do putting this community together. :)

Please add me as a member. Thanks! :)

This is my first venture into an OSS community. I think the ideas behind cycle.js are extremely fascinating and would love to contribute!

I propose a page would be most flexible as like awesome can link to externally maintained stuff. Which of these is best

• Github page?
• wiki Page?
• readme.md or other md file?

[Updated: removed question about repo as this is already an organisation repo]

• Contributing section (highlight that all contributors are welcome, give examples of how to do it)
• Auto generated list of open issues that are tagged with 'pr-welcome' to aid people finding stuff to work on
• Section on moving your repos into the community or making new ones in the community

I really love Cycle.js and its ideas, and have some ideas that might fare better if I place them in this org 😄. Would really love if I could join!

Hello!

I'm Andrea, a software developer who is really interested in functional programming, I'd love to be a member of CycleJS and to contribute to this amazing project!

Thanks in advance! 😄

Hi y'all, I thought that a good way to get to know each other and to welcome new members is to have an issue for introductions. When adding new members in future I feel we should point them here 😄

@cyclejs-community/contributors

If you're unsure what to say, here are some ideas (all optional):

• Your name (or what you'd like to be called)
• Where your home is/where you live now
• What do you want to learn about?
• What do you wish you understood about Cycle/functional programming?
• What are your hobbies outside of programming?

It's been great learning about all of you in the Introductions issue.

I thought we could have an issue where everyone can share ideas for projects they would like to work on.

Existing projects are also okay, as long as you have an idea for something you want to work on.

If you see an idea you like, give it a thumbs up response. Also feel free to leave a comment addressed to the person who suggested the idea.

Once there's been a little bit of time for people to post ideas and add thumbs up, you can make a repo (or move an existing one) in the community and add everyone who thumbed up your idea as a collaborator.

If you're unsure, here's a format for ideas:

Working Title (if any):
Idea:
Help needed:

Hi @cyclejs-community/contributors 😄

I hope y'all are doing well. It's been a while since we've had any community-wide communication go out, but in the meantime things have been ticking along.

I'm reaching out to you because we're looking for someone to step up as a maintainer for redux-cycles.

For those who aren't familiar, redux-cycles is a cool piece of technology that acts as a bridge between redux and cycle, and in my opinion is one of the most elegant solutions for managing asynchronous effects for apps that use redux. It's also one of the most starred pieces of tech in the Cycle.js ecosystem!

redux-cycles was originally created by @nickbalestra and @lmatteis, who did a fantastic job launching the project, but it currently has nobody actively working on it.

A major part of the reason @TylorS and I created this community is because we believe that contributors should be able to work on a project without feeling an obligation to stick around forever, or guilt if they need to walk away. We want working on open source Cycle projects to be a great experience, and in order to do that we need to have each others backs.

To that end, I'm hoping to find one or several people who are interested in doing a bit of maintenance work on redux-cycles. There are several low hanging fruit issues that would go a long way, like updating the dependencies, updating the README and triaging the existing issues.

If you want to be more involved in open source or the Cycle.js community, this is a great opportunity. By putting your hand up, there's no obligation to have a long term commitment to working on the project. Any work that you can find time to do is greatly valued.

I hope that someone is willing to step up and do a little bit of work here, as it would be a shame for such a great project to be deprecated when it just needs a little bit of love.

I'm happy to provide guidance and support for anyone who wants to do some maintenance. I'll give you push access to the repo, arrange for you to have publish access on npm, and field any questions you have. If you're keen, please comment in here or get in touch with me on Gitter. Also feel free to post any questions you have in here!

Just saw that I had to create an issue to that purpose.

Hi! 👋🏼

I am Abhijith, I am a student who wants to know and learn Cycle JS and I want to become a Cycle JS member!

Thank you 😄

If so, I will submit a PR with a small php util (in utilities dir) that converts HTML to hyperscript.

If not, please suggest a better repo where it can help the most people.

Might want a group with right permissions?

I try to learn isolate but I have no idea why isolate won't work.
this can run without error but no scope was added to element. ;(

import {Sources} from "../base/Sources";
import {Sinks} from "../base/Sinks";
import {Observable} from "rxjs";
import {header, h1, a, span, b, nav, div, ul, li, img} from "@cycle/dom";
import isolate from "@cycle/isolate";

var nonIsolatedHeaderComponent = function(sources: Sources): Sinks {

    return {
        DOM: Observable.of(
            header('.main-header', [
                a('.logo', {href:"/" /*TODO*/},[
                    span('.logo-mini',[
                        b('A'),
                        'LT'
                    ]),
                    span('.logo-lg', [
                        b('Admin'),
                        'LTE'
                    ])
                ]),
                nav('.navbar.navbar-static-top',[
                    div('.navbar-custom-menu', [
                        ul('.nav .navbar-nav', [
                            li('.dropdown.user.user-menu', [
                                a('.dropdown-toggle',{attrs: {href : '#'} }, [
                                    img('.user-image', {attrs: {alt:'User Image', src:'/TODO'} }),
                                    span('.hidden-xs', 'test')
                                ])
                            ])
                        ])
                    ])
                ])
            ])
        )
    };
};

var isolatedHeaderComponent = isolate(nonIsolatedHeaderComponent);

export {isolatedHeaderComponent as headerComponent};

I started learning cycle.js and will be presenting about it at my company. While learning, I'm creating this RSS PWA Reader using cycle.js to try and stretch the different use cases we face on our projects. So far, I can say it was pain free experience. Most of the pain was dealing with webpack.

I would like to share my project to get community contribution because I don't think I'll ever have the time to get this project to a polished state alone.

As well, I'd like to learn from the cycle.js gurus the best practices and hopefully get more feedback on how to write better FRP code. Thanks!