Re: Requests and the etiquette involved
I, for one, have never heard of using “w” as “without”. W much, much commonly means “with”.
On Nov 22, 2023, at 9:31 AM, Björn Bidar <bjorn.bidar@thaodan.de> wrote:
Hey,
I fully agree with that statement. The automated checks can only go so far. Of course there are cases where the package has been out of date for longer, however even in such cases the packager might have forgotten to update the package after he got the request or there was an issue on their side. E.g. on case I did an update but forgot to push it.
I also noticed that more users use out-of-date flags as a way to bug the maintainer of a package for attention.
I had a package teams-for-linux-wbunbled-electron that was simply deleted/merged after such a request because the author of the request didn't understood what w as in without means.
I would favor that before a request is send the user should try to send a comment or request simply shouldn't be automatically accepted before the user has time to reply e.g. after at least a week to reply. Sometimes it feels like users except that there is an update at day 1.
Br,
Björn
In the U.S, a common abbreviation is w/ for "with" and w/o for "without". On Wed, Nov 22, 2023, 9:42 AM Lime In a Jacket (Aaron Liu) < aaronliu0130@gmail.com> wrote:
I, for one, have never heard of using “w” as “without”. W much, much commonly means “with”.
On Nov 22, 2023, at 9:31 AM, Björn Bidar <bjorn.bidar@thaodan.de> wrote:
Hey,
I fully agree with that statement. The automated checks can only go so far. Of course there are cases where the package has been out of date for longer, however even in such cases the packager might have forgotten to update the package after he got the request or there was an issue on their side. E.g. on case I did an update but forgot to push it.
I also noticed that more users use out-of-date flags as a way to bug the maintainer of a package for attention.
I had a package teams-for-linux-wbunbled-electron that was simply deleted/merged after such a request because the author of the request didn't understood what w as in without means.
I would favor that before a request is send the user should try to send a comment or request simply shouldn't be automatically accepted before the user has time to reply e.g. after at least a week to reply. Sometimes it feels like users except that there is an update at day 1.
Br,
Björn
Sorry for top-posting, but it's a quick one. Abbreviations causes confusion. If you are going to write a huge email anyways, please take the time to write out the words properly. Your communication would be a lot more clear, and you might get your point across more effectively. On Wed, 22 Nov 2023 at 17:18, Eric <eric2043@gmail.com> wrote:
In the U.S, a common abbreviation is w/ for "with" and w/o for "without".
On Wed, Nov 22, 2023, 9:42 AM Lime In a Jacket (Aaron Liu) < aaronliu0130@gmail.com> wrote:
I, for one, have never heard of using “w” as “without”. W much, much commonly means “with”.
On Nov 22, 2023, at 9:31 AM, Björn Bidar <bjorn.bidar@thaodan.de> wrote:
Hey,
I fully agree with that statement. The automated checks can only go so far. Of course there are cases where the package has been out of date for longer, however even in such cases the packager might have forgotten to update the package after he got the request or there was an issue on their side. E.g. on case I did an update but forgot to push it.
I also noticed that more users use out-of-date flags as a way to bug the maintainer of a package for attention.
I had a package teams-for-linux-wbunbled-electron that was simply deleted/merged after such a request because the author of the request didn't understood what w as in without means.
I would favor that before a request is send the user should try to send a comment or request simply shouldn't be automatically accepted before the user has time to reply e.g. after at least a week to reply. Sometimes it feels like users except that there is an update at day 1.
Br,
Björn
participants (3)
-
Eric
-
Evert Vorster
-
Lime In a Jacket (Aaron Liu)