From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Yann Hodique Newsgroups: gmane.emacs.devel Subject: Re: Adding advisory notification for non-ELPA package.el downloads Date: Mon, 10 Jul 2017 09:48:17 -0700 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1499705958 18322 195.159.176.226 (10 Jul 2017 16:59:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 10 Jul 2017 16:59:18 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (darwin) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 10 18:59:09 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dUc1Z-00042d-4P for ged-emacs-devel@m.gmane.org; Mon, 10 Jul 2017 18:59:05 +0200 Original-Received: from localhost ([::1]:42104 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dUc1e-0004MD-BF for ged-emacs-devel@m.gmane.org; Mon, 10 Jul 2017 12:59:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58439) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dUc1S-0004Jg-0s for emacs-devel@gnu.org; Mon, 10 Jul 2017 12:58:59 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dUc1O-00036D-8z for emacs-devel@gnu.org; Mon, 10 Jul 2017 12:58:58 -0400 Original-Received: from [195.159.176.226] (port=52408 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dUc1O-00035p-2B for emacs-devel@gnu.org; Mon, 10 Jul 2017 12:58:54 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dUc1G-000382-8O for emacs-devel@gnu.org; Mon, 10 Jul 2017 18:58:46 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 66 Original-X-Complaints-To: usenet@blaine.gmane.org Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAAXNSR0IArs4c6QAAACpQTFRF HBgXPyYdPSkeMiwmRkJBYT4sik8zZF1XqWpMx2RDk42MzYRYtrGw09DVySZyaAAAAklJREFUOMuF 0z9v00AUAPCHr/kANgowOi6hjFbOCImp1CdF6kaUCwEmkBJSdYmUSBZRGRMsske1MlKIFKVr5XAr U1TPSFX6XXjvnKp2KOLG97v3x3dnuP7Hgv/B+vLyLlivZkGwSP6GlXABvHmyDese0GIn2zBzNYCX bEGagOswycG6ewMsyMEVVTJMiyQHv2lzuTOSNrDPWfhF8FSpuGXt5IB6s6bCNfLOt8FoEMT1JAv7 wFz25E7gtqFLqS856IJhl481/MyN27tnGe+wc1uprzn4fvS+MFYxwvDtLcyT1Y9oUhyri3ZHtTIg B7NP0WmDMo7VcJABKRvRtKNbq3hxC21ZKx2pMAWVgQt5H95MNSynKnMfZTzTQkSwjKLpPAN1H+CB zogmYaa5ED7eUzMeY+tw9HqRAcEBnoUhxYfFQZIBelRNhGjSKj6cb14kBH3hY5dCGI+XpzXTebzJ gY+CC47FHiGENQdXVfeBuvA55y5eYRgOnTJRdXC+6eFTiiHbHyplKVGoHGDQw1okzi5BCcUbXANn KL4WYAeyZJomJu0l4ALKZvlCvkrBOaG3dhOvdtlLjJt6AP2UN3DosoppOhr20v+Cwq4ncE8JwaLB gJpyPa/n0mQIJn0m0EExTHE5HgxUHAvnsjT41ARTnu8juAaUML5bSQHn8vkLBGYDUCkLS+tD577H qwjcpl8Le+BmIWgnHkrgws5BCvjTMbpaAsHPcK6+jXNhLfqGQND4XHhn4Ik5T8HCzKu+Bk98qwq+ 6AFOimPZ8Aem5xXrk2gG/wAAAABJRU5ErkJggg== Cancel-Lock: sha1:K6pITQf3eJFC64oXB+l+fywcpjI= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:216422 Archived-At: >>>>> "Richard" == Richard Stallman writes: > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] >> Proactively contacting elisp developers to ask them if they would >> consider a copyright assignment (mentioning the benefit of potential >> bundling with Emacs, along with the rest of the implications) seems much >> more OK to me. > That would entail searching for people who are just starting packages > and sending each one mail. I agree it would give better results -- if > we could do it. But it would be a lot of work. Who would do the > work? And how would we find people that are just starting > to get contributions to their packages? > It isn't better if it isn't feasible. Well, one possibility would be to: 1. figure out where most of the code that ends up in MELPA lives (since it seems to be the target so far): ~/src/github.com/melpa/melpa/recipes master ❯ grep :fetcher * | sed 's/.*:fetcher \([a-z]*\).*/\1/' | sort | uniq -c | sort -rg 3393 github 156 wiki 44 git 38 bitbucket 26 gitlab 9 svn 4 cvs 2 darcs 2 bzr 1 hg given that the wiki data is reachable from github (via https://github.com/emacsmirror/emacswiki.org) that means that at least 96.6% of the target is present on github one way or the other. I'm too lazy to extract real trends, but this share is slowly growing | 07/2012 | 07/2013 | 07/2014 | 07/2015 | 07/2016 | 07/2017 | |---------+---------+---------+---------+---------+---------| | 89.8 | 92.4 | 94 | 95.8 | 96.5 | 96.6 | 2. use the fact that github data is published weekly as a BigQuery dataset (https://cloud.google.com/bigquery/public-data/github) to perform fancy queries on it: like what are the emacs repositories that went from 1 contributor last week to 2 contributors this week, crosscheck with paperwork data and identify who to go after next. An example of what has already been achieved using those tools: https://kozikow.com/2016/06/29/top-emacs-packages-used-in-github-repos/ That's kind of handwavy and vaguely creepy (then again, any kind of automatic detection of what I might be doing to "help me being a better member of the community" is gonna creep me out no matter what), but most of the data is definitely readily available. Yann. -- The worst sort of protection is confidence. The best defense is suspicion. -- HASIMIR FENRING