Re: GSoC 2023
Hi and welcome! Do you have a software in particular you'd like to contribute? GSoC is a program to help new contributors integrate an open source community and work on softwares they like. So first to know is which softwares in KDE you like and want to contribute on. Then, you will need to discuss with the team to know if there are subjects that you could work on during GSoC. To answer your question about junior jobs, you can find some in https://bugs.kde.org/buglist.cgi?quicksearch=JJ or https://bugs.kde.org/buglist.cgi?quicksearch=Junior. For now, we have few subjects written in https://community.kde.org/GSoC/2023/Ideas but you should not choose one if it does not interest you. Cheers, Johnny Le jeu. 26 janv. 2023 à 09:42, Tejus Khandelwal a écrit : > Hi everyone, > > I am Tejus Khandelwal, a 2nd year UG student at the Indian Institute of > Technology Kanpur. I have previously worked in C, C++, and Python and am > enthusiastic about learning new things. I wish to contribute to KDE in GSoC > 2023 and need help beginning. > > I would be highly grateful if someone could point out some > beginner-friendly issues to help me get started. > > Thanks. > >
Re: "Gardening" old bugreports
Hello, > Exclusions so far: > - okteta > - krita > - any bug reported by sit...@kde.org > > Thanks again for the feedback! Can you also add Falkon to the exclusion list? There are not that many bugs nor people working on it and at the moment it is easy to browse the bugs. Also I do not know if this was discussed, but some info message on the bugzilla would be nice, if this project is managed by this BugBot or not. Thank you for the help. Best regards, Juraj. On piatok 27. januára 2023 22:56:09 CET Justin Zobel wrote: > Thanks for the feedback, everyone. > > Given the distribution of positive vs negative feedback, we plan to > resume automatic bug triage of old non-wishlist bugs that have not > been updated in over 2 years. If you would like to opt your product > out of this initiative because you're able to keep on top of the > manual bug triage work, please let us know and we'll be happy to > accommodate you. > > Exclusions so far: > - okteta > - krita > - any bug reported by sit...@kde.org > > Thanks again for the feedback! > > On Sun, Jan 22, 2023 at 6:10 PM Thomas Baumgart wrote: > > On Donnerstag, 19. Januar 2023 22:39:45 CET Johannes Zarl-Zierl wrote: > > > Hi, > > > > > > Am Donnerstag, 19. Jänner 2023, 12:26:08 CET schrieb Nicolas Fella: > > > > Am 19.01.23 um 04:04 schrieb Justin: > > > > > The gardening team aims to find out if the bug reports are > > > > > still > > > > > relevant by involving the users who reported them in > > > > > determining if > > > > > they are still valid. This increases community involvement and > > > > > helps > > > > > KDE as there isn't anywhere near enough manpower to review the > > > > > thousands upon thousands of bugs that haven't been touched in > > > > > years. > > > > > > > > Anecdotally many people don't like such automated changes being > > > > done to their bugreports that don't actually engage with the > > > > content of the report.> > > > > Well, anecdotally you will mostly get feedback from people who > > > don't like it. Unless something is exceptionally great, few > > > people will take the time to speak out in favor of something that > > > is already happening. > > > > > > > > The bugs that we are interacting with are ones that have not > > > > > had any > > > > > activity for over 2 years. We are simply trying to > > > > > reinvigorate > > > > > discussion on those bugs to see if they are still valid. If > > > > > the user > > > > > does not reply within the standard 30 day period after a bug > > > > > is set to NEEDSINFO, it is automatically closed by the Bug > > > > > Janitor. > > > > > > > > > > I am not simply closing bugs, so I do take offense that care > > > > > is not > > > > > applied. > > > > > > > > Properly "triaging" old reports requires at least some level of > > > > understanding of the project, codebase etc. I'm afraid there is > > > > no > > > > simple solution to that and rule-based approaches aren't good > > > > enough. > > > > Even taking things like CONFIRMED status or wishlist priority > > > > into > > > > account assumes that these have actually been consistently > > > > applied. > > > > > > As a maintainer on a small project, I'm quite happy to get an > > > occasional nudge on old reports. Yes, I do occasionally go over > > > old reports to see if they are still valid, but having somebody > > > else doing this methodically makes sure I don't gloss over some > > > bug that could be closed or fixed. > > > > > > Having this done by someone else without too much internal > > > knowledge is an absolute plus in my opinion. After all, if you > > > want to clean up your attic, you try to find a helper who does > > > not have the same emotional attachment as yourself. > > > > > > > > I will halt it until it is approved by more developers. > > > > > However if it > > > > > is decided that it isn't wanted then the KDE as a whole will > > > > > need to > > > > > entice more people in sorting old bugs individually as it is > > > > > clearly > > > > > not a priority right now for the majority. > > > > > > Speaking for KPhotoAlbum, I really appreciate the bugzilla > > > gardening. Thank you for doing it! > > > > I can second that for the KMyMoney project. An occasional poke and > > the automated cleanup when no response arrives where it is needed > > helps a lot. > > > > > > -- > > > > Regards > > > > Thomas Baumgart > > > > - > > With every day I come closer to the grave and learn something new. > > It all happens because I have wandered around too much and stumbled > > into the Linux world - which is a fantastic place to be! (Algis > > Kabaila †) > > - signature.asc Description: This is a digitally signed message part.
Re: "Gardening" old bugreports
Hi Juraj, Of course we are happy to exclude Falkon from the list. Regards, Justin On 28/1/23 23:45, Juraj Oravec wrote: Hello, Exclusions so far: - okteta - krita - any bug reported by sit...@kde.org Thanks again for the feedback! Can you also add Falkon to the exclusion list? There are not that many bugs nor people working on it and at the moment it is easy to browse the bugs. Also I do not know if this was discussed, but some info message on the bugzilla would be nice, if this project is managed by this BugBot or not. Thank you for the help. Best regards, Juraj. On piatok 27. januára 2023 22:56:09 CET Justin Zobel wrote: Thanks for the feedback, everyone. Given the distribution of positive vs negative feedback, we plan to resume automatic bug triage of old non-wishlist bugs that have not been updated in over 2 years. If you would like to opt your product out of this initiative because you're able to keep on top of the manual bug triage work, please let us know and we'll be happy to accommodate you. Exclusions so far: - okteta - krita - any bug reported by sit...@kde.org Thanks again for the feedback! On Sun, Jan 22, 2023 at 6:10 PM Thomas Baumgart wrote: On Donnerstag, 19. Januar 2023 22:39:45 CET Johannes Zarl-Zierl wrote: Hi, Am Donnerstag, 19. Jänner 2023, 12:26:08 CET schrieb Nicolas Fella: Am 19.01.23 um 04:04 schrieb Justin: The gardening team aims to find out if the bug reports are still relevant by involving the users who reported them in determining if they are still valid. This increases community involvement and helps KDE as there isn't anywhere near enough manpower to review the thousands upon thousands of bugs that haven't been touched in years. Anecdotally many people don't like such automated changes being done to their bugreports that don't actually engage with the content of the report.> > Well, anecdotally you will mostly get feedback from people who don't like it. Unless something is exceptionally great, few people will take the time to speak out in favor of something that is already happening. The bugs that we are interacting with are ones that have not had any activity for over 2 years. We are simply trying to reinvigorate discussion on those bugs to see if they are still valid. If the user does not reply within the standard 30 day period after a bug is set to NEEDSINFO, it is automatically closed by the Bug Janitor. I am not simply closing bugs, so I do take offense that care is not applied. Properly "triaging" old reports requires at least some level of understanding of the project, codebase etc. I'm afraid there is no simple solution to that and rule-based approaches aren't good enough. Even taking things like CONFIRMED status or wishlist priority into account assumes that these have actually been consistently applied. As a maintainer on a small project, I'm quite happy to get an occasional nudge on old reports. Yes, I do occasionally go over old reports to see if they are still valid, but having somebody else doing this methodically makes sure I don't gloss over some bug that could be closed or fixed. Having this done by someone else without too much internal knowledge is an absolute plus in my opinion. After all, if you want to clean up your attic, you try to find a helper who does not have the same emotional attachment as yourself. I will halt it until it is approved by more developers. However if it is decided that it isn't wanted then the KDE as a whole will need to entice more people in sorting old bugs individually as it is clearly not a priority right now for the majority. Speaking for KPhotoAlbum, I really appreciate the bugzilla gardening. Thank you for doing it! I can second that for the KMyMoney project. An occasional poke and the automated cleanup when no response arrives where it is needed helps a lot. -- Regards Thomas Baumgart - With every day I come closer to the grave and learn something new. It all happens because I have wandered around too much and stumbled into the Linux world - which is a fantastic place to be! (Algis Kabaila †) -
Re: "Gardening" old bugreports
Just to clarify, should we just exclude Falkon from bug report gardening or also from merge request gardening too? Merge request gardening is pinging MRs with no activity for 30 days, then closing if there is no response even two months after the ping message. On Sun, Jan 29, 2023 at 1:18 PM Justin wrote: > > Hi Juraj, > > Of course we are happy to exclude Falkon from the list. > > Regards, > > Justin > > On 28/1/23 23:45, Juraj Oravec wrote: > > Hello, > > > >> Exclusions so far: > >> - okteta > >> - krita > >> - any bug reported by sit...@kde.org > >> > >> Thanks again for the feedback! > > Can you also add Falkon to the exclusion list? > > There are not that many bugs nor people working on it and at the moment > > it is easy to browse the bugs. > > > > Also I do not know if this was discussed, but some info message on the > > bugzilla would be nice, if this project is managed by this BugBot or > > not. > > > > Thank you for the help. > > > > Best regards, > > Juraj. > > > > > > > > > > > > On piatok 27. januára 2023 22:56:09 CET Justin Zobel wrote: > >> Thanks for the feedback, everyone. > >> > >> Given the distribution of positive vs negative feedback, we plan to > >> resume automatic bug triage of old non-wishlist bugs that have not > >> been updated in over 2 years. If you would like to opt your product > >> out of this initiative because you're able to keep on top of the > >> manual bug triage work, please let us know and we'll be happy to > >> accommodate you. > >> > >> Exclusions so far: > >> - okteta > >> - krita > >> - any bug reported by sit...@kde.org > >> > >> Thanks again for the feedback! > >> > >> On Sun, Jan 22, 2023 at 6:10 PM Thomas Baumgart > > wrote: > >>> On Donnerstag, 19. Januar 2023 22:39:45 CET Johannes Zarl-Zierl > > wrote: > Hi, > > Am Donnerstag, 19. Jänner 2023, 12:26:08 CET schrieb Nicolas > > Fella: > > Am 19.01.23 um 04:04 schrieb Justin: > >> The gardening team aims to find out if the bug reports are > >> still > >> relevant by involving the users who reported them in > >> determining if > >> they are still valid. This increases community involvement and > >> helps > >> KDE as there isn't anywhere near enough manpower to review the > >> thousands upon thousands of bugs that haven't been touched in > >> years. > > Anecdotally many people don't like such automated changes being > > done to their bugreports that don't actually engage with the > > content of the report.> > > Well, anecdotally you will mostly get feedback from people who > don't like it. Unless something is exceptionally great, few > people will take the time to speak out in favor of something that > is already happening. > > >> The bugs that we are interacting with are ones that have not > >> had any > >> activity for over 2 years. We are simply trying to > >> reinvigorate > >> discussion on those bugs to see if they are still valid. If > >> the user > >> does not reply within the standard 30 day period after a bug > >> is set to NEEDSINFO, it is automatically closed by the Bug > >> Janitor. > >> > >> I am not simply closing bugs, so I do take offense that care > >> is not > >> applied. > > Properly "triaging" old reports requires at least some level of > > understanding of the project, codebase etc. I'm afraid there is > > no > > simple solution to that and rule-based approaches aren't good > > enough. > > Even taking things like CONFIRMED status or wishlist priority > > into > > account assumes that these have actually been consistently > > applied. > As a maintainer on a small project, I'm quite happy to get an > occasional nudge on old reports. Yes, I do occasionally go over > old reports to see if they are still valid, but having somebody > else doing this methodically makes sure I don't gloss over some > bug that could be closed or fixed. > > Having this done by someone else without too much internal > knowledge is an absolute plus in my opinion. After all, if you > want to clean up your attic, you try to find a helper who does > not have the same emotional attachment as yourself. > > >> I will halt it until it is approved by more developers. > >> However if it > >> is decided that it isn't wanted then the KDE as a whole will > >> need to > >> entice more people in sorting old bugs individually as it is > >> clearly > >> not a priority right now for the majority. > Speaking for KPhotoAlbum, I really appreciate the bugzilla > gardening. Thank you for doing it! > >>> I can second that for the KMyMoney project. An occasional poke and > >>> the automated cleanup when no response arrives where it is needed > >>> helps a lot. > >>> > >>> > >>> -- > >>> > >>> Regards > >>> > >>> Thomas Baumgart > >>> > >>>
Re: "Gardening" old bugreports
Hello, > Just to clarify, should we just exclude Falkon from bug report > gardening or also from merge request gardening too? > > Merge request gardening is pinging MRs with no activity for 30 days, > then closing if there is no response even two months after the ping > message. Good idea, I would also exclude Falkon from MR-Bot. Thank you, Juraj. > On Sun, Jan 29, 2023 at 1:18 PM Justin wrote: > > Hi Juraj, > > > > Of course we are happy to exclude Falkon from the list. > > > > Regards, > > > > Justin > > > > On 28/1/23 23:45, Juraj Oravec wrote: > > > Hello, > > > > > >> Exclusions so far: > > >> - okteta > > >> - krita > > >> - any bug reported by sit...@kde.org > > >> > > >> Thanks again for the feedback! > > > > > > Can you also add Falkon to the exclusion list? > > > There are not that many bugs nor people working on it and at the > > > moment it is easy to browse the bugs. > > > > > > Also I do not know if this was discussed, but some info message on > > > the bugzilla would be nice, if this project is managed by this > > > BugBot or not. > > > > > > Thank you for the help. > > > > > > Best regards, > > > Juraj. > > > > > > On piatok 27. januára 2023 22:56:09 CET Justin Zobel wrote: > > >> Thanks for the feedback, everyone. > > >> > > >> Given the distribution of positive vs negative feedback, we plan > > >> to > > >> resume automatic bug triage of old non-wishlist bugs that have > > >> not > > >> been updated in over 2 years. If you would like to opt your > > >> product > > >> out of this initiative because you're able to keep on top of the > > >> manual bug triage work, please let us know and we'll be happy to > > >> accommodate you. > > >> > > >> Exclusions so far: > > >> - okteta > > >> - krita > > >> - any bug reported by sit...@kde.org > > >> > > >> Thanks again for the feedback! > > >> > > >> On Sun, Jan 22, 2023 at 6:10 PM Thomas Baumgart > > >> > > > > > > wrote: > > >>> On Donnerstag, 19. Januar 2023 22:39:45 CET Johannes Zarl-Zierl > > > > > > wrote: > > Hi, > > > > Am Donnerstag, 19. Jänner 2023, 12:26:08 CET schrieb Nicolas > > > > > > Fella: > > > Am 19.01.23 um 04:04 schrieb Justin: > > >> The gardening team aims to find out if the bug reports are > > >> still > > >> relevant by involving the users who reported them in > > >> determining if > > >> they are still valid. This increases community involvement > > >> and > > >> helps > > >> KDE as there isn't anywhere near enough manpower to review > > >> the > > >> thousands upon thousands of bugs that haven't been touched in > > >> years. > > > > > > Anecdotally many people don't like such automated changes > > > being > > > done to their bugreports that don't actually engage with the > > > content of the report.> > > > > > Well, anecdotally you will mostly get feedback from people who > > don't like it. Unless something is exceptionally great, few > > people will take the time to speak out in favor of something > > that > > is already happening. > > > > >> The bugs that we are interacting with are ones that have not > > >> had any > > >> activity for over 2 years. We are simply trying to > > >> reinvigorate > > >> discussion on those bugs to see if they are still valid. If > > >> the user > > >> does not reply within the standard 30 day period after a bug > > >> is set to NEEDSINFO, it is automatically closed by the Bug > > >> Janitor. > > >> > > >> I am not simply closing bugs, so I do take offense that care > > >> is not > > >> applied. > > > > > > Properly "triaging" old reports requires at least some level > > > of > > > understanding of the project, codebase etc. I'm afraid there > > > is > > > no > > > simple solution to that and rule-based approaches aren't good > > > enough. > > > Even taking things like CONFIRMED status or wishlist priority > > > into > > > account assumes that these have actually been consistently > > > applied. > > > > As a maintainer on a small project, I'm quite happy to get an > > occasional nudge on old reports. Yes, I do occasionally go over > > old reports to see if they are still valid, but having somebody > > else doing this methodically makes sure I don't gloss over some > > bug that could be closed or fixed. > > > > Having this done by someone else without too much internal > > knowledge is an absolute plus in my opinion. After all, if you > > want to clean up your attic, you try to find a helper who does > > not have the same emotional attachment as yourself. > > > > >> I will halt it until it is approved by more developers. > > >> However if it > > >> is decided that it isn't wanted then the KDE as a whole will > > >> need to > > >> entice more people in sorting old bug
