From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: New Emacs features via Google Summer of Code (or other similar stipend schemes) Date: Mon, 12 Aug 2024 18:59:04 +0000 Message-ID: <87ed6tin47.fsf@localhost> References: <87bk20yoya.fsf@dataswamp.org> <86zfpjirkg.fsf@gnu.org> <877ccnj9dp.fsf@localhost> <86bk1zhrf5.fsf@gnu.org> <874j7qkj97.fsf@localhost> <87y152x5v8.fsf@dataswamp.org> <87r0aui7ay.fsf@localhost> <8634nahu9u.fsf@gnu.org> <86msliym9t.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8641"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , emacs-devel@gnu.org To: Joel Reicher Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 12 20:58:54 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sdaFq-0001yc-2W for ged-emacs-devel@m.gmane-mx.org; Mon, 12 Aug 2024 20:58:54 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sdaF1-00030u-75; Mon, 12 Aug 2024 14:58:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sdaEz-0002sY-9Z for emacs-devel@gnu.org; Mon, 12 Aug 2024 14:58:01 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sdaEw-0002NY-S9 for emacs-devel@gnu.org; Mon, 12 Aug 2024 14:58:01 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 179E4240028 for ; Mon, 12 Aug 2024 20:57:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1723489076; bh=sP3T17BjvMpcHFJx/+ghUShTNnnCnq1UEX49OBZLI+E=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=Gm68I+8gEqzZ+ZiPDOutOXubTXGyRkxnWHxQRB88uTKCghnJhsCbzC8N0ArMUzkdh lPLpBG/cZ33SYiWSZVtlHWRK3o7RcbUlPwzh3kAYanuGb2ii2b5ukv3Rfyh6v9CEiM VEimNW8cZvZN75mLEgTZ1Tp7OA69uq8/Ro4t2DNdLF4KE3H1FeC1xdu+bGwfyi+ZLu +PyGYUq+aT+VDgSg7NsIZ/QJ9zjBytsf9b5fGIUJeV0P2/+pWGIi/Qxd8/fJl1hnC2 t86yU3h2hdgSczqsaiUtVLTAH1crU3jgaVB9TRlgRiEKzr+TiQS68qrRC44efAyR5G F8BYBfGE23TlA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4WjP0f5hQnz9rxF; Mon, 12 Aug 2024 20:57:54 +0200 (CEST) In-Reply-To: <86msliym9t.fsf@gmail.com> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:322681 Archived-At: Joel Reicher writes: >>> Eli, have you considered using GSC to get volunteers for >>> implementing some moderately difficult Emacs features? Since >>> GSC provides financial incentive, it may be possible to get >>> student volunteers. >> >> I can only say that it would be harder for a casual contributor >> to do a GSoC-style job for Emacs than for other projects, >> because Emacs has a lot of specialized needs and requirements >> that take time to learn. But maybe this is not an obstacle. > > Does GSC have an 'avenue' for working on bugfixes rather than > features? AFAIK, no. It is based on well-defined projects. Some nontrivial bugfixes may be worth a whole project, but I doubt that having a goal like "close N bugs" will qualify. > I know that's not where this thread started, and it's > significantly less glamorous, but the requirements for a bugfix > tend to be more immediately clear than a 'library'. If we aim for volunteers to fix bugs, it should probably be some other funding scheme; not GSoC. I am not aware about anything existing. The only somewhat relevant thing I recall was crowdfunding scheme like code bounty (proposed in the past on the list), but that is also more suitable for new features. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at