From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Emacs contributions, C and Lisp Date: Wed, 19 Feb 2014 09:49:40 +0100 Organization: Organization?!? Message-ID: <87fvnfqyfv.fsf@fencepost.gnu.org> References: <52FCD2B4.5080006@yandex.ru> <52FD9F1D.50205@yandex.ru> <83mwhucg1h.fsf@gnu.org> <878ute589i.fsf@fencepost.gnu.org> <83d2iqc84m.fsf@gnu.org> <87wqgxkcr9.fsf@yandex.ru> <834n41db0d.fsf@gnu.org> <52FE2985.4070703@yandex.ru> <831tz5daes.fsf@gnu.org> <8738jlohd6.fsf@yandex.ru> <83txc1bl83.fsf@gnu.org> <5300189A.9090208@yandex.ru> <83wqgv9fbj.fsf@gnu.org> <20140216180712.236069f6@forcix.jorgenschaefer.de> <83sirj9cyp.fsf@gnu.org> <20140217203145.71a849f7@forcix.jorgenschaefer.de> <837g8t8ouc.fsf@gnu.org> <20140219080524.25689b6b@forcix.jorgenschaefer.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1392799805 29510 80.91.229.3 (19 Feb 2014 08:50:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Feb 2014 08:50:05 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 19 09:50:13 2014 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 1WG2r4-0007ZR-8n for ged-emacs-devel@m.gmane.org; Wed, 19 Feb 2014 09:50:10 +0100 Original-Received: from localhost ([::1]:57386 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WG2r3-0003CA-Rb for ged-emacs-devel@m.gmane.org; Wed, 19 Feb 2014 03:50:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40657) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WG2qu-00037O-UN for emacs-devel@gnu.org; Wed, 19 Feb 2014 03:50:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WG2qp-0006ZK-Hr for emacs-devel@gnu.org; Wed, 19 Feb 2014 03:50:00 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:53955) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WG2qp-0006Yu-8L for emacs-devel@gnu.org; Wed, 19 Feb 2014 03:49:55 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WG2ql-00072L-VB for emacs-devel@gnu.org; Wed, 19 Feb 2014 09:49:51 +0100 Original-Received: from x2f44deb.dyn.telefonica.de ([2.244.77.235]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Feb 2014 09:49:51 +0100 Original-Received: from dak by x2f44deb.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Feb 2014 09:49:51 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 55 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f44deb.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:UWz7xxaGsyVLexmjNTbzvaT25zs= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:169756 Archived-At: Jorgen Schaefer writes: > On Mon, 17 Feb 2014 22:29:47 +0200 > Eli Zaretskii wrote: > >> > There are a few other minor problems for me. For example, my last >> > foray in adding a patch to Emacs was so scary regarding the amount >> > of red tape involved in the whole process that I am somewhat >> > reluctant to commit to doing that regularly. >> >> What red tape? Emacs is about the most red-tape-less project as you >> can find, as far as the procedure of admitting a patch is considered. > > If I want to contribute to Emacs, and I want to be good contributor, I > have the following things to keep in mind: > > - Make sure I have done my copyright assignment, and for larger work, > do the same for all contributors. > - Read etc/CONTRIBUTE and follow all the steps > - Which asks me to read the GNU Coding Standards > - Oh, and "Tips and Conventions" in the emacs Lisp Reference > appendix > - Learn a new tool (bzr), for which I have to read [... Lots of bullet points centered around bzr] I've never learnt working with Bzr and never checked out the Emacs repository with it. That did not preclude me from sending the occasional patch to the list, based on the Git mirror of the Emacs repository. You are confusing "contributing to Emacs" with "being a core developer of Emacs", one who is able and willing to make the decisions about what to push where and when to ask back all on his own. > Emacs just thinks it's more important to have those procedures than to > have more contributors. Which is a perfectly valid decision to make. That's a bad representation of the issue. We are not talking about "more important" but rather "prerequisites". With regard to coding styles, it's fine to submit a patch without heeding them but it does cause more work for everybody involved than if you take a look at the respective perfectly available information yourself at your own pace and initiative. With regard to copyright assignments, you pretend that it is some magic ritual of initiation. There is nobody who'd be more glad than the FSF if this kind of paperwork was without merit and unneeded. Thank your law makers for that. Or better, tell them that you want them to work on getting back the situation before the Berne convention where copyright is only asserted when a copyright notice is placed in a document. -- David Kastrup