DragonPlayer

or admit defeat and just recommend VLC or MPV or something else? Nate Graham

Re: To start contributing to kde and participate in soK as a student.

advanced Let us know once you start working on something! Nate Graham On 12/15/2017 06:33 AM, Siva Kumaran wrote: I am new to the organization and would like to participate in soK as a student. I am quite familiar with c++. Can you please guide me on how to proceed.

Re: Looking for mentor for new KDE developer

On 01/04/2018 07:23 AM, Christian Gerloff wrote: Hello all, I've recently ported the unmaintained KDE application "KuickShow" to KDE 5 and plan to at least keep it working in the forseeable future. In order to get a KDE developer account to maintain the application on the KDE infrastructure, i

Re: Looking for mentor for new KDE developer

rship. At this point Henrik seems like the natural candidate, but he's mentioned that he lacks the time. Maybe Blue Systems should hire him to do it... ;-) Nate On 01/14/2018 01:32 PM, Kai Bojens wrote: Am 2018-01-04 15:35, schrieb Nate Graham: Gwenview is similarly unmaintained and in nee

Re: KDE and Google Summer of Code 2018

I've submitted an idea for System Settings: Improve handling for touchpads and mice with Libinput https://community.kde.org/GSoC/2018/Ideas#Improve_handling_for_touchpads_and_mice_with_Libinput This is pretty important going forward since most distros are shipping with Libinput now, but our us

git repo issues

de.org/D10131 -> commit shows up in git history, but does not appear on https://cgit.kde.org/discover.git Mind taking a look? Thanks! Nate Graham

Re: git repo issues

Thanks a bunch! Looks like the missing commits are tricking back into the web interface. Nate On 01/27/2018 12:23 PM, Ben Cooksley wrote: On Sun, Jan 28, 2018 at 4:54 AM, Nate Graham wrote: Hello Ben (et al), Hi Nate, I've noticed that in the last hour, git commits don't se

Re: Baloo is not dead, it just smells a little funny

Thanks Ben, and thanks Michael for this effort! Our users are really going to appreciate it. I plan to run promo on this to try to counteract some of the negativity out there. While we're on the subject of Phabricator projects, Ben, do you think you could also create a formal project for Gwenv

Re: Need enlightenment on bug 318998; Add option to exit after printing

1. Yes. It looks like the original request was for an additional --print_and_exit option, which would quit after closing the print dialog. 2. it might be nice to control that with another option, actually. More flexibility. Nate On 02/01/2018 12:21 PM, Dileep Sankhla wrote: Hello, I'm work

Re: Adding application to KDE and getting image of current

/DamirPorobic/ksnip (except for editing and annotation), and it's already shipped by default in all KDE distros that I'm aware of. Your work would have a hugely greater impact if you extended Spectacle instead! Nate Graham On 02/03/2018 05:30 AM, Damir Porobic wrote: The link th

Re: Adding application to KDE and getting image of current

g KSnip a KDE app if others think approve, but I want to bring this up as a long-term strategic matter. I think we all benefit from having one really strong choice that's developed by many. Nate Graham On 02/03/2018 11:02 AM, Damir Porobic wrote: Yeah, I was kind of afraid that you would

Re: Adding application to KDE and getting image of current

T6321 Happy coding, Nate Graham On 02/03/2018 01:15 PM, Damir Porobic wrote: I do see your point here and it indeed makes sense. I could invest some time and add the annotation features (and eventually other stuff) to Spectacle. The lack of those features is actually the reason why we're h

Re: Framework testing

I'll tell you what I do, at the risk of embarrassing myself. I do all my development in a KDE Neon VM. When I need to patch or test a framework, I make a snapshot in the VM in case things go bad, then deploy the patched/edited framework to /usr (`cmake -DCMAKE_PREFIX_PATH=/usr && make && sudo

https://phabricator.kde.org/ seems to be down

Any chance of resuscitation? Nate

Re: Closing old Plasma 4 bugs

+ kde-devel to widen the conversation On 02/10/2018 05:48 PM, Nicolás Alvarez wrote: Meanwhile... maybe you can do some loud blog posts calling for triagers? :) Sounds good. Before then, we need to clean up the wiki page for this: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Re: Closing old Plasma 4 bugs

All right, so let's give it a shot. How about we make it so that normal users have full privilages except the following: - Can't bulk change - Can't change Importance field - Can't re-open bugs in the CLOSED state Nate On 02/11/2018 09:17 AM, David Edmundson wrote: Interesting. If the

Re: Closing old Plasma 4 bugs

> On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: > >> On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: >> I have editbugs power on bugs.kde.org, but cannot edit the Importance field >> or mark a bug as CLOSED on bugstest.kde.org. I appear to have the new normal >> permissions. > > Than

Re: Closing old Plasma 4 bugs

On 02/21/2018 06:26 AM, Nate Graham wrote: On Feb 21, 2018, at 12:59 AM, Ben Cooksley wrote: On Wed, Feb 21, 2018 at 9:34 AM, pointedstick wrote: I have editbugs power on bugs.kde.org, but cannot edit the Importance field or mark a bug as CLOSED on bugstest.kde.org. I appear to have the

Re: Closing old Plasma 4 bugs

I have also cleaned up the bug triaging page: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging It's still a bit long, so any further editing to condense it a bit would be welcome. Nate On 02/21/2018 07:16 AM, Nate Graham wrote: On 02/21/2018 06:26 AM, Nate Graham

Re: Plasma Vault and BUG:390830

Maybe automatically disable indexing for cryfs and encfs volumes, no matters where they live? Vault allows you to change the default location of your vault, I believe. Nate On 02/24/2018 01:57 AM, Michael Heidelbach wrote: Hi! The best option to fix this bug is by excluding Vaults from bein

Re: Latte Dock and tangerine font

Maybe create a Phabricator task and see which VDG people show up? Andres Betts was the primary creator of Falkon's logo; he's really great with that sort of thing. Nate On 02/27/2018 05:43 PM, Valorie Zimmerman wrote: This discussion is icky to me. 1. I do not want to login to Github to dis

Recent disk mounting regressions in Solid framework

Howdy folks, What are we going to do about https://bugs.kde.org/show_bug.cgi?id=391706? This regression made it into a Manjaro release and was noticed by Igor Ljubuncic in https://www.dedoimedo.com/computers/manjaro-17-1-6-hakoila-plasma.html: > Also, if you try to mount internal volumes (har

Re: Recent disk mounting regressions in Solid framework

On 03/19/2018 03:04 PM, David Edmundson wrote: What is "the patch" you're referring to that Arch cherry-picked? https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/solid&id=069d565428658007ba8f983a06c8cd776d702d18 I wonder if this is the cause, actually. Can any Arch users

Re: Re: major memory leak

If you're using a slideshow as wallpaper or in a photo frame widget, then you're hitting https://bugs.kde.org/show_bug.cgi?id=368838. If so, try running plasmashell with "QSG_RENDER_LOOP=threaded" and see if that fixes the issue (and let us know if it does!). Nate On Mon, 26 Mar 2018 14:

Unable to compile KWidgetsAddons

In trying to test out a KWidgetsAddons patch, I find that I'm unable to compile it on KDE Neon dev unstable the code due to a CMake error: CMake Error in autotests/CMakeLists.txt: No known features for CXX compiler "GNU" version 5.4.0. Full output available at https://paste.kde.org/piy

Re: Unable to compile KWidgetsAddons

On 03/29/2018 08:06 AM, David Edmundson wrote: ​Do you have that error for just that one framework? Just for this framework. > Make sure you've fetched any relevant build deps. I have all the build deps that the Neon packaging knows about, at least: $ sudo apt build-dep kwidgetsaddons Readi

Re: Unable to compile KWidgetsAddons

On 03/31/2018 02:55 PM, Albert Astals Cid wrote: El dijous, 29 de març de 2018, a les 15:53:25 CEST, Nate Graham va escriure: In trying to test out a KWidgetsAddons patch, I find that I'm unable to compile it on KDE Neon dev unstable the code due to a CMake error: Have you tried a clean

Re: Unable to compile KWidgetsAddons

On 03/31/2018 03:05 PM, Albert Astals Cid wrote: El dissabte, 31 de març de 2018, a les 22:56:26 CEST, Nate Graham va escriure: On 03/31/2018 02:55 PM, Albert Astals Cid wrote: El dijous, 29 de març de 2018, a les 15:53:25 CEST, Nate Graham va escriure: In trying to test out a KWidgetsAddons

Re: Unable to compile KWidgetsAddons

On 03/31/2018 03:28 PM, Albert Astals Cid wrote: El dissabte, 31 de març de 2018, a les 23:16:12 CEST, Nate Graham va escriure: On 03/31/2018 03:05 PM, Albert Astals Cid wrote: El dissabte, 31 de març de 2018, a les 22:56:26 CEST, Nate Graham va escriure: On 03/31/2018 02:55 PM, Albert

Re: Unable to compile KWidgetsAddons

, 29 March 2018 15:53:25 CEST Nate Graham wrote: In trying to test out a KWidgetsAddons patch, I find that I'm unable to compile it on KDE Neon dev unstable the code due to a CMake error: CMake Error in autotests/CMakeLists.txt: No known features for CXX compiler "GNU"

bugs.kde.org: kio vs frameworks-kio vs kfile etc.

Howdy folks, Right now we have a lot of KIO bugs scattered around in various places: - kio - frameworks-kio - kfile Should we mark kio and kfile as not accepting new bugs, add some more components to frameworks-kio, consolidate everything there, and then eventually remove kio and kfile? Nate

Re: bugs.kde.org: kio vs frameworks-kio vs kfile etc.

On Mon, 09 Apr 2018 11:35:49 -0700 Elvis Angelaccio wrote > Yes. > > Note that this is not kio-specific: every library in kdelibs that used to > have its own bugzilla product should be "merged" with the new > frameworks-xxx product (actual bugs still open should be moved,

Re: bugs.kde.org: kio vs frameworks-kio vs kfile etc.

Here's another thing that may need changing: the frameworks-kio product doesn't allow votes. Nate On Mon, 09 Apr 2018 11:43:25 -0700 Nate Graham wrote > > > On Mon, 09 Apr 2018 11:35:49 -0700 Elvis > Angelaccio wrote > > Yes.

Re: bugs.kde.org: kio vs frameworks-kio vs kfile etc.

On Mon, 09 Apr 2018 13:46:22 -0700 Nicolás Alvarez wrote > Note that any changes will cause email notifications. If you close a fixed > bug that's fine, but for mass-moving from kio -> frameworks-kio that would > be just noise, especially annoying for old and already-closed bugs.

Re: bugs.kde.org: kio vs frameworks-kio vs kfile etc.

On Mon, 09 Apr 2018 14:21:45 -0700 David Edmundson wrote > > Not sure why this seems to be the case for some items. Maybe a sysadmin > > can look into it? > > Voting is deliberately turned off by some maintainers who find it > destructive. > That's definitely the case for plasm

Re: bugs.kde.org: kio vs frameworks-kio vs kfile etc.

Yep, just got my permissions, and I've pinged David Faure regarding the proposed changes. Nate On Mon, 09 Apr 2018 14:42:11 -0700 David Edmundson wrote > > ​> Should we mark kio and kfile as not accepting new bugs, add some more > components to frameworks-kio, consolidate ever

Re: Flatpak packaging for stable releases

I would strongly encourage it. Flathub is quickly becoming the de facto source for Flatpak apps, and all of GNOME’s apps are already there. It would be great to get some more KDE representation there too. Nate > On Apr 14, 2018, at 3:20 PM, Matthieu Gallien > wrote: > > Hello, > > I really

Re: Changes to Phabricator review subscriptions

1. What is the canonical way to be notified of Phabricator changes for projects you're interested in? Subscribe to that project's mailing list? Can you clarify what this means for someone who joins or "watches" a project in Phabricator? Should we stop doing that? 2. If someone is subscribed to

Re: Changes to Phabricator review subscriptions

https://community.kde.org/Infrastructure/Phabricator and for individual Phabricator project pages. Also, was this discussed somewhere before the change was rolled out? I didn't see anything about it on kde-devel. Nate On Wed, 09 May 2018 12:21:57 -0700 Ben Cooksley wrote ---- >

Re: Changes to Phabricator review subscriptions

On Wed, 09 May 2018 12:46:30 -0700 Luigi Toscano wrote > Nate Graham ha scritto: > > Thanks for the responses, Ben. > > > > I'm a bit concerned that all of this raises the barrier to entry for new > > contributors. Now they'll have

Re: Closing old Plasma 4 bugs

No objections from me. It was definitely not the intention to prevent users from being able to report wishlist tickets, or to prevent DrKonqi from being able to correctly file crash bugs. Nate On Fri, 11 May 2018 14:06:46 -0700 Christoph Feck wrote > On 11.02.2018 20:52, N

Re: Closing old Plasma 4 bugs

Kubuntu 18.04 has now now been out for a month, so if there are no further objections, I'll begin preparations for this Plasma 4 mass bug close. Nate On 02/14/2018 10:16 AM, Christoph Feck wrote: On 10.02.2018 21:24, Nate Graham wrote: Hello folks, We have more than 2,500 Pla

Re: Closing old Plasma 4 bugs

I don't know if it has an impact but in case I wanted to point it out. Cheers, Olivier Le samedi 26 mai 2018, 05:09:06 CEST Nate Graham a écrit : Kubuntu 18.04 has now now been out for a month, so if there are no further objections, I'll begin preparations for this Plasma 4 mass bug

Re: Closing old Plasma 4 bugs

This work is done; all the bugs and feature requests in the plasma4 product have been closed. Hope all of your inboxes survived the onslaught! Nate On 02/21/2018 07:21 AM, Nate Graham wrote: I have also cleaned up the bug triaging page: https://community.kde.org/Guidelines_and_HOWTOs

Re: Flatpak/Snap BoF at Akademy

I'd like to be there too! Nate On 06/28/2018 06:18 AM, Aleix Pol wrote: On Thu, Jun 28, 2018 at 7:54 AM Jan Grulich wrote: Hi, I would like to organize a BoF for Flatpak and Snap related stuff, to discuss our support of sandboxing, plans for future and so on. I would like to know whether th

Re: Submitting a distribution to wiki page

It's a wiki; please feel free to add your distro to the list (following the pattern)! Nate On Fri, 03 Aug 2018 13:23:05 -0700 Silvan Calarco wrote > Hello and sorry if this might be considered off-topic in this list, > > I've been looking at the page https://community.kde.or

Re: Contribute to KDE - Digikam

[cc'ing digikam-devel] Hello Jameer, you might have a look at: - https://community.kde.org/Get_Involved - https://community.kde.org/Get_Involved/development Nate On 08/04/2018 02:27 PM, Jameer Babu wrote: > Hello > > I am Jameer studying third year Computer Science and Engineering. I am > ve

Re: new brain on team

Welcome Bartosz! you might have a look at https://community.kde.org/Get_Involved If you're looking for specific projects that could serve as a good introduction, I would recommend tackling some junior-jobs bugs in Dolphin[1] Gwenview[2], Spectacle[3], or KIO[4]. To learn how to submit a patc

Re: KDE service for mounting storage resources

On 08/26/2018 09:04 AM, Elvis Angelaccio wrote: On venerdì 24 agosto 2018 19:37:26 CEST, Luca Carlon wrote: Hello! For some projects I'd need some kind of "service" being able to mount resources like SMB shares, FTP, SFTP etc... I read about KIO a bit, but I'd need something that can be passed

Re: The VDG

On 09/20/2018 09:07 PM, Stef Bon wrote: To start, we need a location on the Internet, starting with documentation, where it's easy to write/create (2d at least) drawings and formulas. Do you agree? We use Phabricator for this--both Maniphest Tasks and also Pholio Mockups (though we're still k

Re: Proposal, Adopt .editorconfig in every project

On 09/21/2018 04:40 AM, Tomaz Canabrava wrote: Hello fellows. In kde software we strive to be inclusive, that means that we don't enforce a coding style in every new project, nor do we adapt to newer styles on old software. This can create a bit of problems when we edit two projects at the

Re: New contributor seeking guidance

Hello Remya, We use phabricator.kde.org for patch submission. Here is the documentation for how to submit your patch: https://community.kde.org/Infrastructure/Phabricator Nate On 11/3/18 10:30 AM, Remya Krishnan wrote: Hi all, Thanks for the pointers. I have the following patch https://pa

Re: Mockup Design Assets for KDE

+visual-design Nate On 12/2/18 12:48 PM, Jacky Alcine wrote: Hey y'all. (posting this to two mailing lists as I'm a bit confused which is most useful) Do we have an equivalent of this for KDE? https://github.com/gnome-design-team/gnome-mockups-resources I was debating just winging it in Qt

Re: Contributing to KDE is hard because of its build architecture

On 12/9/18 10:51 AM, Martin Flöser wrote: Am 2018-12-09 16:41, schrieb Konstantin Kharlamov: Official way of building dependencies is using kdesrc-build. It has multiple problems: Hi Konstantin, sorry for your bad experienced, but I think it would have been much easier. Assuming you are on

Re: Logout from kde and show a black page on Fedora 28 KDE Live x86_64 Virtual machine installed on Qemu and VMware

Hello, This is the development list. To report a bug, please use http://bugs.kde.org/ after reading https://community.kde.org/Get_Involved/Bug_Reporting Nate On 12/20/18 11:58 PM, su...@coretek.com.cn wrote: Hi All! I installed Fedora 28 KDE Live x86_64 as Virtual Machines  on Qemu/KVM an

LXR is inaccessible

Hello Sysadmins, https://lxr.kde.org/ is inaccessible right now. Any ETA on getting it back up? Nate

Re: LXR is inaccessible

Thanks Ben, can confirm that all is well now! Nate On 2/11/19 9:54 AM, Ben Cooksley wrote: On Tue, Feb 12, 2019 at 5:23 AM Nate Graham wrote: Hello Sysadmins, https://lxr.kde.org/ is inaccessible right now. Any ETA on getting it back up? Hi Nate, Sorry for this - LXR went down when the

Phabricator seems down

Hello sysadmins, https://phabricator.kde.org is not responding responding right now for myself and others. Can you give it a kick? Thanks! Nate

Re: Phabricator seems down

Thanks, indeed it has. Nate On 2/12/19 10:22 AM, Ben Cooksley wrote: On Wed, Feb 13, 2019 at 5:09 AM Nate Graham wrote: Hello sysadmins, Hi Nate, https://phabricator.kde.org is not responding responding right now for myself and others. Can you give it a kick? It appears to have

Phabricator is down

Can someone give it a swift kick? Thanks! Nate

Re: What controls the default ordering of which application handles an opened file?

On 11/16/17 6:29 AM, Harald Sitter wrote: The KService frameworks supports a special desktop entry key [3] `X-KDE-InitialPreference` meaning to solve this. It assigns a custom preference score (higher=more preferred) to all mime types associated with the desktop file. To solve the problem with kr

notes.kde.org having auth trouble

Hello Sysadmin, People are having trouble authenticating to any of the documents on notes.kde.org. It's rejecting everyone's credentials for all documents at the moment. Would someone mind taking a look? Nate

Re: Gitlab Evaluation & Migration

On Mon, 25 Feb 2019 09:54:26 -0700 Martin Flöser wrote > You asked for comments. I gave comment that I'm not pleased about yet > another transition. Please keep that in mind. It means learning and > interrupted workflows for every one. If you have already decided and > don't

Re: Gitlab Evaluation & Migration

On Tue, 26 Feb 2019 02:02:08 -0700 Eike Hein wrote > How would GitLab impact the kdesrc-build experience? So this is the current kdesrc-build experience: 1. kdesrc-build [thing] 2. cd ~/kde/src[thing] 3. arc feature my-awesome-patch 4. Start hacking 5. kdesrc-build --no-src --re

Re: Gitlab Evaluation & Migration

On Wed, 27 Feb 2019 12:12:55 -0700 Eike Hein wrote > On 2/27/19 4:38 AM, Nate Graham wrote: > > It's really pretty nice. But Gitlab has a > > fork-the-repo-and-submit-a-merge-request workflow, so in steps 3 and 4, > > people without commit access w

Re: Gitlab Evaluation & Migration

On Wed, 27 Feb 2019 23:02:03 -0700 Ben Cooksley wrote > In terms of server load, it would be nice if the setup of forks was > still something the developer had to initiate rather than being done > automatically for every repository touched by kdesrc-build (I say this > mainly a

ffmpegthumbnailer

Howdy folks, We have https://cgit.kde.org/ffmpegthumbs.git, which is not very actively developed. There is also this upstream project https://github.com/dirkvdb/ffmpegthumbnailer which appears to be more actively developed. It seems kind of wasteful to have two projects that do exactly the sam

Re: ffmpegthumbnailer

On Sun, 03 Mar 2019 09:58:56 -0700 Luigi Toscano wrote > Nate Graham ha scritto: > > Howdy folks, > > We have https://cgit.kde.org/ffmpegthumbs.git, which is not very actively > > developed. > > > > There is also this upstream project

Re: Help regarding Getting involved (and GSoC)

The #kde-devel channel on Freenode IRC/Matrix may be what you're looking for. Nate On Thu, 07 Mar 2019 09:18:00 -0700 Abhinav Ananth wrote > Hi,I have a few queries from the Get Involved page > (https://community.kde.org/Get_Involved/development#Build_some_software) > specifica

Re: Help regarding Getting involved (and GSoC)

On Thu, 07 Mar 2019 10:17:04 -0700 Abhinav Ananth wrote > Thanks for the reply.Whom can I exactly contact amongst all the people there > in that chat room? Someone you might know? Or maybe the mentors of some kde > project under gsoc? If you're looking for specific GSoC projects,

Re: Concluding the Gitlab Discussion

One thing I'd really like to not lose is the review status feature (approved/changes requested/etc). I've head that this is EE only. Is there any word on getting that added to our package? Other than that, I think I think what Gitlab offers over Phabricator is either a significant win or else j

Re: CI system maintainability

With regards to the discussion about mandatory code review, I think it's important to avoid immediately rushing to create new policy as a result of a particular event or abuse. It's always tempting to try to put in place a rule that would have avoided the problem if it had existed and was being

2019 Usability & Productivity sprint

Howdy folks, I'd like to bring people's attention to the 2019 Usability & Productivity sprint in Valencia, Spain on June 19th - June 26th: https://community.kde.org/Sprints/Usability_%26_Productivity/2019. We've got a fun and ambitious agenda planned (https://notes.kde.org/p/usability-productiv

Re: error kio-gdrive

That looks like an issue with the distro or its current state rather than the code. You rebooted after updating, right? If that doesn't help, please ask in a Neon-specific venue (mailing list, forum, IRC/Matrix channel, etc). Nate On Fri, 26 Apr 2019 09:36:11 -0600 luis cardenas wrote

Re: Code Review: Spectacle

On Sun, 05 May 2019 13:57:49 -0600 Reindl Harald wrote > > > Am 05.05.19 um 21:44 schrieb Boudhayan Gupta: > > Hi folks, > > > > I've been hacking on Spectacle again :-P > > if you are at it please bring back the sane behavior of "ksnapshot" to > make "remember selection"

Re: Code Review: Spectacle

Thanks! Looks promising so far. A Phab review would be lovely, yes. Nate On Sun, 05 May 2019 13:44:24 -0600 Boudhayan Gupta wrote > Hi folks, > I've been hacking on Spectacle again :-P > I wanted to refactor the platform backends to make it a little bit cleaner > and more state

Re: Code Review: Spectacle

On Sun, 05 May 2019 14:16:01 -0600 Reindl Harald wrote > Am 05.05.19 um 22:12 schrieb Nate Graham: > > As of 19.04, this is now an optional but off-by-default feature. Feel free > > to turn it on. :) > > that's not the point > > the

Re: Code Review: Spectacle

On Sun, 05 May 2019 14:44:14 -0600 Reindl Harald wrote > what are you talking about? > > * right next to delay there is a checkbox all the time "on click" > * you can switch that checkbox on for years (at least on Fedora) > * but it makes no sense apply it for every mode > * whe

Re: Code Review: Spectacle

On Sun, 05 May 2019 14:49:11 -0600 Reindl Harald wrote > > * right next to delay there is a checkbox all the time "on click" > > * you can switch that checkbox on for years (at least on Fedora) > > * but it makes no sense apply it for every mode > > * when i select a rectangle from

Re: Problems with setting up development environment (for new devs)

Glad to hear you got it up and running. Would you mind submitting a bug report for the issue over at https://invent.kde.org/kde/kdesrc-build/issues? Also, now's the best time for you to update the wiki page (https://community.kde.org/Get_Involved/development) to increase the clarify for anythi

Re: Contribution

On 5/26/19 7:36 AM, Harshita Sahai wrote: Respected Sir/Ma'am I would like to contribute to your community as I believe I have the required skill set to contribute and hence would like to be a part of your community. Please do let me know about your GitHub profile or any version control where

Re: KAuth helper in flatpak - was - Re: Smb4K flatpak build fails due to KAuth helper

On 6/2/19 4:37 AM, Albert Astals Cid wrote: El divendres, 31 de maig de 2019, a les 13:05:04 CEST, Alexander Reinholdt va escriure: Has anyone on this list successfully packaged a program with a KAuth helper included? Or is it impossible to install a KAuth helper into a flatpak? Help is much

Re: KNewStuff problem - GSOC 2019

On 6/5/19 7:51 AM, Ferencz Kovács wrote: > [...] it can be found, then it's gonna be added to the valid categories. Here the uplaodDialog chec

Re:Request for incubation of Kup backup system

I've been using Kup and am very impressed. Its level of system integration makes it a good candidate for incubation IMO and I'm quite willing to be the sponsor. Simon, you would need to move the project from Github to KDE infrastructure (Cgit, Bugzilla, Phabricator or Gitlab, etc.). Is that acc

Re: How is the Font DPI Scale stored?

On 6/12/19 9:53 AM, Elias Mårtenson wrote: On Wed, 12 Jun 2019 at 17:27, Christoph Feck > wrote: https://wiki.archlinux.org/index.php/Font_configuration says: $ xrdb -query | grep dpi Xft.dpi:        144 You can read XResources via libxcb calls, code in Qt

Re: Request for incubation of Kup backup system

ther than "Reply All". Nate On 6/11/19 10:48 PM, Nate Graham wrote: I've been using Kup and am very impressed. Its level of system integration makes it a good candidate for incubation IMO and I'm quite willing to be the sponsor. Simon, you would need to move the project

Re: Request for incubation of Kup backup system

On 6/16/19 7:11 PM, Simon Persson wrote: On 2019-06-17 06:48, Nate Graham wrote: Ping. Simon, do you want to move forward with migrating the source code to KDE infrastructure? Also if you're not already subscribed to the kde-devel@kde.org mailing list, I would recommend that or els

Applications 19.08 release notes

Howdy folks, The deadline for KDE Applications 19.08 is fast approaching and we need release notes! I've created https://notes.kde.org/p/applications_19.08_new_features and done a first pass on populating it with notes, but more are needed. If your awesome features and bugfixes will land in

Re: Portability of KDE Applications

As far as I understand, this is the reason why AppImage was invented. KDE KDE apps can be packaged as AppImages, no problem. You might want to look into that. Nate On 8/21/19 2:36 PM, Никита Сиргиенко wrote: Yes, but setting a few environment variables for each application start doesn't look

Re: Taking over maintainership of libkscreen / KScreen

On 9/14/19 12:36 PM, Roman Gilg wrote: On Fri, Sep 13, 2019 at 3:47 PM David Edmundson Generally I've found bugs better handled to go to blah-product-b...@kde.org then have people use "user watching" in bugzilla so N people can become the default assignee without needing extra rights. Yea, mak

KMPlayer releases

I just triaged a bug about KMPlayer's AppStream ID not working properly: https://bugs.kde.org/show_bug.cgi?id=412542 That the AppStream ID in current git master differs from the version in distro repos, which is a problem because KMPlayer hasn't had a release in 3 years. Luigi, Alexander, and

Re: KMPlayer releases

On 10/8/19 1:59 PM, Luigi Toscano wrote: With the current pace of development, and given the fact that KMPlayer is the only user of a deprecated framework (KMediaPlayer), I'd say it's not worth it right. Should the development restart, we could re-evaluate this In my experience, one often leads

Re: How to prevent users from opening GitLab issues?

GitLab Issues are intended to be the replacement for Phabricator tasks and are not intended to be used for user bug reports. We can't disable this feature or else we lose the project task tracking functionality entirely, which would be a major regression compared to Phabricator. Yes, it is ver

Re: How to prevent users from opening GitLab issues?

On 10/10/19 3:28 AM, Ben Cooksley wrote: Specifying a default issue template is an Enterprise Edition only feature i'm afraid. Please see https://docs.gitlab.com/ee/user/project/description_templates.html#setting-a-default-template-for-merge-requests-and-issues--starter for more information I

Re:Can we agree to change gitlab default behaviour from merge to fast-forward merge for all repos?

+1 Nate On Sun, 13 Oct 2019 14:57:20 -0600 aa...@kde.org wrote I find the merge behavior to be not what we've been doing in phabricator so given the idea is to maintain our workflows i'd appreciate if we can agree on continue doing the same. https://docs.gitlab.com/ee/user/proj

Re: kdesrc-build on centos 8

Hi Mike, Yes, kdesrc-build is the officially-supported method of building KDE software from source yourself (i.e. if you're not a distro packager). If there is ever an EPEL or COPR repo for KDE stuff on CentOS 8, that would probably work too. If you're using kdesrc-build and kwindowsystem can

Re: Looking for Subtitle Composer sponsor

Hello Mladen, I would be happy to be your sponsor! Per https://community.kde.org/Incubator#Candidate, we need you to provide the following information: - A list of the people regularly committing to the project - A plan to be in compliance with the KDE manifesto (https://manifesto.kde.org/in

Re: Looking for Subtitle Composer sponsor

On 11/7/19 12:55 PM, Mladen Milinkovic wrote: Hello Nate, On 11/7/19 3:31 PM, Nate Graham wrote: I would be happy to be your sponsor! Thank you! Per https://community.kde.org/Incubator#Candidate, we need you to provide the following information: - A list of the people regularly committing

Re: Looking for Subtitle Composer sponsor

On 11/8/19 2:42 AM, Ben Cooksley wrote: We'll need a ticket submitted for this (as emails can get lost, but tickets cannot be lost). If you could submit one at https://go.kde.org/systickets that would be appreciated. Done, I've filed https://phabricator.kde.org/T11998 Nate

Re: Looking for Subtitle Composer sponsor

One thing I forgot before we set up the git repo: you will need a developer account. Please apply for one at https://community.kde.org/Infrastructure/Get_a_Developer_Account Nate On 11/7/19 12:58 PM, Nate Graham wrote: On 11/7/19 12:55 PM, Mladen Milinkovic wrote: Hello Nate, On 11/7/19 3

  1   2   3   >