Proposal: Handling the community in the Open Source

link: Handling the community in the Open Source

Few thoughts:

  1. i hope there is enough nuance in the slides/talk to remind the audience to avoid being prejudiced towards these “known patterns” of people.

    The critic: This category would criticize your work,
    if they don’t get a reply within minutes they would blame the company, the environment, and the people too.
    Even though we never met them.

    Every criticism is not going to be a toxic flamer.
    Remind folks to have an open-mind and NOT be fast to jump to judgement.

  2. Regarding working efficiently in public,
    many of the principles involved in Asynchronous communication are relevant.

  3. Building a community is much more than simply publishing some source-code.
    The Seven Deadly Sins of Open Source Communities by Brian Proffitt

1 Like

Thank you @CVS for the feedback.

Every criticism is not going to be a toxic flamer.

Yes in the slide/talk we are going to handle how we handle these kinds of people and how positive criticism helped us over time.

Regarding working efficiently in public,
many of the principles involved in Asynchronous communication are relevant.

We do follow asynchronous communications but this we can’t expect from clients/customers they always expect replies right away, and when I say this I don’t blame every open-source customer out there. This is just 10-20% of people who take more time than you think, mainly because they have never followed the async working environment before or are just not used to it.

Building a community is much more than simply publishing some source code.

Agreed.

I will be updating my slides according to this. Let me know if you want me to change the proposal submission too.