search

thlorenz / rid

Rust integrated Dart framework providing an easy way to build Flutter apps with Rust.
64 stars 4 forks source link

Project gone stale? #63

Open MGlolenstine opened 2 years ago

MGlolenstine commented 2 years ago

What's the state of this project? It seems to have gone stale.

I can help out with some roadblocks, if that's what's holding the project back.

p4-k4 commented 2 years ago

@thlorenz appreciate this would take some time but it literally takes less than 2 minutes to update donors on a monthly basis at least, especially for those who want to donate but are unaware of if it’s active until they get past your pay wall.

what we looking at? 🙂 thanks for the efforts so far.

dariusc93 commented 2 years ago

If the project is dead or if there is no interest, it probably would be fair to have the repo made public for people to contribute to get the project going forward if anybody is interested in contributing.

thlorenz commented 2 years ago

I'm thinking about this @dariusc93 and @p4-k4 I totally get that this is not what you expected.

I've had no bandwidth for the last months to dedicate here due to a new job and shift of focus. However I don't consider the project dead.

@p4-k4 I sense some frustration and I get it so let me give some feedback:

Please also feel free to submit a PR updating the copy in the readme and the website to add that the project is currently inactive (not dead) and people should consider that when sponsoring.

WRT open sourcing I'm considering moving this into a sponsors only project. I just haven't made the final decision yet on how to proceed.

If anyone who contributed to rid in the past wants to take over the reigns I'm open to that as well.

Everyone here could take part in suggesting the road map and how to go about it .. let's keep this issue open to do so.

p4-k4 commented 2 years ago

@thlorenz Thank you for the response and clearing this up.

Sponsors I hope you don't take my responses as if I'm nagging. I just want to leave some suggestions as I'm feeling a little short-changed with regards to what your current pledge is (on the website, Github and YouTube) verus what I saw after donating.

My suggestion is that it might be best that you as current maintainer, notify potential and current sponsors regarding the state of the project and make clear your intentions before continuing to request and accept donations (as the website and GH currently is). Seen as how we as sponsors are not making the request for donations after all, it doesn't make sense that we update your request for donations.

If it were clear that - the project is not active and rather, we're now sponsoring your initial time invested, more than happy to consider that.

The road map It would be a shame to see the project continue to hang in limbo. But perhaps the need for contributions/maintenance can be highlighted on the website/GH examples? Not really sure how to approach that sorry. If I had the skills to contribute I totally would!

p4-k4 commented 2 years ago

If the project is dead or if there is no interest, it probably would be fair to have the repo made public for people to contribute to get the project going forward if anybody is interested in contributing.

I also agree with this, it's a bit of a deterrent for potential contributors to have them too, behind a paywall (should you decide to allow public contributions).

thlorenz commented 2 years ago

I will think about this.

Before I make this public I want to make sure that it can be maintained + evolve going forward as potentially more people will depend on it than now. However I might make it start with a sponsor-only repo and go from there.

At any rate I'll make an announcement about this soon and will ask who of the current contributors who made significant contributions in the past want to help re-activating work of rid. Those will then get write access to that repo.

enzotar commented 2 years ago

If the project is dead or if there is no interest, it probably would be fair to have the repo made public for people to contribute to get the project going forward if anybody is interested in contributing.

I also agree with this, it's a bit of a deterrent for potential contributors to have them too, behind a paywall (should you decide to allow public contributions).

I also agree with this. If you are not actively contributing and don't think it's dead, you want to remove any barriers for others to contribute. The sponsor-only repo only makes sense if you are actively contributing.

If one looks at options to integrate Flutter/Dart and Rust, one sees some manual implementation, like Appflowy, Flutter Rust Bridge which is actively maintained, and RID somewhat stale, behind a paywall with few contributors. Why would anyone pick RID? Why would anyone contribute?

And as someone who is using RID for a prototype/MVP it's hard to continue using RID because it's stale and I'll most likely refactor with Flutter Rust Bridge. I would help but it's not my expertise.

Also, echoing @p4-k4 I find odd that you ask 'Please also feel free to submit a PR updating the copy in the readme and the website to add that the project is currently inactive (not dead) and people should consider that when sponsoring.' If you are no longer contributing and you know the project is inactive, you ought to update it and not ask others for a 'feel free to submit a PR...'

If you want the project to live, it needs a little time from you. And if you have no time, then let other push it forwards without restrictions. You are limiting the potential pool of maintainers with this structure. Still your project, still your baby, but you need the village to take over for a little bit until you're back.

thlorenz commented 2 years ago

Thanks for the clear words @enzotar. I've pushed this off for too long it seems. However I listened to what you said and for now just open source the repo as that was most pressing and also quickest to accomplish.

I'll clean up the text regarding the sponsors and so at a later time.

I will keep write access for anyone who contributed code in the past in the hopes that the project moves faster that way.

If any one else wants to keep write access please LMK.

p4-k4 commented 2 years ago

Thanks for the clear words @enzotar. I've pushed this off for too long it seems. However I listened to what you said and for now just open source the repo as that was most pressing and also quickest to accomplish.

I'll clean up the text regarding the sponsors and so at a later time.

I will keep write access for anyone who contributed code in the past in the hopes that the project moves faster that way.

If any one else wants to keep write access please LMK.

Bravo, I truly hope this project can get the lift it deserves. It would be a shame to let your work go to waste by further restricting it, until of course you have some time. Would still recommend highlighting on the website/GH/YouTube the need for extra contributions asap. Cheers.

John0x commented 2 years ago

You should probably post this on reddit etc. Just noticed this being open now on accident :'D

thlorenz commented 2 years ago

Yeah good point @John0x. I just wanna take care of all the other tasks I mentioned above first.