Skip to content
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

Are you looking for help to maintain the project? #98

Open
richard-lopes opened this issue Jan 8, 2018 · 9 comments
Open

Are you looking for help to maintain the project? #98

richard-lopes opened this issue Jan 8, 2018 · 9 comments

Comments

@richard-lopes
Copy link
Contributor

Hello,

Our team have been an user of cxs for a few months and we like its simplicity and light size. Perfect when shipping simple widgets.

We would love to use it for larger apps and this is why having optional extra features that one could use on top of the library would be great.

I see a few great PRs are waiting to be merged and 2-3 are spot on what we have been looking for.
I do understand that maintaining many open source projects like you do is a super consuming exercise. But instead of having people fork this project to add the bits and pieces they need, it would be great if we could grow this repo. and benefit everybody.

If you are looking for co-maintainers to help out with this library, just give us a shout. As for one would be glad to help out.

Thanks.

@jxnblk
Copy link
Collaborator

jxnblk commented Feb 22, 2018

Hi!

Actually, yes, that would be great! And thank you for asking in such a nice manner :)

For my own purposes, glamor and styled-components has mostly replaced the need for some of the things I was initially experimenting with here, but it seems like there might be a few people still interested in this library.

I think to best let this project live on, it should probably move to its own organization, and I'm planning on starting one and moving this repo over. If anyone would like to help contribute, please give a shout out here to organize.

✌️

@richard-lopes
Copy link
Contributor Author

I am definitively keen @jxnblk
Another company I know is using it to ship standalone widgets and the lead will be very interested to contribute as well.
Thanks a lot for your work on this and all the other great projects you open source.

@richard-lopes
Copy link
Contributor Author

Any news?

@jxnblk
Copy link
Collaborator

jxnblk commented Apr 13, 2018

@richard-lopes Sorry for the delay on this. I was hoping a few others would chime in, but I'll go ahead and add you to the repo org

@richard-lopes
Copy link
Contributor Author

Thanks

@nosamanuel
Copy link

@jxnblk I think this project has a unique perspective with its "zero dependency" approach.

I feel like we could really capitalize on that perspective by becoming totally framework-agnostic (not support for all frameworks, but support for no frameworks).

Happy to contribute however I can if you agree with ceding the "batteries included" territory to the Glamor and Styled Components. In my view, both would be better off using this project as a building block.

@dylmye
Copy link

dylmye commented Dec 14, 2018

Hi, are you looking for any other maintainers?

@osdevisnot
Copy link

I posted some thoughts in #113 about this. In general I want to capitalize on the idea proposed by @nosamanuel

I feel like we could really capitalize on that perspective by becoming totally framework-agnostic (not support for all frameworks, but support for no frameworks).

Attempting this though, I am unsure how we could handle the dynamic styling aspects. i.e. how do we take in dynamic props and generate class name based on current values.

In general, something like this should work, but I haven't had enough time to explore that idea.

cc: @dylmye @richard-lopes

@AlexGalays

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants