From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6CE02138247 for ; Fri, 10 Jan 2014 17:39:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DDBF2E0E09; Fri, 10 Jan 2014 17:39:35 +0000 (UTC) Received: from mail-la0-f53.google.com (mail-la0-f53.google.com [209.85.215.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B3424E0DCA for ; Fri, 10 Jan 2014 17:39:34 +0000 (UTC) Received: by mail-la0-f53.google.com with SMTP id e16so668714lan.26 for ; Fri, 10 Jan 2014 09:39:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:reply-to:message-id:to:subject:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=63jjZQrzNOv/PNaw+sQOSD/Ar6l+o5GLM4FZbh7IhyU=; b=QH9jhGxhsq8u5XSSk2twg6AuNj+B2SJ9bJ2KoIR2QQi6iz0jMi57jQtxkAFgMugqCt ZN8DWkcRAVeB9+P9NgPziQU9jjnofE+IzoZ2IJm5sqdMAsEpl+cfFPzAYMH1YAj0I3hW +Zx4ZpxMR8qTfdAaqStC+mqBizTvmhs3dIg2aJ/MYB9jkOPevdp2HzKDcXgfmJLvZhZO A/pQX+SyrcuR7BRJHbvAj3b3s9/dq8C3gCNSdEGKP8Fo0EFGl1S9NITC/1Twgpz3vEyW vtw1A+0CGYn0zkKm7xK8g/QmOLRce2Umrvm/LSCOr+TvavdwKLftCrwF/WyMbgwJZdQs J5rA== X-Received: by 10.112.130.35 with SMTP id ob3mr4173075lbb.2.1389375573055; Fri, 10 Jan 2014 09:39:33 -0800 (PST) Received: from [192.168.60.64] (office.healtech.ru. [89.208.21.2]) by mx.google.com with ESMTPSA id m5sm4780745laj.4.2014.01.10.09.39.31 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 10 Jan 2014 09:39:32 -0800 (PST) Date: Fri, 10 Jan 2014 21:39:30 +0400 From: Igor X-Priority: 3 (Normal) Message-ID: <52d03054.0524980a.15da.ffffb212@mx.google.com> To: "Andreas K. Huettel" Subject: Re: [gentoo-dev] Question, Portage QOS v2 In-Reply-To: <8864472.OZjXC1DmSv@kailua> References: <52d02b83.4a1b980a.1e8d.ffffb56b@mx.google.com> <8864472.OZjXC1DmSv@kailua> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archives-Salt: c3768f2a-b300-4342-ac4f-5add34e43e7f X-Archives-Hash: 9ef7cf357c534f6a916f9cdc0ac8c3dc Hello Andreas, Friday, January 10, 2014, 9:20:17 PM, you wrote: >> As there are questions at to what we vote. >> ---------------------------------------------- > Realistically most people haven't even read your mails (too much bla). Please read the following and vote. What PortageQOS will be able to accumulate: * Knowledge of the number of Gentoo distros installed world wide - knowing the trend how many users choose Gentoo and where Gentoo is really going down|up|stands still. You can then try different features and see how a feature is met - if the number of systems increase then this feature is probably useful. It's a strategical job, somebody at the very top of the project should analyze databases and make conclusions. * Knowledge of the ebuild popularity - what ebuilds are popular and what are not - what ebuild to give an extra focus and what ebuild could wait * Knowledge of ebuild quality. If some ebuilds fail on many systems - something is wrong and ebuild and may be portage need fixing. It's especially useful to make sure that all ebuilds have correct dependencies, missing dependencies, etc. * A formal esteem of portage quality PortageQ = (the number of successful ebuilds/the number of all ebuild attempts) Portage speed efficiency: Average time before build starts (or download starts) How many times portage fails itself. * Immediate problem detection. If the number of PortageQ went down last day - there is some problem. (then you go to ebuild stats and see what is failing) * Reducing load on bugtracker folks - the build problems will be detected automatically and solved according to their importance. There will be no need to supply bug tracker with ebuild logs and emerge --info if somebody wants to report a problem. * Team efficiency esteem. The stats will tell what ebuilds are failing most often. * Team automated info. When failure rate of a certain ebuild increase the maintainer is automatically informed and he can login in web-interface and see details how exactly ebuild failed. The same for the portage itself. Next day a maintainer could push a new ebuild in the portage and the problem might be solved. It's not possible not to make mistakes. But it's possible to react on their consequences fast. * Knowledge what kernels are used by Gentoo users, how often they update their systems, what flags are used 2nd turn goals: * to integrate forums.gentoo.org and bug tracker. People are offering great workarounds and solutions. But they're not known to the majority of Gentoo users. If a e-build fails - may be there is already a solution - and we can offer the solutions automatically from portage. Like: There might be some work-arounds on this problem: [Gentoo Forum - qt-core ebuild fails - SOLVED] htpp://forums.gentoo.org/..... There is a known bug on this ebuild: [Gentoo Bug - qt-core ebuild fails] htpp://forums.gentoo.org/..... * to make Bug Tracker almost unmanned. We can use gathered infromation on failed e-builds to create bugs in Bug Tracker automatically and automatically set priorities according to the severity. The severity could be assigned automatically from package popularity and failure rate stats. These are the bricks that will be added in the initial design. -- Best regards, Igor mailto:lanthruster@gmail.com