From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Sending automatic crash reports to the FSF Date: Sun, 3 Jan 2016 15:48:16 -0800 Message-ID: <5689B340.3060703@dancol.org> References: <83mvu1x6t3.fsf@gnu.org> <567AD556.6020202@cs.ucla.edu> <567AD766.3060608@dancol.org> <567B5DAB.2000900@cs.ucla.edu> <83fuyromig.fsf@gnu.org> <567C25B1.3020101@dancol.org> <56892FD6.8040708@dancol.org> <568988EE.3010205@dancol.org> <56899278.9000007@dancol.org> <56899EAC.1030408@dancol.org> <5689ACFC.5050407@cs.ucla.edu> <5689AEE8.7030707@dancol.org> <5689B091.5020509@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wqhTrS3P55FOOQqFpq3ULSoC31D0xLH4j" X-Trace: ger.gmane.org 1451864932 15079 80.91.229.3 (3 Jan 2016 23:48:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 3 Jan 2016 23:48:52 +0000 (UTC) To: Paul Eggert , Eli Zaretskii , Emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 04 00:48:43 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aFsOA-0000Ta-LS for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2016 00:48:42 +0100 Original-Received: from localhost ([::1]:43268 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFsO9-00027T-Vg for ged-emacs-devel@m.gmane.org; Sun, 03 Jan 2016 18:48:41 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43744) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFsNv-000272-BL for Emacs-devel@gnu.org; Sun, 03 Jan 2016 18:48:28 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aFsNs-00037b-6Q for Emacs-devel@gnu.org; Sun, 03 Jan 2016 18:48:27 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:40837) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aFsNr-00037R-Tp; Sun, 03 Jan 2016 18:48:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=HQTXha2WxAFZ0RoRUK2dQ+MsKtCmiCXL4vj7CsNGA/g=; b=pSLmfNjQtTJQk7MEQq2fBGgCVMEc4jKERuO5hWK/OaUsw2cHjKwQzPlJCoOwdaK2Zm6+/Ks/bBnvrbW3Rl+5JS4oV6L65Dy2uSWr0LzDRsrI8n8b/7XTX01DMfYPSFiXWSrx6pKOhuj9ya0p/tb9ryZAlDMd46YAGAuuIc4ded7zsWN/p5UGi37QbscUUbxuQc5pKt3GsizQd099Jw+0NZ84QIfJ1sQQGUNTWD02VWdbzvry7R1hIU7lkmrF/tm4Sr+fHt7NYxBrSBEXS+QVnMmasAMvep9tjabu7N07oYZnEdcVDK9EUyD28VxzrCr+LQBqXgV/B53GvVTh1pKGNA==; Original-Received: from mobile-166-176-184-191.mycingular.net ([166.176.184.191] helo=[192.168.43.34]) by dancol.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84) (envelope-from ) id 1aFsNr-00087W-8W; Sun, 03 Jan 2016 15:48:23 -0800 X-Enigmail-Draft-Status: N1110 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:197534 Archived-At: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wqhTrS3P55FOOQqFpq3ULSoC31D0xLH4j Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 01/03/2016 03:39 PM, John Wiegley wrote: >>>>>> Daniel Colascione writes: >=20 >> Do you have any idea who would run the servers that would receive thes= e >> reports? At both Facebook and Microsoft, the resources necessary to st= ore >> user crash reports are quite significant, and I wouldn't impose that b= urden >> on the FSF. We'd definitely need some kind of aggregation and sampling= >> approach. >=20 > I rent a VPS that doesn't do a whole lot (mostly just forwards mail and= runs > my personal webblogs). I administer dovecot and postfix on that box, an= d would > be happy to receive and store crash reports there. I run a similar machine. I suspect that both servers would promptly melt, implode, and then, through sheer energy density, collapse into black holes. Even in this decadent age, there are a *lot* of Emacs users.= I think we can start with the Emacs-next master branch and get a feeling for what kind of workload this project would involve. By the way: Ubuntu (my distribution of choice these days) has its own crash reporting system, this appport/whoopsie thing. I wonder whether we can sample their existing Emacs crash reports somehow. Microsoft also has a way for software vendors to get crash reports from Windows Error Reporting. https://wiki.ubuntu.com/ErrorTracker --wqhTrS3P55FOOQqFpq3ULSoC31D0xLH4j Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWibNAAAoJEN4WImmbpWBl+/IP/01tg24I6B3Nf6b3fAi4w7DH mCRbWby9GT/pO7kwgNJIG51ddzsDtXdudiIHFcoNltw9V3lO5bU20CcMX+oDkjeF QFWdhCCYJ4n2JcF4GJ649FrBPm8lRUCCu+dozIlH/SAJxlNXjB9Kf7WLDwVhZE/F T/KBLbbU2+mynQGlxTwli8ggPcRCzl5vSJjAgBecY1+OJMftBzKf747lDBRkc781 +Y22rjddzir0rKPFO0+wMOqjMwOhq/xkPcK7skmWW7g0b+Bh1cQTbDZIX2Y7hoHq EBKPSVR2l3g3trQ7OST+jeCQztwAgXzi3PaP9kuYFe8lvpiYTtO+EO9d/NUIHkBF Z26cfza+ragJ2Mm5IyJNVoMpyjuO5aGA43V6cpdlKAdjdte/+bIy4YmuiIEZ826K EXeWy0nXpO4o+f/l9EZvgrQl59sakOYQlSYCR9/H+cQewj4xcNGaqzBJE1/ZscY1 ts4PMF8sB5/zDmoyLV0EjXX+qZCPgy1uQixwtMZGKDnh+IlJHIThB5Lnd4UyE69B zQETOY82moaWnT7KudmVmSylXBT6vRoATodPYwkEV05wU7c7IspfyhuL1W+F/cix t/g4oQAGDm2BnPsVq8L0mSCCqdeHJrpm/Q89JRvrsImxOo8Hf9KflIQ0GmyrULUC 5ozf8lSBKWFhhsXg8D4Q =yNmX -----END PGP SIGNATURE----- --wqhTrS3P55FOOQqFpq3ULSoC31D0xLH4j--