From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junio C Hamano Subject: Re: [Administrivia] On ruby and contrib/ Date: Sun, 09 Jun 2013 16:29:09 -0700 Message-ID: <7vli6in9ru.fsf@alter.siamese.dyndns.org> References: <7vtxld30f2.fsf@alter.siamese.dyndns.org> <7va9n52zjc.fsf@alter.siamese.dyndns.org> <7vd2ryueuu.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Johannes Schindelin , Felipe Contreras , David Lang , Greg Troxel , git@vger.kernel.org, Jeff King , Jonathan Nieder , Thomas Rast , =?utf-8?Q?Ren=C3=A9?= Scharfe , Michael Haggerty , Matthieu Moy , =?utf-8?B?Tmd1ecKtbiBUaMOhaSBOZ8O3Yw==?= , Ramsay Jones , Erik Faye-Lund , Johannes Sixt To: Ramkumar Ramachandra X-From: git-owner@vger.kernel.org Mon Jun 10 01:29:19 2013 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ulp2y-0006YB-GC for gcvg-git-2@plane.gmane.org; Mon, 10 Jun 2013 01:29:16 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751903Ab3FIX3M (ORCPT ); Sun, 9 Jun 2013 19:29:12 -0400 Received: from b-pb-sasl-quonix.pobox.com ([208.72.237.35]:51576 "EHLO smtp.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750818Ab3FIX3L (ORCPT ); Sun, 9 Jun 2013 19:29:11 -0400 Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 490AF26096; Sun, 9 Jun 2013 23:29:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:message-id:mime-version:content-type; s=sasl; bh=bct2NpY05BleZ+kZQPKMVIwKgJM=; b=K+nPqF74T3aJCEZlQvAW QejYgbN6KeaZf3If7p2fufNDo+0rNNNY023GkPE8EQolDxPe5kXVqOTEGXiQtue/ EQO83bfJtHVvEKnr1GJwVz866JUrqdEHCtZbSCO0QhdQJUFG0HX4EY/vqOwocB+G qfx8Qr36ZpRRKRtu49D3cTE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:message-id:mime-version:content-type; q=dns; s=sasl; b=Ic3dAuuRjeN0zdh6rMq67CMxYJaKuSsXYqlXG8mu9Z/H01 Pm5urNfui/SkV5W3XiKL7U/pEpuxE64NPPhCPPHMkq1GMIONqhjYcEC+ZlpzynDP XdY6e0u2i36Z0M/r18my2H66vBNB4CIjxsq2B7FbtUBhh84as+bzTfGBGEyVs= Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 3DFC326094; Sun, 9 Jun 2013 23:29:11 +0000 (UTC) Received: from pobox.com (unknown [50.161.4.97]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by b-sasl-quonix.pobox.com (Postfix) with ESMTPSA id 8CC7F26092; Sun, 9 Jun 2013 23:29:10 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) X-Pobox-Relay-ID: 633CD816-D15C-11E2-8DFB-E56BAAC0D69C-77302942!b-pb-sasl-quonix.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Ramkumar Ramachandra writes: > Do you think that the opinions of > inactive community members and non-contributors are _more_ valuable > than those of active contributors, or am I missing something? I am not Dscho, but it probably is worth saying this anyway. 6d297f81373e (Status update on merge-recursive in C, 2006-07-08) stole merge-recursive.c from git-merge-recursive.py with an explicit purpose of making sure that those without a working Python can perform such a core operation like "merge" with Git without extra forking. The person who worked on it, as long as he knows that the project not just accepted the patch and kept using the code but also that the project understood the rationale behind that change, does not necessarily have a reason to appear every week to interject comments in discussions on any part of the system, even to proposed changes to merge-recursive.c, as long as the original thing the change meant to address is not broken (e.g. removing merge-recursive.c and add it as a merge strategy written in Python or Ruby might trigger "huh", but ditching merge-recursive.c and replacing it with merge-replay.c as long as it works would be a "meh" for him). When otherwise silent old-timers feel a need to come during a discussion that might affect the course of the project in a major way, we should pay more attention, not less, to what they say (I am not saying "we should blindly follow"). They can explain why some things are as they are, why some changes that may look like a good idea did not work out and how they failed, etc. Certainly the opinions from them are no less valuable.