From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: emacswiki GSOC Date: Mon, 29 Apr 2013 00:41:25 +0900 Message-ID: <87mwsiwtlm.fsf@uwakimon.sk.tsukuba.ac.jp> References: <877gjmsvql.fsf@ferrier.me.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1367163697 28335 80.91.229.3 (28 Apr 2013 15:41:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 28 Apr 2013 15:41:37 +0000 (UTC) Cc: emacs-devel@gnu.org To: Nic Ferrier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Apr 28 17:41:39 2013 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 1UWTjP-0000qS-FK for ged-emacs-devel@m.gmane.org; Sun, 28 Apr 2013 17:41:39 +0200 Original-Received: from localhost ([::1]:48156 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UWTjP-0007On-4R for ged-emacs-devel@m.gmane.org; Sun, 28 Apr 2013 11:41:39 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:59731) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UWTjK-0007Oi-Vx for emacs-devel@gnu.org; Sun, 28 Apr 2013 11:41:36 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UWTjK-0008Ir-3o for emacs-devel@gnu.org; Sun, 28 Apr 2013 11:41:34 -0400 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:37225) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UWTjJ-0008HG-PT for emacs-devel@gnu.org; Sun, 28 Apr 2013 11:41:34 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id D002A9708E6; Mon, 29 Apr 2013 00:41:25 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 946E111F978; Mon, 29 Apr 2013 00:41:25 +0900 (JST) In-Reply-To: <877gjmsvql.fsf@ferrier.me.uk> X-Mailer: VM undefined under 21.5 (beta32) "habanero" b0d40183ac79 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 130.158.97.224 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:159196 Archived-At: Nic Ferrier writes: > The guy who approached me asked if he could work on the emacswiki stuff > under the GNU project or under the Emacs project (which have got GSOC > approval I think). Emacs is not a GSoC org, and it has no visible presence in a quick look at the ideas page. Hard to see how Emacs is not going to get slots if it wants them, though. > I'm presuming this is not possible... but can someone confirm for me? By whose rules? I see no reason why Google would have a problem with it, as long as you're talking about coding. One-off scripts to move emacswiki content to the new elwiki wouldn't cut it, I'm afraid[1], but code for the wiki itself, or a special version of Emacs performance-tuned for wiki use would be OK. If you're thinking about deadlines, well, lack of time and lack of explicit contact with the community (especially the GNU org and Emacs suborg admins -- Emacs is not a GSoC org) will (should?) hurt a lot, but he's still got almost 3 days, I think. But you need mentors who need to be accepted by the GNU GSoC org, that's the big hurdle. I think mentors can still register, but jumping in at the last minute this way, if I were the org admin, well, *I* would say it better be a blockbuster project and superman mentors. I'm not authoritative for Google or GNU. But if you've got the mentors I don't see how it could hurt to ask. Footnotes: [1] But note that GNU Mailman does have a project for a *robust* set of scripts which *will* be a permanent part of Mailman 3, to move Mailman 2.1 lists to the very different Mailman 3 format.