If someone is a very active contributor, he/she is most likely watching the
commit list as well as the dev list. If someone is just subscribed to the
dev list to watch the key discussions and occasionally gets involved, he/she
would not want to see all the JIRA updates. This assumes that new
ant elder wrote:
On Feb 6, 2008 5:28 PM, Simon Nash [EMAIL PROTECTED] wrote:
snip
One other consideration - sometimes it's appropriate to reply to a
JIRA rather than updating the issue: if there are two lists, on has to
decide - should the replies go to both or just dev?
In such a case I
On Feb 6, 2008 5:28 PM, Simon Nash [EMAIL PROTECTED] wrote:
snip
One other consideration - sometimes it's appropriate to reply to a
JIRA rather than updating the issue: if there are two lists, on has to
decide - should the replies go to both or just dev?
In such a case I think the reply
sebb wrote:
Jean-Sebastien Delfino wrote:
Or can we configure JIRA to only send a message when a comment is added
to an issue?
Surely one needs all the JIRA changes?
You're right, I was initially thinking that we could cut on the number
of useless JIRA notifications, but after reviewing a
ant elder wrote:
On Feb 6, 2008 5:28 PM, Simon Nash [EMAIL PROTECTED] wrote:
snip
One other consideration - sometimes it's appropriate to reply to a
JIRA rather than updating the issue: if there are two lists, on has to
decide - should the replies go to both or just dev?
In such a case I
that could help improve our diversity? Does aiming for the April
board meet sound ok or too soon or too far?
...ant
I've gone through everything suggested so far in this thread and added all
the points to a wiki page -
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Graduation+Next+Steps
in this thread and added all
the points to a wiki page -
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Graduation+Next+Steps.
I've probably missed some and there are some duplicate points, feel free to
edit the page.
So what to do with this? Some of the points are a bit vague, some we may
diversity? Does aiming for the
April
board meet sound ok or too soon or too far?
...ant
I've gone through everything suggested so far in this thread and added
all the points to a wiki page -
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Graduation+Next+Steps
On Feb 4, 2008 8:06 PM, Simon Nash [EMAIL PROTECTED] wrote:
snip
- route the JIRA traffic out of the dev list as suggested by Matthieu
I understand that this traffic can get a bit overwhelming at times, but
I'd like to make the case that it does have value for new developers
(though not
I like to be able to look at a JIRA and readily find the discussion relating
to it, so I find having technical discussion as a series of comments in the
JIRA helpful. In this pattern it makes sense to copy JIRA comments to the
dev list, as it forms the substance of our technical communication. I
If we are going to remove JIRAs from dev list, my personal preference
would be to have a notification list and have JIRA, Build
notifications, etc sent to this list. But I'm still not convinced that
moving JIRA out of the dev mailing list is the best solution here.
On Feb 6, 2008 5:26 AM, ant
/display/TUSCANYWIKI/Graduation+Next+Steps
.
I've probably missed some and there are some duplicate points, feel free
to
edit the page.
So what to do with this? Some of the points are a bit vague, some we may
not
all agree with, some are easy for one person to action if we agree, others
need more
Venkata Krishnan wrote:
Typically these discussions have multiple aspects to it and we end up
bringing perspectives to each aspect. If there is such a topic then I'd
think the WIKI is a good place. There could be one description of the
problem and comments by the community at various points.
sebb wrote:
On 05/02/2008, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Nash wrote:
Jean-Sebastien Delfino wrote:
[snip]
- route the JIRA traffic out of the dev list as suggested by Matthieu
I understand that this traffic can get a bit overwhelming at times, but
I'd like to make
PROTECTED]
Sent: Wednesday, February 06, 2008 8:00 AM
Subject: Re: Graduation next steps
If we are going to remove JIRAs from dev list, my personal preference
would be to have a notification list and have JIRA, Build
notifications, etc sent to this list. But I'm still not convinced that
moving JIRA
Simon Nash wrote:
Jean-Sebastien Delfino wrote:
[snip]
- route the JIRA traffic out of the dev list as suggested by Matthieu
I understand that this traffic can get a bit overwhelming at times, but
I'd like to make the case that it does have value for new developers
(though not for users).
On 05/02/2008, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Nash wrote:
Jean-Sebastien Delfino wrote:
[snip]
- route the JIRA traffic out of the dev list as suggested by Matthieu
I understand that this traffic can get a bit overwhelming at times, but
I'd like to make the case
On Feb 5, 2008 10:09 AM, sebb [EMAIL PROTECTED] wrote:
snip
However few (if any) mail archives seem to offer such facilies and so
can be difficult to read if there are lots of JIRA messages mixed in
with the rest.
Thats a good point. Up till now I've thought its better to have the JIRA
Jean-Sebastien Delfino wrote:
Simon Nash wrote:
Jean-Sebastien Delfino wrote:
[snip]
- route the JIRA traffic out of the dev list as suggested by Matthieu
I understand that this traffic can get a bit overwhelming at times, but
I'd like to make the case that it does have value for new
Typically these discussions have multiple aspects to it and we end up
bringing perspectives to each aspect. If there is such a topic then I'd
think the WIKI is a good place. There could be one description of the
problem and comments by the community at various points. So at any time one
knows
Venkata Krishnan wrote:
Typically these discussions have multiple aspects to it and we end up
bringing perspectives to each aspect. If there is such a topic then I'd
think the WIKI is a good place. There could be one description of the
problem and comments by the community at various points.
: Graduation next steps
Simon Laws wrote:
On Jan 31, 2008 1:41 PM, ant elder [EMAIL PROTECTED] wrote:
I'd like to get some discussion going on what we want to do for
graduating
to an Apache TLP.
The attempt back in November raised issues about diversity and since
then
it
feels like we've just
My +1 as well to all the points that have been brought out. I am certainly
for picking out a couple rightaway and starting with some baby steps.
I think we must have an IRC session soon to review our JIRAs.
Thanks
- Venkat
2008/2/3, Jean-Sebastien Delfino [EMAIL PROTECTED]:
There's a lot i think the project could do to encourage others to
participate, here's a few things I can think of -
We have a lot of downloads and real users, we need to try to get more of
these people engaged and contributing, things
Giorgio Zoppi wrote:
2008/2/3, Jean-Sebastien Delfino [EMAIL PROTECTED]:
There's a lot i think the project could do to encourage others to
participate, here's a few things I can think of -
We have a lot of downloads and real users, we need to try to get more of
these people engaged and
I'm happy to see this discussion going and I think most of the points listed
make a lot of sense.
A small detail to add to the list that I think could have some importance:
your -dev list is flooded by Jira issues. Newcomers interested in Tuscany's
development are very likely to get overwhelmed
Matthieu Riou wrote:
I'm happy to see this discussion going and I think most of the points listed
make a lot of sense.
A small detail to add to the list that I think could have some importance:
your -dev list is flooded by Jira issues. Newcomers interested in Tuscany's
development are very
On Jan 31, 2008 1:41 PM, ant elder [EMAIL PROTECTED] wrote:
I'd like to get some discussion going on what we want to do for graduating
to an Apache TLP.
The attempt back in November raised issues about diversity and since then
it
feels like we've just been waiting around hoping diversity
I'd like to get some discussion going on what we want to do for graduating
to an Apache TLP.
The attempt back in November raised issues about diversity and since then it
feels like we've just been waiting around hoping diversity would improve. We
were unlikely then and we are almost there, would
29 matches
Mail list logo
