search

firtoz / react-three-renderer

Render into a three.js canvas using React.
https://toxicfork.github.com/react-three-renderer-example/
MIT License
1.49k stars 155 forks source link

slow development #153

Open toxicFork opened 7 years ago

toxicFork commented 7 years ago

Hey, an issue from the author!

It's more like a status update, I will update the readme too.

First of all thank you everyone who showed interest in the project. I love you all! I am amazed by what you all have done and are still doing! I still can't believe it sometimes!

As you may have noticed I am having a bit of trouble keeping up with keeping this project up to date with react and threejs. And to fix the bugs and finish development. I feel like I have less and less free time these days, and to divide it between the projects I have is difficult. Apart from the public repos on GitHub I have a full time job and other "own time" research and development work (and to try to have a personal life on top of that :D). Only my full time work brings income. I love and enjoy contributing to the open source community but it is quite difficult to maintain things at a satisfactory rate. There have been moments when I caught myself having fun with going outside or playing a game instead of working on something, and I was feeling guilty! So I'm going to try to reduce my overproductiveness a bit to prevent a burnout.

The point is, I'm not sure how long the next versions will take to release. Please assume development to be frozen. Apologies for the inconvenience, disappointments and breaking expectations.

Ps: I should have finished that damn contribution guide when I had the time instead of doing other things. I will use the excuse of this being my first "popular" project and my "open source noob"ness. You live and learn.

johnrees commented 7 years ago

You're doing a great job @toxicFork! Thanks for all your work.

I've been meaning to 'give back' to this project for a while. It might not be for a few weeks, but where can contributors provide the biggest impact at the moment?

Marviel commented 7 years ago

Hey @toxicFork thanks for all your work thus far! I'll try to contribute where I'm able.

wishfoundry commented 7 years ago

greate work @toxicFork, thank you so much for your efforts!

Have you considered moving this project to a github organization? you could add some moderators to help carry some of the load until suitable project champions surface

toxicFork commented 7 years ago

Thanks for the comments @johnrees, @Marviel and @wishfoundry . Ideally I need to finish the contribution guide to make it easier for contributions to happen.

Currently adding missing props could be the easiest, missing components will help too but a bit more difficult.

Hardest problem is keeping up to date with react and three, I was working on the react part of it but it looks like I'll need to go over all the code and find out what's different in react dom vs r3r again to be able to use the current version of react because at the moment it's doing a few things that are tough to understand.

When I have a few hours of time available I will push what I have so far in a branch, and will merge some of the pull requests to master and hopefully cut another release :D

dkozma commented 7 years ago

@toxicFork I greatly appreciate all of the awesome work you have done on this project. I do agree with what you and @wishfoundry have said - it would be great if it was easier for people who are interested in this project to both make changes and have a small group of people to help approve or respond to PRs.

I completely understand not having enough time to solely maintain this library and keep it updated as it is a huge task. It sounds like there are a bunch of people (myself included) willing to try to help with that effort. It sounds like your idea of creating a contribution guide is a good one, and alongside adding a moderator or two, might be the best thing in the near term to help distribute some of the load of keeping this library current.

Thanks again for this awesome library!

nickpolet commented 7 years ago

@toxicFork This has made working on 3D applications really fun again. While threejs in itself is fantastic, I always felt lost without the state driven nature of react. Combining the two has been a god send. Now, projects that grow quite large aren't burdened by strange state issues that arise when dealing with complex scenes in threejs. When I worked previously (with plain threejs), the code would get very complex very quickly, trying to manage the state in a sane way. Now... I don't have that issue.

Thank you very much for your work on this. I hope it hasn't completely ended. It was nice to see this project mentioned on a slide at Lin Clark's talk about the new Fiber system in the new version of react.

I suspect this project will gain some more popularity over the next year or so, as people realise that 3D projects need solid state management to remain somewhat maintainable and easy to adapt.

Thanks again.