Related to T7014

In regard to UNCOFIRMED/CONFIRMED status, there's a relevant discussion here:
https://mail.kde.org/pipermail/kde-community/2018q1/004395.html
And more about bugzilla's usefulness here:
https://mail.kde.org/pipermail/kde-community/2018q1/004274.html

It should be added to the kdepim workboard

In T7116#134920, @richardbowen wrote:

What do you think about a dedicated stack for web development? As there is C++, Qt/QML for the desktop, like wise a dedicated/preferred programming language(s) and framework can be chosen for the web. This would help in onboarding contributors to the web side of things and potentially make management of the web stack easier for both the developers and the system admins.

What do you think about a dedicated stack for web development? As there is C++, Qt/QML for the desktop, like wise a dedicated/preferred programming language(s) and framework can be chosen for the web. This would help in onboarding contributors to the web side of things and potentially make management of the web stack easier for both the developers and the system admins.

@ngraham ok i did open new bug report : https://bugs.kde.org/show_bug.cgi?id=392339
i hope you will add list this in "Top-notch usability and productivity for basic software" thank you

@manuelmuzzurru, the best place for that kind of request is in the form of a Bugzilla ticket for frameworks-kio.

hi, did you see my comment for filesystem in dolphin (panel information)?

As a newcomer and junior-jobs guy, I'm happy to see this initiative being pushed forward by the Top People(tm) of the KDE organization. I've been stumbling my way through a few patches with the help of @rkflx and @ngraham, the latter of which agreed to mentor me in the ways of KDE. Henrik has been patient with me as I learn C++ and has given me a few assignments for Spectacle bugfixing. Nate has been a good guide to the environment and community. I'm sure there are many more like these two out there. Busy people, but willing to share their knowledge and expertise.

On thing we could use is an official policy regarding whether the stable or master branch is more appropriate for any given patch. Right now it's often not clear for edge cases such as D10651: Fix thumbnail hover icon show-in-fullscreen action. In that patch, a bug was fixed that led to a behavior change. Stable or master? We committed to master to be safe, but it wasn't as clear as we would have preferred.

hi, i wish to ask you:

Recently, I tried to find out KDE best practices to work with Docbook.

I really like UHD's explanatory text above the login box. We should implement that, with some short documentation and a link pointing to identity.kde.org. Who has the power to do this? KDE Sysadmins?

In T7646#127445, @ngraham wrote:

Out of curiosity, what are our criteria for considering this task done?

Well, I reply to myself as I got the following notification just after making the post above :
https://phabricator.kde.org/D10461
gmenu-dbusmenu-proxy
"This application finds windows using GTK GMenu DBus interfaces [1] and forwards them through DBusMenu. This way no adjustments in Plasma are needed."

Hi ! I wonder whether this one would fit in the KDE usability list : global menus don't work with GTK apps, cf :
https://github.com/kotelnik/plasma-applet-active-window-control/issues/78

I have updated https://community.kde.org/Get_Involved#Getting_in_touch_and_working_together and https://community.kde.org/Infrastructure/Phabricator#Logging_in, and included a picture highlighting the login button.

Hi everyone, I feel bad for being quiet over the last couple of weeks. Lots of changes happening in Jan-Feb for me, and also FOSDEM and the KDE Promo sprint are coming up. I'll try to push this goal forward in a consistent way once all these have passed.

@mmustac this is done now!

@ngraham Great to hear that. I will be one of the first to test your explanations if they are also ready for noobs like me :-D And provide my feedback of course.

Yes, it will be a redirect to https://community.kde.org/Get_Involved

Is it going to be a redirect to the existing pages? The example of page shown is a bit too much developer-oriented compared to https://community.kde.org/Get_Involved

@mmustac Yup, I've proposed that and already gotten buy-in and permission to do it. Just working on getting my access to change the page.

What about editing the "Get involved" page on kde.org as first step?
I am missing an up2date step by step guide to get a working development environment.
Because I really would like to get started.

FWIW, I updated https://community.kde.org/Get_Involved#Getting_in_touch_and_working_together with a more clear and concise description of how to sign up and log into Phabricator.

In T6831#124835, @IlyaBizyaev wrote:

The recently introduced KWallet support in VLC is cool; can it also be implemented for Firefox? When a master password is set, Firefox asks for it on every launch, which for me is usually just after unlocking my Wi-Fi passwords with KWallet. If Firefox could make use of KWallet (like Chrome and Opera do), it'd be one password prompt less on every device boot :)

The recently introduced KWallet support in VLC is cool; can it also be implemented for Firefox? When a master password is set, Firefox asks for it on every launch, which for me is usually just after unlocking my Wi-Fi passwords with KWallet. If Firefox could make use of KWallet (like Chrome and Opera do), it'd be one password prompt less on every device boot :)

It would be awesome if we could have a page like https://whatcanidoformozilla.org/#!/progornoprog/advocate

In T7116#123722, @dhaumann wrote:

I think we could obtain the relevant list of contributors from the sysadmins: all accounts that were created since last Akademy.

I would like to add another todo item to the list: All new contributors (e.g. the ones who committed a patch for the first time within the last year) should get a personal email, asking them to please attend the KDE conference. I think Akademy is an integral part of holding people together. As such, we need to push those a bit who are unsure (I was in this situation myself in 2004).

For now I added some information at https://community.kde.org/Get_Involved#Ways_to_contribute

SO, being very much green I wanted to ask you or anyone where/who I would go to for website edits. After some searching, I quickly found the webpage is wiki style. Because of how crazy it has been, I had to ask in the irc how to get to the registration link again so I can submit sample language and placement on community.kde.org. Wouldn't you know, valorie and I started talking about the issue, and bingo, she agreed to put changes to page as suggested. I also pitched for the auto-forward link like mozilla. Pretty cool! This is my first contribution...and it was surprising to see how easy and simple it was. Thanks again for the support and encouragement.

Find below the merged version of previous comments, as requested.

Only the next goal matters.

@michaelh With your goals in mind, you could go to kde.org, and see how you manage to get directions from there for what you want to do, and write down what you think is missing, needs improvement, or is awesome as it is, and then provide such feedback here.

I'm to excited I found this that I'm commenting before having completly read this thread. This topic is very close to an idea I woke up with this morning.

I would say no extensive documentation is needed when the interface is obvious on itself.

Thanks for the video, you are making good progress towards changing things for the better. There are two root problems I can extract from it:

+1 for Junior Jobs!

Thank you, that's quite useful :)

Well, here is a video. I think it might surprise some how much digging you would have to do in order to come to the realization that phabricator is the place where a lot of things get done if one is interested in contributing. Digging into a resource manual after several clicks fall below the bar of what can and should be done, in my opinion.

Cannot be answered in a simple way. Basically what we need is to put Fabricator right in the place where people would be looking for it, and the process to be as simple and straightforward as possible.

@es20490446e agreed. I am super new to this, who would you recommend this get assigned to? And what is the best path for someone who is new to go from posting ---> to implementation for something like this? What is an ideal background someone should have?

Please add this bug to the list: https://bugs.kde.org/show_bug.cgi?id=270808

Don't overthink it, just do it! ;)

Thanks for the attention and comments to this.

In T7646#121756, @vijaykrishnavanshi wrote:

I will create a page for elaborating the process of registering on Phabricator and creating reviews shortly and link it here. Footer idea is also cool :)

I agree there is still room for improvements to make it easier to register. People I have in mind here are those who want to start contributing changes to the code, get involved in the VDG, do promotional things etc., i.e. everything not related to bug reporting or triaging for which Bugzilla is the place to go at the moment.

I will create a page for elaborating the process of registering on Phabricator and creating reviews shortly and link it here. Footer idea is also cool :)

Here are some thoughts on threat models for this, not sure if we have a better place yet to discuss this, so I'll just put it here :)

Hi, just found this task (after the announcement on community list).

In T7050#119392, @knauss wrote:

Do we have a tag to combine all task that are connected to this? Or how we have an overview what to do?
F.ex. T7430 is one […]

In T7116#119541, @jsamuel wrote:

Thanks @ltoscano. But is there a way to check whether an application is part of the bundle or not? Reference: https://www.kde.org/applications/ includes Krita, Calligra.

In T7116#119539, @ltoscano wrote:

In T7116#119538, @jsamuel wrote:

There is now one item on Wikidata that documents and links all KDE applications on Wikidata. Click on any KDE application (especially if you are the developer) and contribute by improving it. Several key information has already been added. Thanks.

It should be fixed and make it more clear though. The wikipedia article associated to that item is about the "KDE Applications" bundle, not *all* applications by KDE.

So only applications part of the bundle should be linked from that object, and not others outside the bundle (like Krita, partitionmanager, Calligra, etc).

In T7116#119538, @jsamuel wrote:

There is now one item on Wikidata that documents and links all KDE applications on Wikidata. Click on any KDE application (especially if you are the developer) and contribute by improving it. Several key information has already been added. Thanks.

There is now one item on Wikidata that documents and links all KDE applications on Wikidata. Click on any KDE application (especially if you are the developer) and contribute by improving it. Several key information has already been added. Thanks.