Vova, I've also started such topic about GitBox messages ( https://lists.apache.org/thread.html/1870ba56e0eb9e184d055ef2c84114ea43219d7c845036566f68e880@%3Cdev.ignite.apache.org%3E ). But it seems no one reacted.
I agree to move out GitHub PR notifications + GitBox messages (see a solution in the thread). I disagree about test failures, because a contributor may just disappear after a fix, and someone else should pick up the test fix. If we will be open, positive and welcoming we will be still in top-5 dev. lists, because we have something to say :) Here are some thoughts about busy lists that - might help to be open, - help everyone to feel free to discuss things - help to notice a useful staff https://grep.codeconsult.ch/2011/12/06/stefanos-mazzocchis-busy-list- pattern/ Sincerely, Dmitriy Pavlov вт, 6 нояб. 2018 г. в 17:31, Vladimir Ozerov <voze...@gridgain.com>: > Igniters, > > I noted that the most common action I do on the devlist is clicking "Mark > As Read". All I see is JIRA and GitHub notifications. I simply counted last > 100 threads and found that 89 of them are automated messages, 2 are MTCGA > bot messages, and 9 are real human-created threads. > > Looks like human-created threads are drown inside generated stuff. As > potentially new contributor you will hardly figure out what is going on. > Does any info about opened tickets and PRs help anyone? Don't we want > instead to have a list like this [1] and move all generated stuff to > separate lists? > > The only drawback I see from this action is that we no longer be able to > brag about "Top 5 active devlist" in annual ASF summary :-) > > Thoughts? > > Vladimir. > > [1] http://apache-spark-developers-list.1001551.n3.nabble.com/ >
