is this project active ?

[fislysandi]

question,

and is there any way to donate for development of the project?

[unfa]

I second that. I think the world needs a FOSS PureRef alternative and BeeRef is great.

[gelatinbomb]

Same. This is the only Foss alternative to pureref and even thought it has most of all good features there there is some killer bugs that needs some fixes.

[stilobique]

Maybe some fork is more active.

[ccoenen]

of the 13 forks, most are "up to date" or behind this project. One has two additional commits (this one https://github.com/mini-ninja-64/beeref ). I did not check if they had any additional branches, just the main branch.

[badrihippo]

@ccoenen I just went through the same analysis and came to the same conclusions!

If the current maintainers are unable to keep the project running, perhaps it could be handed over to someone else? @rbreu, if you see this, could you let us know the status?

Also attn: @mini-ninja-64 who has the latest updated main branch.

If there are no updates to this thread by January, I'll be free by then so I might be able to think of taking over myself (not active development, but at least accepting pull requests and bugfixes). If you're reading this and it's past January 2023, feel free to bump me a reminder 🤪

[mini-ninja-64]

Hello,
yes i updated it in my fork to not crash on pan and also did quick migration to using a Pipfile because i like them (but would clean it up bit more if doing a PR)

I made the changes neccesary for me to run the project as I wanted to have a version I could run locally with rotation support.

I noticed some other glitches with the recently opened ui on the homepage, so I just disabled it on my local binary build, I have been using this successfully for a while and it is working well.

I am very happy to accept pr's or discussions or whatever in regards to features etc

I chose not to make a PR at the time because I saw it was unmaintained 😨.
I am happy to raise a PR though if helpful, but would probably want to seperate into 2 pr's, 1 for the panning fix & 1 for the Pipfile addition

A question from me, would people find it helpful if I enabled pipelines on my fork so they could have working binaries of the latest version?

[unfa]

@mini-ninja-64 Thank you for taking care of BeeRef. It's a valuable tool for artists who want to use FOSS.
I have minor issues with it (lack of image filtering for example), but I love it overall and was sad to see it fall into disarray.

[raghu-kamath]

I have mailed Rebecca, pinged them on Krita-artists.org, and messaged on twitter, about this thread and give us an update. Hopefully we will have some reply.

[ghost]

Hello,
yes i updated it in my fork

@mini-ninja-64 Could you provide binary for Linux?

[mini-ninja-64]

@Symbian9 sure thing, will have some time to enable github actions this week

[5310]

Tried out the Ubuntu build on Manjaro after getting notification for the new release on @mini-ninja-64's branch (thanks again!) Unfortunately, it simply segfaults—

Launch output:

INFO __main__: Starting BeeRef version 0.3.0
INFO __main__: Using settings: /home/scio/.config/BeeRef/BeeRef.ini
INFO __main__: Logging to: /home/scio/.config/BeeRef/BeeRef.log
Segmentation fault (core dumped)

~/.config/BeeRef/BeeRef.log:

2023-03-14 09:26:09,049 __main__ 3230 140373254664640 Starting BeeRef version 0.3.0
2023-03-14 09:26:09,054 __main__ 3230 140373254664640 System: Linux unum 5.15.94-1-MANJARO #1 SMP PREEMPT Tue Feb 14 19:45:58 UTC 2023 x86_64 
2023-03-14 09:26:09,054 __main__ 3230 140373254664640 Python: 3.10.10
2023-03-14 09:26:09,054 __main__ 3230 140373254664640 Using settings: /home/scio/.config/BeeRef/BeeRef.ini
2023-03-14 09:26:09,054 __main__ 3230 140373254664640 Logging to: /home/scio/.config/BeeRef/BeeRef.log
2023-03-14 09:26:19,864 __main__ 3350 140184430563776 Starting BeeRef version 0.3.0
2023-03-14 09:26:19,866 __main__ 3350 140184430563776 System: Linux unum 5.15.94-1-MANJARO #1 SMP PREEMPT Tue Feb 14 19:45:58 UTC 2023 x86_64 
2023-03-14 09:26:19,866 __main__ 3350 140184430563776 Python: 3.10.10
2023-03-14 09:26:19,866 __main__ 3350 140184430563776 Using settings: /home/scio/.config/BeeRef/BeeRef.ini
2023-03-14 09:26:19,867 __main__ 3350 140184430563776 Logging to: /home/scio/.config/BeeRef/BeeRef.log

(Apologies for making a comment in this thread, as there's no Issues tab on the fork...)

[ghost]

Tried out the Ubuntu build on Manjaro

Same with MX Linux MX-21 (Debian 11.x):

$ ./BeeRef-0.3.0
INFO __main__: Starting BeeRef version 0.3.0
INFO __main__: Using settings: /home/user/.config/BeeRef/BeeRef.ini
INFO __main__: Logging to: /home/user/.config/BeeRef/BeeRef.log
Segmentation fault

~/.config/BeeRef/BeeRef.log:

2023-03-14 11:07:40,622 __main__ 38684 140310364457856 Starting BeeRef version 0.3.0
2023-03-14 11:07:40,625 __main__ 38684 140310364457856 System: Linux mx 5.18.0-0.bpo.1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.2-1~bpo11+1 (2022-06-14) x86_64 
2023-03-14 11:07:40,625 __main__ 38684 140310364457856 Python: 3.10.10
2023-03-14 11:07:40,626 __main__ 38684 140310364457856 Using settings: /home/user/.config/BeeRef/BeeRef.ini
2023-03-14 11:07:40,626 __main__ 38684 140310364457856 Logging to: /home/user/.config/BeeRef/BeeRef.log

To note that there is no ~/.config/BeeRef/BeeRef.ini.

[mini-ninja-64]

Yep, apologies, it wasnt quite ready yet as I was still testing but then life got in the way and I had to take a break, currently fixing it

I have also enabled issues on the project

I have setup working linux builds on a branch just need to finish up other OS and merge into the primary branch and run a release

[5310]

(This isn't an issue, in fact this is an opposite of an issue, so I'm posting it in this thread for closure: ) v0.3.1-beta now works flawlessly on Manjaro!

Thank you very much again for reviving BeeRef! 😊

[mini-ninja-64]

Woooo, i expect to properly release v0.3.1 tonight, time permitting.

Thank you for your patience (⁠ﾉ⁠◕⁠ヮ⁠◕⁠)⁠ﾉ⁠*⁠.⁠✧

[mini-ninja-64]

I have the github actions working nicely now, and as such have pushed release for v0.3.1

[rbreu]

It is. :)