Goal settings 2017Goal
ActivePublic

Details

Description

This project is used to collect and work on the KDE community's goals in 2017.

Recent Activity

Yesterday

xyquadrat added a comment to T6832: Improvements to Bugzilla - Making it easier and simpler.

Thanks @lueck for pointing these applications out; I have now re-added them to my active list.

Mon, May 21, 7:33 PM · Goal settings 2017
lueck added a comment to T6832: Improvements to Bugzilla - Making it easier and simpler.

knetattach

Not able to find a repository on cgit.kde.org nor a release in Ubuntu 16.04...

plasma-desktop/knetattach/

konsolekalendar

I can find the package in Ubuntu 16.04 (from a very old version), but not a repository

pim/akonadi-calendar-tools/konsolekalendar/

korgac

Not able to find a repository on cgit.kde.org nor a release in Ubuntu 16.04...

pim/korganizer/korgac/

kwikdisk

Not able to find a repository on cgit.kde.org nor a release in Ubuntu 16.04...

kdeutils/kdf

libalkimia

I can find the package in Ubuntu 16.04 (from a very old version), but not a repository

extragear/office/alkimia/

pimsettingsexporter

I found pim-data-exporter, which might be the same thing (?)

Yes pim/pim-data-exporter/

Mon, May 21, 7:36 AM · Goal settings 2017

Sun, May 20

xyquadrat added a comment to T6832: Improvements to Bugzilla - Making it easier and simpler.

Hm, is there a compelling reason to remove obsolete products from the database? If they are marked as obsolete, no new bugs can be filed against it anyway, and those should not show up in a browsable list for the user. Of course if you have admin rights they will show, but how often does an admin have to browse a product list without a filter?

I must admit that I just realized that the list of apps you can report a bug against is not the same as the ones accessible through clicking "Browse"...
But I think we should consider hiding the obsolete products not only when reporting bugs, but also in a) the advanced search & b) in the list from Browse. It'd simplify the search process for triagers a lot. Additionally, there are some products which are obsolete but you can still file bugs against them (e.g kaveau).

Sun, May 20, 2:42 PM · Goal settings 2017
lueck added a comment to T6832: Improvements to Bugzilla - Making it easier and simpler.

I decided to do something remotely useful with my free time and sifted through all applications/libraries present on bugs.kde.org, removing most obsolete products. My guidelines to determine whether a product was deprecated were:

  1. Is the product not marked as "unmaintained"/"deprecated"/"replaced"?
  2. Is the product in the repositories of Ubuntu LTS?
  3. Is the product on cgit.kde.org?
  4. If it is on cgit.kde.org, does it have any activity in the last year?

    After applying this criteria to all 737 (!) products available, only 455 remained (so nearly 300 products are obsolete, and should be removed from bugs.kde.org). It is of course entirely possible that I have either missed a deprecated product or have accidentally deleted an active product... Feedback is always welcome!

    All products:

    Only active ones:
Sun, May 20, 1:45 PM · Goal settings 2017
ltoscano added a comment to T6832: Improvements to Bugzilla - Making it easier and simpler.

Ok, so it seems that you only created a list and you are asking for feedback. Fine then, sorry for the misunderstanding, the wording could be misleading.

Sun, May 20, 1:18 PM · Goal settings 2017
ltoscano added a comment to T6832: Improvements to Bugzilla - Making it easier and simpler.

Just to be sure, @xyquadrat : did you already remove the products? In the future, don't remove first and ask later, but do the opposite. It's a bit too late to ask whether you had accidentally deleted an active product.

Sun, May 20, 1:14 PM · Goal settings 2017
schweingruber added a comment to T6832: Improvements to Bugzilla - Making it easier and simpler.

Hm, is there a compelling reason to remove obsolete products from the database? If they are marked as obsolete, no new bugs can be filed against it anyway, and those should not show up in a browsable list for the user. Of course if you have admin rights they will show, but how often does an admin have to browse a product list without a filter?

Sun, May 20, 1:09 PM · Goal settings 2017

Sat, May 19

dkardarakos updated subscribers of T8686: Junior Jobs.

Following a discussion with @bshah about T8685, we opted for revamping Plasma Mobile phabricator tasks. The status of many tasks has been changed in order to avoid offering to the potential contributor a task already done.

Sat, May 19, 6:54 PM · Goal settings 2017
xyquadrat added a comment to T6832: Improvements to Bugzilla - Making it easier and simpler.

I decided to do something remotely useful with my free time and sifted through all applications/libraries present on bugs.kde.org, removing most obsolete products. My guidelines to determine whether a product was deprecated were:

  1. Is the product not marked as "unmaintained"/"deprecated"/"replaced"?
  2. Is the product in the repositories of Ubuntu LTS?
  3. Is the product on cgit.kde.org?
  4. If it is on cgit.kde.org, does it have any activity in the last year?
Sat, May 19, 5:17 PM · Goal settings 2017
neofytosk added a comment to T8712: Forming a welcome team to guide newcomers.
In T8712#142098, @hein wrote:

It's worth noting we have this in a non-formalized way. The Getting Involved pages have always listed mentors you can contact for 1on1 questions (I've responsed to mails due to this for many years).

Sat, May 19, 3:49 PM · Goal settings 2017
neofytosk updated subscribers of T8686: Junior Jobs.

I'm not a developer, so perhaps I'm missing important aspects here, but how about using a common template with the things that would interest people, so they can quickly review what's it about before going into the details?

Sat, May 19, 3:22 PM · Goal settings 2017

Thu, May 17

sharvey added a comment to T8686: Junior Jobs.

What constitutes a "junior job" does indeed vary immensely. The maintainers or "lead" developers need to flag bugs carefully and appropriately. I've worked on junior jobs that ranged from string and icon changes, to adding a new API call to KWin. These were all referred to as JJ's, but they're definitely on different levels.

Thu, May 17, 6:53 PM · Goal settings 2017

Wed, May 16

hein added a comment to T8712: Forming a welcome team to guide newcomers.

I sometimes try IRC but that does not work very well, because a developer needs to be online at the same time you are online

Wed, May 16, 9:42 AM · Goal settings 2017
simgunz added a comment to T8712: Forming a welcome team to guide newcomers.

The link to the Mentoring page is literally the last word of the Getting involved page. I did read the getting involved page (maybe with not too much attention), but I did not reach the mentoring page and did not figured out I could contact a developer directly. Maybe this link can be highlight better somehow?

Wed, May 16, 7:42 AM · Goal settings 2017
profetikx added a comment to T7646: Make it SUPER obvious how to register for Phabricator for newer KDE fans.

Great stuff.

Wed, May 16, 12:16 AM · Goal settings 2017

Tue, May 15

paulb added a comment to T8685: First commit, made easy.

even if it requires a bit of effort up front to help people get started

Tue, May 15, 10:25 PM · Goal settings 2017
ngraham added a comment to T8685: First commit, made easy.

I don't think anyone's proposing an easy-but-broken method of brute-forcing the first commit. Rather, I think we're all discussing how to make it easier to get started the right way so that first commit is not only easier, but also conforms to KDE best practices.

Tue, May 15, 9:09 PM · Goal settings 2017
dkardarakos added a comment to T8685: First commit, made easy.
In T8685#141924, @aacid wrote:

The translation teams have said various times in the past that translations from random people in the internet with no commitment usually just bring in more work than they help since they totally fail at syntax, style guide, etc. I wouldn't be sure this has changed at all.

I mean would you let people edit code form the internet and submit a patch directly without having them compile and try it whatsoever? Probably not, so why would it be different for translations?

Tue, May 15, 2:11 PM · Goal settings 2017
hein added a comment to T8712: Forming a welcome team to guide newcomers.

It's worth noting we have this in a non-formalized way. The Getting Involved pages have always listed mentors you can contact for 1on1 questions (I've responsed to mails due to this for many years).

Tue, May 15, 12:04 PM · Goal settings 2017
neofytosk added a comment to T7116: Streamlined onboarding of new contributors.

It's great to see so much valuable feedback rolling in to this thread, especially from people that are new to KDE. Many thanks for that!

Tue, May 15, 8:43 AM · Goal settings 2017
neofytosk updated the task description for T8712: Forming a welcome team to guide newcomers.
Tue, May 15, 8:35 AM · Goal settings 2017
neofytosk added a subtask for T7116: Streamlined onboarding of new contributors: T8713: Finding a mentor for each newcomer.
Tue, May 15, 8:35 AM · Goal settings 2017
neofytosk added a parent task for T8713: Finding a mentor for each newcomer: T7116: Streamlined onboarding of new contributors.
Tue, May 15, 8:35 AM · Goal settings 2017
neofytosk triaged T8713: Finding a mentor for each newcomer as Normal priority.
Tue, May 15, 8:35 AM · Goal settings 2017
neofytosk triaged T8712: Forming a welcome team to guide newcomers as Normal priority.
Tue, May 15, 8:34 AM · Goal settings 2017
neofytosk added a subtask for T7116: Streamlined onboarding of new contributors: T8712: Forming a welcome team to guide newcomers.
Tue, May 15, 8:33 AM · Goal settings 2017
neofytosk added a parent task for T8712: Forming a welcome team to guide newcomers: T7116: Streamlined onboarding of new contributors.
Tue, May 15, 8:33 AM · Goal settings 2017
neofytosk created T8712: Forming a welcome team to guide newcomers.
Tue, May 15, 8:33 AM · Goal settings 2017
neofytosk added a parent task for T8711: Gathering feedback from newcomers on the current onboarding experience: T7116: Streamlined onboarding of new contributors.
Tue, May 15, 8:16 AM · Goal settings 2017
neofytosk added a subtask for T7116: Streamlined onboarding of new contributors: T8711: Gathering feedback from newcomers on the current onboarding experience.
Tue, May 15, 8:16 AM · Goal settings 2017
neofytosk triaged T8711: Gathering feedback from newcomers on the current onboarding experience as Normal priority.
Tue, May 15, 8:16 AM · Goal settings 2017
neofytosk added a subtask for T7116: Streamlined onboarding of new contributors: T8710: Documentation: maintaining an updated Get Involved page.
Tue, May 15, 8:03 AM · Goal settings 2017
neofytosk added a parent task for T8710: Documentation: maintaining an updated Get Involved page: T7116: Streamlined onboarding of new contributors.
Tue, May 15, 8:03 AM · Goal settings 2017
neofytosk triaged T8710: Documentation: maintaining an updated Get Involved page as Normal priority.
Tue, May 15, 8:03 AM · Goal settings 2017

Mon, May 14

sharvey added a comment to T8685: First commit, made easy.

As a relative newcomer (January), this is a very real and very powerful
thing. We should do whatever we can to encourage it. When my first
commit got landed (a simple plasmoid fix), it was a great feeling. Now
you'll probably never get rid of me.

Mon, May 14, 8:15 PM · Goal settings 2017
nicolasfella added a comment to T8686: Junior Jobs.

I totally agree that the jobs need a better description. This task is all about discussing what should be in there

Mon, May 14, 7:08 PM · Goal settings 2017
guntbertreiter added a comment to T8686: Junior Jobs.

May I suggest that you don't add more jobs to this list just now but instead focus on making the existing ones really junior friendly.

Mon, May 14, 7:05 PM · Goal settings 2017
aacid added a comment to T7116: Streamlined onboarding of new contributors.

BTW, Akademy is nearing, registration is open. Could we send a mail to all (!) contributors who have a KDE commit account? I think this does make a lot of sense to trigger everyone (especially new contributors) to come to this event.

Mon, May 14, 6:31 PM · Goal settings 2017
aacid added a comment to T8685: First commit, made easy.

The translation teams have said various times in the past that translations from random people in the internet with no commitment usually just bring in more work than they help since they totally fail at syntax, style guide, etc. I wouldn't be sure this has changed at all.

Mon, May 14, 6:29 PM · Goal settings 2017
dkardarakos added a comment to T8685: First commit, made easy.

TBH, my suggestion is primarily focused on the facilitation of a really fast and simple first contribution. Like the case when we learn a new programming language, almost always we try to run a "hello world" example, without having any real knowledge of the language or having read (almost) any page of the language reference. After the successful execution of the “hello world” , we feel a little bit more comfortable to continue studying. It's the "hello world" psychological effect accompanied with the feeling of membership and commitment to the KDE family that the solution tries to reproduce .

Mon, May 14, 2:59 PM · Goal settings 2017

Sun, May 13

lydia added a comment to T8623: sprint for onboarding goal.

We should definitely do something during Akademy but I don't think it should and can replace the sprint.

Sun, May 13, 12:47 PM · Goal settings 2017

Sat, May 12

richardbowen added a comment to T8685: First commit, made easy.

If we want to create a website (even it it's something like myfirstpatch.kde.org), we should put a link on the user's desktop at installation. That's relatively inoffensive, easily removed, and requires less coding than a desktop widget.

Sat, May 12, 11:18 PM · Goal settings 2017
sharvey added a comment to T8685: First commit, made easy.

If we want to create a website (even it it's something like myfirstpatch.kde.org), we should put a link on the user's desktop at installation. That's relatively inoffensive, easily removed, and requires less coding than a desktop widget.

Sat, May 12, 10:56 PM · Goal settings 2017
skadinna added a comment to T8623: sprint for onboarding goal.

Would it make sense to have this sprint as part of the BoFs and Workshops week at Akademy? Or maybe we can have a smaller session as a prep-event for the actual sprint.

Sat, May 12, 9:19 PM · Goal settings 2017
dhaumann added a comment to T7116: Streamlined onboarding of new contributors.

BTW, Akademy is nearing, registration is open. Could we send a mail to all (!) contributors who have a KDE commit account? I think this does make a lot of sense to trigger everyone (especially new contributors) to come to this event.

Sat, May 12, 8:14 PM · Goal settings 2017
simgunz added a comment to T7116: Streamlined onboarding of new contributors.

Here are my 2 cents.

Sat, May 12, 6:25 PM · Goal settings 2017
nicolasfella added a project to T8686: Junior Jobs: Goal settings 2017.
Sat, May 12, 5:55 PM · Goal settings 2017
nicolasfella added a subtask for T7116: Streamlined onboarding of new contributors: T8686: Junior Jobs.
Sat, May 12, 5:54 PM · Goal settings 2017
IlyaBizyaev added a comment to T8685: First commit, made easy.

Another website like that is https://whatcanidoformozilla.org

Sat, May 12, 4:09 PM · Goal settings 2017
bshah added a comment to T8685: First commit, made easy.

One of nice example I found earlier : https://howcanihelpubuntutouch.io/

Sat, May 12, 4:06 PM · Goal settings 2017