From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: JD Smith Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] New package: activities Date: Mon, 29 Jan 2024 21:50:04 -0500 Message-ID: <372A4DA3-F690-47FC-9B1B-4E042B3E8B8A@gmail.com> References: <0A512CBA-B05F-4E55-AA1D-72BF85E6F078@gmail.com> <7F448098-FBFD-4495-8FB4-1A035AAF2EC9@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25657"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel To: Chris Van Dusen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 30 03:51:18 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 1rUeDW-0006XS-CS for ged-emacs-devel@m.gmane-mx.org; Tue, 30 Jan 2024 03:51:18 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rUeCe-0004By-Qr; Mon, 29 Jan 2024 21:50:26 -0500 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 1rUeCb-0004Bb-2v for emacs-devel@gnu.org; Mon, 29 Jan 2024 21:50:21 -0500 Original-Received: from mail-io1-xd30.google.com ([2607:f8b0:4864:20::d30]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rUeCX-0001Z3-CF for emacs-devel@gnu.org; Mon, 29 Jan 2024 21:50:19 -0500 Original-Received: by mail-io1-xd30.google.com with SMTP id ca18e2360f4ac-7baa8da5692so194951239f.0 for ; Mon, 29 Jan 2024 18:50:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706583016; x=1707187816; darn=gnu.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=oMx5vXdT5U+dcl2LRt/VsXMIuSF69SXj+vFo/71i+d8=; b=hqFwO70CcpmLm/6crjQxNnv3KBWbw706XUFIOa/xc76a5LRniGRCKTUEvi1Jjque1s rKYHr6UUIOvSWQhAYSYo0OlBpdUCnxOb3BbaZEqJ/CbTttgCvpx/ISabPIq91uE6tNBn Kf4Hvpm+DlnxEDd3hEhRJOl8mseRNNrHkLBBDFjoGo2aTOI87w5OqW6NUHMf8n4Z0m0+ TfjSwpOP5cvYYc/XUHhlEkCoWSnC2hPBibfc32HmMTBEzRX5fPZc37Fb+srW4Qf1IzWB q/wLd/Bw5liLKppxE93TYCe2TvLPmX014dl2crcB8EvCFTqf+yocF5DFw/zudTdK6h5l S4lA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706583016; x=1707187816; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=oMx5vXdT5U+dcl2LRt/VsXMIuSF69SXj+vFo/71i+d8=; b=RLq02nCbO3k9RuGbd4/zmtmgFavQYjJf9eCkQZbUs7SrGIhR/KTFva/J5hN4eIzGvC hmnnNFi65ZCxK9LIhzvi2M/nPwwR61B6R49fku/eeCtRBiijTVRkJ0TxUW04oCY9OF9g 8Xeyu1u8BylIaSE2FqzYb5iJKk/irSiUgedDGuY8bMpWIEh375vEMCae1FsoOYvPHvTc CUUC2n1JhlFI9hZAhRqN4/aJq9AhWGCnE7FyKMc5nMN/pKg4C4V7KM84/BVMnxdRNP1s DrovksDsVfWD/kyHwOySXK4p8UzR4ZvLfBhyqooXGG0rzTBA/XTLZlpoz7D16QYAo0Ca P6hQ== X-Gm-Message-State: AOJu0YzM48RuBIjHxX/NFSIy/eelk/ATn2zUc43L7CmlcNH5vNn3yQn+ jy1kOvbFAom/6jfob6WlTYR1RR0jiwRruTLUtqH+NGq4BBoI6I9ffZDjKaeq X-Google-Smtp-Source: AGHT+IFb5ox6unNspW/mPKNODQePVjQ9DcEDH2KQXl+8rcUCL5cz5hLVK5WKz4PY4Va0wTjg6tUNyg== X-Received: by 2002:a5d:9a8a:0:b0:7be:f34a:5b53 with SMTP id c10-20020a5d9a8a000000b007bef34a5b53mr8916634iom.9.1706583015767; Mon, 29 Jan 2024 18:50:15 -0800 (PST) Original-Received: from smtpclient.apple (cm-24-53-187-34.buckeyecom.net. [24.53.187.34]) by smtp.gmail.com with ESMTPSA id y9-20020a02a389000000b0046e578ed0aasm2015090jak.96.2024.01.29.18.50.14 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Jan 2024 18:50:15 -0800 (PST) In-Reply-To: <7F448098-FBFD-4495-8FB4-1A035AAF2EC9@gmail.com> X-Mailer: Apple Mail (2.3774.300.61.1.2) Received-SPF: pass client-ip=2607:f8b0:4864:20::d30; envelope-from=jdtsmith@gmail.com; helo=mail-io1-xd30.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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:315619 Archived-At: > On Jan 29, 2024, at 7:08=E2=80=AFPM, Chris Van Dusen = wrote: >=20 >> On Jan 29, 2024, at 15:49, JD Smith wrote: >>=20 >> PS: I personally feel that by the time a package author presents a = well-written and fairly complete package for inclusion into ELPA, it is = too late to make the argument that they should have instead contributed = that functionality to a built-in package. If you can convince them = earlier in the process, of course, but it certainly adds to the outside = impression that ELPA is a gauntlet that must be run, which I think all = agree is not desired. >=20 > I=E2=80=99m not sure I follow. Most of the time package authors = don=E2=80=99t ssy anything until they want to publish the package, so = how can the maintainers suggest to them to contribute to an existing = package? That's a different issue than how to receive new packages with = advancements that might have, in an alternate Universe, been contributed = to core. But it's a fair point. I'm not sure I have a solution to the chicken and egg problem. = Advertising "low-hanging fruit" capabilities that core packages need, = and providing starter packs for aspiring package developers? Perhaps = with the explicit offer of the occasional core developer's ear for = questions? I mean the quality of answers here is usually off-scale = good. > An alternative would be for potential package authors to post to = emacs-devel, stating that they would like to see feature foo in package = bar. If it turns out that it is not feasible to implement the feature, = then sure, a new package can be created. I could also imagine a yearly "meet and greet with core developers" type = of event, where new ideas get passed around, people talk about the = packages they'd love to build next, and others in the know can mention = how those may relate to or potentially extend core packages. An = old-fashioned spit-balling session.