Re: flathub now supports tag, but which id to use for KDE? (was: Re: Defining a developer name for our applications metadata)

"https:// > kde.org", while others use "kde.org" (non-reverse DNS). > > Given the purpose of the id is to be unique per group, this should be > standardized, no? :) > > Confusingly enough one doc talks about "tld.domain" as pattern of the id > (flathub), while

flathub now supports tag, but which id to use for KDE? (was: Re: Defining a developer name for our applications metadata)

omain" as pattern of the id (flathub), while the other talks about "gnome.org" as example (appstream): https://docs.flathub.org/docs/for-app-authors/metainfo-guidelines/#name-summary-and-developer-name vs. https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag

Re: Defining a developer name for our applications metadata

Hi Albert, Am Dienstag, 30. Jänner 2024, 22:27:22 CET schrieb Albert Astals Cid: > "The KDE Community" is like "ATM Machine", KDE is *already* the community. I have to say this is definitely *not* like "ATM Machine". At least I hope nobody is saying "the C in KDE stands for Community"... ;-)

Re: Defining a developer name for our applications metadata

a warning) on appstream 1.0.1. See also the Developer section from https://planet.kde.org/matthias-klumpp-2023-11-11-appstream-1-0-released/. -- Timothée Ravier CoreOS co-Team Lead Red Hat <https://www.redhat.com/> trav...@redhat.com <https://www.redhat.com/>

Re: Defining a developer name for our applications metadata

Hi, Just to be sure, do we know which appstream version do we use to validate our appdata files ( https://invent.kde.org/frameworks/extra-cmake-modules/-/blob/master/kde-modules/appstreamtest.cmake) and if the deprecated tag will issue a warning, an error or nothing in it? Cheers, Johnny Le

Re: Defining a developer name for our applications metadata

Sounds good! Thanks for tackling this, Timothée. Nate On 2/2/24 08:55, Timothée Ravier wrote: Hi everyone, Following suggestions in the thread, I'll start updating our AppStream metadata with: ``` KDE ``` Thanks -- Timothée Ravier CoreOS co-Team Lead Red Hat

Re: Defining a developer name for our applications metadata

Hi everyone, Following suggestions in the thread, I'll start updating our AppStream metadata with: ``` KDE ``` Thanks -- Timothée Ravier CoreOS co-Team Lead Red Hat trav...@redhat.com

Re: Defining a developer name for our applications metadata

On Wed, Jan 31, 2024 at 8:57 AM Ben Cooksley wrote: > Wait, so Flathub has begun requiring an older tag that the Appstream > developers have deprecated? > > So we need to add tags to our metadata that are already deprecated and > which are going to result in future failures of our own unit tests

Re: Defining a developer name for our applications metadata

Am Mi., 31. Jan. 2024 um 08:50 Uhr schrieb Ben Cooksley : > On Wed, Jan 31, 2024 at 7:04 AM Timothée Ravier > wrote: > >> Hi folks, >> >> Flathub is now requiring that applications define a "developer_name" tag >> in their metadata (see [1], [2]). >> >> What do folks think would be a good value

Re: Defining a developer name for our applications metadata

Thanks, > Cheers, Ben > > [1] > https://docs.flathub.org/docs/for-app-authors/appdata-guidelines/#name-summary-and-developer-name > [2] > https://docs.flathub.org/docs/for-app-authors/linter/#appstream-missing-developer-name > [3] > https://freedesktop.org/softwar

Re: Defining a developer name for our applications metadata

ty" is like "ATM Machine", KDE is *already* the community. > > Also "KDE" works in all languages while "The KDE Community" is english-only. The developer name is a translatable tag (but can be explicitly marked as "do not translate" if that is not

Re: Defining a developer name for our applications metadata

; "developer_name" tag. > > > > I'm open to suggestions. > > > > Thanks, > > > > [1] > > https://docs.flathub.org/docs/for-app-authors/appdata-guidelines/#name-sum > > mary-and-developer-name > > <https://docs.flathub.org/d

Re: Defining a developer name for our applications metadata

authors/appdata-guidelines/#name-summary-and-developer-name <https://docs.flathub.org/docs/for-app-authors/appdata-guidelines/#name-summary-and-developer-name> [2] https://docs.flathub.org/docs/for-app-authors/linter/#appstream-missing-developer-name <https://docs.flathub.org/docs/for-app-aut

Re: Defining a developer name for our applications metadata

Hi, I recently added an application in flathub and found https://discourse.flathub.org/t/deprecated-developer-name-element/5746 which is related to the subject. I used appstreamcli to generate the appdata and it changes to . The new format emits a warning on flathub linter (missing

Re: Defining a developer name for our applications metadata

On Dienstag, 30. Januar 2024 18:34:46 CET Timothée Ravier wrote: > Flathub is now requiring that applications define a "developer_name" tag in > their metadata (see [1], [2]). > > What do folks think would be a good value for our application there? > > Based on the suggestion in the

Defining a developer name for our applications metadata

r KDE Apps with "The KDE Community" as the "developer_name" tag. I'm open to suggestions. Thanks, [1] https://docs.flathub.org/docs/for-app-authors/appdata-guidelines/#name-summary-and-developer-name [2] https://docs.flathub.org/docs/for-app-authors/linter/#appstream-mi

Re: developer account set up

On Tue, 2023-05-09 at 10:57 +0200, Johnny Jazeix wrote: > > I remember when we were integrating Gitlab at work, people for some reason > > were > > attempting to create branches in the upstream repo rather than on their own > > fork. Had to do some explanation that this isn't the way to go,

Re: developer account set up

Hi, Le dim. 7 mai 2023 à 17:54, Konstantin Kharlamov a écrit : > On Sun, 2023-05-07 at 17:21 +0200, Nate Graham wrote: > > There's also no reason anymore why they need to use a work branch in the > > main repo; a fork works just fine. I do nearly all of my development > > using personal forks;

Re: developer account set up

being freed, and around 600,000 inodes being released - mostly due to forks that only got used a small handful of times. > > Nate > Thanks, Ben > > On 5/7/23 17:06, Joshua Goins wrote: > >> We usually recommend contributors to create branches in the main > reposito

Re: developer account set up

On Sun, 2023-05-07 at 17:21 +0200, Nate Graham wrote: > There's also no reason anymore why they need to use a work branch in the > main repo; a fork works just fine. I do nearly all of my development > using personal forks; it's a 100% supported first-class citizen experience. +1 I remember

Re: developer account set up

contributors to create branches in the main repository (work/gsoc/...). Is it possible without a developer account? Johnny It doesn't have to be the GSoc student that creates the branches, only that they are the ones putting commits in it. Something I've seen done is the mentor creates the work branch (work

Re: developer account set up

> We usually recommend contributors to create branches in the main repository > (work/gsoc/...). Is it possible without a developer account? > > Johnny It doesn't have to be the GSoc student that creates the branches, only that they are the ones putting commits in it. Something I'

Re: developer account set up

Le dim. 7 mai 2023 à 11:22, Nate Graham a écrit : > -Utarsh > > It might be worth re-thinking this policy now that we use GitLab. People > don't need a developer account to fully contribute anymore. > > Nate > > We usually recommend contributors to create branches in t

Re: developer account set up

So Right now what do I need to do? Can you suggest to me anything that is beneficial for me? On Sun, May 7, 2023 at 2:53 PM Nate Graham wrote: > -Utarsh > > It might be worth re-thinking this policy now that we use GitLab. People > don't need a developer account to fully contri

Re: developer account set up

-Utarsh It might be worth re-thinking this policy now that we use GitLab. People don't need a developer account to fully contribute anymore. Nate On 5/7/23 09:41, Johnny Jazeix wrote: Le sam. 6 mai 2023 à 23:31, Nate Graham <mailto:n...@kde.org>> a écrit : Hello Utkarsh,

Re: developer account set up

Le sam. 6 mai 2023 à 23:31, Nate Graham a écrit : > Hello Utkarsh, > > You don't need a developer *account* to start contributing, and in fact > you can't have one until you've made a number of contributions already. :) > > If you're looking for information about st

Re: developer account set up

Hello Utkarsh, You don't need a developer *account* to start contributing, and in fact you can't have one until you've made a number of contributions already. :) If you're looking for information about starting the process of contributing with code, we have a bunch of documentation at https

developer account set up

Hlw, I am Utkarsh Kumar and I want to need help creating a developer account setup. so please can someone suggest to me the steps I need to follow to create a developer account?

Re: Developer setups for user D-Bus service files?

Am Mittwoch, 12. Januar 2022, 11:49:26 CET schrieb David Edmundson: > > This triggered yet another idea with me, and I came across > > https://www.freedesktop.org/software/systemd/man/environment.d.html > > upon which I tried to add a file > > /home/mydevuser/.config/environment.d/60-test.conf > >

Re: Developer setups for user D-Bus service files?

> This triggered yet another idea with me, and I came across > https://www.freedesktop.org/software/systemd/man/environment.d.html > upon which I tried to add a file > /home/mydevuser/.config/environment.d/60-test.conf > with the content > --- 8< --- >

Re: Developer setups for user D-Bus service files?

Am Dienstag, 11. Januar 2022, 22:49:47 CET schrieb David Edmundson: > I did start another idea. > > If you populate the dev session environment variables *really* early > must we even go through pam you can set your XDG_DATA_DIRS before DBus > daemon has loaded it will then have the right stuff.

Re: Developer setups for user D-Bus service files?

Am Dienstag, 11. Januar 2022, 22:49:47 CET schrieb David Edmundson: > >at least with systemd controlled start (but possibly also before > > Since forever. Okay, guessed so, as I had found decade old queries trying to solve similar challenges, though systemd also is that age, thus was not that

Re: Developer setups for user D-Bus service files?

>at least with systemd controlled start (but possibly also before Since forever. >So, what standard approach should we take as developers here? Personally I would say developers should avoid having a system installed KDE, you're only making life harder for yourself. Then things are relatively

Re: Developer setups for user D-Bus service files?

Am Dienstag, 11. Januar 2022, 19:38:09 CET schrieb Friedrich W. H. Kossebau: > YOUR INPUT NEEDED > So, what standard approach should we take as developers here? Ideally we all > do something similar, so any issues hit are more easy to > understand/reproduce when we discuss them. And ideally that

Developer setups for user D-Bus service files?

into a user-selected prefix, like in case of usual KDE developer setups (e.g. ~/kde/usr as used in documentation): a) typically the D-Bus session will not see those and thus be unable to start any service described in them, thus things being broken b) there is no option to override any service files

Re: Should we change how we approve developer account requests?

On Tue, Aug 17, 2021 at 4:15 PM Nate Graham wrote: > > > On 8/16/21 10:11 PM, Nicolás Alvarez wrote: > > It's not that odd :) We as sysadmins don't know if you're actually > > sponsoring them until you reply approving the request, since people > > can request develope

Re: Should we change how we approve developer account requests?

On 8/16/21 10:11 PM, Nicolás Alvarez wrote: It's not that odd :) We as sysadmins don't know if you're actually sponsoring them until you reply approving the request, since people can request developer access and enter any name as the sponsor. That's pretty much what the approval

Re: Should we change how we approve developer account requests?

El lun, 16 de ago. de 2021 a la(s) 13:50, Nate Graham (n...@kde.org) escribió: > While writing an email in support of a recent request for developer > access that I encouraged someone to apply for, it struck me as odd that > the sponsor can approve. I would expect the sponsor to approv

Should we change how we approve developer account requests?

While writing an email in support of a recent request for developer access that I encouraged someone to apply for, it struck me as odd that the sponsor can approve. I would expect the sponsor to approve or else they would not have sponsored the application in the first place! Instead, wouldn't

Re: Restore SVN developer/commiter access

El mié, 28 de abr. de 2021 a la(s) 08:24, Diniz Bortolotto (diniz.bortolo...@gmail.com) escribió: > > Hi friends! > > I'm a translator/dev from ancient times. :-D > I'm trying to get back to contributing to KDE. But, of course, I've lost my > old SSH keys. > > diniz@darkstar:/home$ ssh

Re: Restore SVN developer/commiter access

Hi Diniz, On Mittwoch, 28. April 2021 10:50:11 CEST Diniz Bortolotto wrote: > Hi friends! > > I'm a translator/dev from ancient times. :-D > I'm trying to get back to contributing to KDE. But, of course, I've lost my > old SSH keys. > > diniz@darkstar:/home$ ssh s...@svn.kde.org >

Restore SVN developer/commiter access

Hi friends! I'm a translator/dev from ancient times. :-D I'm trying to get back to contributing to KDE. But, of course, I've lost my old SSH keys. diniz@darkstar:/home$ ssh s...@svn.kde.org s...@svn.kde.org: Permission denied (publickey). Could someone help me to update that on the SVN server?

Re: Any Developer available for Sok

contributed > to kdenlive in past on multiple occassion. But as Sok requires a mentor and i > don't have one it becomes difficult for me to participate. Can anyone of the > kde developer mentor me for Sok. You can checkout my gitlab profile > https://invent.kde.org/vivekkde to se

Any Developer available for Sok

a mentor and i don't have one it becomes difficult for me to participate. Can anyone of the kde developer mentor me for Sok. You can checkout my gitlab profile https://invent.kde.org/vivekkde to see my work. Thank you

Re: KDE Developer portal

r solution we choose, you can count on me to help with > the content. And again, thank you so much for working on this! > > Cheers, > Ivana Isadora > > Den sön 12 juli 2020 kl 00:29 skrev Carl Schwan : > > > Hello everyone, > > > > Some of you probabl

Re: KDE Developer portal

on me to help with the content. And again, thank you so much for working on this! Cheers, Ivana Isadora Den sön 12 juli 2020 kl 00:29 skrev Carl Schwan : > Hello everyone, > > Some of you probably saw the "First-class user & developer documentation > centralized on a portal" goal pro

Re: KDE Developer portal

El diumenge, 12 de juliol de 2020, a les 17:39:51 CEST, Albert Astals Cid va escriure: > El diumenge, 12 de juliol de 2020, a les 0:28:58 CEST, Carl Schwan va > escriure: > > Hello everyone, > > > > I experiment with creating such a developer portal for KDE using the st

Re: KDE Developer portal

El diumenge, 12 de juliol de 2020, a les 0:28:58 CEST, Carl Schwan va escriure: > Hello everyone, > > I experiment with creating such a developer portal for KDE using the static > site generator Hugo and the docsy theme. The result with a few converted > articles can be

KDE Developer portal

Hello everyone, Some of you probably saw the "First-class user & developer documentation centralized on a portal" goal proposal by Isadora one year ago (https://phabricator.kde.org/T11096). I shared Isadora's opinion, of having a good developer portal with all the information

Re: Urgent(ish) Contract KDE Developer availability?

Hi Kai, Thanks for the update, I actually got in touch with Meven Car directly while I was waiting for this message to land on the list (I am subscribed BTW). He very kindly agreed to take a look for me - very glad to hear it's in tow! Regards, Bernie On Thu, 2 Apr 2020, 6:23 pm Kai Uwe

Re: Urgent(ish) Contract KDE Developer availability?

Hi Bernard, Bug 418906 is actually already being worked on right now and should be fixed soon. See https://phabricator.kde.org/D28476 and https://phabricator.kde.org/D28488 Cheers Kai Uwe

Re: Urgent(ish) Contract KDE Developer availability?

Hi Bernie, have a look at the list of trusted consulting firms: https://ev.kde.org/consultants/[1] Cheers Nico On Montag, 30. März 2020 07:23:04 CEST Bernard Gray wrote: > Hi all, > My name is Bernie, I work for an Australian Winemaking company and we > have been KDE Users for many years now

Urgent(ish) Contract KDE Developer availability?

Hi all, My name is Bernie, I work for an Australian Winemaking company and we have been KDE Users for many years now (https://dot.kde.org/2014/02/18/kde-software-down-under) I apologise if this is the wrong platform to pose the question, but I wasn't sure where else would suit - In short, due to

Re: KDE Developer Documentation

and the much older developer guide were part of my survey of currently available documentation. In fact, I was quite impressed by the depth of content in the Frameworks Cookbook. Sadly, it only touches on a few of the frameworks. Having all Frameworks contain that much documentation would go a long way

Re: KDE Developer Documentation

On Sat, Dec 28, 2019, 08:39 Olivier Churlaud wrote: > Hi, > > At CERN we didn't speak about this, except with the Plasma team who spoke > about having a cookbook based on git containing all the code and > explanations. > > Sebastian Klüger was the one who raised the idea. I have no idea if >

Re: KDE Developer Documentation

eworks, or >tutorials >for other KDE software and components that don't neatly fit into the >apidocs (at least afaik). The Qt docs are full of such tutorials (like >[1] >for starters) that live alongside the apidocs. > >Was there any discussion on where such developer documentation wou

Re: KDE Developer Documentation

On Fri, Dec 27, 2019 at 10:39 PM Carl Schwan wrote: > It shouldn't be very difficult to create a MediaWiki plugins that embed a > specific file from git in a MediaWiki page. We already have an extension > for Bugzilla integration, so it is possible. But before trying to solve the > technical

Re: KDE Developer Documentation

rials (like [1] for starters) > that live alongside the apidocs. > > Was there any discussion on where such developer documentation would live > other than the wiki? I was not at CERN so I'm afraid I'm not up-to-date in > that matter. If they should live in the wikis, we're back

Re: KDE Developer Documentation

Hi Carl, Thank you for the response! On Wed, Dec 25, 2019 at 5:59 AM Carl Schwan wrote: > Hi, > thanks for the report. An issue I see currently is that we have three > entries for our KDE frameworks and developer utilities: > > 1. https://kde.org/develop > 2. https:

Re: KDE Developer Documentation

, or tutorials for other KDE software and components that don't neatly fit into the apidocs (at least afaik). The Qt docs are full of such tutorials (like [1] for starters) that live alongside the apidocs. Was there any discussion on where such developer documentation would live other than the wiki? I

Re: KDE Developer Documentation

er > > [1] https://phabricator.kde.org/D14955 > [2] https://phabricator.kde.org/D14957 > > Le lundi 23 décembre 2019, 12:00:43 CET Juan Carlos Torres a écrit : > > > Greetings KDE developers and community members! > > In March this year, we started on a journe

Re: KDE Developer Documentation

Hi, thanks for the report. An issue I see currently is that we have three entries for our KDE frameworks and developer utilities: 1. https://kde.org/develop 2. https://kde.org/products/frameworks/ 3. https://techbase.kde.org/Welcome_to_KDE_TechBase Maybe we could merge some of them. Could

Re: KDE Developer Documentation

a journey to take stock of our developer > documentation and what needs to be done to make them not only more helpful > to current contributors but also more inviting to new ones as well as > external users of frameworks. > > The formal work ended in June and I submitted a full re

Re: KDE Developer Documentation Support update

On Fri, Mar 29, 2019 at 3:11 AM Olivier Churlaud wrote: > I started porting some tutorials to the repos where they belongs as > examples (for instance KWallet (https://phabricator.kde.org/D14955) and > KMessageBox (https://phabricator.kde.org/D14957). That's awesome! Thanks for getting this

Re: KDE Developer Documentation Support update

Hi Juan Carlos, Le mercredi 27 mars 2019, 14:03:54 CET Juan Carlos Torres a écrit : > Greetings KDE Community! > > I'm Juan Carlos Torres (Jucato on IRC) and I've recently been hired as a > contractor to get the ball rolling on updating our developer documentation. > Over

KDE Developer Documentation Support update

Greetings KDE Community! I'm Juan Carlos Torres (Jucato on IRC) and I've recently been hired as a contractor to get the ball rolling on updating our developer documentation. Over the years, our community has produced an incredible wealth of knowledge that now needs our attention and love. While

Re: Looking for mentor for new KDE developer

Hi, adding kde-community as this is actually a community matter as well as a -devel issue. On Sun, Jan 7, 2018 at 3:15 PM, Albert Astals Cid wrote: > El dilluns, 8 de gener de 2018, a les 0:07:00 CET, Albert Astals Cid va > escriure: > > El dilluns, 8 de gener de 2018, a les

Re: Looking for mentor for new KDE developer

We are still looking for a maintainer. Henrik Fehlauer is kindly helping Gwenview limp along--submitting many patches, and reviewing others. Peter Mühlenpfordt and I have also submitted a few patches. But it's mostly just maintenance work, not actual maintainership or technical leadership.

Re: Looking for mentor for new KDE developer

Am 2018-01-04 15:35, schrieb Nate Graham: Gwenview is similarly unmaintained and in need of a new maintainer, but already using KF5 and more commonly used today. Is there any ongoing discussion about its current development? The mailing list seems to be dead and the forum is filled with

Re: Looking for mentor for new KDE developer

On Mon, Jan 8, 2018 at 12:07 PM, Albert Astals Cid wrote: > El dilluns, 8 de gener de 2018, a les 8:15:54 CET, Ben Cooksley va escriure: >> Hi all, >> >> Just following up on this - is there anyone who is looking into >> helping Christian here? Hi Albert, > > I don't understand

Re: Looking for mentor for new KDE developer

El dilluns, 8 de gener de 2018, a les 0:07:00 CET, Albert Astals Cid va escriure: > El dilluns, 8 de gener de 2018, a les 8:15:54 CET, Ben Cooksley va escriure: > > Hi all, > > > > Just following up on this - is there anyone who is looking into > > helping Christian here? > > I don't understand

Re: Looking for mentor for new KDE developer

El dilluns, 8 de gener de 2018, a les 8:15:54 CET, Ben Cooksley va escriure: > Hi all, > > Just following up on this - is there anyone who is looking into > helping Christian here? I don't understand why we're forcing this "he needs a mentor". As Dominik says, he seems to know stuff since he

Re: Looking for mentor for new KDE developer

Hi all, Just following up on this - is there anyone who is looking into helping Christian here? Thanks, Ben Cooksley KDE Sysadmin

Re: Looking for mentor for new KDE developer

Hi Nicolás, On Thu, Jan 4, 2018 at 3:59 PM, Nicolás Alvarez <nicolas.alva...@gmail.com> wrote: > El 4 ene. 2018, a la(s) 11:29, Dominik Haumann <dhaum...@kde.org> escribió: >> >> [...] >> My very personal opinion on that is: [...] > > He did ask sysadmins to

Re: Looking for mentor for new KDE developer

Christian Gerloff - 04.01.18, 16:30: > On 01/04/2018 03:35 PM, Nate Graham wrote: > > Thanks for taking the initiative here! Would you consider using your > > talents to work on Gwenview instead of KuickShow? Gwenview is similarly > > unmaintained and in need of a new maintainer, but already using

Re: Looking for mentor for new KDE developer

On 01/04/2018 03:35 PM, Nate Graham wrote: > Hi Christian, > Thanks for taking the initiative here! Would you consider using your > talents to work on Gwenview instead of KuickShow? Gwenview is similarly > unmaintained and in need of a new maintainer, but already using KF5 and > more commonly used

Re: Looking for mentor for new KDE developer

rloff <chrgerl...@gmx.net> >>>> 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. >>>> I

Re: Looking for mentor for new KDE developer

gt; 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 >>> th

Re: Looking for mentor for new KDE developer

Hi Christian, On Thu, Jan 4, 2018 at 3:23 PM, Christian Gerloff <chrgerl...@gmx.net> 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

Looking for mentor for new KDE developer

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, it was suggested that I first find a mentor

New Developer

Hi, i am new to KDE. I would like to help in the development of existing projects. Can somebody guide me or give me some task that'll help me out to get to know it better. Thank you. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: New Developer

Hi, Welcome to KDE. For starter you can fix few bugs of different KDE application(whichever suits you best). Check this out -> https://bugs.kde.org/ . You can also look into our junior jobs. The link is same as the above. Cheers, Sayan On Sat, Jan 23, 2016 at 3:44 PM, Sangeeta Sharma

Re: New developer

Most of bugs are resolved already. בתאריך 30 בדצמ׳ 2015 12:49,‏ "Kevin Funk" כתב: > On Wednesday, December 30, 2015 03:51:49 PM Anirudh GP wrote: > > Hi guys, > > > > I'm Anirudh and I want to start contributing to the KDE community. How > do I > > get started? > > > > Thanks > >

Re: New developer

On Wednesday, December 30, 2015 06:44:49 PM Yosef Levy wrote: > Most of bugs are resolved already. Uh? http://kde.org/jj only shows open bugs. Cheers, Kevin > בתאריך 30 בדצמ׳ 2015 12:49,‏ "Kevin Funk" כתב: > > On Wednesday, December 30, 2015 03:51:49 PM Anirudh GP wrote: > > >

New developer

Hi guys, I'm Anirudh and I want to start contributing to the KDE community. How do I get started? Thanks Anirudh >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: New developer

On Wednesday, December 30, 2015 03:51:49 PM Anirudh GP wrote: > Hi guys, > > I'm Anirudh and I want to start contributing to the KDE community. How do I > get started? > > Thanks > Anirudh Heya, this question has been asked a few times on this mailing list already. Let me give you starting

Re: hiring kde theme developer

a flamewar (on this list) about "why the panel is styled differently" (it *will* turn into a flamewar) Thanks, I have been in touch with breeze theme developer, I will write a set of needed features. concerning the dashboard, that does not work with touchscreen. What "dashboar

Re: hiring kde theme developer

On Donnerstag, 12. November 2015 15:03:22 CEST, Stéphane ancelot wrote: Yes, the actual dashboard. (https://www.youtube.com/watch?v=ktDpkuEj3X4) I won't debate why it is no more available, but I will give my opinion. https://bugs.kde.org/show_bug.cgi?id=344180 Is there an equivalent

Re: hiring kde theme developer

On 10/11/2015 10:17, Thomas Lübking wrote: On Dienstag, 10. November 2015 09:50:16 CEST, Stéphane ancelot wrote: * The grey colour will need being changed Colors aren't hardcoded, "kcmshell5 colors" Ok, I gave it a try, we may tune what is needed, but unfortunately. We found nothing for the

Re: hiring kde theme developer

On Dienstag, 10. November 2015 15:51:21 CEST, Stéphane ancelot wrote: Ok, I gave it a try, we may tune what is needed, but unfortunately. We found nothing for the panel background color. The panel is done by an svg theme, please don't start a flamewar (on this list) about "why the panel is

Re: hiring kde theme developer

On Tue, Nov 10, 2015 at 2:20 PM, Stéphane ancelot wrote: > Hi Guys, > > No, This is not a SPAM. At first, We are very happy of the kde team work. > It permitted us to customize and lock down some desktop features very > quickly and efficiently for an industrial

Re: hiring kde theme developer

Hi Guys, No, This is not a SPAM. At first, We are very happy of the kde team work. It permitted us to customize and lock down some desktop features very quickly and efficiently for an industrial application. Few problems are remaining, like not being able to efficiently remove clipboard, but

Re: hiring kde theme developer

You should now have permissions to view the screenshots, sorry On 10/11/2015 09:54, R.Harish Navnit wrote: On Tue, Nov 10, 2015 at 2:20 PM, Stéphane ancelot > wrote: Hi Guys, No, This is not a SPAM. At first, We are very happy

Re: hiring kde theme developer

On Dienstag, 10. November 2015 09:50:16 CEST, Stéphane ancelot wrote: * The grey colour will need being changed Colors aren't hardcoded, "kcmshell5 colors" * scrollbars size should be bigger, since it is dedicated to a touchscreen application I suggest to ask hugo or on the VDG group on

Re: hiring kde theme developer

You may want to ask also in the community of http://kde-look.org/ >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

Re: hiring kde theme developer

can you be more specific whats your need. cu Andreas Am 09.11.2015 08:27 schrieb "Stéphane ancelot" : > Hi, > > We would like to customise a theme based on the breeze theme. > > We are looking for a guy able doing this, depending on our needs. > > Please send me private

Re: hiring kde theme developer

On Montag, 9. November 2015 18:10:27 CEST, Claudio Autiero wrote: Hello, I think it's a spam ;-) That would be the most impressive spam setup i've ever seen =) (Numalliance is a french industrial and he's running around for 2 weeks about porting some of their system to KDE) @Stéphane, If

Re: hiring kde theme developer

Hello, I think it's a spam ;-) 2015-11-09 16:25 GMT+01:00 kainz.a : > can you be more specific whats your need. > > cu Andreas > Am 09.11.2015 08:27 schrieb "Stéphane ancelot" : > >> Hi, >> >> We would like to customise a theme based on the breeze

hiring kde theme developer

Hi, We would like to customise a theme based on the breeze theme. We are looking for a guy able doing this, depending on our needs. Please send me private email. Or give me the right site to post if if this not right place. Regards S.Ancelot Visit

Re: Volunteer developer without much experience

On Mon, Sep 21, 2015 at 2:47 AM, Jeremy Whiting wrote: > If there's a branch name, then that's the branch where the porting > effort is taking place. The columns show the status of the porting > effort (whether it is on a branch or on master doesn't matter). We > release

  1   2   >