cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Yadav <>
Subject [DISCUSS] Improving community experience for (new) contributors
Date Wed, 26 Aug 2015 10:20:41 GMT
Hi all,

I’ve identified few issues around the recent changes that I don’t know
how we can fix or improve but I hope to get feedback from the

I understand that you may disagree with what I’m sharing which is
alright, even in your disagreement I hope that you don’t take an
offence on that, that is certainly not my aim. I personally want to
the community to be felt welcoming so that we can attract and retain
new contributors and have a nice environment for everyone.

Some observations and comments:

- Generally those of us who have worked for long in the community or
have colleagues from dayjob working in the ACS community - we have
better chances in getting their PRs merged; for new contributors this
pattern is not encouraging and certainly not welcoming if their PRs
get closed.

- The recent drive to use Github PRs seems to be really working great
for us, but still the requirements of at least 2 +1s/LGTM, unit tests
and pedantic bike-shedding has cost us new developers/contributors and
kills the joy of programming for some; for experienced and
commercially backed developers this makes sense. I personally try to
be pragmatic and lenient on code reviews as long as smoke tests
(Travis) pass.

- Contributions are process-oriented that cost time and effort; there
have been initiative to satisfy the tool but not the human, and not
optimizing on developer time.

- What should we do to get more developer contributors and how to
attract hobbyists or casual contributors.


View raw message