Re: Proposal unify back our release schedules

(apologize, resending, I've missed a CC) Carl Schwan ha scritto: > Hello Community, > > I know this might be a controversial idea, but I would like to propose reunify > our release schedules. I feel like splitting our releases schedules between > Frameworks, Plasma and Gear is not working as

Re: Proposal unify back our release schedules

Nate Graham ha scritto: > I expect a vast amount of discussion to result from this proposal, and I think > that's great. It'll be good to talk about it. But I suspect in the end we'll > likely not achieve 100% consensus, and in that event I'd like for us to put it > to a formal KDE e.V. vote so

Re: Proposal unify back our release schedules

Carl Schwan ha scritto: > Hello Community, > > I know this might be a controversial idea, but I would like to propose reunify > our release schedules. I feel like splitting our releases schedules between > Frameworks, Plasma and Gear is not working as well as we intended it to be > when > we

Re: Post-MegaRelease projects

Nate Graham ha scritto: > I've started pondering post-megarelease projects. We've spent so long on > porting and bugfixing that I think it might be useful to shift gears to > feature work, and I'd like to brainstorm potential large-scale projects and > gauge the level of interest in putting

Re: Retirement of IRC Services and KDETalk.net (Jabber)

Ben Cooksley ha scritto: > On Sun, May 21, 2023 at 10:42 PM Christian (Fuchs) > wrote: > > Skreamer / Pursuivant: I'd retire these when the replacement is there, and > not > before it. I also seem to have missed which part does the auto > announcement of

Re: Extending the license policy to include Apache-2.0

Jonathan Riddell ha scritto: > I don't think it needs to be restricted to infrastructural tooling, maybe just > a line somewhere saying Apache 2 is an option if needed for code sharing > compatibility with third party projects. That still prevents the usage of Apache 2.0 from scratch, as someone

Re: Extending the license policy to include Apache-2.0

Jonathan Riddell ha scritto: > I think I'd be against adding it to the policy, the aim of the policy has > always been to keep it simple which licence to use so ensure code and be > swapped around within and outwith KDE with minimal worry about different > licences.  Apache 2 doesn't add any

Re: Extending the license policy to include Apache-2.0

Alexander Potashev ha scritto: > Hi, > > Parts of https://invent.kde.org/websites/aether-sass/ are licensed > under Apache License 2.0. This disagrees with the KDE licensing > policy. > > Considering Apache-2.0 is similar to MIT, I don't see why it shouldn't > be allowed by the policy. Is anyone

Re: Releasing a non-KF5 library under MIT License

Alexander Potashev ha scritto: > Hi, > > I would like to release a Go library under the terms of the MIT > License and host it at invent.kde.org. The library definitely won't > fit in KF5 because it has nothing to do with Qt. > > The https://community.kde.org/Policies/Licensing_Policy says I

Re: Rebranding the release service

Philippe Cloutier ha scritto: > Hi Jonathan, > > Le 2021-02-15 à 09:49, Christoph Cullmann a écrit : >> On 2021-02-15 15:36, Nate Graham wrote: >>> On 2/15/21 6:01 AM, Jonathan Riddell wrote: Here at KDE we've always struggled a bit with branding and the announcement of formats for the

Re: New mailing list for Bugsquad

Thiago Masato Costa Sueto ha scritto: > Hello community, > > > I've requested a new mailing list for Bugsquad yesterday. > > > https://mail.kde.org/cgi-bin/mailman/listinfo/bugsquad > > > I'd strongly appreciate if current bug triagers and interested people > subscribe to it. I created an

Re: auto-comment on bugzilla when making an MR?

Nate Graham ha scritto: > On 5/20/20 6:50 AM, Boudewijn Rempt wrote: >> On woensdag 20 mei 2020 14:33:42 CEST Filipe Saraiva wrote: >>> I like the idea, but I hope in future we use Gitlab issues as our tool >>> for bug management. :) >> >> This has been discussed to death before... The plan is to

Re: auto-comment on bugzilla when making an MR?

Nate Graham ha scritto: > On 5/20/20 6:50 AM, Boudewijn Rempt wrote: >> On woensdag 20 mei 2020 14:33:42 CEST Filipe Saraiva wrote: >>> I like the idea, but I hope in future we use Gitlab issues as our tool >>> for bug management. :) >> >> This has been discussed to death before... The plan is to

Re: Information regarding upcoming Gitlab Migration: clarifications

Ben Cooksley ha scritto: > On Fri, May 1, 2020 at 4:38 PM Nate Graham wrote: >> >> >> >> On 4/30/20 5:59 PM, Aleix Pol wrote: >>> El jue., 30 de abr. de 2020 a la(s) 18:15, Albert Astals Cid Am I the only person that just has all the repos on the same folder? I thought it was the

Re: Information regarding upcoming Gitlab Migration

Bhushan Shah ha scritto: > - But most importantly, this breaks with the non-unique leaf repository > names feature offered by the proposed structure. So, There could be > maui/documentation and wikitolearn/documentation. But we would have > single KDE/documentation redirect Just to

Re: Licensing Policy and modified Apache License

Jonathan Riddell ha scritto: > On Thu, 12 Mar 2020 at 15:41, L. E. Segovia > wrote: > > The modification in question is located here: > https://github.com/wdas/SeExpr/blob/master/LICENSE > > > Copyright Disney Enterprises, Inc.  All rights reserved. > >

Re: Sysadmin Load Reduction: Code Related Services

Ben Cooksley ha scritto: > On Tue, Nov 19, 2019 at 6:20 AM Luigi Toscano > wrote: >> >> Ben Cooksley ha scritto: >>> On Tue, Nov 19, 2019 at 1:34 AM Harald Sitter wrote: >>>> >>>> On Sat, Nov 16, 2019 at 9:40 PM Ben Cooksley wrote: >>>

Re: Sysadmin Load Reduction: Code Related Services

Ben Cooksley ha scritto: > On Tue, Nov 19, 2019 at 1:34 AM Harald Sitter wrote: >> >> On Sat, Nov 16, 2019 at 9:40 PM Ben Cooksley wrote: >>> >>> On Sun, Nov 17, 2019 at 5:19 AM Carl Schwan wrote: Hi all, >>> >>> Hi Carl, >>> Can the gitlab api be of useful in the future?

Re: Sysadmin Load Reduction: Subversion Infrastructure

Māris Nartišs ha scritto: > pirmd., 2019. g. 11. nov., plkst. 16:02 — lietotājs Luigi Toscano > () rakstīja: >> >> Alexander Potashev ha scritto: >>> вс, 10 нояб. 2019 г. в 18:09, Luigi Toscano : >>>> >>>> Nate Graham ha scritto: >>>>

Re: Sysadmin Load Reduction: Subversion Infrastructure

Ilya Bizyaev ha scritto: > A task shows this attitude much better as it is something that will be > completed eventually. "[WIP] Migrate translations from SVN to Git" to me > sounds like a clear intention. A task and a document are different thing. A set of tasks are action items which specifies

Re: Sysadmin Load Reduction: Subversion Infrastructure

Ben Cooksley ha scritto: > On Tue, Nov 12, 2019 at 10:00 AM Alexander Potashev > wrote: >> >> пн, 11 нояб. 2019 г. в 17:02, Luigi Toscano : >>> >>> Alexander Potashev ha scritto: >>>> вс, 10 нояб. 2019 г. в 18:09, Luigi Toscano : >>>>

Re: Sysadmin Load Reduction: Subversion Infrastructure

Alexander Potashev ha scritto: > вс, 10 нояб. 2019 г. в 18:09, Luigi Toscano : >> >> Nate Graham ha scritto: >>> On 11/9/19 4:50 PM, Nicolás Alvarez wrote: >>>> El sáb., 9 de nov. de 2019 a la(s) 20:29, Nate Graham (n...@kde.org) >>>>

Re: Sysadmin Load Reduction: Subversion Infrastructure

Nate Graham ha scritto: > On 11/9/19 4:50 PM, Nicolás Alvarez wrote: >> El sáb., 9 de nov. de 2019 a la(s) 20:29, Nate Graham (n...@kde.org) >> escribió: >>> >>> Not knowing anything about the translation system we use... what are the >>> blockers to moving it over to git? >>> >> Not necessarily

Re: Reducing the load on Sysadmin

KDE ha scritto: > Hi, > > It seems there is always seem to be someone within KDE that wants something > new and shiny, I name gitlab, Discourse, a new identity system, etc. > > On the flip side, there is always someone that does not want to part with the > old stuff.  > > Hence there is always

Re: Sysadmin Load Reduction: Subversion Infrastructure

Ben Cooksley ha scritto: > On Sun, Nov 10, 2019 at 12:20 AM Luigi Toscano > wrote: >> >> Ben Cooksley ha scritto: >>> Hi all, >>> >>> When KDE committed to performing a migration to Git back in 2010, one >>> of the things that was ag

Re: Sysadmin Load Reduction: Code Related Services

Ben Cooksley ha scritto: > Hi all, > > In the category of code related services, Sysadmin currently supports > a wide-ranging number of services (which makes sense given the nature > of the community). Some of these however may no longer be in use or > will be duplicative of other services

Re: Sysadmin Load Reduction: Subversion Infrastructure

Ben Cooksley ha scritto: > Hi all, > > When KDE committed to performing a migration to Git back in 2010, one > of the things that was agreed at the time was that translators could > remain on Subversion to avoid disrupting their workflows. > > This however has led to a certain amount of

Re: Licensing policy and Apache 2.0

Jonathan Riddell ha scritto: > I'm not against this but the downsides are: > -it's yet another licence so would add confusion > -it's incompatible with the GPL 2 so there's an increased risk of incompatible > licences interfering with each other > > It doesn't seem to cover any use case that

Licensing policy and Apache 2.0

Hi, right now the licensing policy does not contain the Apache 2.0 license: https://community.kde.org/Policies/Licensing_Policy While it may not be really useful for C++ code, the Apache 2.0 license is more extensively used by the Python community, and it may be useful for infrastructure

Re: Invent/gitlab, issues and bugzilla

Bhushan Shah ha scritto: > Everyone, let's take a step back. > > Original discussion was, if project X can use gitlab issues instead of > bugzilla? If the developers/maintainers prefer? > > Potential arguments to which are either, > > - No they can't because we forbid it in our manifesto or

Re: Invent/gitlab, issues and bugzilla

Boudewijn Rempt ha scritto: > On woensdag 3 juli 2019 20:23:41 CEST Nate Graham wrote: >> On 7/3/19 11:53 AM, Albert Astals Cid wrote: >>> If the new is much better than the old, let's just remove the old. >>> >>> As said, having two things that do the same is just confusing for everyone. >> >> I

Invent/gitlab, issues and bugzilla

Hi, one of the main point of the gitlab migration has been so far the replacement for phabricator. We didn't discuss about bug tracking. Despite this, I've seen a few projects using issues as replacement for bugzilla. We can all debate which is better, whether bugzilla or the gitlab issues,

Re: Testbed Discourse Server For Trial discuss.kde.org.uk

Nate Graham ha scritto: > On 6/29/19 4:04 PM, Thomas Pfeiffer wrote: >> Hi Jonathan, >> Thank you for setting this up! >> I've recently had the opportunity to experience Discourse in action in >> another community, and found it to fulfill most of the things we found >> lacking in both of our

Re: Licensing policy change proposal

Mirko Boehm (KDE) ha scritto: Hello, On 28. Jan 2019, at 13:23, Krešimir Čohar > wrote: I don't think there are any problems with using public domain images, and even if there were I'd rather view them as challenges to overcome than obstacles to avoid. This is not

Re: Policy on stale bugs (was Re: Closing NEEDSINFO bugs after 30 days)

Luigi Toscano ha scritto: Andrew Crouthamel ha scritto: I've been spending a lot of time browsing, searching, and filtering our bugs in Bugzilla. One of the areas I've found that could use improvement, are the NEEDSINFO bugs. Often, bugs are placed into this status, either awaiting additional

Policy on stale bugs (was Re: Closing NEEDSINFO bugs after 30 days)

Andrew Crouthamel ha scritto: I've been spending a lot of time browsing, searching, and filtering our bugs in Bugzilla. One of the areas I've found that could use improvement, are the NEEDSINFO bugs. Often, bugs are placed into this status, either awaiting additional information or backtraces,

Re: Improving Bugzilla Status Names

Kai Uwe Broulik ha scritto: Hi, > Here is my follow-up change recommendation based on feedback and research: > > UNCONFIRMED -> REPORTED > WONTFIX -> INTENTIONAL > INVALID -> NOTABUG one issue I'm having with "REPORTED" is that it shows up as "REPO" in the list and can easily be confused

Re: Improving Bugzilla Status Names

Nate Graham ha scritto: On 09/23/2018 03:40 AM, Elvis Angelaccio wrote: On sabato 22 settembre 2018 17:31:31 CEST, Nate Graham wrote: e.g. RESOLVED WONTFIX and RESOLVED INTENTIONAL both mean the same thing ("We won't be implementing this"). I'm not sure how "intentional" mean the same

Re: Call for contributors for Fixture [ Qt5 based raster graphics editor ]

Andy B ha scritto: Can you guys maybe now move this discussion to telegram or phabricator? It seems that there is good debate and good will. I'm not sure why this discussion should be diverted from a mailing list to a messaging system (*) and a planning and development system like

Re: pseudonymous contributions to KDE

Jonathan Riddell ha scritto: On Wed, Sep 19, 2018 at 06:38:15AM -0400, Adriaan de Groot wrote: On Wednesday, September 19, 2018 6:02:22 AM EDT Luigi Toscano wrote: Jonathan Riddell ha scritto: On Tue, Sep 18, 2018 at 07:38:35PM +0200, Jos van den Oever wrote: Can one sign a Fiduciary License

Re: pseudonymous contributions to KDE

Christian Loosli ha scritto: Am Mittwoch, 19. September 2018, 12:02:22 CEST schrieb Luigi Toscano: Same as above on the whole. At least in Scotland there's no restrictions on what name you chose to use for any purpose as long as it's not for fraud. Obviously the harder it is to prove a name

Re: pseudonymous contributions to KDE

Jonathan Riddell ha scritto: On Tue, Sep 18, 2018 at 07:38:35PM +0200, Jos van den Oever wrote: Hi all, What is the KDE policy on accepting code contributions under pseudonym? I've gotten review requests on Rust Qt Binding Generator under a pseudonym. Now I wonder if I can accept the

Re: Closing NEEDSINFO bugs after 30 days

Harald Sitter ha scritto: On Tue, Sep 18, 2018 at 12:59 PM Boudewijn Rempt wrote: Would it also be possible to automatically remove the needinfo status if the reporter adds a comment after it's set to needinfo? Yes. I know that this proposal was rejected in the past, but if the needinfo

Re: Deleting https://userbase.kde.org/Krita/Manual

On Tuesday, 12 June 2018 05:51:08 CEST Yuri Chornoivan wrote: > понеділок, 11 червня 2018 р. 23:00:55 EEST Boudewijn Rempt написано: > > This version of Krita's manual is dead. It's outdated, it's not even > > pushing up the daisies, it's been decomposed too much to aid any daisy in > > its growth

Re: Let's get rid of UNCONFIRMED/CONFIRMED

Adriaan de Groot ha scritto: > On Tuesday, 10 April 2018 19:18:07 CEST, Nate Graham wrote: >> OPEN -> Nobody's looked at it yet >> TRIAGED -> Somebody looked at it but couldn't reproduce it yet >> CONFIRMED -> Somebody looked at it and was able to reproduce it >> > > Is bugzilla really that hard

Re: do you need www.kde.org write access?

Aleix Pol ha scritto: > On Fri, Mar 9, 2018 at 5:57 PM, Ilya Bizyaev wrote: >> On Thu, 08 Mar 2018 11:23:08 +0300 Sebastian Kügler >> wrote >> >> That's part of what we need to review: is the new site missing relevant >> things which need to be

Re: Let's get rid of UNCONFIRMED/CONFIRMED

On Wednesday, 28 February 2018 10:32:58 CET Boudewijn Rempt wrote: > On Wednesday, 28 February 2018 00:14:30 CET Luigi Toscano wrote: > > On bugzilla.redhat.com some teams use the Triaged keyword. I think it > > would > > be a good solution. > > I've been trying tha

Re: FOSDEM retrospective

Nicolás Alvarez ha scritto: > 2018-02-05 20:33 GMT-03:00 Luigi Toscano <luigi.tosc...@tiscali.it>: >> And we can use also phabricator (again, only Akademy): >> https://phabricator.kde.org/calendar/export/3/ > > It says you're the only one with permissions to acces

Re: FOSDEM retrospective

Albert Astals Cid ha scritto: > El dimarts, 6 de febrer de 2018, a les 0:15:21 CET, Lays Rodrigues va > escriure: >> Hello Adriann, thanks for the report! >> We could have a calendar of events where KDE will attend, and work with >> Promo before them to set up material and promo actions. > > We

Re: bugzilla, it's products, how they relate to projects. it's a mess...

On Wednesday, 31 January 2018 16:15:41 CET Boudewijn Rempt wrote: > On Wednesday, 31 January 2018 15:44:01 CET Nate Graham wrote: > > >> As Nate has now attained demigod status with his usability blog posts, > > >> I > > >> think it would be good to take advantage of all the positive attention > >

Re: Splitting Craft, move the recipes to GitHub

On Wednesday, 23 August 2017 15:33:09 CEST Hannah von Reth wrote: > Hi everyone, > > We have been thinking about splitting the Craft recipes into a separate > repository for some time now. > To have a Craft core and the recipes separated would enable us to > provide more stable user experience.

Re: radical proposal: move IRC to Rocket.Chat

While I generally agree with your feeling that the feeling for IRC was a bit negative, I disagree here: Il 10 agosto 2017 22:34:19 EEST, Christian Loosli ha scritto: > >If people want to switch themselves: already possible, with or without >this >thread and the etherpad. >

Re: radical proposal: move IRC to Rocket.Chat

Il 10 agosto 2017 22:22:04 EEST, Thomas Pfeiffer ha scritto: >On Donnerstag, 10. August 2017 20:38:11 CEST Christian Loosli wrote: >> Am Donnerstag, 10. August 2017, 20:31:22 CEST schrieb Thomas >Pfeiffer: >> > On Donnerstag, 10. August 2017 18:40:34 CEST Christian

Re: github, phabricator: a new threadZ

Il 10 agosto 2017 11:45:14 EEST, Harald Sitter ha scritto: >Seems to me y'all aren't appreciating that I am telling you my point >of view. One thing is say "adding an easier workflow for scratch repo to our infra is much required for this and that", which I can agree too;

Re: How about an inclusive "and" approach instead of fighting IRC versus something new? (was: Re: Collecting requirements for a KDE-wide instant messaging solution)

Il 10 agosto 2017 10:24:08 EEST, Martin Steigerwald ha scritto: >Martin Klapetek - 09.08.17, 16:12: >> > But KDE is not a tech startup. As people correctly wrote, KDE has a >very >> > long >> > history and contributors of all age. I'd rather be that than one of >the >> >

Re: github, phabricator: a new threadZ

Il 10 agosto 2017 10:02:43 EEST, Harald Sitter ha scritto: >I for one would pick the alternative which is not using our >infrastructure and instead click two buttons so I don't have to file >paperwork manually nor have to wait for said paperwork to get faxed to >HQ for approval.

Re: radical proposal: move IRC to Rocket.Chat

Il 08 agosto 2017 19:09:28 CEST, Eike Hein <h...@kde.org> ha scritto: > > >On 08/09/2017 01:16 AM, Luigi Toscano wrote:> We have an alternative >already working, which bridges IRC (freenode.net and >> OFTC): matrix.org. >> I don't know how many times I sh

Re: radical proposal: move IRC to Rocket.Chat

On Tuesday, 8 August 2017 17:52:00 CEST Jonathan Riddell wrote: > Like all sensible open source communities we use IRC lots for real > time communication essential to making low bandwidth decisions in a > reasonable timeframe as well as socialising. > > 20 years ago IRC was cool but these days

Re: Retirement of SVN Commitfilter and Legacy Get Hot New Stuff systems

Ben Cooksley ha scritto: > On Sat, Jul 29, 2017 at 11:33 PM, Luigi Toscano > <luigi.tosc...@tiscali.it> wrote: >> Ben Cooksley ha scritto: >> >>> I've checked and it appears that only a small handful of applications >>> still use newstuff.kde.org: >

Re: Retirement of SVN Commitfilter and Legacy Get Hot New Stuff systems

Ben Cooksley ha scritto: > Hi all, > > Last year sysadmin was given access to the system which hosts the SVN > Commitfilter (which lived at commitfilter.kde.org) and the predecessor > to the OCS network of sites (now store.kde.org). > > Earlier this year we started having some issues with that

Re: Applications Lifecycle Policy

On Monday, 17 July 2017 18:01:39 CEST Martin Flöser wrote: > Am 2017-07-17 17:47, schrieb Jonathan Riddell: > > I propose to make this final if there's no further comments. > > as I explained: I think the review process should be removed, playground > should be removed. > > There were both

Re: latest draft for mission (and strategy)

Alexander Neundorf ha scritto: > On 2017 M07 5, Wed 15:05:26 CEST Clemens Toennies wrote: >> On Jul 5, 2017 13:14, "Sebastian Kügler" wrote: >>> Should we make privacy our main focus for the next 5 years? >> >> How about Freedom? > > The "KDE - Digital Freedom" is one of my

Re: Applications Lifecycle Policy

Martin Flöser ha scritto: > Am 2017-07-04 13:20, schrieb Jonathan Riddell: >> The applications lifecycle policy needs an update >> >> Is this a good current state of it or are there more stages? >> > > Hi all, > > I'm now going to propose a rather radical change to the process: > > 1. Remove

Re: Applications Lifecycle Policy

Boudewijn Rempt ha scritto: > On Wed, 5 Jul 2017, Martin Flöser wrote: >> Extragear: to me extragear is a relict from the time of the big one KDE svn >> trunk repository. There was "KDE" and everything else, aka. extragear. When I >> started to compile KDE software it looked to me like something

Re: Applications Lifecycle Policy

Harald Sitter ha scritto: > On Wed, Jul 5, 2017 at 7:01 AM, Christian Mollekopf >>From where I am standing we should have a stage before playground. > Scratch repos if you will (although those are slated for deprecation > without replacement). This addresses the code-dumping github-like use >

Re: Applications Lifecycle Policy

Christian Mollekopf ha scritto: > Overall I just find the cost/benefit factor in the beginning of a > project not at all good when using KDE infrastructure. > I have to request repos and can't just create them, I have to request > tarballs to be uploaded instead of just uploading them, I have to

Re: Applications Lifecycle Policy

Jonathan Riddell ha scritto: > I used the Sanity Checklist I made for the releasing extragear page as > the list of some stuff people will look at in kdereview > https://techbase.kde.org/ReleasingExtragearSoftware#Sanity_Checklist > what else should go in here? It doesn't require docbook docs,

Re: Applications Lifecycle Policy

Christian Mollekopf ha scritto: > > > On Tue, Jul 4, 2017, at 11:16 PM, Luigi Toscano wrote: >> Christian Mollekopf ha scritto: >>> On Tue, Jul 4, 2017, at 01:20 PM, Jonathan Riddell wrote: >>>> The applications lifecycle policy needs an update &g

Re: Applications Lifecycle Policy

Christian Mollekopf ha scritto: > On Tue, Jul 4, 2017, at 01:20 PM, Jonathan Riddell wrote: >> The applications lifecycle policy needs an update >> >> Is this a good current state of it or are there more stages? >> >> https://community.kde.org/Policies/Application_Lifecycle/Draft >> > > Looks

Re: [kde-community] Re: Applications Lifecycle Policy

On Tuesday, 4 July 2017 14:27:07 CEST Jonathan Riddell wrote: > On Tue, Jul 04, 2017 at 02:24:30PM +0200, Luigi Toscano wrote: > > Are we focusing on the graph for now, and then we can move to the content > > of the page, or can we start the general discussion as well? > > G

Re: Applications Lifecycle Policy

On Tuesday, 4 July 2017 13:20:43 CEST Jonathan Riddell wrote: > The applications lifecycle policy needs an update > > Is this a good current state of it or are there more stages? > > https://community.kde.org/Policies/Application_Lifecycle/Draft Are we focusing on the graph for now, and then we

Re: KDE licence policy update

Jonathan Riddell ha scritto: > The main change is for docs and other non-code files to become > CC-BY-SA 4. This allows it to be converted to code (it's one-way > compatible with LGPL 3) Do you have more details for this? I see contradicting information, it does not seem to be totally future

Re: KDE licence policy update

On Friday, 10 February 2017 14:54:52 CET Jonathan Riddell wrote: > I'd like to get back to my proposed update of the KDE licence policy > > https://community.kde.org/Policies/Licensing_Policy/Draft > > I got some comments from Matija Šuklje which I incorporated and it now > includes a handy

Re: Kubuntu and other KDE distribution's use of KDE infrastructure

Adriaan de Groot ha scritto: > I don't think votes are the way to go, really. I'd much rather just get on > with it. For the FreeBSD project on KDE's phab, I didn't even think about it: > I'm a KDE person, I'm interested in delivering KDE software to a particular > group, and I do lots of

Re: Changes to the bugzilla workflow: 2 proposals

On Monday, 12 December 2016 19:34:55 CET Eike Hein wrote: > On 12/12/2016 07:27 PM, Elvis Angelaccio wrote: > > On Sun, Dec 11, 2016 at 10:35 PM, Luigi Toscano > > > > <luigi.tosc...@tiscali.it> wrote: > >> I would introduce an ASSIGNED state

Re: Fwd: Top 15 Mailinglists with messages in moderation

Il 02 dicembre 2016 20:29:17 CET, Aaron Honeycutt ha scritto: >I thought kde-telepathy was to replace kopete? Yes and no. And right now kopete is alive. -- Luigi

Re: Decommisioned from service: quickgit.kde.org

Adriaan de Groot ha scritto: > On Tuesday 15 November 2016 12:24:29 Elvis Angelaccio wrote: >> On Tue, Nov 15, 2016 at 8:22 AM, Ben Cooksley wrote: >>> Hi all, >>> >>> Please note that we've now decommissioned quickgit.kde.org in favour >>> of cgit.kde.org. This change has been

Re: KDE Licensing Policy Updates

On Friday, 23 September 2016 16:46:22 CEST Jonathan Riddell wrote: > On Fri, Sep 23, 2016 at 06:41:57PM +0200, Riccardo Iaconelli wrote: > > Hi all, > > > > On 20 September 2016 at 19:04, Jonathan Riddell wrote: > > > Added: > > > "Content on collaborative edited websites such

Re: Creating a map of KDE contributors?

On Tuesday, 20 September 2016 13:42:35 CEST Thomas Pfeiffer wrote: > Hi everyone, > I recently realized that unless you ask fellow KDE contributors personally > where they live, you don't really know where over the world (or even in > your home country) KDE is spread. > > [...] > > So, two

Re: [kde-community] KDE Sysadmin and GPG Encryption

On Tuesday, 26 July 2016 19:25:25 CEST Boudhayan Gupta wrote: > 2) GPG doesn't simply encrypt the email, but also digitally signs it. > Signatures are required to prove the authenticity of the email, and to > detect if it was tampered with. However, given our email > infrastructure, a GPG

Re: [kde-community] Our new project metadata system

On Thursday 31 of March 2016 14:29:19 Jaroslaw Staniek wrote: > On 31 March 2016 at 14:18, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: > > On Thursday 31 of March 2016 17:23:37 Boudhayan Gupta wrote: > > > On 31 March 2016 at 17:13, Luigi Toscano <luigi.tosc...

Re: [kde-community] Our new project metadata system

On Thursday 31 of March 2016 17:23:37 Boudhayan Gupta wrote: > On 31 March 2016 at 17:13, Luigi Toscano <luigi.tosc...@tiscali.it> wrote: > > Wait, no. The metadata there are outdated, the ones in project > > repositories > > have been updated _and_ translated in the mea

Re: [kde-community] Our new project metadata system

On Thursday 31 of March 2016 12:31:39 Olivier Churlaud wrote: > Le 31/03/2016 12:07, kde-community-requ...@kde.org a écrit : > > Message: 8 > > Date: Thu, 31 Mar 2016 12:06:50 +0200 > > From: Luigi Toscano<luigi.tosc...@tiscali.it> > > To:kde-community@kde.

Re: [kde-community] What is a GitHub pull request exactly?

Riccardo Iaconelli ha scritto: > On Sunday, September 20, 2015 12:26:41 PM Sune Vuorela wrote: >> Free software needs free tools. > > I am sorry, but sadly this is not the state of the art. KDE has been created > with many non free tools and currently co-exists in many non-free > environments.

Re: [kde-community] Official KDE mirror on github

Il 19 settembre 2015 12:00:11 CEST, Vishesh Handa ha scritto: > On Sat, Sep 19, 2015 at 11:44 AM, Luca Beltrame > wrote: > > > > And besides... hasn't the BitKeeper story taught us *anything*? > > > > I don't know about you guys, but it has taught me that we

Re: [kde-community] Official KDE mirror on github

Kevin Krammer ha scritto: > On Saturday, 2015-09-19, 12:29:31, Vishesh Handa wrote: >> On Sat, Sep 19, 2015 at 12:09 PM, Ivan Čukić wrote: >>> alternatives. Just as they do not have access to my personal inbox >>> where much corresponse often happens, and patches are

Re: [kde-community] Kdetoys

Jeremy Whiting ha scritto: Hello all, tldr, should we kill kdetoys? As Applications 15.08 has been released I thought I'd take a look at which of our applications still need to be ported to Qt5/kf5. I did a diff of what we released in the 15.08 release vs what is already kf5 based and

Re: [kde-community] Renaming KScreenGenie

Jaroslaw Staniek ha scritto: On 24 August 2015 at 15:53, Martin Klapetek martin.klape...@gmail.com wrote: On Mon, Aug 24, 2015 at 9:24 AM, Boudhayan Gupta bgu...@kde.org wrote: On 24 August 2015 at 18:45, Martin Klapetek martin.klape...@gmail.com wrote: KSnapshot2. One of the points

Re: [kde-community] Renaming KScreenGenie

Ivan Čukić ha scritto: +1 for snapshot It is a part of Plasma workspace (and possibly other friendly workspaces), so I don't even see it as a problem if other applications with the same name exist (the only thing I've checked is that debian has no package named 'snapshot'). It's not part

Re: [kde-community] Updating TechBase Getting_Started pages

On Monday 17 of August 2015 09:53:58 John Layt wrote: My aim is to teach the one simplest quickest way to build KF5 for new KDE contributors. There's a few key concepts I want this rewrite to follow: 1) There is only one way to do things, no giving alternatives 2) There is only KF5, no KDE4

Re: [kde-community] Work on Krusader new release

On Wednesday 24 of June 2015 11:17:46 Laszlo Papp wrote: On Wed, Jun 24, 2015 at 11:06 AM, Luigi Toscano luigi.tosc...@tiscali.it So if you want to help us, please join krusader-de...@googlegroups.com mailing list and send your proposals. (and move the site too Why move the site

Re: [kde-community] retiring unmaintained modules?

Myriam Schweingruber ha scritto: Last time I was trying to close the kmail 1 bugs as unmaintained, asking people to reopen if it stilkl applies to kmail2 I was shouted at and told that somebody has to check if that still applies to Kmail2 before closing, go figure! I just fear that with 880

Re: [kde-community] retiring unmaintained modules?

Boudewijn Rempt ha scritto: I guess we should also be really careful, as you said some software is done and the fact that it didn't get any development doesn't mean it should be killed. Of course. But kmail (not kmail2) is _dead_. It's bugs should be closed. I would ask Laurent first. He

Re: [kde-community] Proposal One: KDE (Core) Apps and Suites

On Friday 02 of May 2014 19:53:47 Jos Poortvliet wrote: * we know there's a release every month. That might seem more often than now, but honestly - we DO have releases *multiple times* per month already. Not at the same rate as it will go, I think: one thing is to release (these days)

Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

Adriaan de Groot wrote: Note also that we *have* some kinds of metapackages already defined. Thery're on our website, at http://www.kde.org/applications/ . You'll note that the list of applications in graphics doesn't coincide with the repositories, and does include digiKam, because

Re: [kde-community] Applications in KDE Generation 5

John Layt wrote: One other thing I would do is change our app lifecycle slightly. I'd introduce a new status of Deprecated that lies between Released and Unmaintained, for apps like Kopete and KPPP that are no longer relevant for most people or are being replaced, but may still have limited