This project is used to collect and work on the KDE community's goals in 2017.
It would be awesome if we could have a page like https://whatcanidoformozilla.org/#!/progornoprog/advocate
Wed, Jan 17
Sat, Jan 13
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).
Thu, Jan 11
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.
Sun, Jan 7
Find below the merged version of previous comments, as requested.
Sat, Jan 6
Fri, Jan 5
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.
Wed, Jan 3
I would say no extensive documentation is needed when the interface its 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.
Tue, Jan 2
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?
Sun, Dec 31
Please add this bug to the list: https://bugs.kde.org/show_bug.cgi?id=270808
Wed, Dec 27
Don't overthink it, just do it! ;)
Thanks for the attention and comments to this.
Tue, Dec 26
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 :)
Mon, Dec 25
Dec 21 2017
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 :)
Dec 17 2017
Dec 10 2017
Hi, just found this task (after the announcement on community list).
Dec 3 2017
Dec 2 2017
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.
Nov 30 2017
I also would support some kind of first run wizard setting up standard keyboard shortcuts and panel widgets. Especially for migrating Windows users. I believe it is feasible to make the wizard in an unobtrusive way. E.g. an icon could be shown in the system tray which shows popup that informs the user briefly about the existence of the customization wizard. Ideally, the wizard can also be run at a later time with a fine-grained selection of what should be changed from the installation default (or back to the default).
We should be cautious in mixing up what Calamares (not a KDE project) does with what the desktop environment might do. For background, Calamares can be used in two ways:
- as a system installer; you boot a live CD or memory stick, and install some (Linux) system to a hard disk
- as a system configurator; you boot a newly purchased laptop and it starts into a "newuser" which reconfigures the system with the user preferences (and login name) you give
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, where we need to have to look at. Because we need to think about how to implement a good proxy support for application and an override structure...