On Wednesday, 15 April 2020 12:02:17 CEST Christian wrote:

Hi,

nowadays there are strage side effects for SuSE packaging (new rules???):

### comment abouts declining a Submit Request ### - "update to 0.95.9" Upper case please. Same for 'rebase' etc... - You should use upper case for the first word. Not "update to 0.95.9" but "Update to 0.95.9".

Iff this is the only reason to reject, it seems somewhat questionable. On the other hand, there are some rules for changelog entries, and though spelling and grammar are some of the lesser concerns people should try to get it right. After all, if the submitter corrects it it's work done once, otherwise every reader has to correct it. Unfortunately, your message is missing any references, so its hard to say how many changes were requested, and if there was something more serious among the reasons.

Are you SUSE guys _serious_ ??? Is this the way you encourage community to do volunteer work and deny their effort ?

Yelling at people is probably not the best way to be get heard. The rejection of the submission is not blank denial. The reviewer found some things which could be improved. It would have taken you probably 10 seconds to correct any typos etc., and resubmit it. And please remember, the maintainer is probably also a volunteer (even people working for SUSE often maintain packages in their spare time). Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019

Am 15.04.20 um 13:26 schrieb Stefan Brüns:

On Wednesday, 15 April 2020 12:02:17 CEST Christian wrote:

...

Hi,

nowadays there are strage side effects for SuSE packaging (new rules???):

### comment abouts declining a Submit Request ### - "update to 0.95.9" Upper case please. Same for 'rebase' etc... - You should use upper case for the first word. Not "update to 0.95.9" but "Update to 0.95.9".

Iff this is the only reason to reject, it seems somewhat questionable. This is not only questionable ...

On the other hand, there are some rules for changelog entries, and though spelling and grammar are some of the lesser concerns people should try to get it right. After all, if the submitter corrects it it's work done once, otherwise every reader has to correct it.

I know the rules (most of them). I am not contributing since yesterday. And I did more contributions to that package in the past than the "maintainer" himself ...

Unfortunately, your message is missing any references, so its hard to say how many changes were requested, and if there was something more serious among the reasons.

https://build.opensuse.org/request/show/792020

...

Are you SUSE guys _serious_ ??? Is this the way you encourage community to do volunteer work and deny their effort ?

Yelling at people is probably not the best way to be get heard.

You don't want me to hear when I am really yelling ...

The rejection of the submission is not blank denial. The reviewer found some things which could be improved. It would have taken you probably 10 seconds to correct any typos etc., and resubmit it.

If he prefers to have it this way he schould do it on his own, and not bossing around the submitter with nonsense like this.

And please remember, the maintainer is probably also a volunteer (even people working for SUSE often maintain packages in their spare time).

If this is really the case, then why is disrespecting volunteer work ???

Regards,

Stefan

-- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------

On Wednesday, 15 April 2020 13:42:45 CEST Christian wrote:

Am 15.04.20 um 12:17 schrieb Adam Majer:

...

This is not SUSE guys or some policy. This is probably just someone nitpicking because they can. But given how bad we are at making readable changelogs entries in internal submissions, I'm not sure that upper/lowercase is really a valid reason to reject.

Yes, it is nitpicking

see also https://build.opensuse.org/request/show/792020

As the lone reason, it would have been. But the SR was rejected because a patch was disabled, breaking reproducible builds. You had to fix the SR anyway, why you did not respect the maintainers request to also fix any typos while at it is beyond my understanding. Michael (jubalh) gave you an nice and encouraging answer, and asked you to change it. ("Much better! But like I mentioned in the first review. You should use upper case for the first word.") But instead of investing 10 seconds and change the remaining typos, your behavior became just inacceptable IMHO: "Wenn Du ein großes 'U' haben willst, dann mach es Dir selber in einem deiner nächsten _U_pdates !!! Du hast doch nicht mehr alle Latten am Zaun !!! Bist wohl Quarantäne geschädigt" "If you want a big 'U', make it yourself in your next _U_pdate !!! You are completely out of your mind !!! You seem damaged by the quarantine" Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019

On Wed, 2020-04-15 at 13:57 +0200, Dan Čermák wrote:

Christian writes:

...

Am 15.04.20 um 12:17 schrieb Adam Majer:

...

This is not SUSE guys or some policy. This is probably just someone nitpicking because they can. But given how bad we are at making readable changelogs entries in internal submissions, I'm not sure that upper/lowercase is really a valid reason to reject. Yes, it is nitpicking

...

For myself at least, a valid reason to reject is to have a version update without any change mentioned.

my entries to changes file: - update to 0.95.9 * SwitchPanel is now more configurable: you can configure the switch panel icon size by setting the “SwitchPanelIconSize” option to your preferred value in ~/GNUstep/Defaults/WindowMaker. The font size used in this panel now is also sensible to changes in the system font. * New user configuration directory environment variable: In previous versions, the GNUstep directory used to store a user’s Window Maker configuration files was specified by the GNUSTEP_USER_ROOT environment variable, which defaulted to ~/GNUstep. However, this environment variable was deprecated in gnustep-make v2. Therefore, it has been replaced by the WMAKER_USER_ROOT environment variable. * libXmu is now an optional dependency If the library is not found, compilation work, the only limitation will arise when trying to install the standard colormap on displays which are not TrueColor. Please note that if you have the library but not the headers, configure will still stop; there is no user option to explicitly disable the library use. - rebase patches * WindowMaker-config.patch * WindowMaker-menu.patch - rework reproducible patch * remove WindowMaker-0.95.8-reproducible.patch * add WindowMaker-reproducible.patch

see also https://build.opensuse.org/request/show/792020

No offense Christian, but while the reviewer's comments might be nitpicking, your reaction in the superseeded request is absolutely *not* acceptable. Insulting the package maintainer is not ok, even if you don't agree with their wish to have a capitalized U. +9000

That does not mean that this couldn't have been handled better by both sides, but once you start insulting people, you imho should not complain about u-vs-U. I could not agree more

That being said obviously u-vs-U was not the only reason for declining the request, as already noticed by others in this thread. If anything you owe package maintainer apology for your rude behavior, same as to subscribers of this mailing list for wasting our time by trying to pull us into some sort of personal vendetta of yours. Regards Martin -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Are you seriously using an ongoing global pandemic as your punchline? Please, just stop. On Wed, 2020-04-15 at 12:02 +0200, Christian wrote:

Hi,

nowadays there are strage side effects for SuSE packaging (new rules???):

### comment abouts declining a Submit Request ### - "update to 0.95.9" Upper case please. Same for 'rebase' etc... - You should use upper case for the first word. Not "update to 0.95.9" but "Update to 0.95.9".

Are you SUSE guys _serious_ ??? Is this the way you encourage community to do volunteer work and deny their effort ?

I hope not ... thanks

-- Atri Bhattacharya -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Hi, On Wed, 15 Apr 2020 14:03:01 +0200 Stefan Brüns wrote:

On Wednesday, 15 April 2020 13:42:45 CEST Christian wrote:

...

Am 15.04.20 um 12:17 schrieb Adam Majer:

...

This is not SUSE guys or some policy. This is probably just someone nitpicking because they can. But given how bad we are at making readable changelogs entries in internal submissions, I'm not sure that upper/lowercase is really a valid reason to reject.

Yes, it is nitpicking

...

see also https://build.opensuse.org/request/show/792020

As the lone reason, it would have been. But the SR was rejected because a patch was disabled, breaking reproducible builds.

You had to fix the SR anyway, why you did not respect the maintainers request to also fix any typos while at it is beyond my understanding.

Yes, this was my thinking. I just thought if he has to change something anyway, then let's make it totally right. On Wed, 15 Apr 2020 12:02:17 +0200 Christian wrote:

Are you SUSE guys _serious_ ??? Is this the way you encourage community to do volunteer work and deny their effort ?

What makes you think this has to do with me working for SUSE? I was an openSUSE contributor and user before and probably will be after. Honestly I don't see where I acted discouraging or rude. To me it looks like this happened: - You create SR#792020. Which is an update, edit of changes and disabling of patches. - I say: "why do you disable the reproducible patch? "update to 0.95.9" Upper case please. Same for 'rebase' etc." - Your answer contains three questionmarks. I don't know why, I guess either because you are very curious or already upset because I ask a simple question: "cause the code changed and the used "../../ChangeLog" does not exist ... so how should it work then ???" - To which I answer that you can make the patch work because the changelog is still there. So you didn't even care to look at the patch clearly, but just disabled it without any notice in the changelog. Which can happen to all of us, sometimes we are lazy. No problem, but if you get asked about it, why is it such a problem? Why not fix it if you want to contribute and improve things? - So you answer "ok ok ... did dig into it and did rework a level higher ... superseed will follow" which is nice. So after asking you two times you actually cared enough to fix the patch. And it means you took the time and touched the changelog and the package again. So at that time, why didn't you just change to uppercase? - You create SR#793111 which I decline because of the uppercase (which I told you about right from the start, when there was also something bigger to change) - You get upset, using several questionmarks again, which to me makes it likely that you were upset before already. Then you start to be quite unfriendly attacking me personally. And after that you come here and try to paint it like you have been treated unfairly by a "SUSE guy" and "maintainer god". Already the assumption that you are treated wrong by a person because that person works for a company is strange to me. I'm just a maintainer like any other. And the assumption that I want to express "power" by declining submit requests is also a funny one. Sometimes I do submit requests and have to adapt my changes 8 times because the maintainer doesn't like it as is. Often they also don't tell all changes in the first review but in each review pick on something else. I can't remember a fight breaking loose from it. Most of the time they are right and their way is a bit cleaner/better/more accurate. In any case, I just do it if it's not wrong. Otherwise I discuss. So I guess the question is what will happen now (since you just reopened the SR). And I guess I'll just accept it, change to uppercase myself, and move on. But I'm not sure whether I will have the feeling that your contribution was a good use of everybodys time and energy. And that a feeling of community work will prevail. Best, Michael -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Am Mittwoch, 15. April 2020, 12:02:17 CEST schrieb Christian:

Hi,

nowadays there are strage side effects for SuSE packaging (new rules???):

### comment abouts declining a Submit Request ### - "update to 0.95.9" Upper case please. Same for 'rebase' etc... - You should use upper case for the first word. Not "update to 0.95.9" but "Update to 0.95.9".

Are you SUSE guys _serious_ ??? Is this the way you encourage community to do volunteer work and deny their effort ?

Apart what being said already, having a readable changelog carries value on its own. As a rule of thumb, mimic existing patterns improves this notion.k Have a look at the entries. Interestingly, you seem to insist in keeping your style (starting entries with lower case). You might not notice, but such behavior carries subliminal rudeness of some kind. Cheers, Pete Stupidity is a contagious sociosemantic disturbance which afflicts all of us. Robert Anton Wilson -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org