The advantage of jira is that the person working on the issues sees
the posted comments, the advantage of the mailing list is to have more
clear threads with more readable subjects.
My suggestion thus is:
- Post to jira comments and hints for the implementer, review comments
on concrete code suggestions "In path #5675 you modify Foo.scala but
the comment has not been changed, please...". Also you might post
questions with supposedly uncontroversial answers to jira ("how do I
add a customized greeting message?"), broader questions ("isn't the
named graph approach fundamentally wrong?") should go to the mailing
list
- Start a thread on the mailing list to discuss questions regarding
the broader architecture. So when fundamentally questioning the need
for an issue start a thread on the mailing-list and only post a link
with the issue. The reason for this is that such discussions require
the big picture and canot be easily be attributed to the individual
issues. Also once there is a consensus that ISSUE-XY should be
addressed the whole discussion might be of little use to the
implementer.
Reto
