On 5/11/07, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
On Thu, 10 May 2007, Gilles Scokart <[EMAIL PROTECTED]> wrote: > Shouldn't we define guidelines on how/when to use jira. > > More particularly: Should we use jira to discuss some new features, > or when we want to propose a new feature but we don't have a precise > idea of how this feature should look like. Each project is free to create their own guidelines for this, as long as in the end all discussion is archived and decisions are made on a mailing list. Most ASF people prefer email over websites, that's why we have mailing lists instead of some kind of forum. I for one prefer to have discussions land in my mailbox instead of having to actively look for them in a browser,
I follow the jira "discussions" from my mail box too, by subscribing to the ivy-commit list. and I prefer to use the mail client to participate
in them as well.
Sure it's much easier.
Or alternatively, should we always use the mailing list to discuss > first (dev or user?), and only enter an issue when a consensus is > reached? Would be my preference, but it is your (as in the Ivy's community's) decision how to use JIRA - as long as you make sure you summarize the discussion to the list and make decisions here.
I agree for the decisions, but do we have to summarize the discussion to the list since it's already recorded on the ivy-commit list? Xavier Stefan
-- Xavier Hanin - Independent Java Consultant Manage your dependencies with Ivy! http://incubator.apache.org/ivy/
