Org-mode mailing list
 help / color / mirror / Atom feed
From: Timothy <tecosaur@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: emacs-orgmode@gnu.org
Subject: Re: Concerns about community contributor support
Date: Mon, 19 Apr 2021 03:12:03 +0800
Message-ID: <87blabo1a4.fsf@gmail.com> (raw)
In-Reply-To: <87sg3n4ejd.fsf@tsdye.online>


Thomas S. Dye <tsd@tsdye.online> writes:

>> Hmmm, what constitutes noise?
>>
> Good question.  I suppose like most words the meaning changes over time.  Early
> on, posts along the lines of "Wouldn't it be cool if Org mode would do this?"
> were given more space than they seem to be today.  Tim Cross points out a
> project trajectory that appears to be common and would explain why.  At a more
> concrete level, I can offer several of my posts to the list :)

Follow up: What should be the response to "noise", because I don't think
it should be a cold shoulder.

>> I think here there may have been a minor misunderstanding
>> /miscommunication. Reading this paragraph I get the sense you read my
>> email as complaining about a delay in merging patches, however this is a
>> separate ---if related--- point to what I intended to raise: the
>> lack of /response/ to patches.
>>
>> 1. [snip]
>> 2. [snip]
> So, something in between merging (or not) and appearing on the public list that
> Bastien keeps?

I'll try to clarify my meaning:
+ Patches are sent in
+ The /do/ appear on the public list
+ Months go by without anyone even replying to the patch

I think it's fair to expect something along the lines of: "Not sure
about this, will require further thought", "Looks good, but want to wait
for X to approve", "Not quite sure why this is a good idea, please
explain further", or one of a hundred other suitable cursory responses.

Instead, there are currently 24 patches listed on
https://updates.orgmode.org/#patches which have not received a single
response. Then, there are also a large number of other patches with 1-2
cursory replies that seem stuck in limbo (e.g. [1]), with no signs of
being merged or rejected (better than 0 replies, but still not good).

>> Once again, with reference to my earlier paragraph, IMO slowed
>> development is one thing, not responding at all to attempted
>> contributors for months on end another. It is the latter which I seek to
>> improve. I can, have, and will try to help with this myself; but I think
>> we would benefit from a "community effort" and a discussion on what the
>> best way to improve this is.
>>
>
> What do you think of Tim Cross' suggestion that a way forward is for "new
> features and enhancements to be initially implemented as add on contribution
> packages rather than as extensions/enhancement to the core 'org-mode' package"?
> This sounds good to me, but I'm not much of a programmer and lack the ability to
> suss out its ramifications fully.  I can see how it would ease Org mode
> maintenance, though.

I'm going to reply to Tim Cross' email, but a short version of my
current thoughts is:
+ This feels like a little bit of a tangent from the lack of response
+ Many patches are modifying core functionality, and would not be
  suitable as an add-on (e.g. [2], [3], [4], and more)
+ I'm concerned that good changes could quickly make there way here and
  never make their way into Org

> All the best,
> Tom

--
Timothy

[1]: [PATCH] ob-lilypond: allow user configuration of header-args
     https://orgmode.org/list/CANwLyLNCUDEqrtLe9DxB+xZg9T-DWfmfHzrPMuqcUZLZW347Tg@mail.gmail.com/
[2]: [PATCH] Add org-meta*-final-hook
     https://orgmode.org/list/CAOywxZg1cBL07THLZXHBBCzm6te2vMtqnmM0w63331gybrjZuw@mail.gmail.com/
[3]: [PATCH] ob-C.el: Fix a number a bugs related to table parameters
     https://orgmode.org/list/874kkqao1e.fsf@bzg.fr/
[4]: [PATCH] Fontification for inline src blocks
     https://orgmode.org/list/87pmzf4bd0.fsf@gmail.com/


  reply	other threads:[~2021-04-18 19:12 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 18:43 Timothy
2021-04-17 23:29 ` Thomas S. Dye
2021-04-18  1:56   ` Tim Cross
2021-04-18 19:39     ` Timothy
2021-04-18 22:45       ` Tim Cross
2021-04-19 21:43     ` David Masterson
2021-04-19 22:21       ` Gustav Wikström
2021-04-23  0:16         ` David Masterson
2021-04-19 23:46       ` Tim Cross
2021-04-20  8:21         ` Tom Gillespie
2021-04-23  0:34           ` David Masterson
2021-04-20  9:28       ` Jean Louis
2021-04-23  0:38         ` David Masterson
2021-04-18  5:04   ` Timothy
2021-04-18 18:45     ` Thomas S. Dye
2021-04-18 19:12       ` Timothy [this message]
2021-04-18 19:46         ` Thomas S. Dye
2021-04-18 19:59           ` Timothy
     [not found] ` <a64adc3de7be49039372851ea31e4f7c@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com>
2021-04-19 10:04   ` Eric S Fraga
2021-04-20  3:54     ` Timothy
2021-04-19 22:07 ` Gustav Wikström
2021-04-21  9:33   ` Jean Louis
2021-04-21  9:50     ` Tim Cross
2021-04-21 10:25       ` Heinz Tuechler
2021-04-21 12:55         ` ian martins
2021-04-21 13:07         ` Timothy
     [not found]         ` <1c557c0e35e04440ba2dadfe57e5b590@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com>
2021-04-21 13:27           ` Eric S Fraga
2021-04-21 15:31             ` ian martins
2021-04-21 15:38               ` Bruce D'Arcus
2021-04-21 19:35                 ` Tim Cross
2021-04-22  0:36                   ` ian martins
2021-04-22  0:48                     ` Tim Cross
2021-04-22  2:35                       ` Timothy
2021-04-22  5:14                         ` Maintaining babel packages — a list of packages that need help? Dr. Arne Babenhauserheide
2021-04-22 10:10                           ` ian martins
2021-04-26  7:25                           ` Bastien
2021-04-22 10:00                       ` Concerns about community contributor support ian martins
2021-04-21 19:31             ` Tim Cross
2021-04-25  4:30 ` Bastien
2021-04-25  5:52   ` Contributor Steward role (was Re: Concerns about community contributor support) Timothy
2021-04-25  7:13     ` Bastien
2021-04-25  6:17   ` Concerns about community contributor support Tim Cross
2021-04-25  7:19     ` Bastien
2021-04-26  0:23       ` Tim Cross
2021-04-26  5:00         ` Bastien
2021-04-26  6:07           ` Tim Cross
2021-04-26  7:34             ` Bastien
2021-04-25 10:10   ` Help with reproducing bugs reported on this list (was: Concerns about community contributor support) Bastien
2021-04-27  6:28     ` Help with reproducing bugs reported on this list Bastien
2021-04-25 21:40   ` Concerns about community contributor support Nick Savage
2021-04-26  7:22     ` Bastien
2021-04-29 14:07 ` D
2021-04-29 14:16   ` Bastien
2021-04-29 14:44     ` D
2021-04-29 14:29   ` Ihor Radchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://orgmode.org

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87blabo1a4.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.online \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Org-mode mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://orgmode.org/list/0 list/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 list list/ https://orgmode.org/list \
		emacs-orgmode@gnu.org
	public-inbox-index list

Example config snippet for mirrors.
Newsgroups are available over NNTP:
	nntp://news.yhetil.org/yhetil.emacs.orgmode
	nntp://news.gmane.io/gmane.emacs.orgmode


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git