Advance Downtime Notification

into account potential system unavailability, and where possible reschedule the release outside of the window. Should anyone have any concerns please contact us. Regards, Ben Cooksley KDE Sysadmin

Re: Advance Downtime Notification

On Wed, Nov 29, 2017 at 8:11 PM, Ben Cooksley wrote: > Hi all, Hi everyone, > > Over the past 24 hours we have received initial warning notifications > that a disk in our bulk storage server has begun to show signs of > failure. We have now begun the process of having thi

Re: SoK 2018 Project - 'New Season of KDE Website'

de-org.git/tree/protected/data/ This is in addition to the standard LDAP objectClasses of course. Please let me know if you have any questions about the specific data which might be stored for a user. > > Thanks, > Mayank Gupta Cheers, Ben Cooksley KDE Sysadmin

Mirror of Qt being discontinued

e let us know. Cheers, Ben Cooksley KDE Sysadmin

Re: UI tests on build.kde.org

ely on any plugins which could be popping up a message box or anything along those lines? > > The tests was reported to work on other computers by two developers. > > Best > Christian > Regards, Ben Cooksley KDE Sysadmin > >

Re: Looking for mentor for new KDE developer

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

Re: Looking for mentor for new KDE developer

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

Re: Kamoso in KDE Applications

On Tue, Jan 16, 2018 at 10:49 AM, Albert Astals Cid wrote: > El dilluns, 15 de gener de 2018, a les 4:05:05 CET, Aleix Pol va escriure: >> On Sun, Jan 14, 2018 at 11:31 PM, Albert Astals Cid wrote: >> > El divendres, 12 de gener de 2018, a les 3:51:03 CET, Aleix Pol va > escriure: >> >> On Thu, J

Re: [kdesrc-build] qca build failed

On Sun, Jan 21, 2018 at 3:33 PM, Christoph Feck wrote: > On 20.01.2018 17:33, Mathieu Tarral wrote: >> >> I'm trying to build KDE from source using kdesrc-build script. >> However, each time i have tried these last days, it failed on the QCA >> module. > > > This might have to do with incompatible

Re: git repo issues

On Sun, Jan 28, 2018 at 4:54 AM, Nate Graham wrote: > Hello Ben (et al), Hi Nate, > I've noticed that in the last hour, git commits don't seem to show up in the > web interface. Examples: > > https://phabricator.kde.org/D10143 -> commit shows up in git history, but > does not appear on https://c

Re: Baloo is not dead, it just smells a little funny

than just a description we can also look into that. > > > So here's my plea: > > If you are an experienced C++-programmer and know the KDE code-base well, > please watch the things the two of us doing for baloo, criticize me, and > first of all: become a reviewer for the requests targeted at baloo or > baloo-widgets, please! Help me keep the pace! > > > Thank you for reading all this, > > Michael > > Cheers, Ben Cooksley KDE Sysadmin

Re: Closing old Plasma 4 bugs

On Sun, Feb 11, 2018 at 4:06 PM, Nate Graham wrote: > + kde-devel to widen the conversation Hi Nate, > > > On 02/10/2018 05:48 PM, Nicolás Alvarez wrote: >> >> Meanwhile... maybe you can do some loud blog posts calling for triagers? >> :) > > > Sounds good. Before then, we need to clean up the w

Re: Closing old Plasma 4 bugs

On Mon, Feb 12, 2018 at 8:52 AM, Nate Graham wrote: > All right, so let's give it a shot. 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 Sounds reasonable.

Re: Closing old Plasma 4 bugs

Hi all, I've now put together the necessary changes and have deployed them on the Bugzilla Testbed, at bugstest.kde.org. If people could please login and verify things are working correctly for them still that would be appreciated. I've given anyone with editbugs membership currently membership o

Re: Closing old Plasma 4 bugs

t few days to do so. Cheers, Ben > > Nate > > > On Sat, 17 Feb 2018 23:51:42 -0800 Ben Cooksley > wrote > > Hi all, > > I've now put together the necessary changes and have deployed them on > the Bugzilla Testbed, at bugstest.kde.org. > If people coul

Global Dependency and Release Freeze

eeBSD images, in addition to sorting out the other tickets we have received over the past few days some of which will require some time to deal with. Requests for exceptions to these freezes are not available, however we will endeavour to lift them as soon as is practicable. Regards, Ben Cooksle

Re: CI fails to build my last commit in a file I did not change

On Fri, Mar 2, 2018 at 10:08 AM, Albert Astals Cid wrote: > El dijous, 1 de març de 2018, a les 10:25:51 CET, Michael Heidelbach va > escriure: >> Hi! >> >> Applications baloo-widgets kf5-qt5 FreeBSDQt5.9/ >> > kf5-qt5%

Re: Global Dependency and Release Freeze

Hi all, We've now finished catching up on everything and getting the CI system settled down again so we're now able to lift the freeze. I'll start sorting out the releases which have been requested shortly. There is still some lingering breakage impacting Akonadi and KIO however those can be fixe

Phabricator Notification Mails

Hi all, It has been brought to my attention that some find that they are receiving too much mail or other notifications from Phabricator. For those who are unaware there are numerous options available within Phabricator to allow you to control how much it notifies you of changes. To customise the

Phabricator mail disruption

who don't mind HTML based email. My apologies for the disruption. Regards, Ben Cooksley KDE Sysadmin

Re: bugs.kde.org: kio vs frameworks-kio vs kfile etc.

On Tue, Apr 10, 2018 at 6:43 AM, Nate Graham wrote: > > > On Mon, 09 Apr 2018 11:35:49 -0700 Elvis > Angelaccio wrote > > Yes. > > > > Note that this is not kio-specific: every library in kdelibs that used to > > have its own bugzilla product should be "merged" with the new > > fra

Upcoming CI changes - service disruption

Hi all, In order to allow for two replacement physical build hosts to be rotated in and the old ones to be decommissioned, i'm scheduling some downtime for both the CI system and the Binary Factory tomorrow. Assuming all goes well, this downtime should be fairly short. During the downtime Jenkins

Re: Upcoming CI changes - service disruption

On Tue, Apr 10, 2018 at 10:42 PM, Ben Cooksley wrote: > Hi all, Hi everyone, > > In order to allow for two replacement physical build hosts to be > rotated in and the old ones to be decommissioned, i'm scheduling some > downtime for both the CI system and the Bin

Re: Flatpak packaging for stable releases

On Sun, Apr 15, 2018 at 11:52 AM, Aleix Pol wrote: > On Sat, Apr 14, 2018 at 11:20 PM, Matthieu Gallien > wrote: >> Hello, >> >> I really appreciate the work that has gone into flatpak and the excellent >> support for it in KDE and the KDE infrastructure for it. >> >> I have an hard time understa

Re: kdesrc-build: cmake should take local (instead of system-wide) cmake modules

On Wed, May 9, 2018 at 9:28 AM, gregor.mi.sw wrote: > > > On 08.05.2018 23:15, Milian Wolff wrote: >> >> On Dienstag, 8. Mai 2018 22:40:39 CEST gregor.mi.sw wrote: >>> >>> Hello, >>> >>> I have a question regarding kdesrc-build and CMake. >>> >>> I setup the build environment variables and ran kde

Re: Changes to Phabricator review subscriptions

On Wed, May 9, 2018 at 8:33 PM, Boudewijn Rempt wrote: > On Wednesday, May 9, 2018 10:08:28 AM CEST you wrote: >> Hi all, >> >> To improve the user experience around email and in-application >> notifications from Phabricator, sysadmin have made some changes to the >> configuration of our Herald ru

Re: Changes to Phabricator review subscriptions

On Wed, May 9, 2018 at 9:25 PM, Timothée Giet wrote: > Le 09/05/2018 à 10:33, Boudewijn Rempt a écrit : >> >> On Wednesday, May 9, 2018 10:08:28 AM CEST you wrote: >>> >>> Hi all, >>> >>> To improve the user experience around email and in-application >>> notifications from Phabricator, sysadmin ha

Re: Changes to Phabricator review subscriptions

On Wed, May 9, 2018 at 9:47 PM, Milian Wolff wrote: > On Mittwoch, 9. Mai 2018 10:08:28 CEST Ben Cooksley wrote: >> Hi all, >> >> To improve the user experience around email and in-application >> notifications from Phabricator, sysadmin have made some changes to the >

Re: Changes to Phabricator review subscriptions

On Wed, May 9, 2018 at 10:45 PM, Timothée Giet wrote: > Le 09/05/2018 à 12:11, Ben Cooksley a écrit : >> >> On Wed, May 9, 2018 at 9:25 PM, Timothée Giet wrote: >>> >>> Le 09/05/2018 à 10:33, Boudewijn Rempt a écrit : >>>> >>>> On Wednesda

Re: Changes to Phabricator review subscriptions

s they have been individually subscribed to. > > > > To help this change take full effect, it would be appreciated if > > people refrain from adding Projects as reviewers, as that will have > > the effect of subscribing the Project to the review as well > > (Phabricator does not require you specify a reviewer) > > > > Should anyone have any questions regarding this, please open a thread > > on the kde-devel@kde.org mailing list. > > > > Regards, > > Ben Cooksley > > KDE Sysadmin > > > >

Re: Changes to Phabricator review subscriptions

On Thu, May 10, 2018 at 8:08 AM, Nate Graham wrote: > On Wed, 09 May 2018 12:46:30 -0700 Luigi > Toscano wrote > > Nate Graham ha scritto: > > > Thanks for the responses, Ben. > > > > > > I'm a bit concerned that all of this raises the barrier to entry for new > contributors. Now t

Re: Changes to Phabricator review subscriptions

On Fri, May 11, 2018 at 8:25 PM, Dmitry Kazakov wrote: > Hi, Ben! Hi Dmitry, > > There is a small problem with not-subscribing Differential Revisions to > projects: one cannot use Phabricator's Dashboard functionality for filtering > the incoming revisions. Is there any way to configure dashboar

Re: Closing old Plasma 4 bugs

On Sun, May 27, 2018 at 9:05 PM, Elvis Angelaccio wrote: > On Fri, May 11, 2018 at 11:06 PM Christoph Feck wrote: > >> On 11.02.2018 20:52, Nate Graham wrote: >> > All right, so let's give it a shot. How about we make it so that normal >> > users have full privilages except the following: >> > >>

Re: Closing old Plasma 4 bugs

ve also cleaned up the bug triaging page: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > It's still a bit long, so any further editing to condense it a bit would > be welcome. > > Nate > > > > On 02/21/2018 07:16 AM, Nate Graham wrote: > > > &g

Binary Factory & Windows CI builds temporarily offline

stall, you receive a version of MSBuild which only works properly with 15.7. In most circumstances this would not be an issue, however other changes necessitate a complete rebuild of the entire dependency tree (including glib and Qt). My apologies for any inconvenience this causes. Regards, Ben Coo

Re: Binary Factory & Windows CI builds temporarily offline

On Mon, Jun 11, 2018 at 4:18 PM, Ben Cooksley wrote: > Hi everyone, Hi all, > > Due to some issues with MSVC we are currently encountering, the Binary > Factory is currently unable to successfully complete Windows builds. > As part of diagnosing these, reinstallation of MSVC ha

Upcoming change to mail infrastructure

Once the filter has been sufficiently trained, we will commence the cutover and transfer handling of kde.org mail, including mailing lists, to the new system. Should anyone have any questions regarding this process, please let us know. Regards, Ben Cooksley KDE Sysadmin

Re: Upcoming change to mail infrastructure

On Tue, Jul 3, 2018 at 10:44 PM, Paul Brown wrote: > On martes, 3 de julio de 2018 12:29:41 (CEST) Ben Cooksley wrote: >> Hi all, >> >> We've recently completed configuration of a new mail server which will >> be replacing the current system which handles kde.

Re: Upcoming change to mail infrastructure

On Tue, Jul 3, 2018 at 11:11 PM, Paul Brown wrote: > On martes, 3 de julio de 2018 12:59:49 (CEST) Ben Cooksley wrote: >> On Tue, Jul 3, 2018 at 10:44 PM, Paul Brown wrote: >> > On martes, 3 de julio de 2018 12:29:41 (CEST) Ben Cooksley wrote: >> >> Hi all, >&g

Re: Upcoming change to mail infrastructure

On Tue, Jul 3, 2018 at 11:25 PM, Paul Brown wrote: > On martes, 3 de julio de 2018 13:12:56 (CEST) Ben Cooksley wrote: >> On Tue, Jul 3, 2018 at 11:11 PM, Paul Brown wrote: >> > On martes, 3 de julio de 2018 12:59:49 (CEST) Ben Cooksley wrote: >> >> On Tue, Jul 3

Re: Upcoming change to mail infrastructure

On Wed, Jul 4, 2018 at 10:30 AM, Reindl Harald wrote: > > > Am 03.07.2018 um 12:29 schrieb Ben Cooksley: >> We've recently completed configuration of a new mail server which will >> be replacing the current system which handles kde.org mail. This >> system wil

Re: Upcoming change to mail infrastructure -> SPF still broken

On Wed, Jul 4, 2018 at 10:52 PM, Reindl Harald wrote: > > > Am 04.07.2018 um 12:38 schrieb Ben Cooksley: >> On Wed, Jul 4, 2018 at 10:30 AM, Reindl Harald >> wrote: >>> did you also notice and fix the long outstanding bugzilla SPF problems >>> within you

Re: Upcoming change to mail infrastructure -> SPF still broken

ever be sending as @KDE.org (and is authorised to do so in our SPF records). The fact that it isn't is due to a bug in software we use, which we are in the process of fixing. Therefore from my perspective everything is configured correctly, as Bluemchen is external as far as Postbox (and Letterbox) are concerned. Regards, Ben Cooksley KDE Sysadmin >

Mail system switchover complete

d from KTown to Postbox) We'd like to thank Bytemark (bytemark.co.uk) for sponsoring the Letterbox server. Should anyone have any queries regarding the status of the system, please contact sysad...@kde.org, or file a Sysadmin ticket. Thanks, Ben Cooksley KDE Sysadmin

Re: KDE Frameworks 5.48.0 released

bscr...@kde.org or visit https://mail.kde.org/mailman/options/ and follow the prompts there. This information is also included in the RFC standard List-Unsubscribe header, contained in all emails you've received from our lists. Regards, Ben Cooksley KDE Sysadmin > > On Sat, Jul 14, 201

Re: Limiting who can create v${NUMBER}.${NUMBER}.${NUMBER} tags in KDE Applications git repos

Hi all, Given that no objection has been raised to this, I have now implemented this. All repositories in Frameworks, KDE Applications and Plasma can now only have tags starting with the convention of vN. modified by their respective release managers. This has been implemented using a whitelist o

Upcoming reorganisation of the CI system

system (although downtime will be needed in order to allow for the changeover). Thanks, Ben Cooksley KDE Sysadmin

Re: Upcoming reorganisation of the CI system

On Tue, 14 Aug 2018, 17:09 Christoph Feck, wrote: > On 14.08.2018 15:03, Ben Cooksley wrote: > > Currently CI jobs are all created within a flat namespace, meaning > > that it is quite difficult to view the overall status of an individual > > project. Additionally, it creat

Re: Upcoming reorganisation of the CI system

Hi all, Final call for objections or queries for this change - i'll be looking to roll this out this weekend. Note: Plasma and KDevelop, i'm not subscribed to your lists so please ensure i'm in CC for any responses. Cheers, Ben

Re: Upcoming reorganisation of the CI system

, "") > qt.qpa.gl: QWindowsOpenGLTester::supportedRenderers > GpuDescription(vendorId=0x0, deviceId=0x0, subSysId=0x0, revision=0, driver: > "", version=, "") renderer: QFlags(0x8|0x20) > qt.qpa.gl: Qt: Using EGL from libEGLd > qt.qpa.gl: Qt: Using OpenG

CI System Reorganisation

e DSL Job is run the views I mentioned previously, which will provide recursive overviews for those who prefer those, will become available. If anyone encounters any issues please let us know. Thanks, Ben Cooksley KDE Sysadmin

Re: CI System Reorganisation

On Mon, 10 Sep 2018, 01:17 Christoph Feck, wrote: > On 09.09.2018 10:59, Ben Cooksley wrote: > > As a followup to my earlier mail sent about 3 weeks ago, i've now > > transitioned all builds on the CI system over to the folder layout > > previously described. > >

Emergency downtime notice

econd be replaced. To preserve our data in the meantime I have shutdown the container hosting Phabricator/Git/Subversion, so they will be unavailable for the next few hours. My apologies for the inconvenience. Regards, Ben Cooksley KDE Sysadmin

Re: Emergency downtime notice

On Wed, Oct 10, 2018 at 8:51 PM Ben Cooksley wrote: > > Hi all, > > We've just received notice that both disks in the server hosting > Phabricator, along with our Git and Subversion repositories have > failed their SMART self-assessment tests. > > I have now requeste

Re: Emergency downtime notice

On Wed, Oct 10, 2018 at 9:35 PM Ben Cooksley wrote: > > On Wed, Oct 10, 2018 at 8:51 PM Ben Cooksley wrote: > > > > Hi all, > > > > We've just received notice that both disks in the server hosting > > Phabricator, along with our Git and Subversion repo

Downtime announcement: www.kde.org

captive portal) - Any application using GHNS In addition, any other site which is hosted by the server known as "olios.kde.org" will also be unavailable during this time. Apologies for any inconvenience caused. Regards, Ben Cooksley KDE Sysadmin

Re: Downtime announcement: www.kde.org

On Sat, Nov 3, 2018 at 7:50 AM Ben Cooksley wrote: > > Hi all, Hi all, > > In order to allow for hardware maintenance, one of our physical > hardware hosts will need to be shutdown for a few hours on Monday. > This downtime will commence around 9:30am UTC and may ta

Re: TechEvent Telegram Channel

Hi all, The sender of these messages has now been removed from both this, and all other KDE.org mailing lists (they sent it elsewhere for those not subscribed to other affected lists) Regards, Ben

Transitioning CI builds of all non-Frameworks from Qt 5.9

Hi all, I've been informed by the PIM developers that they would like to bump the dependency of the Qt version they use, from Qt 5.9 which it's on currently, to Qt 5.10. As a consequence, due to many KDE projects using PIM libraries, their dependency on Qt will also be effectively bumped. To mini

Re: Transitioning CI builds of all non-Frameworks from Qt 5.9

On Mon, Dec 3, 2018 at 10:31 PM René J.V. Bertin wrote: > > Hi, > > Can't you just configure the CI to use Qt 5.10? I think it's not good to > hardcode an "overzealous" (for lack of a better word) Qt version in projects > that don't require them AND I think that one should support the current LT

Re: Transitioning CI builds of all non-Frameworks from Qt 5.9

On Tue, Dec 4, 2018 at 9:45 AM Elvis Angelaccio wrote: > > > > On 03/12/18 09:46, Ben Cooksley wrote: > > Hi all, > > Hi Ben Hi Elvis, > > > > > I've been informed by the PIM developers that they would like to bump > > the dependency of

Re: Transitioning CI builds of all non-Frameworks from Qt 5.9

On Wed, Dec 5, 2018 at 7:22 AM Albert Astals Cid wrote: > > El dimarts, 4 de desembre de 2018, a les 18:10:44 CET, Thiago Macieira va > escriure: > > On Monday, 3 December 2018 01:30:25 PST René J.V. Bertin wrote: > > > Can't you just configure the CI to use Qt 5.10? I think it's not good to > >

Re: Transitioning CI builds of all non-Frameworks from Qt 5.9

On Wed, Dec 5, 2018 at 8:18 AM Albert Astals Cid wrote: > > El dimarts, 4 de desembre de 2018, a les 20:13:43 CET, Ben Cooksley va > escriure: > > On Wed, Dec 5, 2018 at 7:22 AM Albert Astals Cid wrote: > > > > > > El dimarts, 4 de desembre de 2018, a les

CI system disruption

aused. Regards, Ben Cooksley KDE Sysadmin

Re: CI system disruption

On Sun, Jan 6, 2019 at 10:14 PM Ben Cooksley wrote: > > Hi all, Hi everyone, > > Due to a massive translation change which took place in the last 24 > hours, the CI system is currently in the process of rebuilding the > whole of KDE for all the platforms it covers (both branch

Bugzilla Server Move

Hi all, We've just completed the migration of Bugzilla from a previous system to a newer system. While this hasn't changed Bugzilla itself much, it did involve an update from Ubuntu 14.04 to Ubuntu 18.04. >From our testing everything appears to be operating correctly. Should anyone see anything

Upcoming Service Downtime

Hi all, Sysadmin is currently in the process of planning server migrations for a large number of services which have significant visibility, and which are often substantially involved in the release process for projects as well as general community operation. As it may take several hours to perfo

Re: Request from Finland

On Sun, Jan 13, 2019 at 10:09 AM Valorie Zimmerman wrote: > > > Hi all, is there a better list for this inquiry? If so, please forward it > there. Hi Edward, In order to best assist here, it would be nice to know which operating system the students are running on their laptops. Based on it not

Re: Troubles with icon themes

On Wed, Jan 23, 2019 at 4:48 PM Jonathan Schultz wrote: > > Hello KDE developers, Hi Jonathan, > > I wonder if someone can help me work out what is going on here. > > I have build some KDE applications (konsole and okular) from source using > kdesrc-build, using QT5 version 5.11.3 also built fr

Re: LXR is inaccessible

On Tue, Feb 12, 2019 at 5:23 AM Nate Graham wrote: > > Hello Sysadmins, > https://lxr.kde.org/ is inaccessible right now. Any ETA on getting it > back up? Hi Nate, Sorry for this - LXR went down when the physical host for it crashed around 18 hours ago. While the physical host was revived, the c

Re: Phabricator seems down

On Wed, Feb 13, 2019 at 5:09 AM Nate Graham wrote: > > Hello sysadmins, Hi Nate, > https://phabricator.kde.org is not responding responding right now for > myself and others. Can you give it a kick? It appears to have corrected itself. > > Thanks! > > Nate >

Re: notes.kde.org having auth trouble

On Wed, Feb 20, 2019 at 4:48 AM Nate Graham wrote: > > Hello Sysadmin, Hi Nate, > People are having trouble authenticating to any of the documents on > notes.kde.org. It's rejecting everyone's credentials for all documents > at the moment. It seems Nginx freaked out and forgot how to talk to LD

Gitlab Evaluation & Migration

ne by everyone involved in the intervening months, and stand by to help implement a community decision based on what was collected. Based on all of the above we'd like to propose migrating towards Gitlab. Comments? Thanks, Ben Cooksley KDE Sysadmin

Re: Gitlab Evaluation & Migration

On Sun, Feb 24, 2019 at 4:56 AM Boudewijn Rempt wrote: > > On zaterdag 23 februari 2019 14:49:25 CET Konstantin Kharlamov wrote: > > > As someone who uses gitlab on a dayjob I can tell it's pretty easy too. > > With disregard to server interface you do `git push my-fork HEAD`, > > right? Now, when

Re: Gitlab Evaluation & Migration

ncerns changes to the Binary Factory are not under consideration at this time. > > Sincerely, > Boudhayan Gupta > Cheers, Ben > > On Sat, 23 Feb 2019 at 11:04, Gleb Popov <6year...@gmail.com> wrote: >> >> >> >> On Sat, Feb 23, 2019 at 1:44 PM Ben Cooksl

Re: Gitlab Evaluation & Migration

On Sun, Feb 24, 2019 at 8:06 AM Boudewijn Rempt wrote: > > On zaterdag 23 februari 2019 18:58:46 CET ste...@derkits.at wrote: > > > "A lot" is probably a bit exaggerated, e.g. I don't really know where to > > upload patches to Phabricator or create a pull request there, but do > > understand how G

Re: Gitlab Evaluation & Migration

On Sun, Feb 24, 2019 at 10:30 AM Alexander Potashev wrote: > > сб, 23 февр. 2019 г. в 12:44, Ben Cooksley : > > Based on all of the above we'd like to propose migrating towards > > Gitlab. Comments? > > Hi, Hi Alexander, > > 1. We migrated from github.com

Re: Gitlab Evaluation & Migration

On Mon, Feb 25, 2019 at 8:31 AM Martin Flöser wrote: > > Am 2019-02-23 10:44, schrieb Ben Cooksley: > > Hi all, > > > Based on all of the above we'd like to propose migrating towards > > Gitlab. Comments? > > I'm totally honest here: I'm not happy

Re: Gitlab Evaluation & Migration

On Tue, Feb 26, 2019 at 10:02 PM Eike Hein wrote: > > > > On 2/26/19 4:17 AM, Nate Graham wrote: > > Like you, I have some reservations about Gitlab. I'm not thrilled about > > losing approve/request changes statuses (that's in the EE edition only > > right now). > > Me too. It's one of the thin

Re: Gitlab Evaluation & Migration

On Tue, Feb 26, 2019 at 5:54 AM Martin Flöser wrote: > > Am 2019-02-24 21:03, schrieb Ben Cooksley: > > On Mon, Feb 25, 2019 at 8:31 AM Martin Flöser > > wrote: > >> > >> Am 2019-02-23 10:44, schrieb Ben Cooksley: > >> > Hi all, > >&

Re: Gitlab Evaluation & Migration

On Tue, Feb 26, 2019 at 10:26 PM wrote: > > On 2019-02-26 10:13, Ben Cooksley wrote: > > > No decision has been made, that's what this thread is about. > > I may have my personal views on what may be best, but that's all they > > are - my views. > > I m

Re: Gitlab Evaluation & Migration

On Wed, Feb 27, 2019 at 5:18 AM Harald Sitter wrote: > > On Mon, Feb 25, 2019 at 2:38 PM Boudewijn Rempt wrote: > > > > On zaterdag 23 februari 2019 12:08:05 CET Boudewijn Rempt wrote: > > > > > * Is there anything we can have that can replace tasks and workboards? We > > > usually have some ver

Re: Gitlab Evaluation & Migration

On Thu, Feb 28, 2019 at 5:12 PM Michael Pyne wrote: > > On Wed, Feb 27, 2019 at 03:15:58PM -0700, Nate Graham wrote: > > On Wed, 27 Feb 2019 12:12:55 -0700 Eike Hein wrote > > > On 2/27/19 4:38 AM, Nate Graham wrote: > > > > It's really pretty nice. But Gitlab has a > > fork-the-re

Re: Gitlab Evaluation & Migration

On Thu, Feb 28, 2019 at 11:24 AM Albert Astals Cid wrote: > > El dimecres, 27 de febrer de 2019, a les 20:12:55 CET, Eike Hein va escriure: > > > > On 2/27/19 4:38 AM, Nate Graham wrote: > > > It's really pretty nice. But Gitlab has a > > > fork-the-repo-and-submit-a-merge-request workflow, so i

Re: Gitlab Evaluation & Migration

On Thu, Feb 28, 2019 at 10:23 PM Filipe Saraiva wrote: > > Em 24/02/2019 22:25, Filipe Saraiva escreveu: > > > > 4. Is there any date to officially start the migration for all projects? > > How will it be? > > > > Will the migration happen before GSoC? Is it possible to a project > request for mig

Re: Gitlab Evaluation & Migration

On Fri, Mar 1, 2019 at 3:13 AM Nate Graham wrote: > > On Wed, 27 Feb 2019 23:02:03 -0700 Ben Cooksley > wrote > > In terms of server load, it would be nice if the setup of forks was > > still something the developer had to initiate rather than being done &

Re: Gitlab Evaluation & Migration

On Fri, 1 Mar 2019, 07:21 Gleb Popov <6year...@gmail.com wrote: > > > On Thu, Feb 28, 2019 at 9:43 PM Ben Cooksley wrote: > >> On Fri, Mar 1, 2019 at 3:13 AM Nate Graham wrote: >> > >> > ---- On Wed, 27 Feb 2019 23:02:03 -0700 Ben Cooksley < >> b

Concluding the Gitlab Discussion

ructure for the transition (such as the anongit network, which will need a full rebuild as part of switching). Once this is complete, we'll be in touch with more information on how the transition will take place. Thanks, Ben Cooksley KDE Sysadmin

Re: Gitlab Evaluation & Migration

On Sat, Mar 23, 2019 at 12:42 AM Milian Wolff wrote: > > On Donnerstag, 28. Februar 2019 07:02:03 CET Ben Cooksley wrote: > > On Thu, Feb 28, 2019 at 5:12 PM Michael Pyne wrote: > > > On Wed, Feb 27, 2019 at 03:15:58PM -0700, Nate Graham wrote: > > > > O

Re: Concluding the Gitlab Discussion

o discussing this with them. > > Other than that, I think I think what Gitlab offers over Phabricator is > either a significant win or else just something different that you can get > used to quickly. > > Nate Regards, Ben > > > On Tue, 19 Mar 2019 02:26:24 -0600 B

Re: Concluding the Gitlab Discussion

On Tue, Mar 19, 2019 at 9:26 PM Ben Cooksley wrote: > > Hi all, > > Over the past few weeks we've had a discussion on whether we'd like to > migrate from Phabricator to Gitlab, for handling both our code reviews > as well as internal tasks (user facing bug reports are

Re: Concluding the Gitlab Discussion

On Sun, Mar 24, 2019 at 8:46 AM Tomaz Canabrava wrote: > > People, and the apps that are still in svn, like kmldonkey, will be migrated > too ? Subversion will not be impacted in any form. They'll remain outside of Gitlab. Cheers, Ben > > Em sáb, 23 de mar de 2019 às

CI system maintainability

system vs. the amount of care actually being given by some developers (who are ignoring it's failure emails) it becomes questionable whether the effort is worth the return (and if not, we should just shut it down) Regards, Ben Cooksley KDE Sysadmin

Re: CI system maintainability

On Thu, Mar 28, 2019 at 7:56 PM Konstantin Kharlamov wrote: > > > > On Чт, Mar 28, 2019 at 19:40, Ben Cooksley wrote: > > Hi all, > > > > We currently have a rather substantial issue, in that the CI system > > has been once again left in a position where it is

Re: Updating the Framework apidocs part 1: fixing the presentation

On Fri, Mar 29, 2019 at 9:47 PM Juan Carlos Torres wrote: > > Hello everyone! > > It's that docs guy again! Hope you don't mind this brief interruption of > coding activities to give our apidocs some TLC. > > I recently went over the KDE Frameworks apidocs, one framework and class at a > time, t

Re: CI system maintainability

On Fri, Mar 29, 2019 at 6:45 AM Johannes Zarl-Zierl wrote: > > Hi, Hi, > > (Sorry for top-posting) > > I fear that a mandatory reviews would add too juch strain on smaller teams. > If there's just one person with an intimate knowledge of the code-base, plus > two co-developers, then who should

Re: CI system maintainability

On Fri, Mar 29, 2019 at 10:33 PM Friedrich W. H. Kossebau wrote: > > Am Donnerstag, 28. März 2019, 23:06:17 CET schrieb laurent Montel: > > Le jeudi 28 mars 2019, 18:27:42 CET Friedrich W. H. Kossebau a écrit : > > > Am Donnerstag, 28. März 2019, 16:56:33 CET schrieb laurent Montel: > > > > Le jeu

Re: CI system maintainability

On Fri, Mar 29, 2019 at 9:56 PM Kevin Ottens wrote: > > Hello, > > On Thursday, 28 March 2019 20:35:11 CET Dr.-Ing. Christoph Cullmann wrote: > > I and others tried to get more reviews done in the past, but actually I > > merged more than once stuff that I reviewed but it did break the CI. > > Tha

Re: CI system maintainability

On Sat, Mar 30, 2019 at 10:46 PM Volker Krause wrote: > > On Friday, 29 March 2019 20:54:54 CET Ben Cooksley wrote: > > On Fri, Mar 29, 2019 at 6:45 AM Johannes Zarl-Zierl > > > I fear that a mandatory reviews would add too juch strain on smaller > > > teams. If t

Re: Signing keys for commercial app stores

On Mon, Jun 10, 2019 at 2:03 PM Simon Redman wrote: > > Hello, Hi Simon, > > I am Simon, and I work on KDE Connect. This summer, KDE Connect has two > excellent GSoC students, one working on a MacOS port and one working on > a Windows port, with the end goal of bringing those ports to feature >

  1   2   3   4   5   6   7   8   >