flameshot-org
New Version Release
Feature Description
The last version was 2 years ago. There have hundreds of updates since. The maintainers are busy and as they say, not being paid a penny for their work. Going to try and create a bounty for this and I suggest others pitch in to one of the best screenshot tools out there. If you're like me and you find that the 'pin' feature of this tool is the best productivity boost in the last 5 years, you should throw them some money because it's more useful than half the crappy big-company software you have to use on a regular basis. Thanks for the great product!
@jpmorris Thank you for your kind words and your concerns. The features queued for v13 is tracked in the following milestone: https://github.com/flameshot-org/flameshot/issues?q=milestone%3Av13+
We have been asking for C++ developer for over a year now, and so far no one bothered to join or contribute. This is a community project (from the community for the community), and it cannot go forward without the community either. As we have said numerous times, every help, even as little as fixing a typo is highly appreciated and is a step forward. The more eyes that are on the code, the better and safer software we all will have. So if you can contribute (documentation, code, ideas,...) please do so.
Regarding Rysolv, as I also explained in #3084, choosing an alternative platform is not straightforward. I'll look into it though and see if there are platforms that we can use. It would be great if you can chime in and help us going through them and discussing them. Perhaps the best place for that would be our Matrix channel in the Help room:
https://matrix.to/#/#flameshot-org:matrix.org
I will keep this thread open, but I will hid the non-constructive comments above to keep the thread clean and easier to read by others in case they also want to weigh in and provide their opinions/ideas. Thanks again.
@NeilRiver No, the project is not dead, nor it's maintainers.
Hi, I've watched a recent review of Flameshot (on YouTube) and I noticed a comment claiming that the project was "deprecated", so I came here to take a look.
Seeing many PRs merged since 2022 is a great sign, despite the uncertainty about when a new release would be feasible. Looking at the milestones, there's not that much left to do. But maybe you should consider postponing the remaining unimplemented features for a future update.
Most people are not comfortable with compiling code, and they are also the most likely to be annoyed by some random issue in nightly builds, so a fresh official release seems like a good way to bring attention to the project. OMGUbuntu and other sites will likely talk about the new release, and if you add a call for contributors in the release notes, that might do good. It's not a guarantee, but it sounds like a decent shot.
As you can see based on the PRs merged just this past two months, we are progressing, but it would be wrong to make a release without proper software design and checks in place, just because some youtuber has said something.
That said, it would be great if people can follow changes and give us feedback on what works and what doesn't.
The youtuber was really happy with Flameshot, it was just someone in the comments casually mentioning that the project was "deprecated". You obviously know what's best for the next version. My thinking was that if the remaining PRs are not important enough, it was worth postponing them for the sake of reviving the community, publishing the changes done in ~100 merged PRs since the last version, and hopefully draw enough attention to get more people to contribute to the project.
I've been involved in many FOSS projects in the last ~25 years and I've seen a few sink due to very slow releases cadence. Some developers can get bored or demotivated and leave, some users end up moving to other projects that get frequent releases, so sometimes it's a good idea to draw the line with the scope for new releases.
When I landed on the front page of your GitHub and saw the date of the most recent release, I also thought there's a good chance the project was dormant or abandoned, but I went to the commits page and then I looked for issues about a new release to see what was going on. 😄
I will tell the youtuber to consider making a followup video about Flameshot, with an invitation to anyone who wants to test the nightlies and share their feedback if they run into issues. Are the nightlies a good target for this purpose?
@kneekoo
My thinking was that if the remaining PRs are not important enough, it was worth postponing them for the sake of reviving the community, publishing the changes done in ~100 merged PRs since the last version
We have a milestone for v13 and we have added a subset of PRs to that milestone.
https://github.com/flameshot-org/flameshot/milestone/7
Not all the PRs are going to be merged for this release, especially because we have a big thing cooking up, which is the plugin system and is already in a draft PR. But that needs more work and more careful design. Hopefully by the end, users can use C++, Lua, and Python to write plugins for their usecases, and we keep Flameshot core lean and without bloat.
I will tell the youtuber to consider making a followup video about Flameshot, with an invitation to anyone who wants to test the nightlies and share their feedback if they run into issues. Are the nightlies a good target for this purpose?
The nighlys are good, but apart from that, the Arch AUR is built on head of master branch, and many Arch users are already using that. That said, we always make a pre release to get feedback from users before releasing. This means put stable release is usually more polished.
For nightly builds people can go to the following and download based on their operating system:
https://flameshot.org/docs/installation/development-build/
For linux users I can suggest trying out the AppImage as it doesn't need any installation and they just need to:
- Download the zip file
- Extract the zip file and find the AppImage
- Make it executable (e.g.,
chmod +x flameshot.….appimage) - Run it
But for future olans, we have two things to work on:
- Plugin system so that we can focus more on wayland instead of responding to none-screenshot related issues like Imgur
- Move from Qt5 to Qt6
Both of these require major code changes unfortunately.
As part of my effort to clean up our open issues I am going to close this. I am actively working on issues and will release the next version when its ready :)
