[kde-community] Discussion: KDE Manifesto, established practices

Hello, In the principles, section of the manifesto we have the following point: The project stays true to established practices common to similar KDE projects unless special considerations force it to deviate. I guess after lengthy discussions you end up with points like that which says...

Re: [kde-community] Proposal: KDE Manifesto wording revision

On Sunday 10 November 2013 19:03:45 David Edmundson wrote: 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

Re: [kde-community] Discussion: KDE Manifesto, web services

On Monday 11 November 2013 10:44:35 Aaron J. Seigo wrote: On Sunday, November 10, 2013 19:12:29 Kevin Ottens wrote: Projects that do not use KDE infrastructure for their online services must work with the KDE sysadmin team on an agreement to ensure continuity. Perhaps it could be stated

Re: [kde-community] Discussion: KDE Manifesto, established practices

On Sunday 10 November 2013 16:47:43 Carl Symons wrote: The project stays true to established practices common to similar KDE projects. Could be a solution indeed. Anybody against it apart from Peter?[*] Cheers. [*] @Peter, I read your points. I understand the worries and I think they got

Re: [kde-community] Proposal: KDE Manifesto wording revision

On Tuesday 12 November 2013 17:51:36 Eike Hein wrote: On Tuesday 12 November 2013 17:33:08 Aaron J. Seigo wrote: if that is not clear (and apparently it is not .. you aren’t the first to suggest this) then perhaps we need a phrase other than “project assets” or some clarification of it. I

Re: [kde-community] Discussion: KDE Manifesto, established practices

On Tuesday 12 November 2013 18:38:24 Myriam Schweingruber wrote: Hi all, Sorry to top-post, but this is getting wordier and wordier and I have long lost trace of what is said. Could we have a tl::dr wrap-up, please? On Tue, Nov 12, 2013 at 2:54 PM, Aaron J. Seigo ase...@kde.org wrote: On

Re: [kde-community] Proposal: KDE Manifesto wording revision

Hello, On Sunday 10 November 2013 21:46:41 Ingo Klöcker wrote: On Sunday 10 November 2013 18:28:58 Kevin Ottens wrote: That's what this email is about, I'd like to apply the attached patch, it's mostly about small scale changes. I don't see anything which could be controversial

Re: [kde-community] Discussion: KDE Manifesto, established practices

On Tuesday 12 November 2013 21:45:40 Peter Grasch wrote: On 11/12/2013 06:35 PM, Aaron J. Seigo wrote: which established practices did Necessitas not follow? I would argue that Use kdelibs would be an established practice in KDE but I recognize that there was/is some disagreement as to what

Re: [kde-community] Proposal: KDE Manifesto wording revision

On Wednesday 13 November 2013 18:44:45 Eike Hein wrote: On Tuesday 12 November 2013 23:22:59 Thomas Pfeiffer wrote: To me, source materials means anything that cannot be produced automatically from the other source materials. I'd assume that when in doubt whether they should put something

Re: [kde-community] KDE Manifesto Revision (round 2)

On Friday 22 November 2013 09:33:07 Carl Symons wrote: It's correct to have both to and by prepositions in the sentence as it's written. However, I seems to me that Kévin's question is not about grammar, but about the implications of the adjectives available and writable in the same

Re: [kde-community] KDE Manifesto Revision (round 2)

On Monday 25 November 2013 07:47:14 Mirko Boehm wrote: On 24 Nov 2013, at 11:17, Marta Rybczynska rybczyn...@gmail.com wrote: Just a doubt about two lines: Licensing policy must be respected. branding guidelines are respected. +1. Unified to are since the tendency is to use active forms

[kde-community] The KDE Incubator needs YOU

Hello community, This year during Akademy I announced the idea to create an incubator for projects joining our community. We also had a BoF on the topic to collect opinions and ideas from people. Now fast forward a couple of months, some work has been done toward putting such an incubator

Re: [kde-community] Incubating project

Hello, On Monday 30 December 2013 13:37:43 Jeremy Whiting wrote: I'm pleased to announce the KDE Incubator is incubating a project WikiFM as described here: http://community.kde.org/Incubator/Projects/WikiFM . Though the incubation process is still a work in progress we thought we'd kick

[kde-community] Manifesto update applied

Hello community, Since the vote to update the manifesto passed, I committed the changes today. The new version is now online. Thanks everyone involved for your input! Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com signature.asc

Re: [kde-community] Plasmoids and Apps - was - Re: Applications in KDE Generation 5

On Thursday 16 January 2014 14:48:22 Martin Graesslin wrote: On Thursday 16 January 2014 13:24:51 Aaron J. Seigo wrote: Martin Graesslin wrote: 'We all know Albert and we all know that his writing reads more harsh than he intents to.’ IOW: it’s OK for Albert, because we all know he’s gruff

Re: [kde-community] Request to join the Kde incubator for GCompris

Hello, On Thursday 13 February 2014 04:48:00 Bruno Coudoin wrote: [...] So this is a brain new project with just a demonstrator of only 4 activities on 140. I think it is a good time frame for GCompris to join the Kde community for different reasons: [...] I hope my request did raise your

Re: [kde-community] SCRUM in KDE

Hello, On Monday 03 March 2014 18:56:43 Ivan Čukić wrote: Hi dude, Not sure whether this is the topic for kde-community, but here it goes... :) for this years Open Academy project, we have decided to use SCRUM. I have looked at tools that could help us implement the various practices

Re: [kde-community] Closing the kde-core-devel mailing list

Hello, On Monday 04 August 2014 20:36:44 Vishesh Handa wrote: Random Idea: Heh, someone with too much time at hand? :-) Note that I generally find that fiddling with lists is generally generating quite some boring work across the board. How about we close the k-c-d mailing list? I think

Re: [kde-community] Closing the kde-core-devel mailing list

On Tuesday 26 August 2014 17:17:43 Kevin Krammer wrote: On Tuesday, 2014-08-26, 16:15:56, Aaron J. Seigo wrote: Stuff means more than code. A best practice is shared stuff; a community-wide policy is shared stuff. The difference between having an agreed upon best practice or policy and a

Re: [kde-community] Official KDE mirror on github in the light of the KDE manifesto

On Sunday 27 September 2015 08:25:49 Ben Cooksley wrote: > On Sat, Sep 26, 2015 at 9:33 AM, Albert Astals Cid wrote: > > El Divendres, 25 de setembre de 2015, a les 13:16:46, Jaroslaw Staniek va > > > e.g. Gitlab? > > > > AFAIR last time we tried gitlab it crawled under "KDE size"

Re: [kde-community] finding a clear vision for KDE - first draft for discussion

Hello, Sorry, but there was a bait I couldn't resist here. :-) On Tuesday, 9 February 2016 11:55:35 CET Marco Martin wrote: > * "makes simple things easy" not sure about that, aren't simple things > already supposed to be easy? :p (makes doing things easy?) In fact not, simple things can be

Re: KDE End of Year 2016 Fundraising

Hello, On Saturday, 3 December 2016 00:31:43 CET Heiko Tietze wrote: > On 12/02/2016 11:21 PM, Albert Astals Cid wrote: > > El dimecres, 30 de novembre de 2016, a les 9:54:18 CET, Heiko Tietze va > > > > escriure: > >> Would be good not have alternatives to Paypal, like gittip or bitcoins. > >

Re: Proposal: Have the Community Set Ambitious Goals for Itself

Hello, On Monday, 31 July 2017 16:20:11 CEST Lydia Pintscher wrote: > Thanks everyone who worked on putting this together at Akademy. I > believe this is a way that can work well for us as a community. > > So one of the things we still need to iron out is the timeline. Here > is a straw man

Re: latest draft for mission (and strategy)

Hello, On Friday, 7 July 2017 23:16:32 CEST Alexander Neundorf wrote: > On 2017 M07 7, Fri 07:21:32 CEST Kevin Ottens wrote: > > > How about collecting ideas for that ? > > > We have already 5. > > > > 5? I missed a couple I guess. I spotted only &

Proposal: Have the Community Set Ambitious Goals for Itself

Dear Community, Based on the mission and strategy discussions on this list and during Akademy, some of the Akademy attendees had a BoF where they discussed topics like direction, cohesion, creativity, and ambition. The outcome of that discussion is that we would like to suggest a bottom-up

Re: latest draft for mission (and strategy)

Hello, On Monday, 29 May 2017 21:17:29 CEST Lydia Pintscher wrote: > [...] > I'd like to invite you all to take a look at the current draft and > provide your constructive feedback so we can use this as the basis for > our work for the next years. > > https://community.kde.org/KDE/Mission Took

Re: Applications Lifecycle Policy

Hello, 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 Didn't we have cases of applications

Re: latest draft for mission (and strategy)

Hello, On Tuesday, 4 July 2017 23:20:18 CEST Christian Mollekopf wrote: > On Sun, Jul 2, 2017, at 03:43 AM, Kevin Ottens wrote: > > I hope for another fate. Because of that, I don't think this is a proper > > conclusion to the Evolving KDE effort or a proper answer to Paul's tal

Re: latest draft for mission (and strategy)

Hello, On Tuesday, 4 July 2017 22:28:24 CEST Alexander Neundorf wrote: > On 2017 M07 2, Sun 03:43:57 CEST Kevin Ottens wrote: > ... > > > In my opinion our answer to "where we want to go" was supposed to be > > something else than "nowhere in particular&q

Re: latest draft for mission (and strategy)

Hello, On Sunday, 2 July 2017 20:06:41 CEST Sebastian Kügler wrote: > On zondag 2 juli 2017 03:43:57 CEST Kevin Ottens wrote: > > In my opinion our answer to "where we want to go" was supposed to be > > something else than "nowhere in particular". Then I

Re: latest draft for mission (and strategy)

Hello, On Wednesday, 5 July 2017 13:14:19 CEST Sebastian Kügler wrote: > On woensdag 5 juli 2017 12:17:10 CEST Kevin Ottens wrote: > > IOW, knowing the organization as a whole decided on some sort of direction > > at least for a while would prompt me into looking beyond my usual c

Re: latest draft for mission (and strategy)

On Wednesday, 5 July 2017 23:12:38 CEST Alexander Neundorf wrote: > On 2017 M07 5, Wed 12:17:10 CEST Kevin Ottens wrote: > > Hello, > > > > On Tuesday, 4 July 2017 22:28:24 CEST Alexander Neundorf wrote: > > > On 2017 M07 2, Sun 03:43:57 CEST Kevin Ottens wrote:

Re: Applications Lifecycle Policy

Hello, I don't want to dive too much in this particular thread. A couple of things I'd like to bring though. I won't quote what I agree with but just what worries me a bit. On Wednesday, 5 July 2017 21:37:09 CEST Martin Flöser wrote: > [...] > With extragear gone I don't really see the need of

Re: latest draft for mission (and strategy)

Hello, On Thursday, 6 July 2017 01:19:00 CEST Clemens Toennies wrote: > More like "Practical Freedom"? > The KDE community imo shouldnt be about "technicalities", thats up to > how each project tries to contribute or work towards that ultimate goal > that is freedom. > Wiki2Learn for example

Re: latest draft for mission (and strategy)

Hello, On Wednesday, 5 July 2017 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? > Fits "KDE - be free". > There is also no freedom without privacy. Way

Re: latest draft for mission (and strategy)

Hello, On Thursday, 6 July 2017 21:27:52 CEST Clemens Toennies wrote: > Am 06.07.2017 um 07:30 schrieb Kevin Ottens: > > Hello, > > On Thursday, 6 July 2017 01:19:00 CEST Clemens Toennies wrote: > > >> > More like "Practical Freedom"? >> The KDE com

Re: latest draft for mission (and strategy)

Hello, On Thursday, 6 July 2017 21:27:45 CEST Alexander Neundorf wrote: > On 2017 M07 6, Thu 07:29:39 CEST Kevin Ottens wrote: > > On Wednesday, 5 July 2017 23:12:38 CEST Alexander Neundorf wrote: > ... > > > > Except that I don't think "Open Data" should reall

Re: Proposal: Have the Community Set Ambitious Goals for Itself

Hello, On Wednesday, 16 August 2017 12:38:17 CEST Sebastian Kügler wrote: > On dinsdag 15 augustus 2017 00:47:15 CEST Lydia Pintscher wrote: > > If I get at least two people to agree in this thread that they will > > submit a goal I commit to making the process work according to the > > proposed

Re: Invent/gitlab, issues and bugzilla

w), I have to agree with > that. Count me on that particular group. It's just not the same volumes between project tasks and bugs. Besides I agree with Boud that it's good for the developers to have a space undisturbed from the support hotline. It's fine for tasks in gitlab/phab to refer bugs in b

Re: Invent/gitlab, issues and bugzilla

mines on such a topic in the coming weeks. I "just" need to manage to resurface. Regards. -- Kevin Ottens, http://ervin.ipsquad.net signature.asc Description: This is a digitally signed message part.

Re: List of available sprint venues for 2020 and beyond

orting would be very welcome. Regards. -- Kevin Ottens, http://ervin.ipsquad.net enioka Haute Couture - proud patron of KDE, https://hc.enioka.com/en signature.asc Description: This is a digitally signed message part.

Re: Showing respect (was: Re: The KDEPIM / Akonadi situation)

cussion topics for the past few KDEPIM sprints. And also during BoFs at Akademy. I even think there's been discussions about that on the pim list and IRC channels. Regards. -- Kevin Ottens, http://ervin.ipsquad.net signature.asc Description: This is a digitally signed message part.

Re: Showing respect (was: Re: The KDEPIM / Akonadi situation)

Hello, On Friday, 12 June 2020 20:47:55 CEST Carl Schwan wrote: > Le vendredi, juin 12, 2020 1:45 PM, Kevin Ottens a écrit : > > Incidentally it's been the top discussion topics for the past few KDEPIM > > sprints. And also during BoFs at Akademy. I even think there's been > &

Re: Proposal unify back our release schedules

someone who didn't reply to this thread and have no strong opinion about the topic: keep monitoring that thread and maybe evaluate volunteering to facilitate if we start throwing mud at each other. ;-) Regards. -- Kevin Ottens, http://ervin.ipsquad.net enioka Haute Couture - proud supporting memb

Re: Proposal unify back our release schedules

ange" loop). > > * "KDE Framework" will still exists as an entity and its ABI and API > > > > compatibility requirement. Only change is the release frequency and the > > > > introduction of a stable branch in sync with the other components. > > That part I'm against for the above mentioned reasons, KF's release > frequency is a major feature of it. Regards. -- Kevin Ottens, http://ervin.ipsquad.net enioka Haute Couture - proud supporting member of KDE https://hc.enioka.com/en signature.asc Description: This is a digitally signed message part.

Re: Proposal unify back our release schedules

Hello, On Saturday 20 April 2024 15:12:48 CEST Ingo Klöcker wrote: > On Freitag, 19. April 2024 22:40:38 CEST Ben Cooksley wrote: > > On Sat, Apr 20, 2024 at 4:39 AM Kevin Ottens wrote: > > > The example you give shows Plasma depending on Gear, this shouldn't > > >

Re: Proposal unify back our release schedules

Hello, On Monday 22 April 2024 18:08:04 CEST Carl Schwan wrote: > On Friday, April 19, 2024 6:39:01 PM GMT+2 Kevin Ottens wrote: > > Unsurprisingly I'll be pretty much aligned with Luigi, Sune and Volker > > here I think. I'll try to add a couple of extra aspects to feed t

Re: Proposal unify back our release schedules

econd because these was already used in the past. Sure, why not. This is not engineering I'm less opinionated about it. Apart from decoupling more between engineering effort and marketing announcements that is. Maybe reconsider the "Megarelease" term though... I've literally been laughed