+1 (nonbinding) to at least announcing major architectural improvements on dev email.
I don’t know that it’s going to help encourage more contributors like Chris suggests, but it seems like at worst it won’t hurt, and certainly should help make people aware of Jiras that would otherwise slip by unnoticed. On 8/15/16, 7:22 AM, "Jonathan Ellis" <jbel...@gmail.com> wrote: >A long time ago, I was a proponent of keeping most development discussions >on Jira, where tickets can be self contained and the threadless nature >helps keep discussions from getting sidetracked. > >But Cassandra was a lot smaller then, and as we've grown it has become >necessary to separate out the signal (discussions of new features and major >changes) from the noise of routine bug reports. > >I propose that we take advantage of the dev list to perform that >separation. Major new features and architectural improvements should be >discussed first here, then when consensus on design is achieved, moved to >Jira for implementation and review. > >I think this will also help with the problem when the initial idea proves >to be unworkable and gets revised substantially later after much >discussion. It can be difficult to figure out what the conclusion was, as >review comments start to pile up afterwards. Having that discussion on the >list, and summarizing on Jira, would mitigate this. > >-- >Jonathan Ellis >Project Chair, Apache Cassandra >co-founder, >https://urldefense.proofpoint.com/v2/url?u=http-3A__www.datastax.com&d=DQIBaQ&c=08AGY6txKsvMOP6lYkHQpPMRA1U6kqhAwGa8-0QCg3M&r=yfYEBHVkX6l0zImlOIBID0gmhluYPD5Jje-3CtaT3ow&m=sw6DH_A1qpHeVAQNIUqFE0MwHlAsEAfFgqpciRBV2JY&s=bo665yjr_ozrH_nDYzW1afy_N8N3JJ_TTPaB2rkghYM&e= > >@spyced
smime.p7s
Description: S/MIME cryptographic signature
