From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tom Newsgroups: gmane.emacs.devel Subject: Re: Developers, developers, developers Date: Fri, 14 Nov 2014 20:11:36 +0000 (UTC) Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1415995948 2169 80.91.229.3 (14 Nov 2014 20:12:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 14 Nov 2014 20:12:28 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 14 21:12:22 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 1XpNEC-0007JJ-Ck for ged-emacs-devel@m.gmane.org; Fri, 14 Nov 2014 21:12:20 +0100 Original-Received: from localhost ([::1]:37722 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpNEB-0004Q7-Tc for ged-emacs-devel@m.gmane.org; Fri, 14 Nov 2014 15:12:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33269) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpNDt-0004Pv-Iv for emacs-devel@gnu.org; Fri, 14 Nov 2014 15:12:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XpNDg-0001TE-Q0 for emacs-devel@gnu.org; Fri, 14 Nov 2014 15:12:01 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:53315) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XpNDg-0001Ss-K9 for emacs-devel@gnu.org; Fri, 14 Nov 2014 15:11:48 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XpNDf-000705-FB for emacs-devel@gnu.org; Fri, 14 Nov 2014 21:11:47 +0100 Original-Received: from 94-21-239-44.pool.digikabel.hu ([94.21.239.44]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 14 Nov 2014 21:11:47 +0100 Original-Received: from adatgyujto by 94-21-239-44.pool.digikabel.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 14 Nov 2014 21:11:47 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 40 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 94.21.239.44 (Mozilla/5.0 (Windows NT 6.1; rv:33.0) Gecko/20100101 Firefox/33.0) 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:177108 Archived-At: Lars Magne Ingebrigtsen gnus.org> writes: > > Since Emacs is now on git, we'll get tons and tons of new Emacs > developers, right? Git is a good step in this direction (a widely used VC), but something else would also be useful. Is there an uptodate list of small tasks which someone can starts working on? I don't mean bug reports and stuff, but specific small tasks which are clearly defined, have to be done and they are good for getting a taste of contributing to emacs. Something which takes, say, a half on hour, or 1-2 hours to done. E.g. adding documentation for something, adding new automatic tests, doing some small code fix, etc. There are many small tasks like this which occur during development and it would be useful to have an uptodate list of these. Maybe with a time estimation ("takes about 1 hour") Keeping such a list increases the administration a bit, but it would also be beneficial for offloading these tasks to casual contributors. E.g. someone says: "I have an hour of free time, I'll fix something in emacs." and he goes to this list, picks a task, does it, sends the patch and it can be crossed out. So the regular developers would regularly add these small tasks to the list which could be done by the casual contributors, so it would free up core developers to work on other, more demanding tasks. It seems to me the little more administration which consists of adding these tasks to this list would be worth it.