I had a poke round.
There's a new section on the show_bug page between the status summary and
the attachments list, which shows a time tracker where you say how long a
job should take/is taking.
I don't think this makes any sense outside a coroporate environment, so we
should turn this off.
It's
On Sun, Dec 11, 2016 at 9:35 PM, Luigi Toscano
wrote:
> Hi,
>
> I would like to propose two changes to the Bugzilla workflow for our
> instance
> on bugs.kde.org. The two proposals are totally independent from each
> other.
>
> a) use the "needinfo" flag instead of the NEEDINFO status.
>
> This i
> 2. Remove playground
>
Lots of projects get started and die.
I think it's important to have some flag (however you want to call it) that
says; CI admins, translators and even packagers should not bother looking
at this project yet. Otherwise we waste a lot of people's time.
The review process
>We should probably also ask the sysadmin team whether they would be
willing to maintain our own chat server.
That's "maintain a third chat server".
They maintain both kdetalk (jabber) and Conpherence (phabricator) already.
David
If there's sitll space, I'm happy to come help out.
David
I can be there and help run a booth.
I'll take leftover flyers from QtWs.
David
>Can we ship it on KDE's file server
I would strongly say no.
Partly because of the legalities of that code, but also because unless you
want to allow everyone to do device specific Neon customisations upstream
in Neon, Neon itself shouldn't be doing any.
David
On Fri, Jan 19, 2018 at 9:42 AM, Marco Martin wrote:
> On Mon, Jan 15, 2018 at 8:15 PM, Nate Graham
> wrote:
> > I've submitted an idea for System Settings: Improve handling for
> touchpads
> > and mice with Libinput
>
> Speaking of systemsettings, would be a good fit porting to qml some
> mediu
On Fri, Jan 19, 2018 at 4:41 PM, Marco Martin wrote:
> On venerdì 19 gennaio 2018 13:42:25 CET David Edmundson wrote:
> > Note that they'll be finishing GSOC around the same time as 5.14, so that
> > potentially means GSOC work released in 5.15.
> > We shouldn't
For existing stuff there's a problem that bugzilla names are hardcoded into
apps.
There's kdepackages.h in frameworks that provides a list of all products so
that help->report bug works
and there's data that drkonqi uses. All done by string not product ID.
Renaming any referenced here is we can't
I've started a wiki page, please add yourself when you know you're coming.
https://community.kde.org/Sprints/Plasma/2018
This is in addition to the reimbursments page if needed.
I'm thinking given there's so many cheap hostels in Berlin we could book a
couple of big dorm rooms together if we have
We have a thread where someone proposes removing statuses, and a proposal
which involves adding a status :/
That doesn't sound like we're unified on what we need at all.
Personally I would use flags for this "reproducible" or not.
Advantages are:
- it visibly lists who could reproduce it in a w
> So that's a no then. Tell these higher-ups that partial blocking of a
> proven contributor from completing a specific task when they have 15
> years of track record is demotivating and not how things should be
> done in KDE.
>
Peer review is exactly how things should be done in KDE.
I don't un
> Maybe someone can edit the wik page and remove my name.
Done
David
It's not a mistake. From the thread where permissions are relaxed:
>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
For a user user the bug that affects them is a
New/confirmed are more about before/after triage than focussing on
reproducible or not.
Reproducible or not isn't really a particularly useful thing to know from a
dev side. I regularly fix things I can't immediately reproduce. If we want
that information a flag solves it better.
What's important
> One of the areas I've found that could use improvement
IMHO it's really not a huge problem*.
If a reporter doesn't answer back, then they clearly don't care.
If its marked as needsinfo it's not in my lists, it doesn't affect me as a
dev in the slightest. They're filtered out by default, I have
>I'm also wondering whether other KDE projects have the
seem need as we have for Krita,
With my Plasma hat on:
Surprisingly, we don't get too many end user questions on bugzilla. I think
it tends to get loaded onto the distros instead.
We do get quite a few where the user thinks they have a bug
There are legal implications as the copyright is ultimately held by real people.
Right now the linux kernel does not accept anonymous or pseudonyms for
that reason.
There was a thread a while back, it needs a real free software lawyer
to give an answer.
David
We would need to ask a lawyer.
I only know enough to know that I don't know enough.
>
> Plasma Mobile projects are not included in bugzilla. So, gitlab issues
> is the only "decent" alternative for bug tracking. If we disable
> issues, then the only alternative I see is to report issues to
> Phabricator, which, from my point of view, should be avoided.
>
Things can be added to bug
For EBN, personally I don't find myself using it. I think clang / llvm
warnings / new Qt warnings cover a large part of the source code
section.
I've made a task listing everything EBN currently checks. Then
together can mark off what things have other replacement, and what
remaining things are ac
Let's avoid taking the politics to the mailing list as well please,
that's even worse.
David
>From that website, one thing I'd like to make clear (and I don't know
how) is the different target audience/state of completion for plasma
vs plasma mobile.
Plasma is a ready-to-use user facing product that unskilled people can
"just use"
Plasma mobile is still aimed at the developers stage.
I f
As a general rule, brand new programs do not make for good GSOCs.
They stall after GSOC ends, and students don't get the real-world
experience of working in a team on a project.
I would also recommend being more conservative with your goals, so
that any pending mentors see them as realistic. A ga
On Sun, Jul 12, 2020 at 11:14 AM sabayon11 wrote:
> I have a question:
> Is it legal for reddit moderators of r_KDE to use KDE logo in LGBT
> colors. Is it consistent with logo license?
>
Like KDE itself, Oxygen Icons have a liberal copying policy. Anyone may,
and is encouraged to, use Oxygen Ic
> - discover
> - plasma (including plasmashell, systemsettings)
Plasma has always had public review at every single step from at least
two reviewers.
David
https://phabricator.kde.org/D24011
https://phabricator.kde.org/D5961
> - The telemetry policy says: « applications honor system-wide telemetry
> settings where they exist (global "kill switch") »
>
> Is it documented? How can a system administrator prevent users from turning
> telemetry on?
>
```
/etc/xdg/KDE/UserFeedback.conf
[UserFeedback]
Enabled=false
```
Docu
That subject title is misleading.
>From a user point of view, there will be no impact.
David
> Recently I made a minimum viable patch for the KDE Gear release tooling to
> bump up the version numbers where those apps have snapcraft packaging files.
> However I've been told I shouldn't "overstate the nature of the goal" with an
> objection to integrating the packaging into the app repos
>The reason for this change was to stop users with excessive ego from marking
>their own tickets and tickets they care deeply about as having the "critical"
>Severity level.
So what will we do to avoid getting this situation back?
I don't care if a user changes it once, but users who constantly
>
> I might recommend taking those on a case-by-case basis, by removing
> severity-modification privileges for just the problematic users who
> abuse the system.
If we have the ability to do that, then I have no objections.
David
>
>
> P.S: This is all David Edmundson's fault/responsibility I'm just the
> messenger
>
Which means I should volunteer to organise something in England. Probably
Cambridge.
If anyone has thoughts or wants to help on that feel free give me a shout.
I will be organising a party in the UK in Cambridge.
Details (or lack thereof) are on the wiki. Please let me know if
you're interested.
David
>> in that event I'd like for us to put it
>> to a formal KDE e.V. vote
> Is this an eV topic?
Yes and no.
The original decision had a big impact, changing things again will
have a big impact. It's not something that should be decided by a few
people, nor is it something that should be decided
> As a result I'll rescind my idea to slow down Frameworks feature
> releases.
Then I'll take over and fight for it!
>that having a fast Frameworks release cycle allows
> people developing apps with features in Frameworks to not have to live
> on master like we do in Plasma.
That was the motivat
There is a BOF session booked on the Monday to get some defined
actions on how we move forward with this.
David
I don't understand the purpose of this email.
It is not the job of the KDE community to attempt to bash Canonical at
every turn.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
I was directing my question to Jos, not Albert.
On Thu, Aug 15, 2013 at 2:39 PM, David Edmundson wrote:
> I don't understand the purpose of this email.
>
> It is not the job of the KDE community to attempt to bash Canonical at
> every turn.
>
___
As a KBibTex user I would happily welcome this.
I imagine you'll be aiming to be in extragear, so unfortunately you're
still on your own for release cycles - but there are some utilities
that will make your life easier.
Before we continue, can I ask you to go through the KDE manifest and
check th
There's a change from
"_can_ be defended via the FLA"
to
"_will_ be protected defended via the FLA"
(emphasis added by me)
As I understand it the FLA is opt in (http://ev.kde.org/rules/fla.php)
and does not automatically cover all projects.
David
___
Given my project is explicitly mentioned, I should reply :)
When KTp was moving out of playground, I was told:
"It can't go into the SC because Kopete is there and we have a duty to
maintain that as the official client for all of 4.x"
I don't know if that is true or not, it may have been a commun
I think this makes a lot sense and I would welcome QtCurve into KDE.
Can you read though http://manifesto.kde.org/ and confirm you would
agree to all the commitments
(http://manifesto.kde.org/commitments.html) of a KDE project.
David
___
kde-community m
Brilliant.
So the next page to read is
http://techbase.kde.org/Policies/Application_Lifecycle. It explains
the entrance process and the SC vs extragear.
In short we leave this thread for a few days for anyone else to make
positive or negative comments about the software entering KDE. Then if
ever
> kde-telepathy team. Working tirelessly to bring us a nice chatting experience.
Thanks :)
My personal hero of the year is Diane Trout. We have had broken video
calls for ages because we don't have Qt bindings for GStreamer 1.0,
only the older version. People would always ask us, and I would alwa
On Wed, Feb 19, 2014 at 9:18 PM, Thomas Zander wrote:
> On Wednesday 19. February 2014 12.58.57 Agustin benito bethencourt wrote:
>> I must confess though that I am worry about the association between:
>> * proprietary platforms = commercial
>> * free platforms = non commercial
>>
>> that might be
AFAIK QTox doesn't have group video just 1-1.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
>
>
> Simple "Make the world better - link". Bugzilla mails always have at least
> 2 lines footer anyway, like
>
> Better yet, only include it when it changes to RESOLVED - FIXED :D
I liked my own idea so much I wanted to see how easy it would be.
Should be just changing newchangedmail.txt.tmpl to
On Thu, Oct 23, 2014 at 7:19 AM, Martin Gräßlin wrote:
> On Thursday 23 October 2014 00:27:29 David Edmundson wrote:
> > > Simple "Make the world better - link". Bugzilla mails always have at
> least
> > > 2 lines footer anyway, like
> > >
> >
On Fri, Dec 19, 2014 at 11:08 AM, Lydia Pintscher wrote:
>
> Hey folks :)
>
> 2014 is coming to an end. This gives us some time for reflection. What
> are your KDE highlights of 2014? A team that kicked ass? A really good
> release? An event where you made great new friends? Something entirely
> d
On Sat, Dec 20, 2014 at 10:11 PM, Ben Cooksley wrote:
> On Sun, Dec 21, 2014 at 4:54 AM, Albert Astals Cid wrote:
> > El Dissabte, 20 de desembre de 2014, a les 22:19:35, Ben Cooksley va
> escriure:
> >> On Sat, Dec 20, 2014 at 8:54 PM, Valorie Zimmerman
> >>
> >> wrote:
> >> > On Fri, Dec 19,
On 23 Dec 2014 20:19, "Jonathan Riddell" wrote:
>
>
> I moved to Barcelona so I could spend my days in the KDE office here
*blue systems office
>
> Jonathan
> ___
> kde-community mailing list
> kde-community@kde.org
> https://mail.kde.org/mailman/listi
On Tue, Dec 23, 2014 at 11:39 PM, Aaron J. Seigo wrote:
> On Tuesday, December 23, 2014 20.31:55 Jonathan Riddell wrote:
> > Sign on the door says KDE
>
> Does it say "Blue Systems" on the door, or just "KDE"?
>
It says "1a" in large silver letters. We then added a gratuitous amount of
stickers.
I intend to close all systemsettings->kcm_randr
It's obsoleted in the last cycles of 4.x by kscreen and completely dropped
in Plasma 5. They're of no use to anyone now.
David
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mai
On Tue, Apr 21, 2015 at 10:11 AM, Boudhayan Gupta
wrote:
> Hi Aaron,
>
> KScreenGenie actually works now, for daily use purposes (it probably
> has a few bugs, but I'm handling them as reports come in), so I
> thought I'd pop over to the KDE forums and make a request for a new
> icon so that I co
On Mon, Aug 17, 2015 at 9:53 AM, John Layt wrote:
> Hi,
>
> I've started to update the old TechBase Getting_Started pages for the
> new KF5 world [1].
>
> 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
>
On Thu, Aug 27, 2015 at 3:43 PM, Sebastian Kügler wrote:
> On Wednesday, August 26, 2015 20:57:25 Jaroslaw Staniek wrote:
> > +1
> > (I am using it as if it was official)
>
> Same here. The Plasma team is in the process of migrating to
> phaaab!
> already.
>
To clarify, the mobile only s
> that we'll be moving forward with Phabricator
Can we confirm what parts we're moving forwards with right now
i.e out of projects.kde.org reviewboard, bugzilla, etc.
>Because a number of policy matters need to be decided, it would be
nice if a small group of people would work with sysadmin to
I'm on it.
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
I am great.
https://github.com/kde is now ours.
David
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
On Thu, Sep 17, 2015 at 10:03 AM, Ben Cooksley wrote:
> On Thu, Sep 17, 2015 at 12:57 AM, David Edmundson
> wrote:
> > I am great.
> >
> > https://github.com/kde is now ours.
>
> Well done, that was quick. Anyone volunteers to write the script which
> mirr
On Thu, Sep 17, 2015 at 1:12 PM, Patrick von Reth wrote:
> Hm I have an existing github mirror with some stars. Instead of
> creating a new mirror I'd prefer to just set KDE to the new owner of
> the Project.
> I guess this is not the only project where that kind of migration is
> preferable.
> S
On Fri, Sep 18, 2015 at 1:41 PM, Martin Graesslin
wrote:
> On Friday, September 18, 2015 2:14:00 PM CEST Jaroslaw Staniek wrote:
> > On 18 September 2015 at 14:00, Ben Cooksley wrote:
> > > On Fri, Sep 18, 2015 at 11:54 PM, Jaroslaw Staniek
> wrote:
> > >> On 18 September 2015 at 13:42, Boudhay
On Fri, Sep 18, 2015 at 9:10 PM, Friedrich W. H. Kossebau
wrote:
> Hi,
>
> Am Freitag, 18. September 2015, 17:12:12 schrieb Boudhayan Gupta:
> > Ladies and gentlemen, as you read this mail github.com/kde is being
> > populated by the initial sync of all repositories.
>
> Pardon for the late input
> >
> > I was under the impression they were disabled by the options we had
> > selected. Unfortunately that is not the case.
>
> Thanks for clarifying on this.
>
> I hope they can still be disabled.
>
> They can't. I had spent some time looking before. Sorry.
However, we have solid hard data that
On Sun, Sep 20, 2015 at 3:56 PM, Martin Klapetek
wrote:
> On Sun, Sep 20, 2015 at 10:53 AM, Bhushan Shah wrote:
>
>> On Sun, Sep 20, 2015 at 8:20 PM, Martin Klapetek
>> wrote:
>> >
>> > Gnome in their years history of github mirroring had 4 pull requests
>> > (it was mentioned in the other thre
I have two main questions. I'll make them as new threads.
KDE as a community currently has a clear unique selling point for new
projects; Qt libraries, Qt expertise, and connections. A common thread that
makes it worth being a community. We've seen this work in the past with
existing Qt projects l
On Thu, Apr 14, 2016 at 2:16 PM, Jonathan Riddell wrote:
> A while ago Albert gave a talk at Akademy about collecting some data
> on our users. This got me thinking and with Neon I wanted to see how
> many installs we had. Our package install software will check for new
> versions being availab
68 matches
Mail list logo
