Hi Janne, On Oct 29, 2007, at 11:11 AM, Janne Jalkanen wrote:
Or simply create jspwiki-bugs which would get all the discussion.
This is an idea, although I don't know of any other project with this policy. One of the things that we encourage at Apache is reliance on lists to facilitate communication. And having lots of lists tends to defeat that objective.
I think it's actually okay to let everybody know about new issues (but not about edits or comments to existing ones - but possibly closed issues). That way people can actually take action on the new issues...
In other projects, I've seen a lot of discussion on jirs issues that is usefully seen by the developer community. Features as well as bugs can be discussed on jira and it's useful to have everyone see the discussion.
That said, I'm not committed to any particular strategy. Just looking to make sure we build a strong community here and using jira for communication in conjunction with email lists should help.
Regards, Craig
/Janne On Oct 29, 2007, at 20:06 , Craig L Russell wrote:Cool. I think the only issue will be if people on the dev list get tired of seeing all the jira traffic. I hope not.If need be, in future we could change it to jspwiki-commits which is a somewhat smaller list but let's see how it works for now.Craig On Oct 29, 2007, at 10:58 AM, Janne Jalkanen wrote:No worries, wasn't sure what the right report procedure was, so I just put something in for the meanwhile so that we don't miss any./Janne On Oct 29, 2007, at 19:32 , Craig L Russell wrote:Hi,I noticed that I was directly notified upon creation of JSPWIKI-11 and thought that strange, so I checked the notification scheme and updated it.I updated it so that now all of the notifications send mail to jspwiki-dev@ and I removed the specific notification for team lead and role committers.I also removed "current assignee" since jspwiki-dev@ should cover that.I retained "watchers" and "reporter" since these might not be part of the implementation team.Craig Craig RussellArchitect, Sun Java Enterprise System http://java.sun.com/ products/jdo408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!Craig RussellArchitect, Sun Java Enterprise System http://java.sun.com/products/ jdo408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
