+1 for me too. Should be simpler. Le lun. 12 avr. 2021 à 19:51, Bart Maertens <[email protected]> a écrit :
> How about we start by adding a pointer to the ASF CoC to our community > pages? > > We could add the checklist Matt provided. As the CoC states, we should > assume that "bad behaviour" is unintentional in a lot of (or most) cases. > We could add a couple of items to the checklist from the other point of > view: "how can I ask for help or get answers to my questions in a > non-offensive way"? > > I assume these pages will mostly be read by people who are on the receiving > end of negative behavior and will only be needed on very rare occasions, > but at least it gives us a document to point to in case the need arises. > > Regards, > Bart > > > > On Mon, Apr 12, 2021 at 5:46 PM Julian Hyde <[email protected]> wrote: > > > Thanks for starting this conversation, Matt. FYI, ASF has a CoC [1] > > and it automatically applies to the Hop community, but it's great if > > Hop wants to extend it with its own culture/values. > > > > Julian > > > > [1] https://www.apache.org/foundation/policies/conduct > > > > On Mon, Apr 12, 2021 at 7:40 AM Matt Casters > > <[email protected]> wrote: > > > > > > Dear Hoppers, > > > > > > In our short history we've been on the receiving end of very little > > > negative feedback. It's been a very fun experience to help each other > > out > > > and the source code in general is very accomodating to doing your own > > thing > > > in your own plugin without getting in the way of others. > > > > > > However, when negative feedback does come on occasion (it does and it > > will) > > > we need to be a bit more prepared for it. As such I would like to > have > > a > > > developer/community "code of conduct" on our website so that we can > help > > > people to react appropriately to negative feedback. > > > > > > I believe that in essence any conflict in software or architecture is > an > > > opportunity for improvement. I would very much like such an attitude > to > > be > > > the leading principle in this scenario. > > > > > > Can we come up with a list of advice for recipients of negative > feedback? > > > Or perhaps a checklist? > > > > > > - Take a deep breath, read the message a few more times. Do not reply > > > immediately. > > > - If you can not give a constructive response, consider not responding > at > > > all or with a question asking for clarification. > > > - Empathically consider that the person in question is perhaps > > frustrated / > > > using a foreign language / stressed out / in a pinch / ... > > > - If you feel you are bothered by the feedback; can you figure out > > > why exactly this is? The tone of the feedback should be disregarded. > > Its > > > actual content should be taken seriously. > > > - Consider the opportunities for improvement of our software. A lot of > > > people take software as is and are not even aware that we can fairly > > > quickly change a lot of things. > > > - Consider creating JIRA cases based on the feedback to capture > negative > > > feedback with bug reports, improvements or even taks for architectural > > > changes. > > > > > > Anyway, feel free to pile on. > > > Cheers, > > > Matt > > >
