Open gregorypratt opened 8 years ago
@gregorypratt If no one else (read: actual RiotGear contributors) steps up, I'd be happy to help out.
I'm a relative Riot newb, but what I've seen has been very impressive and I'm currently rewriting my biggest project using Riotโ even using a few RiotGear components.
I'm probably not your ideal candidate, but I'd hate to see this project die out.
Can't think of a better reason to take it on! If you still want it it's yours ๐
I'll transfer ownership of this org in due course and get your npm and twitter deets too
@gregorypratt It looks like you have your man, if it doesn't work out, i'd happily take this on. I've been working with riotjs for a few months now and looking forward to see where it goes.
The more the merrier! @restlessmedia I've added you as an admin.
๐ nice!
Hi Id like to get involved, Id be happy to see whats invovled in the refactoring for blaze 2x
I'd like to help out as well if possible.
I would love to become another contributor to this as I thought of something like this when I first heard of Riot. I have some code to adapt to this to make it more feature rich. Maybe do a bootstrap version. I want to help Riot become as popular as React.
Hello. I'm interested in taking this over and porting it to riot 4.
I can contribute what I did for Riot2 Happy to hand that over too. I'm too busy on other projects to do this justice.
I definitely would be down to incorporate riot gear 2 into the library if I take it over. Right now I'm mostly struggling with how much backwards compatibility to preserve. Should I support riot 3, 4, or both? Should I focus on upgrading the build tools? Should I upgrade to blaze UI? Should I focus on generalizing the CSS to support other frameworks?
I've only used RG for two small projects in the past and am hoping to modernize it for an upcoming riot 4 project. If anyone has any thoughts on which direction to go or where I could an audience for such questions please let me know.
@chriscauley I created RG2, so that one is easy to handover. Maybe the best way forward to upgrade those components. They are definitely not compatible with the current Blaze CSS. I've hacked it a bit, going to an old version off a CDN, but even that seems to have failed.
Suggest we continue this conversation in the RG2 side, since whilst I have access to this repository, maybe once you convert all the code, you can update this one.
Would you like to own this Open Source Project?
If so please get in touch via this issue. I can transfer the ownership of this organisation, the associated npm packages and it's twitter account (https://twitter.com/riotcomponents) to anyone who can take it further than my time permits