From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Emacs as the windows manager for graphical windows, How can I help? Date: Wed, 03 Apr 2013 15:43:57 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1365018253 4698 80.91.229.3 (3 Apr 2013 19:44:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 3 Apr 2013 19:44:13 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Malk'Zameth" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 03 21:44:37 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 1UNTbj-0008GG-Q4 for ged-emacs-devel@m.gmane.org; Wed, 03 Apr 2013 21:44:31 +0200 Original-Received: from localhost ([::1]:50435 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UNTbL-0000eo-3O for ged-emacs-devel@m.gmane.org; Wed, 03 Apr 2013 15:44:07 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:53734) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UNTbG-0000ZX-Qd for emacs-devel@gnu.org; Wed, 03 Apr 2013 15:44:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UNTbC-0005hu-LG for emacs-devel@gnu.org; Wed, 03 Apr 2013 15:44:02 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:9714) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UNTbC-0005hk-Gu for emacs-devel@gnu.org; Wed, 03 Apr 2013 15:43:58 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwGABK/CFFFxLSu/2dsb2JhbABEvw4Xc2eBHRMHAQEEAVYjBQsLLQcSFBgNJIVcB4I7BsEtjQ9GgzUDpHqBXoMTgVM X-IPAS-Result: ApwGABK/CFFFxLSu/2dsb2JhbABEvw4Xc2eBHRMHAQEEAVYjBQsLLQcSFBgNJIVcB4I7BsEtjQ9GgzUDpHqBXoMTgVM X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="6412270" Original-Received: from 69-196-180-174.dsl.teksavvy.com (HELO pastel.home) ([69.196.180.174]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 03 Apr 2013 15:43:55 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 95C8367A1E; Wed, 3 Apr 2013 15:43:57 -0400 (EDT) In-Reply-To: (Malk'Zameth's message of "Wed, 3 Apr 2013 12:04:35 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 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:158622 Archived-At: > Well, time to put my free time where my mouth is : I volunteer to work > on that, giving it all my "sideproject time" from the first of may > until completion. Great! > (maybe there is a welcome guide somewhere?) Not really, sorry. > 1. What needs to be done? what "format" does a code needs to conform > to be acceptable by the mainline Emacs? Obviously, Joakim knows better what needs to be done, but here are some comments from "the other end": to be acceptable for inclusion in the trunk I think the main criteria are along the following lines: - the new code is unlikely to need to be replaced later on by something completely different. That is meant to rule out "experimental" code. Also, while we try to speed it up, Emacs release cycle is pretty long/slow, so take into account that the code won't be in a release for at the very least another year, probably two, so try to make sure it doesn't rely on some external package that will be obsolete by then. - the patch should be safe in that most/all the code it touches is properly #ifdef'd. - nitpickers are satisfied (send your patch for review, and you'll see what I mean ;-). Read the GNU coding standards beforehand, since it describes most of the details we like. I think the best is if Joakim can give you a "first chunk" to chew on. > 2. Where do I need to apply to have the right to contribute those > changes to emacs at all? I just sent you a private email for that. Stefan