Re: Proposal unify back our release schedules

2024-04-19 Thread Kevin Ottens
Only have one release announcement on our website. We can call it > Megarelease 6.XX like we did for Plasma 6/Gear 24.02 or find a better name. > I would avoid reusing Software Collection first because the name is quite > technical and second because these was already used in the pas

Re: Proposal unify back our release schedules

2024-04-19 Thread Kevin Ottens
in the game this time and already engaged in the conversation. So if you're 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

Re: Proposal unify back our release schedules

2024-04-19 Thread Kevin Ottens
constant "learning new stuff" and "adapting to change" 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

2024-04-20 Thread Kevin Ottens
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

2024-04-22 Thread Kevin Ottens
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

Re: Proposal unify back our release schedules

2024-08-14 Thread Kevin Ottens
Room_2 > > If you're attending Akademy and interested in the topic, please join! > There should be remote participation options as well. Any chance to move it to 16:00? I'm interested but I'll be in the KDE PIM one until 16:00. Regards. -- Kevin Ottens, http://ervin.ips

[kde-community] Proposal: KDE Manifesto wording revision

2013-11-10 Thread Kevin Ottens
Hello community, After the publication of the initial version of the manifesto, I said I'd act as curator for the time being and that it should be a living document which would get updated from time to time. I didn't really live up to it so far as no revision has been done. But somehow I found

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

2013-11-10 Thread Kevin Ottens
On Sunday 10 November 2013 18:45:42 Marta Rybczynska wrote: > leadin -> leading Great, I managed to introduce a typo... Thanks for spotting it. It's fixed on my side. Regards. -- Kévin Ottens, http://ervin.ipsquad.net KDAB - proud supporter of KDE, http://www.kdab.com signature.asc Descrip

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

2013-11-10 Thread Kevin Ottens
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... we

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

2013-11-10 Thread Kevin Ottens
Hello community, In the principles section of the manifesto, we have the following point: "Projects that choose not to host their web services on KDE infrastructure need to provide administrative access to the KDE sysadmin team; or, if such access cannot be granted, a regular backup of all the c

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

2013-11-10 Thread Kevin Ottens
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 automatica

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

2013-11-11 Thread Kevin Ottens
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 continui

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

2013-11-11 Thread Kevin Ottens
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

2013-11-11 Thread Kevin Ottens
Hello, On Monday 11 November 2013 13:56:32 Eike Hein wrote: > After the exchanges in this and the other leg of the subthread > there ended up being a follow-up discussion on IRC, with Aaron, > Sune (svuorela), me (Sho_) and others contributing. I'd like to note I'm glad that you all took the time

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

2013-11-11 Thread Kevin Ottens
On Tuesday 12 November 2013 00:23:29 Lydia Pintscher wrote: > On Mon, Nov 11, 2013 at 8:04 PM, Ingo Klöcker wrote: > > Is the "which is approved by the KDE system administration team" really > > needed? I think it could be left out. If the fact that the action plan > > needs to be approved should

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

2013-11-12 Thread Kevin Ottens
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 i

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

2013-11-12 Thread Kevin Ottens
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 wrote: > > On Tuesda

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

2013-11-12 Thread Kevin Ottens
Hello, On Monday 11 November 2013 10:21:52 Aaron J. Seigo wrote: > On Sunday, November 10, 2013 18:28:58 Kevin Ottens wrote: > > Any opinions on this? > > second read on a monday morning: > > "Interact with teams that have common values, leadin to the > cross-pollina

Re: [kde-community] Proposal: KDE Manifesto wording revision, "financial support"

2013-11-12 Thread Kevin Ottens
On Monday 11 November 2013 22:38:21 Albert Astals Cid wrote: > El Diumenge, 10 de novembre de 2013, a les 18:28:58, Kevin Ottens va escriure: > > Hello community, > > > > Any opinions on this? I'd like to collect feedback before proceeding with > > a > > vote

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

2013-11-12 Thread Kevin Ottens
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

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

2013-11-13 Thread Kevin Ottens
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

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

2013-11-13 Thread Kevin Ottens
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

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

2013-11-13 Thread Kevin Ottens
On Wednesday 13 November 2013 20:57:51 Olaf Schmidt-Wischhöfer wrote: > Am Mittwoch, 13. November 2013, 20:32:26 schrieb Kevin Ottens: > > On Tuesday 12 November 2013 21:45:40 Peter Grasch wrote: > > > On 11/12/2013 06:35 PM, Aaron J. Seigo wrote: > > > > which establ

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

2013-11-13 Thread Kevin Ottens
On Wednesday 13 November 2013 20:58:46 Olaf Schmidt-Wischhöfer wrote: > Am Mittwoch, 13. November 2013, 18:44:45 schrieb Eike Hein: > > On Tuesday 12 November 2013 23:22:59 Thomas Pfeiffer wrote: > > > To me, "source materials" means anything that cannot be produced > > > automatically from the oth

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

2013-11-18 Thread Kevin Ottens
On Monday 18 November 2013 17:40:36 Thomas Pfeiffer wrote: > On 18.11.2013 17:31, Aaron J. Seigo wrote: > > If people really feel the name, the “established practices” could link to: > > http://techbase.kde.org/Policies > > > > This would be much like how the CoC is linked to rather than includ

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

2013-11-21 Thread Kevin Ottens
Hello community, So after the three threads I started a couple of weeks ago, I collected the feedback (thanks to everyone who participated!) and made a new patch out of it. It should cover everything which was discussed previously. So please review that new patch, and let me know if you still

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

2013-11-22 Thread Kevin Ottens
On Thursday 21 November 2013 21:24:21 Eike Hein wrote: > +1 from me, too, though iirc native speakers requested 'writable by' :) You mean it should say: * All source materials are hosted on infrastructure available and writable by all KDE contributor accounts Is it correct? I guess the problem is

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

2013-11-22 Thread Kevin Ottens
On Friday 22 November 2013 10:09:34 Paul Gideon Dann wrote: > On Friday 22 Nov 2013 10:27:09 Kevin Ottens wrote: > > On Thursday 21 November 2013 21:24:21 Eike Hein wrote: > > > +1 from me, too, though iirc native speakers requested 'writable by' :) > > > >

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

2013-11-22 Thread Kevin Ottens
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

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

2013-11-25 Thread Kevin Ottens
On Monday 25 November 2013 07:47:14 Mirko Boehm wrote: > On 24 Nov 2013, at 11:17, Marta Rybczynska 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 AFAICT. >

[kde-community] The KDE Incubator needs YOU

2013-12-17 Thread Kevin Ottens
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 into

Re: [kde-community] Incubating project

2013-12-30 Thread Kevin Ottens
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 k

[kde-community] Manifesto update applied

2014-01-06 Thread Kevin Ottens
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 Descript

Re: [kde-community] Non Api-stable libraries/frameworks - Re: Applications in KDE Generation 5

2014-01-16 Thread Kevin Ottens
On Thursday 16 January 2014 12:16:48 Sebastian Kügler wrote: > On Thursday, January 16, 2014 12:00:36 Kevin Krammer wrote: > > On Thursday, 2014-01-16, 01:33:34, Albert Astals Cid wrote: > > > El Dimecres, 15 de gener de 2014, a les 21:47:17, John Layt va escriure: > > > > * Application domain-spec

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

2014-01-16 Thread Kevin Ottens
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

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

2014-01-18 Thread Kevin Ottens
Hello, Very important thread IMO, but way too big for me to follow properly already. I tried to locate one email I could use to reply "after the facts", that one doesn't look too bar. :-) On Thursday 16 January 2014 11:42:43 Aaron J. Seigo wrote: > On Wednesday, January 15, 2014 21:47:17 Jo

Re: [kde-community] QtCurve

2014-01-20 Thread Kevin Ottens
Hello, On Monday 20 January 2014 15:29:00 David Edmundson wrote: > 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. Note there's the incubator now for existing projects willing to join

Re: [kde-community] QtCurve

2014-01-20 Thread Kevin Ottens
On Monday 20 January 2014 23:44:01 Eike Hein wrote: > On Monday 20 January 2014 17:13:47 Yichao Yu wrote: > > QtCurve (although being not very polished) is already stable and have > > made several releases that are packaged by a number of distributions. > > Is there anything I am missing here? > >

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

2014-02-16 Thread Kevin Ottens
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

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

2014-02-19 Thread Kevin Ottens
Hello, On Wednesday 19 February 2014 00:11:31 Bruno Coudoin wrote: > I am ready to start at your convenience. Let me know how do you want to > proceed. Let's start to look into that next week, I'm at conf.kde.in right now. I'll take the discussion mostly off list, for the curious I'll make the

Re: [kde-community] SCRUM in KDE

2014-03-04 Thread Kevin Ottens
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 practice

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

2014-08-12 Thread Kevin Ottens
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 o

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

2014-08-26 Thread Kevin Ottens
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 p

Re: [kde-community] Trademark clause in the Manifesto

2015-07-28 Thread Kevin Ottens
Hello, On Tuesday 28 July 2015 09:37:40 Boudewijn Rempt wrote: > I had a long discussion with Clemens yesterday after the Evolve BoF > session about the trademark clause in the commitments page linked from our > manifesto, and I'm not sure we don't actually do have a problem here. > > This is the

[kde-community] Phabricator: Make it happen already!

2015-08-26 Thread Kevin Ottens
Hello all, So we've been evaluating different options to modernize our tooling, and for some reason it looks like we're still waiting on some external pressure to pick one. I'll then try to be this external pressure with this war cry: Phaaab! Make it happen already! It is basically what I repo

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

2015-09-27 Thread Kevin Ottens
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" scenario, so >

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

2016-02-09 Thread Kevin Ottens
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 terr

Re: KDE End of Year 2016 Fundraising

2016-12-04 Thread Kevin Ottens
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: latest draft for mission (and strategy)

2017-07-01 Thread Kevin Ottens
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 m

Re: Applications Lifecycle Policy

2017-07-04 Thread Kevin Ottens
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 movin

Re: latest draft for mission (and strategy)

2017-07-05 Thread Kevin Ottens
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)

2017-07-05 Thread Kevin Ottens
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 think w

Re: latest draft for mission (and strategy)

2017-07-05 Thread Kevin Ottens
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&

Re: latest draft for mission (and strategy)

2017-07-05 Thread Kevin Ottens
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)

2017-07-05 Thread Kevin Ottens
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 too abstract to

Re: latest draft for mission (and strategy)

2017-07-05 Thread Kevin Ottens
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: latest draft for mission (and strategy)

2017-07-05 Thread Kevin Ottens
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 reall

Re: Applications Lifecycle Policy

2017-07-05 Thread Kevin Ottens
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)

2017-07-06 Thread Kevin Ottens
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)

2017-07-06 Thread Kevin Ottens
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

Re: latest draft for mission (and strategy)

2017-07-09 Thread Kevin Ottens
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 "priv

Re: latest draft for mission (and strategy)

2017-07-10 Thread Kevin Ottens
Hello, First of all, thanks a lot to Adriaan for putting my thought in much better words than I can. :-) On Monday, 10 July 2017 13:54:09 CEST Sebastian Kügler wrote: > I forgot to make that clear: I was thinking of a poll / vote / survey thing, > lightweight, but not email and get active commun

Proposal: Have the Community Set Ambitious Goals for Itself

2017-07-25 Thread Kevin Ottens
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 pro

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

2017-07-31 Thread Kevin Ottens
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 propo

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

2017-08-20 Thread Kevin Ottens
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 t

Re: Invent/gitlab, issues and bugzilla

2019-07-04 Thread Kevin Ottens
r post of 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: Invent/gitlab, issues and bugzilla

2019-07-04 Thread Kevin Ottens
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/pha

Re: List of available sprint venues for 2020 and beyond

2020-01-05 Thread Kevin Ottens
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: The chat situation

2020-06-10 Thread Kevin Ottens
h. Can we > fix Matrix? Or should we migrate to something that offers a better UX? I've not been a good citizen like you and stuck mostly to IRC so I got a question out of curiosity (and because I think it'll impact the decision making). Regarding the lags and the breakages, do they ha

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

2020-06-12 Thread Kevin Ottens
p discussion 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)

2020-06-13 Thread Kevin Ottens
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 b