From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?UTF-8?B?UHJ6ZW15c8WCYXcgV29qbm93c2tp?= Newsgroups: gmane.emacs.devel Subject: Re: More metaproblem Date: Wed, 10 Dec 2014 20:46:25 +0100 Message-ID: <5488A311.9020501@cumego.com> References: <20141203142859.24393.98673@vcs.savannah.gnu.org> <20141203192721.GE12748@thyrsus.com> <547F6774.50700@cs.ucla.edu> <838uio5vjw.fsf@gnu.org> <20141203211447.GB15111@thyrsus.com> <871toge5zw.fsf@floss.red-bean.com> <83388v6hsq.fsf@gnu.org> <87egsftgd5.fsf@ktab.red-bean.com> <83egsf3yci.fsf@gnu.org> <87iohq6nvn.fsf@ktab.red-bean.com> <85bnnhkuep.fsf@stephe-leake.org> <857fy4ipsd.fsf@stephe-leake.org> <85y4qjdsg0.fsf@stephe-leake.org> <548616BE.3050701@cumego.com> <83oarcwype.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1418240815 23924 80.91.229.3 (10 Dec 2014 19:46:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 10 Dec 2014 19:46:55 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 10 20:46:49 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 1XynDk-0001bu-BT for ged-emacs-devel@m.gmane.org; Wed, 10 Dec 2014 20:46:48 +0100 Original-Received: from localhost ([::1]:47672 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XynDj-0005tO-Uv for ged-emacs-devel@m.gmane.org; Wed, 10 Dec 2014 14:46:47 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33175) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XynDa-0005sx-TG for emacs-devel@gnu.org; Wed, 10 Dec 2014 14:46:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XynDV-000618-8r for emacs-devel@gnu.org; Wed, 10 Dec 2014 14:46:38 -0500 Original-Received: from smtp11.iq.pl ([86.111.242.220]:57189) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XynDU-00060j-UB for emacs-devel@gnu.org; Wed, 10 Dec 2014 14:46:33 -0500 Original-Received: (qmail 1591 invoked from network); 10 Dec 2014 19:46:26 -0000 Original-Received: from unknown (HELO [192.168.1.106]) (esperanto@cumego.com@[159.205.31.128]) (envelope-sender ) by smtp11.iq.pl with AES128-SHA encrypted SMTP for ; 10 Dec 2014 19:46:26 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 In-Reply-To: <83oarcwype.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 86.111.242.220 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:179694 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 W dniu 09.12.2014 o 17:54, Eli Zaretskii pisze: >> Date: Mon, 08 Dec 2014 22:23:10 +0100 From: Przemysław Wojnowski >> >> >> 1. How to build a project from source >> (http://lars.ingebrigtsen.no/2014/11/13/welcome-new-emacs-developers/ is >> a good start). > > Is it different from INSTALL.REPO in the Emacs tree? A bit. The blog has also good hints on installing deps: sudo apt-get build-dep emacs24 >> 2. How to run (automated) tests - IMHO a must if a project want to be >> perceived as modern by young developers. Without automated tests young >> devs will think that project stuck in 80's. Moreover, automated tests >> enable refactoring, which is standard now. Writing tests is very good >> starting point for new devs, because one can learn about the system and >> make it more resistant to unintended changes at the same time. > > Did you look in tests/ ? Yes. It contains automated tests for elisp and IMHO instructions for new devs should tell how to work with it. What about tests for C code? IMHO even one test would be helpful, just to show which test library should be used and how to run those tests. AFAIK writing tests is standard way to join a project and gain knowledge about it. >> 4. GH has fantastic pull requests that make contribution easier to do and >> less public, which is encouraging. Here, sending patches to the list, is >> technically harder (less of a problem) and discouraging (send a patch >> and watch 100 emails humiliating you :-) ). > > When did you see 100 humiliating emails in response to a patch? I think > you have some other project/forum in mind. It was just a metaphorical expression. I meant that it's discouraging to send a patch seeing people fighting in other threads. Maybe for patches it's a bit different - sorry, don't have time reading all emails on the list. :-| Thanks for response, Przemyslaw -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUiKMJAAoJEC3CE3LuBFUoUNkQAIB57tQ8X3R3anqWjHQWIOLc 6AK0uD+MklOQm6TNz9oSau7p9BeNJsVyz4nBVBHyjmV3tScZPzs5H7TM2zEr0o24 UIijVIgWiyMc7gPkalReV8UwikB0h6BieZxqSlqDJT2waHPVvxrD3JOyGXEzD+ci LLrBtiH/kcXdEYkkZZEVMPp+jIY6x050kZuALt/QiGGBxZM6MvvC47EDPpXL6xDH hua7Epwdb+eh+nvwVaA/1uLvXS02GUeRigmygX1sXhYBrTuftrDMN9UkE5PhPIxx ghm0eRk9qZ2Z7bMPiO914ikER6grBC7CvUDeoGPl9GbO9262dw3GleSU8yjdP3Lf 068HNQ5CKDDu3ieO/+PaT2a7BZqkWDg8zs9NhCNLNiKa1GE5JlAJBSh11Pw8jueR mtBHhC0wJ5626LEzIRxanh88lT4LiqFiYyHr0nxTJsPNA9L9VdXYouj15eSWeUHH AGt9puKuNxwmbC/0reAK1T8WMdUqb4uJCg673HY5pSy2qaF0wicEQBjX6ztCvgZa CLhYbDUy51cGfldbaHleZxE90u0A7V1dzQmfCxYNaVOABjW3RIo+ebJlLMHa/DbX eJGm/NDtuL75EV7mNmzpTF9LNDHPKbbGSxEqLr1IevHot9uGio503fGMZgcYaP7X 4wMwMoneeHbvckeQlp2x =mnyd -----END PGP SIGNATURE-----