+1 on camel-issues.
Notifications could go to commits@ imho. It's not that hard to filter. I
am a +0 on this one.
Hadrian
On 10/26/2011 07:54 PM, Daniel Kulp wrote:
On Thursday, October 27, 2011 12:03:49 AM Christian Müller wrote:
At present, we have four sub-forums:
- camel-users
- camel-commits
- camel-development
- camel-extra
What's about adding a fifth sub-forum "camel-issues" (as we already have for
CXF) and send all [jira] messages into this forum?
+1
It makes perusing the mail archives a LOT easer to not have all the JIRA stuff
in there. Finding the onlist discussions is much simpler. Just look at the
difference between:
http://mail-archives.apache.org/mod_mbox/cxf-dev/201110.mbox/browser
and
http://mail-archives.apache.org/mod_mbox/camel-dev/201110.mbox/browser
THAT said, there is a slight downside. In some cases, people say "hey, I
have an issue, post to issues@.." so people do have to be diligent to watch
for "real" things in there and direct them back here.
Also, you want to make sure infra sets up the reply-to to be dev@ so any non-
JIRA discussions go to dev list.
Another thing to "consider" would be a notifications@ list for Jenkins
notifications. Right now, we only have notifications going to those that
have committed things. Nothing logged or archived.
I could imagine we have to much messages in the camel-development forum
which are not really interesting for the developers subscribed to this list.
Maybe this is the reason why some discussions are not very active. Maybe we
overlooked they...
