Is this project abandoned?
There has not been much activity recently regarding updating the depencies of egui and wpgu despite the PRs so I was wondering what the maintainers have in mind, if anything. Do you recommend that everyone who wishes to keep using this starts maintaining their own forks from now on? I appreciate the project and this is not an ungrateful demand for updates, just looking for some clarifications.
Thanks!
It is for sure under-maintained. I have very little time for it, unfortunately. I use puffin and puffin_viewer a lot, but it is good enough that I don't feel a strong need to be actively working on it.
I would for sure appreciate some help here.
@emilk : I can be interested to help maintain puffin.
At the moment, I don't have a project to test puffin change, but I can found an application support to test change.
@kaphula @Vrixyz @phenaultBH @jakkos-net @Azkellas @SallySoul @kikawet @MarijnS95 @theoparis and others Given @emilk's response and the fact that EmbarkStudios no longer seems interested in maintaining Puffin, would you be able to support a revival (or fork) of the project? And if so, how? I have several ideas for improvements and new features, and I've even already worked on some of them. But for this to be viable, I would need sponsorship for my work.
I’d like to help. But I don’t have prior experience with public at such level, so I can only contribute in my spare time and without sponsorship. If that still works, please tell me what tasks or areas need help and I’ll pick something to start with!!.
I tend to agree with @emilk that the project is good enough for my needs at the moment and I do value stability.
However, if a feature is helpful to my work, or If there is need to review PRs, update dependencies, ect, I can help with that.
My use of this tool is limited to my academic work at the moment, so I am not in a position to help with sponsorship, my apologies.
I am mainly interested in getting the dependencies updated whenever wgpu and egui update so I can keep up with them without puffin holding me back. I am now doing this locally, and I am only using puffin + puffin_egui. If there is going to be a new fork I could maybe occasionally submit PRs that handle the updates to latest version in case things seem to get stuck.
This project serves me well for what it is now and I have no plans or time to commit for developing it further, although I do not oppose it if someone wants to do that as long as the existing features stay somewhat similar and no additional dependencies are added to the project. And if that happens, I can always maintain my own local fork, so no worries.
I would be able to support. I would like to see the dependencies at least kept up to date.