I've been using it daily for a few years now; with librewolf, I don't get a menu at all, I have the issue with Scribus, and there used to be an Inkscape bug that caused problems with it (now fixed) but those are the only issues I've had with it in all that time.
Last post by AdmFubar - September 02, 2023, 10:32:51 PM
Wasnt sure about this, so i activated the global menu and started scribus. This global menu doesnt seem ready for primetime. Had issues with scribus and waterfox as soon as it started. This probably needs more fine tuning before it will work without issues in all deployments of kde.
And yes it is a kde thing... it puts the application menu on a toolbar at the top of the screen like one finds in gnome.
Last post by NathanUp - September 01, 2023, 08:16:02 PM
I'm wondering if anyone else here uses Scribus with a global menu. I'm running it on EndeavourOS + KDE Plasma using a global menu, and I have a strange issue where menu dropdowns simply stop working after working for a while. To resolve the issue, I have to close and re-launch Scribus.
Last post by NathanUp - September 01, 2023, 04:12:13 PM
Unfortunately, I'd only really be able to help with Yunohost when it comes to server setup and administration. While I am a daily desktop GNU/Linux user, I'm not a professional admin, so I use Yunohost because it makes setting up multiple publicly accessible applications in a reasonably secure way possible for someone like me. It comes with a pre-configured firewall, fail2ban, et cetera, and on my instances I also change the SSH port and switch to key based authentication. Beyond the inherent increase in attack surface that comes with installing multiple applications on one server, I think the only big differences between Yunohost and any other Debian server are likely the user portal and the web admin / API, and the latter can be disabled.
All that said, I'm happy to pitch in my limited skills where I can be useful.
Last post by a.l.e - September 01, 2023, 10:52:17 AM
thanks for your offer!
at work we're using our own instance of gitlab. in a perfect world, that would my preferred solution: it's comfortable to use. but it's also pretty heavy (or the server is heavily underpowered).
for many years now, i have been working with both github and gitlab, and (for the low expectations i have) they both work more than ok for me. of course, i would prefer using one of both since they would allow so many people to discover scribus (mainly in the case of github) and make contributing (and reporting issues) easier: no need for a specific account and a well known UI.
but craig has set the context and i agree with you that gitea could be a good alternative.
i think that the biggest challenge is to set up a CI and manage the shared resources.
gitea seems to be lightweight enough and has a good features set.
one important thing from my side: in the case of scribus, i would refrain from using yunohost: it's probably preferable to directly install it on the server (the attack surface is much lower...).
and now a few more inputs:
i think that the final goal should be to install gitea (or another git solution) on the scribus own server
the solution should first be tested on a different server
if you (or somebody else) can provide a server (i don't recall: does the scribus server run on linux or freebsd?) for the tests that would make things easier
how to migrate the mantis bug tracker content to gitea?
what are the resources needed (HD, RAM, CPU)?
what are the needs for setting up the continuous integration?
we should probably setup a test mirror (in a similar way, as it has been done for github and gitlab)
i can help in setting up the server
an ok from craig and jean is needed before the tests are started (we don't need one more platform that is not officially in use).
all in all, i would be really glad, if scribus could switch to git (and a modern software management platform) once scribus 1.6 is released!