This is mostly about integration/infrastructure, the community is independent if this (look at Krita).
That would be @devernay or myself.
There are many pros and cons regarding this. But as you say could be worth exploring …
1 Like
I think @hellozee is here, and perhaps they coul d answer and questions you might have about joining KDE. They are a Krita Dev.
.Though moving to KDE might be a bit problem in this situation. Considering KDE uses a self hosted GitLab instance for hosting the git repos & code review and bugzilla for bug tracking, not GitHub. And the official mode of communication is Matrix, though the channels are bridged with IRC and sometimes even Telegram. On the other hand we have folks who could take care of promotion, system administration, translations and most likely even some developers, 
I am also one of the web devs for digiKam. Most of the KDE stuff is nice… but bugzilla is a disaster.
In general (KDE) GitLab is ok, but we might get less contributions since it’s more complicated to submit a pull request compared to GitHub(?). The use of Jenkins is nice, we have already used that in the past, so that should not be an issue. Regarding bug tracking, Bugzilla is not something I would prefer to use (I also don’t think the users would prefer to use it).
Submitting a pull request or in case of GitLab, a merge request is pretty similar but ymmv. I have seen Kdenlive folks using the Gitlab issues for internal bug tracking, I guess someone could talk to Ben or any sys admin to use that instead I guess.
Ohh, we are going to have a new identity system similar to the blender one and if everything goes okay, we might get the blender funding platform running for Krita,
Also, there are plans to move the phpbb forums to Discourse, afaik.
1 Like
Okay that sounds great then. 
I don’t think we need to change what’s already working (github + pixls.us + fb + discord). What we really need is developpers who jump in.
There have been something like 2 or 3 external contributions to the code during the past year. That’s a good start, but we’re still far from having regular maintainers.
And Natron is not only a (open) source project, but we also have many users who cannot even compile a software, so we have to distribute binaries, which actually took most of our maintainer time during the past year.
True that.
Isn’t every user facing open source project like that? I can bet most of Krita users do not even know what Linux is. Being a KDE project helps us to focus just on to writing good code. There are sysadmins, web masters, promo folks who take care of the other tasks. Even for things like GSoC/Season of KDE we have designated folks who manage that, 
.
And of course how can I not talk about our yearly sprints which are sponsored by KDE allowing us to meet in person and talk about our favorite software, 
Most of our time on Natron is spent maintaining the build system, I don’t see how KDE can “fix” this. We still need to update, patch and test third-party dependencies for three platforms, this is a full time job.
Ahh, right, 
Ok I am back after a long job year and covid stuff. I am looking at documentation again and am going to start with building the app local.
- I am going to try from instructions to get a build env locally.
- Submit docs updates if there are any based on documentation.
- Then I want to build app from build scripts
- Update docs based on what I find there aslo.
I figure I will start here as I can get used to how the projects builds first.
5 Likes
Natron has an issue launching with AMDGPU-PRO driver.
AMDGPU-PRO seems to be broken on 20.04 for the past few months. It can be installed but it requires some dirty hacks.
When they fix the driver I’ll try compiling Natron against it and report the issues I find.
I’m not a developer so if anyone else with AMD GPU could take a look too, it would be of great help. If not, I’ll try it myself and see where it gets us.
Remember to build against the headers included with the driver, /opt/something.
2 Likes
Nice I see the Natron Devs have docker containers for building already was about to ask! Along this line then are the devs maintaining the local building AND docker building or just docker? Does anyone care? I want to vet all build processes that are available and expected to work hence the question.
The official builds are made with docker.
You can generate the docker images from Natron/tools/docker at RB-2.3 · NatronGitHub/Natron · GitHub - we currently have centos 6,7,8 and ubuntu 18.04,20.04 docker images.
I don’t see the difference between building in a docker image or using a local build: you can install all you need in the docker image, and compiling does not need any specialized hardware.
Thanks sir! I agree. Just wanted a little info. As a feet getting wet exercise I wanted to vet your build processes to for myself to get to know the project and see were I can help. This is while I read the docs and code. Thanks again for the answer I appreciate your time sir.