Hi, I’ve been using kdenlive for a few weeks and started to think about contributions, but I’m already a bit confused where to go.
I found some links that I think could be changed, but I wasn’t able to paste links, so I’ll save that for another time.
How do the “invent issues” and the “bugs” trackers relate, are they just different views?
The former seems a bit more approachable, but I don’t seem to find same issues in both, e.g. this:
bugs; #509752
Apparently the “bugs” is the place to register new issues, so I should create an account there, apart from the one the forum? Would it be yet another account to contribute code, or is there one account to rule them all? And Matrix is a requirement too, to discuss code changes?
Users of Kdenlive are asked to report bugs or feature requests in bugs.kde.org as this is the official bug tracker for KDE. Issues in invent should only be created by developers or contributors. The team tries to vet bugs and feature requests from bugs.kde.org as quickly as possible and devote enough time to them there. The community can help with triaging bugs and try to replicate them on their systems. That helps us a lot.
Yes, please.
Both belong to the KDE environment so you need only one.
It’s not a requirement to discuss code changes. In fact, the discussion takes place in the MR itself. However, it is good practice to discuss any planned contributions to see whether there is support for it in the user community. These kind of discussion can take place here or on Matrix and Telegram.
Thanks for the quick reply! Sounds like I can start here.
Is the prevention of links posted here a general block, or just because I’m a new user? Is there, a “known workaround” e.g. remove http, to circumvent it? I tried a bit, but gave up.
I didn’t want to create an issue first, but maybe that’s the correct way to point out erroneous links on the documentation.
Issues in invent should only be created by developers or contributors.
Got it. I’m not going to ask why they are not the same system. Is it ok for noobs to comment on “invent issues” as well?
Both belong to the KDE environment so you need only one.
Good, I was surprised that the forum wasn’t also the same. I think saw something about using “contributor account” on the forum, so would that be a better first step, or no real difference?
Nice, I already got the “basic” badge and should be able to post links now. I also saw your “wildfire comment” in another thread, so I understand that link-blocking is recurrently confusing newcomers. As such it fits my onboarding discussion (and maybe we can save you from responding to those comments in the future).
That blog is old, but mentions that “Every new user gets a welcome PM mentioning the trust system and linking to this blog post”. I didn’t get that, as far as I can see.
There is also no mention on the guidelines/FAQ that new users are in quarantine. Maybe first is not the right place, but I kind of think it is.
I’m not sure I would have seen those before posting, but at least they would help explain afterwards.
Finally, the error message came after typing a long post, trying to submit, and it simply was “links not allowed” or similar. If there was a motivation, a link to (improved) FAQ, or so I think that could help.
A bigger task than the others, but I think it detected links while writing, so the warning could have come earlier.
I do understand that KDE is a much bigger umbrella than I meant to carry, but would anyone suggest where to discuss these suggestions for smoother forum onboarding? You may already know more of the background and reasons than I ever will, but perhaps my “first impression” can be useful while I’m new.
If that’s actually true, it would be a bug in discourse which we don’t maintain.
You’ll need to talk to its maintainers about that.
The problem paradox is that you usually can’t fix “people don’t read documentation” by writing more documentation. That just make it even more likely they will TLDR.
