You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Patrick Lightbody <fo...@opensymphony.com> on 2006/01/17 02:11:28 UTC
Non-discussion emails
I just realzied that the non-discussion emails (bugs, wiki, and commits) are going in to the forums. The account that is subscribed is forum-struts-dev@opensymphony.com. Is there any way we can disable those other emails to that account?
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=28683#28683
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Don Brown <mr...@twdata.org>.
I don't think anyone, and certainly not I, is arguing that wiki and ticket messages are somehow less important, only
that they are different, and perhaps viewed at different times or in different ways.
Just as those that prefer mail clients heavily use folders to sort their mail, I've found RSS readers to be a great way
to track different types of discussions or sites. I've found it productive personally to only use email for things I
need to respond to, i.e. interpersonal discussions. I keep my inbox completely empty and rarely use folders.
On the other hand, for my day job, I use the RSS feed from Trac to follow a project's "Timeline", or history of commits,
ticket updates, and wiki changes. Since 95% of the time I don't need to respond, the RSS approach works well.
My point is we need to keep an open mind, and allow people to use whatever tools or approaches they find most valuable.
This WebWork merger is bigger than a merging of code, but also one of people, development styles, project directions,
etc. We need to make an extra effort not to try force everyone to do it "our way" or reject new ideas or styles
outright. I'm not saying anyone is doing that currently, but we must be extra vigilant to protect against it.
If Struts is going to be accepting of what some would call two opposite web framework approaches, we should also be
tolerant, even encouraging, of different personal ideas, approaches, and perspectives.
</sermon> ;)
Don
Ted Husted wrote:
> On 1/17/06, Don Brown <mr...@twdata.org> wrote:
>
>>I'd like to see a compromise where I could sign up for mailing list that only contains
>>discussions, yet track tickets,
>>wiki updates, and commits via RSS. This discussion-only mailing list could be a second
>>mailing list that just
>>automatically filters out undesired messages.
>
>
> I guess what I don't understand is why relay one via RSS and not the other.
>
> The mailing list discussions may be free-form, but that does not make
> them more or less valuable than the discussions we have through the
> issue ticket, wiki, and repository logs.
>
> Wendy updates the release plan, and through the wiki log automatically
> discusses her changes with me and with the rest of us. Craig commits
> and automatically discusses what he just did and what he's going to do
> next. Looking over the issue tickets, every third or fourth turns into
> a discussion. Sometimes the discussion is: "Got a problem or a patch",
> followed by "Fixed", but that's a discussion nonetheless.
>
> What bothers me most is the implication that just because these logs
> are being forwarded from the issue tracker, or repository, or wiki,
> they are somehow less valuable than a free-form message. In practice,
> I'd say the opposite is more likely to be true. The *real* development
> decisions are being made on the tickets and in the commits. It's only
> the odds and ends that we discuss here.
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Ted Husted <te...@gmail.com>.
On 1/17/06, Don Brown <mr...@twdata.org> wrote:
> I'd like to see a compromise where I could sign up for mailing list that only contains
> discussions, yet track tickets,
> wiki updates, and commits via RSS. This discussion-only mailing list could be a second
> mailing list that just
> automatically filters out undesired messages.
I guess what I don't understand is why relay one via RSS and not the other.
The mailing list discussions may be free-form, but that does not make
them more or less valuable than the discussions we have through the
issue ticket, wiki, and repository logs.
Wendy updates the release plan, and through the wiki log automatically
discusses her changes with me and with the rest of us. Craig commits
and automatically discusses what he just did and what he's going to do
next. Looking over the issue tickets, every third or fourth turns into
a discussion. Sometimes the discussion is: "Got a problem or a patch",
followed by "Fixed", but that's a discussion nonetheless.
What bothers me most is the implication that just because these logs
are being forwarded from the issue tracker, or repository, or wiki,
they are somehow less valuable than a free-form message. In practice,
I'd say the opposite is more likely to be true. The *real* development
decisions are being made on the tickets and in the commits. It's only
the odds and ends that we discuss here.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Martin Cooper <ma...@apache.org>.
On 1/17/06, Don Brown <mr...@twdata.org> wrote:
>
> That's great for folks that manage their information via email and email
> folders, but not all do. I'm finding myself
> use RSS more and more to manage project, hobby, and personal information,
> leaving email only for correspondences that I
> need to respond to.
>
> I'd like to see a compromise where I could sign up for mailing list that
> only contains discussions, yet track tickets,
> wiki updates, and commits via RSS. This discussion-only mailing list
> could be a second mailing list that just
> automatically filters out undesired messages. This would leave struts-dev
> untouched, yet allow those that take the RSS
> path to not fill up their email boxes or have to setup new filters on
> multiple email clients (yes, I on an average day
> use 4 or 5 and it is a pain to keep them in sync).
>
> Anyways, it is important to remember that not everyone works in the same
> way or uses the same tools.
Agreed. It's also important to remember that, beyond keeping all of the dev
discussions in one place, one of the main reasons ASF projects are set up
this way, with commit messages and wiki changes going to the dev list, is
for legal oversight. That doesn't necessarily preclude other options, but
whatever else we do, we need to ensure that we retain oversight.
--
Martin Cooper
Don
>
> Martin Cooper wrote:
> > On 1/17/06, Sean Schofield <se...@gmail.com> wrote:
> >
> >>>IMHO, it sounds like Jive is not up to the task of managing an
> >>>ASF-style dev list. Any decent mailreader can filter mails into
> >>>whatever folders we find convenient, creating the personal equivalent
> >>>of five or six separate lists, if that's what someone wants.
> >>
> >>GMail also has *excellent* search capabilties. I find it to be
> >>superior to searching the public archives so I just never delete my
> >>mailing list emails!
> >
> >
> >
> > +1. All my open source mail goes to GMail. I have 50+ filters set up,
> and as
> > many labels, and it's really a snap to find anything (and not lose
> anything
> > important).
> >
> > --
> > Martin Cooper
> >
> >
> > BTW, there was talk of switching to JIRA a while back. I'm still +1
> >
> >>for that. Its a much nicer system and I find it less cumbersome then
> >>bugzilla. My point here is that its more tempting to "reply" to the
> >>bug in the proper place.
> >>
> >>
> >>>-Ted.
> >>
> >>Sean
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>For additional commands, e-mail: dev-help@struts.apache.org
> >>
> >>
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Non-discussion emails
Posted by Don Brown <mr...@twdata.org>.
That's great for folks that manage their information via email and email folders, but not all do. I'm finding myself
use RSS more and more to manage project, hobby, and personal information, leaving email only for correspondences that I
need to respond to.
I'd like to see a compromise where I could sign up for mailing list that only contains discussions, yet track tickets,
wiki updates, and commits via RSS. This discussion-only mailing list could be a second mailing list that just
automatically filters out undesired messages. This would leave struts-dev untouched, yet allow those that take the RSS
path to not fill up their email boxes or have to setup new filters on multiple email clients (yes, I on an average day
use 4 or 5 and it is a pain to keep them in sync).
Anyways, it is important to remember that not everyone works in the same way or uses the same tools.
Don
Martin Cooper wrote:
> On 1/17/06, Sean Schofield <se...@gmail.com> wrote:
>
>>>IMHO, it sounds like Jive is not up to the task of managing an
>>>ASF-style dev list. Any decent mailreader can filter mails into
>>>whatever folders we find convenient, creating the personal equivalent
>>>of five or six separate lists, if that's what someone wants.
>>
>>GMail also has *excellent* search capabilties. I find it to be
>>superior to searching the public archives so I just never delete my
>>mailing list emails!
>
>
>
> +1. All my open source mail goes to GMail. I have 50+ filters set up, and as
> many labels, and it's really a snap to find anything (and not lose anything
> important).
>
> --
> Martin Cooper
>
>
> BTW, there was talk of switching to JIRA a while back. I'm still +1
>
>>for that. Its a much nicer system and I find it less cumbersome then
>>bugzilla. My point here is that its more tempting to "reply" to the
>>bug in the proper place.
>>
>>
>>>-Ted.
>>
>>Sean
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Martin Cooper <ma...@apache.org>.
On 1/17/06, Sean Schofield <se...@gmail.com> wrote:
>
> > IMHO, it sounds like Jive is not up to the task of managing an
> > ASF-style dev list. Any decent mailreader can filter mails into
> > whatever folders we find convenient, creating the personal equivalent
> > of five or six separate lists, if that's what someone wants.
>
> GMail also has *excellent* search capabilties. I find it to be
> superior to searching the public archives so I just never delete my
> mailing list emails!
+1. All my open source mail goes to GMail. I have 50+ filters set up, and as
many labels, and it's really a snap to find anything (and not lose anything
important).
--
Martin Cooper
BTW, there was talk of switching to JIRA a while back. I'm still +1
> for that. Its a much nicer system and I find it less cumbersome then
> bugzilla. My point here is that its more tempting to "reply" to the
> bug in the proper place.
>
> > -Ted.
>
> Sean
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Non-discussion emails
Posted by Sean Schofield <se...@gmail.com>.
> IMHO, it sounds like Jive is not up to the task of managing an
> ASF-style dev list. Any decent mailreader can filter mails into
> whatever folders we find convenient, creating the personal equivalent
> of five or six separate lists, if that's what someone wants.
GMail also has *excellent* search capabilties. I find it to be
superior to searching the public archives so I just never delete my
mailing list emails!
BTW, there was talk of switching to JIRA a while back. I'm still +1
for that. Its a much nicer system and I find it less cumbersome then
bugzilla. My point here is that its more tempting to "reply" to the
bug in the proper place.
> -Ted.
Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Ted Husted <te...@gmail.com>.
On 1/17/06, Patrick Lightbody <fo...@opensymphony.com> wrote:
> I definitely understand where you are coming from, and I hope you can see where I'm
> coming from. Often when people have different work behaviors, the best bet is to provide
> more options. This can be done by somehow allowing individuals to opt out of those
> generated emails. I hope we can do something about this.
I think an important point is that these emails are being generated by
people. People are making the wiki changes, and people are creating
the issue tickets, and people are making the subversion commits. Each
and every one of those emails contains original input from a real
person that deserves the attention of the dev list.
The issue trackers posts are marked "DO NOT REPLY", because we want to
keep the discussion under the comments for each issue. So, to reply,
you follow the link to the ticket. But, by posting the status changes
to the ticket, we are all being kept abreast of what is happening on a
ticket, whether we click thru or not. We don't have to schedule time
to review the issue tracker, the issue tracker comes to us in real
time.
Case in point: Right now, Roller is being incubated, and we don't have
JIRA posting to the dev list yet. I created and posted a ticket over
the weekend. But, no one noticed until I made a second post to dev@
mentioning the ticket. Volunteers should not have to make a redundant
post to the mailing list when JIRA can do it automatically.
For a number of reasons, including legal ones, we do want all the
input and discussions, whether they take place on the wiki or the
issue tracker or anywhere else, to end up on a mailbox on an ASF
server.
Now, we could create a wiki@ mailing list and an issue@ mailing list,
to match the commit@ list, but now when people opt-in, they have to
opt into five lists instead of three. If we add a Roller blog to the
mix, then there would be six.
Right now, the ASF norm is three lists: That's what we create when
projects come through the Incubator.If we want more than that (and I'm
not sure that we do), I'd be happy to bring it up on the internal ASF
members list, to get input from other ASF communities. Perhaps someone
else here has already discussed having more lists at length, or even
tried more lists.
IMHO, it sounds like Jive is not up to the task of managing an
ASF-style dev list. Any decent mailreader can filter mails into
whatever folders we find convenient, creating the personal equivalent
of five or six separate lists, if that's what someone wants.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Joe Germuska <Jo...@Germuska.com>.
Sean, you write as if it's a zero-sum game. Sure, chat may exclude
those who aren't there, but it's not like decisions are only made in
chat rooms. I don't know of any way that code could be effectively
changed and committed from a chat room.
If people chat and decide to code something that non-chatting
committers didn't like, the non-chatting committers would express
their objections wherever they may, and vetos could happen, and all
the like.
I know a lot of projects use IRC and other chat strategies
successfully. I don't see how it can hurt anything, even if some of
us don't participate.
Joe
At 10:53 AM -0500 1/19/06, Sean Schofield wrote:
>The problem with chat is that not everyone is available to participate
>at the designated time that people decide to have a chat. As I
>mentioned earlier, there are timezone differences and day job
>commitments that make it difficult for everyone to participate in a
>discussion simultaneously.
>
>So by its nature, chat is exclusionary. I agree that its more
>expedient but it does not offer the chance for everyone to
>participate. My personal view of open source is that its not about
>what is most efficient. You give up certain efficiencies (like quick
>turnaround times) but you gain more then you give up (synthesis of
>great ideas, massive amounts of around the clock manpower.) A
>transcript is helpful but its basically a record of a conversation
>that took place without everyone's involvement.
>
>Sean
>
>
>On 1/18/06, Patrick Lightbody <fo...@opensymphony.com> wrote:
>> James,
>> We also agree that side conversations are no good, but that chat
>>can be helpful. To solve this, the WebWork forums have an XMPP chat
>>room attached to them, and each night the transcript of the chat is
>>added to the forums:
>>
>> http://forums.opensymphony.com/thread.jspa?threadID=14656
>>
>> I can set this up for the Struts forums too, but everyone needs to
>>be aware that emails could come as frequent as once a night in this
>>format.
>>
>> Patrick
>> ---------------------------------------------------------------------
>> Posted via Jive Forums
>>
>>http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=29283#29283
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>For additional commands, e-mail: dev-help@struts.apache.org
--
Joe Germuska
Joe@Germuska.com * http://blog.germuska.com
"You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed. Try something new."
-- Robert Moog
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Greg Reddin <gr...@apache.org>.
On Jan 19, 2006, at 9:53 AM, Sean Schofield wrote:
> A transcript is helpful but its basically a record of a conversation
> that took place without everyone's involvement.
Seeing as how I *never* have time to participate in chat, transcripts
would provide me with way more involvement than I currently have :-)
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Sean Schofield <se...@gmail.com>.
> Once the chat transcript is posted, people can reply to it
> asynchronously, like anything else. Back when we were setting up
> Maven, James and Wendy mentioned that had a few chats while getting
> everything configured. If they were chatting in a place that was
> automatically transcripted, some of us might know a little bit more
> about our infrastructure today :)
I agree with this (and have already said as much) when it comes to
infrastructure changes. And yes a record of these chats would be
helfpul.
> -Ted.
Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Sean Schofield <se...@gmail.com>.
> Trust me, you didn't miss anything. The things discussed offlist, as I do
> with yourself, Martin and others are almost always unrelated to decision
> making. I'm glad I was able to help Wendy and others get up to speed with
> what I had done so far with Maven, and since then she has far surpassed the
> extent of my Maven knowledge. Wendy is a regular Maven maven ;)
Don't worry. I wasn't referring to the infra/maven discussions. I
totally agree that those are more productive offline (once the basic
outline has been agreed to on the list.)
> James Mitchell
Sean
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by James Mitchell <jm...@apache.org>.
Trust me, you didn't miss anything. The things discussed offlist, as I do
with yourself, Martin and others are almost always unrelated to decision
making. I'm glad I was able to help Wendy and others get up to speed with
what I had done so far with Maven, and since then she has far surpassed the
extent of my Maven knowledge. Wendy is a regular Maven maven ;)
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring
678.910.8017
----- Original Message -----
From: "Ted Husted" <te...@gmail.com>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Thursday, January 19, 2006 11:17 AM
Subject: Re: Non-discussion emails
On 1/19/06, Sean Schofield <se...@gmail.com> wrote:
> So by its nature, chat is exclusionary. I agree that its more
> expedient but it does not offer the chance for everyone to
> participate. My personal view of open source is that its not about
> what is most efficient. You give up certain efficiencies (like quick
> turnaround times) but you gain more then you give up (synthesis of
> great ideas, massive amounts of around the clock manpower.) A
> transcript is helpful but its basically a record of a conversation
> that took place without everyone's involvement.
Once the chat transcript is posted, people can reply to it
asynchronously, like anything else. Back when we were setting up
Maven, James and Wendy mentioned that had a few chats while getting
everything configured. If they were chatting in a place that was
automatically transcripted, some of us might know a little bit more
about our infrastructure today :)
This is not to say that any of us is not sharing information. We all
do. It's just that our systems should be configured to *automatically*
share information. A transcript-bot for chats does exactly that.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Ted Husted <te...@gmail.com>.
On 1/19/06, Sean Schofield <se...@gmail.com> wrote:
> So by its nature, chat is exclusionary. I agree that its more
> expedient but it does not offer the chance for everyone to
> participate. My personal view of open source is that its not about
> what is most efficient. You give up certain efficiencies (like quick
> turnaround times) but you gain more then you give up (synthesis of
> great ideas, massive amounts of around the clock manpower.) A
> transcript is helpful but its basically a record of a conversation
> that took place without everyone's involvement.
Once the chat transcript is posted, people can reply to it
asynchronously, like anything else. Back when we were setting up
Maven, James and Wendy mentioned that had a few chats while getting
everything configured. If they were chatting in a place that was
automatically transcripted, some of us might know a little bit more
about our infrastructure today :)
This is not to say that any of us is not sharing information. We all
do. It's just that our systems should be configured to *automatically*
share information. A transcript-bot for chats does exactly that.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Sean Schofield <se...@gmail.com>.
The problem with chat is that not everyone is available to participate
at the designated time that people decide to have a chat. As I
mentioned earlier, there are timezone differences and day job
commitments that make it difficult for everyone to participate in a
discussion simultaneously.
So by its nature, chat is exclusionary. I agree that its more
expedient but it does not offer the chance for everyone to
participate. My personal view of open source is that its not about
what is most efficient. You give up certain efficiencies (like quick
turnaround times) but you gain more then you give up (synthesis of
great ideas, massive amounts of around the clock manpower.) A
transcript is helpful but its basically a record of a conversation
that took place without everyone's involvement.
Sean
On 1/18/06, Patrick Lightbody <fo...@opensymphony.com> wrote:
> James,
> We also agree that side conversations are no good, but that chat can be helpful. To solve this, the WebWork forums have an XMPP chat room attached to them, and each night the transcript of the chat is added to the forums:
>
> http://forums.opensymphony.com/thread.jspa?threadID=14656
>
> I can set this up for the Struts forums too, but everyone needs to be aware that emails could come as frequent as once a night in this format.
>
> Patrick
> ---------------------------------------------------------------------
> Posted via Jive Forums
> http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=29283#29283
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by netsql <ne...@pointcast.com>.
Of course http://struts.roomity.com is both (as is news.gmane.org)
(It's a nail, I am the hammer)
.V
> To that end, mailing lists work, and forums do not.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Patrick Lightbody <fo...@opensymphony.com>.
James,
We also agree that side conversations are no good, but that chat can be helpful. To solve this, the WebWork forums have an XMPP chat room attached to them, and each night the transcript of the chat is added to the forums:
http://forums.opensymphony.com/thread.jspa?threadID=14656
I can set this up for the Struts forums too, but everyone needs to be aware that emails could come as frequent as once a night in this format.
Patrick
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=29283#29283
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by James Mitchell <jm...@apache.org>.
My 2 cents (I know, you were dying to know how I feel ;):
I want to be a part of this (and many other) communities, and that
means keeping up to date with the discussions that happen for a given
project.
To that end, mailing lists work, and forums do not. It's nice to be
able to filter messages but that's not a deal breaker for me. What
is a deal breaker for me is how much time I have to spend going
through all of the communications (discussions, commits, wiki
updates, whatever). Hell, if someone would email the irc transcripts
for any project I'm a part of, I'd say "thank you, may I have another".
For me, it's about time management, with mailing lists, it's as
simple as reading the subject and deleting the entire thread with the
push of 1 key, or if I'm interested, I don't have to hit anything, I
just glance down to the reading pane and read until I'm satisfied
that either:
a) I can help, so I hit reply
b) I can help, but no time at the moment, delete
c) I can't help, and I'm not interested anyway, delete
d) I can't help, but I am interested, keep it until the thread
completes, and if there is a solution, save it
So, I don't care about the implementation as long as it meets my
requirements, otherwise I simply must opt out. I hope that doesn't
happen with my favorite community, Struts.
Thanks
--
James Mitchell
EdgeTech, Inc.
http://edgetechservices.net/
678.910.8017
Skype: jmitchtx
On Jan 17, 2006, at 2:14 PM, Sean Schofield wrote:
> I agree with Ted about the importance of mailing lists. Mailing lists
> are the "Apache Way." The only time I have used off-llist
> communication is during an infrastructure move where we needed to
> rapidly complete several steps in a short period of time. Even then
> the basic outline of work was agreed to in advance on the mailing
> list.
>
> Mailing lists may seem outdated but they are the lifeblood of the ASF
> and they continue to serve us well. There may be more rapid ways of
> communicating (phone calls and internet chat come to mind) but these
> are exclusionary. The community is world wide and people have day
> jobs. It takes a little longer to hash things out over email but
> everyone gets to participate this way.
>
> The result is a single archive that is publicly searchable and
> contains all relevant decisions (no matter how trivial) in one place.
>
> My .02
>
> Sean
>
> On 1/17/06, Patrick Lightbody <fo...@opensymphony.com>
> wrote:
>> Ted,
>> I'm sure you didn't mean it this way, but you seem to imply that I
>> don't have any experience with this sort of stuff. I do.
>>
>> We too at OpenSymphony use mailing lists quite heavily (as does
>> every other decent open source project out there). However, as
>> technologies like RSS have grown more popular, we adapted. Now we
>> get our wiki changes and CVS changes through RSS (Confluence and
>> FishEye both provide RSS feeds). We also offer the option of email
>> messages, but that is up to the individual.
>>
>> Conversations still continue around wiki changes and commits. For
>> those that subscribe to the mailing lists, they simply forward the
>> message to the dev list. For those that don't, they simply post a
>> new message asking, "John, can you explain why you changed
>> Foo.java yesterday?".
>>
>> Try to understand where I'm coming from: the wiki and commit
>> changes aren't interesting to me (I don't have time to look
>> through any of them). Not just for Struts, but for WebWork too.
>> Instead, I do weekly reviews. With Struts, I just delete those
>> messages as they come in. And when I look at the forums:
>>
>> http://forums.opensymphony.com/forum.jspa?forumID=34
>>
>> I see "NO NOT REPLY" and "[Struts Wiki]", making it just as
>> difficult for me to keep up with the other conversations. I didn't
>> mean to imply that those messages sometime don't spur a
>> conversation, but pragmatically 99% of the chatter I've seen does
>> not come from them.
>>
>> I definitely understand where you are coming from, and I hope you
>> can see where I'm coming from. Often when people have different
>> work behaviors, the best bet is to provide more options. This can
>> be done by somehow allowing individuals to opt out of those
>> generated emails. I hope we can do something about this.
>>
>> Patrick
>>
>> ---------------------------------------------------------------------
>> Posted via Jive Forums
>> http://forums.opensymphony.com/thread.jspa?
>> threadID=14616&messageID=28843#28843
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Sean Schofield <se...@gmail.com>.
I agree with Ted about the importance of mailing lists. Mailing lists
are the "Apache Way." The only time I have used off-llist
communication is during an infrastructure move where we needed to
rapidly complete several steps in a short period of time. Even then
the basic outline of work was agreed to in advance on the mailing
list.
Mailing lists may seem outdated but they are the lifeblood of the ASF
and they continue to serve us well. There may be more rapid ways of
communicating (phone calls and internet chat come to mind) but these
are exclusionary. The community is world wide and people have day
jobs. It takes a little longer to hash things out over email but
everyone gets to participate this way.
The result is a single archive that is publicly searchable and
contains all relevant decisions (no matter how trivial) in one place.
My .02
Sean
On 1/17/06, Patrick Lightbody <fo...@opensymphony.com> wrote:
> Ted,
> I'm sure you didn't mean it this way, but you seem to imply that I don't have any experience with this sort of stuff. I do.
>
> We too at OpenSymphony use mailing lists quite heavily (as does every other decent open source project out there). However, as technologies like RSS have grown more popular, we adapted. Now we get our wiki changes and CVS changes through RSS (Confluence and FishEye both provide RSS feeds). We also offer the option of email messages, but that is up to the individual.
>
> Conversations still continue around wiki changes and commits. For those that subscribe to the mailing lists, they simply forward the message to the dev list. For those that don't, they simply post a new message asking, "John, can you explain why you changed Foo.java yesterday?".
>
> Try to understand where I'm coming from: the wiki and commit changes aren't interesting to me (I don't have time to look through any of them). Not just for Struts, but for WebWork too. Instead, I do weekly reviews. With Struts, I just delete those messages as they come in. And when I look at the forums:
>
> http://forums.opensymphony.com/forum.jspa?forumID=34
>
> I see "NO NOT REPLY" and "[Struts Wiki]", making it just as difficult for me to keep up with the other conversations. I didn't mean to imply that those messages sometime don't spur a conversation, but pragmatically 99% of the chatter I've seen does not come from them.
>
> I definitely understand where you are coming from, and I hope you can see where I'm coming from. Often when people have different work behaviors, the best bet is to provide more options. This can be done by somehow allowing individuals to opt out of those generated emails. I hope we can do something about this.
>
> Patrick
>
> ---------------------------------------------------------------------
> Posted via Jive Forums
> http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=28843#28843
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Non-discussion emails
Posted by Patrick Lightbody <fo...@opensymphony.com>.
Ted,
I'm sure you didn't mean it this way, but you seem to imply that I don't have any experience with this sort of stuff. I do.
We too at OpenSymphony use mailing lists quite heavily (as does every other decent open source project out there). However, as technologies like RSS have grown more popular, we adapted. Now we get our wiki changes and CVS changes through RSS (Confluence and FishEye both provide RSS feeds). We also offer the option of email messages, but that is up to the individual.
Conversations still continue around wiki changes and commits. For those that subscribe to the mailing lists, they simply forward the message to the dev list. For those that don't, they simply post a new message asking, "John, can you explain why you changed Foo.java yesterday?".
Try to understand where I'm coming from: the wiki and commit changes aren't interesting to me (I don't have time to look through any of them). Not just for Struts, but for WebWork too. Instead, I do weekly reviews. With Struts, I just delete those messages as they come in. And when I look at the forums:
http://forums.opensymphony.com/forum.jspa?forumID=34
I see "NO NOT REPLY" and "[Struts Wiki]", making it just as difficult for me to keep up with the other conversations. I didn't mean to imply that those messages sometime don't spur a conversation, but pragmatically 99% of the chatter I've seen does not come from them.
I definitely understand where you are coming from, and I hope you can see where I'm coming from. Often when people have different work behaviors, the best bet is to provide more options. This can be done by somehow allowing individuals to opt out of those generated emails. I hope we can do something about this.
Patrick
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=28843#28843
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Ted Husted <te...@gmail.com>.
I'm not sure if I'd call those posts "non-discussion". We often have
discussions by commenting on bug tickets. Since we are "commit then
review", a commit log or wiki post is often the genesis of a
discussion about the change.
A commit or wiki event are not historical footnotes. These posts are a
request for a peer review of the change, and an implicit vote as to
whether the change should even take place. if someone is not following
these posts, then much of the activity on the project will be missed.
If a forum is going to be a replacement for the mailing lists, then
the forum must cover all the mailing lists, else forum followers will
be given a false sense of currency.
There is a separate commits@ list, and so it would be easy to setup a
separate forum for those. (But, again, we send out the commit logs so
that they can be reviewed, so there should be a forum for those too!)
The wiki and issue-trackers are both subscribed directly to dev@, so
getting those into separate forums would be problematic, unless Jive
does filtering on its own.
I can't over-emphasize the vital importance of mailing lists to an ASF
project. We consider the mailing list to be our communal memory. If
something doesn't happen on the list, then it didn't happen.
For today, we want everything that you can know about a project to go
over the lists, so that the PMC and others can monitor everything that
happens on a project. For tomorrow, we want everything to go over the
lists, so that our successors can search the archives and see what we
already decided and why.
Every decision we make is in exactly one place: the mailing list archives.
I'm a big fan of Jive forums, and I think having forums for the
project lists is a Good Thing. But, the forums should cover all the
traffic, because all the traffic is there for a reason.
-Ted.
On 1/16/06, Patrick Lightbody <fo...@opensymphony.com> wrote:
> I just realzied that the non-discussion emails (bugs, wiki, and commits) are going in to the forums. The account that is subscribed is forum-struts-dev@opensymphony.com. Is there any way we can disable those other emails to that account?
>
> ---------------------------------------------------------------------
> Posted via Jive Forums
> http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=28683#28683
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Patrick Lightbody <fo...@opensymphony.com>.
Fair enough to wait a few months while infrastructure sorts things out.
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=29056#29056
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Ted Husted <te...@gmail.com>.
On 1/17/06, Patrick Lightbody <fo...@opensymphony.com> wrote:
> Thoughts? I understand that this does involve some work, and for those of you who are
> quite happy with how things are now, it may seem like a waste of time. As such, I'm
> more than willing to do the actual work for any proposed solution.
The ASF infrastructure is about to enter into a transitional period.
After more than a year of hemming and hawing, we finally made some
decisions as to how to proceed. Two new infrastructure teams will be
coming on board. One will handle the mail, and the other will handle
everything else.
This is just not a good time to try and do things that deviate from
the ASF norm. My suggestion would be to table the discussion for six
months and revisit it when the new infrastructure teams are up and
running, and ready to prove themselves.
Of course, if there are things that can be done without involving the
ASF infrastructure, by all means, go ahead and do it. :)
My suggestion would be to setup Jive forums for each of the lists that
we would like to see (user, dev, commit, issues, and wiki), and use
filters to separate content as needed. Then, people will be able to
see exactly what the effect would be. After six months, we'd have
enough experience and traffic to demonstrate how well it works, and we
could pitch it to the new infrastructure team.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Greg Reddin <gr...@apache.org>.
On Jan 18, 2006, at 12:21 PM, Laurie Harper wrote:
> Just to point out the obvious: directing wiki/commit/issue logs to
> separate lists in no way precludes having everything show up on the
> dev list as well. We could have dev-svn@, dev-wiki@, dev-issues@,
> etc plus dev-discuss@ and simply subscribe dev@ to each of those to
> obtain an aggregate.
>
> The only sticky point would be ensuring that replies on dev@ went
> to the appropriate partial list, which should be solvable but
> would, of course, require a little more help from infrastructure.
Good point. Perhaps the dev-*@ lists should be only for automated
posts and we'd want responses to go to dev@ anyway.
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Laurie Harper <la...@holoweb.net>.
Just to point out the obvious: directing wiki/commit/issue logs to
separate lists in no way precludes having everything show up on the dev
list as well. We could have dev-svn@, dev-wiki@, dev-issues@, etc plus
dev-discuss@ and simply subscribe dev@ to each of those to obtain an
aggregate.
The only sticky point would be ensuring that replies on dev@ went to the
appropriate partial list, which should be solvable but would, of course,
require a little more help from infrastructure.
For that reason Ted's proposal, doing this 'after the fact' in the
forums, is probably the right short-term solution but I don't think
there's any technical reason Patrick's requirements can't be met.
L.
Greg Reddin wrote:
> There are several things I've been thinking about as this discussion has
> developed.
>
> First, it is true with any craft, but especially with technology, that
> we must always be willing to change when better ways come along.
> Otherwise we stagnate and fade away. So if I would be more productive
> using these other tools it would be wise for me to consider using them.
>
> However, I can't imagine I would be more productive by having to open an
> RSS reader to follow "the other stuff". As it is I glance at my email
> several times a day and read what I can and delete the rest (similar to
> James' approach). I would actually be *less* productive if that
> involved opening up another reader. The end result is that I'd probably
> not read the commits, wiki updates, and tickets. Then I would lose
> track with what's going on and fade away.
>
> I'm ok with multiple lists. I tend to subscribe once and stay
> subscribed. I could potentially be subscribed from this email address
> for the rest of my life :-) If that supports both ways, then cool.
>
> You guys have made some good points about the WW merger being a merger
> of communities not just code. To that end I think there should be
> compromise on both sides to merge the communities and get them working
> together. However I think one should expect movement on the ASF side to
> be slower and more incremental because we're talking about the whole ASF
> not just Struts. The other side of that coin is that I hope the WW
> people will bring these new ideas to the table and eventually institute
> change for the better. Just be aware that this is a slow-moving train.
> That pace is one of the things I enjoy about the ASF. I can go away for
> a while and when I come back things will likely be in a state where I
> can jump back into familiar territory.
>
> I, for one, will try to embrace the new ideas, but it will take a lot of
> time. I'd much rather be working on Tiles than figuring out new ways of
> keeping up with the discussions :-) +1 for the incremental approach Ted
> (I think) proposed.
>
> Greg
>
> On Jan 17, 2006, at 7:45 PM, Patrick Lightbody wrote:
>
>> Wow, seems like there is a lot of push back on this topic. All I ask
>> Please respect that Jason and I (as well as the WebWork community)
>> come from a very well-established open source community and have a lot
>> of alternative experience in this area. We both have different
>> perspectives, but this merger is more than dumping code in the Struts
>> codebase. It is working with the teams too.
>>
>> To Ted's specific points:
>>
>> * I am very well aware the emails are a direct result of a peron's
>> action. To my original point: I don't care. I personally review the
>> wiki and bug tracker at a different time than when I check email.
>> * Jive Forums certainly can filter the email, and I may turn that on,
>> but then I've bypassed the team rather than working with them. I don't
>> like that approach at all.
>>
>> To Sean's points:
>>
>> * I am not proposing that we get rid of email lists. I am only
>> suggesting that there be ways to opt out of certain lists/types of
>> mail. Why is offering more options such a problem? I fail to see how
>> everything being list-based leads to the conclusion that "The result
>> is a single archive that is publicly searchable and contains all
>> relevant decisions (no matter how trivial) in one place." Why can't
>> there be multiple archives that can all be searched at once? We
>> provide that with WebWork by allowing users to search the WebWork
>> _category_, which includes the Dev, User, and CVS lists.
>>
>> To James:
>>
>> * I fully support that you work that way and am not suggesting your
>> workflow change at all. I 100% support complete email-based
>> communication. I only ask that some users such as myself be able to
>> opt out.
>>
>> So, I'd like to propose something. Ted said:
>>
>>
>>> Now, we could create a wiki@ mailing list and an issue@ mailing list,
>>> to match the commit@ list, but now when people opt-in, they have to
>>> opt into five lists instead of three. If we add a Roller blog to the
>>> mix, then there would be six.
>>>
>>
>> I offer two suggestions, either is perfectly fine with me. Any other
>> suggestions that provide more alternatives are also of course welcome:
>>
>> 1) Why not create a simple web-based form to manage all the lists. By
>> default, all 5, 6, or 7 lists are checked when the user clicks the
>> "subscribe" button, but each list can be independently subscribed and
>> unsubscribed. You can even set the Reply-To header for some of the
>> lists (bugs, wiki, etc) to point back to the dev@ list.
>>
>> and/or
>>
>> 2) Using a Forums-based approach and different mailing lists for each
>> type of content (wiki@, dev@, bug@, etc), create a single Struts
>> category with several sub-forms that sync to the lists. Now users can
>> search the Struts category and get a unified archive.
>>
>> Thoughts? I understand that this does involve some work, and for those
>> of you who are quite happy with how things are now, it may seem like a
>> waste of time. As such, I'm more than willing to do the actual work
>> for any proposed solution.
>>
>> Patrick
>> ---------------------------------------------------------------------
>> Posted via Jive Forums
>> http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=29027#29027
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Greg Reddin <gr...@apache.org>.
On Jan 18, 2006, at 12:49 PM, faisal abdallah wrote:
> It is also an un-unsubscribtion mailing list. Has anybody managed
> to unsubscribe from this mailing list
Yes, several times using the information below.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by faisal abdallah <ju...@yahoo.co.uk>.
It is also an un-unsubscribtion mailing list. Has anybody managed to unsubscribe from this mailing list
Greg Reddin <gr...@apache.org> wrote: There are several things I've been thinking about as this discussion
has developed.
First, it is true with any craft, but especially with technology,
that we must always be willing to change when better ways come
along. Otherwise we stagnate and fade away. So if I would be more
productive using these other tools it would be wise for me to
consider using them.
However, I can't imagine I would be more productive by having to open
an RSS reader to follow "the other stuff". As it is I glance at my
email several times a day and read what I can and delete the rest
(similar to James' approach). I would actually be *less* productive
if that involved opening up another reader. The end result is that
I'd probably not read the commits, wiki updates, and tickets. Then I
would lose track with what's going on and fade away.
I'm ok with multiple lists. I tend to subscribe once and stay
subscribed. I could potentially be subscribed from this email
address for the rest of my life :-) If that supports both ways, then
cool.
You guys have made some good points about the WW merger being a
merger of communities not just code. To that end I think there
should be compromise on both sides to merge the communities and get
them working together. However I think one should expect movement on
the ASF side to be slower and more incremental because we're talking
about the whole ASF not just Struts. The other side of that coin is
that I hope the WW people will bring these new ideas to the table and
eventually institute change for the better. Just be aware that this
is a slow-moving train. That pace is one of the things I enjoy about
the ASF. I can go away for a while and when I come back things will
likely be in a state where I can jump back into familiar territory.
I, for one, will try to embrace the new ideas, but it will take a lot
of time. I'd much rather be working on Tiles than figuring out new
ways of keeping up with the discussions :-) +1 for the incremental
approach Ted (I think) proposed.
Greg
On Jan 17, 2006, at 7:45 PM, Patrick Lightbody wrote:
> Wow, seems like there is a lot of push back on this topic. All I
> ask Please respect that Jason and I (as well as the WebWork
> community) come from a very well-established open source community
> and have a lot of alternative experience in this area. We both have
> different perspectives, but this merger is more than dumping code
> in the Struts codebase. It is working with the teams too.
>
> To Ted's specific points:
>
> * I am very well aware the emails are a direct result of a peron's
> action. To my original point: I don't care. I personally review the
> wiki and bug tracker at a different time than when I check email.
> * Jive Forums certainly can filter the email, and I may turn that
> on, but then I've bypassed the team rather than working with them.
> I don't like that approach at all.
>
> To Sean's points:
>
> * I am not proposing that we get rid of email lists. I am only
> suggesting that there be ways to opt out of certain lists/types of
> mail. Why is offering more options such a problem? I fail to see
> how everything being list-based leads to the conclusion that "The
> result is a single archive that is publicly searchable and contains
> all relevant decisions (no matter how trivial) in one place." Why
> can't there be multiple archives that can all be searched at once?
> We provide that with WebWork by allowing users to search the
> WebWork _category_, which includes the Dev, User, and CVS lists.
>
> To James:
>
> * I fully support that you work that way and am not suggesting
> your workflow change at all. I 100% support complete email-based
> communication. I only ask that some users such as myself be able to
> opt out.
>
> So, I'd like to propose something. Ted said:
>
>
>> Now, we could create a wiki@ mailing list and an issue@ mailing list,
>> to match the commit@ list, but now when people opt-in, they have to
>> opt into five lists instead of three. If we add a Roller blog to the
>> mix, then there would be six.
>>
>
> I offer two suggestions, either is perfectly fine with me. Any
> other suggestions that provide more alternatives are also of course
> welcome:
>
> 1) Why not create a simple web-based form to manage all the lists.
> By default, all 5, 6, or 7 lists are checked when the user clicks
> the "subscribe" button, but each list can be independently
> subscribed and unsubscribed. You can even set the Reply-To header
> for some of the lists (bugs, wiki, etc) to point back to the dev@
> list.
>
> and/or
>
> 2) Using a Forums-based approach and different mailing lists for
> each type of content (wiki@, dev@, bug@, etc), create a single
> Struts category with several sub-forms that sync to the lists. Now
> users can search the Struts category and get a unified archive.
>
> Thoughts? I understand that this does involve some work, and for
> those of you who are quite happy with how things are now, it may
> seem like a waste of time. As such, I'm more than willing to do the
> actual work for any proposed solution.
>
> Patrick
> ---------------------------------------------------------------------
> Posted via Jive Forums
> http://forums.opensymphony.com/thread.jspa?
> threadID=14616&messageID=29027#29027
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
---------------------------------
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.
Re: Non-discussion emails
Posted by Greg Reddin <gr...@apache.org>.
There are several things I've been thinking about as this discussion
has developed.
First, it is true with any craft, but especially with technology,
that we must always be willing to change when better ways come
along. Otherwise we stagnate and fade away. So if I would be more
productive using these other tools it would be wise for me to
consider using them.
However, I can't imagine I would be more productive by having to open
an RSS reader to follow "the other stuff". As it is I glance at my
email several times a day and read what I can and delete the rest
(similar to James' approach). I would actually be *less* productive
if that involved opening up another reader. The end result is that
I'd probably not read the commits, wiki updates, and tickets. Then I
would lose track with what's going on and fade away.
I'm ok with multiple lists. I tend to subscribe once and stay
subscribed. I could potentially be subscribed from this email
address for the rest of my life :-) If that supports both ways, then
cool.
You guys have made some good points about the WW merger being a
merger of communities not just code. To that end I think there
should be compromise on both sides to merge the communities and get
them working together. However I think one should expect movement on
the ASF side to be slower and more incremental because we're talking
about the whole ASF not just Struts. The other side of that coin is
that I hope the WW people will bring these new ideas to the table and
eventually institute change for the better. Just be aware that this
is a slow-moving train. That pace is one of the things I enjoy about
the ASF. I can go away for a while and when I come back things will
likely be in a state where I can jump back into familiar territory.
I, for one, will try to embrace the new ideas, but it will take a lot
of time. I'd much rather be working on Tiles than figuring out new
ways of keeping up with the discussions :-) +1 for the incremental
approach Ted (I think) proposed.
Greg
On Jan 17, 2006, at 7:45 PM, Patrick Lightbody wrote:
> Wow, seems like there is a lot of push back on this topic. All I
> ask Please respect that Jason and I (as well as the WebWork
> community) come from a very well-established open source community
> and have a lot of alternative experience in this area. We both have
> different perspectives, but this merger is more than dumping code
> in the Struts codebase. It is working with the teams too.
>
> To Ted's specific points:
>
> * I am very well aware the emails are a direct result of a peron's
> action. To my original point: I don't care. I personally review the
> wiki and bug tracker at a different time than when I check email.
> * Jive Forums certainly can filter the email, and I may turn that
> on, but then I've bypassed the team rather than working with them.
> I don't like that approach at all.
>
> To Sean's points:
>
> * I am not proposing that we get rid of email lists. I am only
> suggesting that there be ways to opt out of certain lists/types of
> mail. Why is offering more options such a problem? I fail to see
> how everything being list-based leads to the conclusion that "The
> result is a single archive that is publicly searchable and contains
> all relevant decisions (no matter how trivial) in one place." Why
> can't there be multiple archives that can all be searched at once?
> We provide that with WebWork by allowing users to search the
> WebWork _category_, which includes the Dev, User, and CVS lists.
>
> To James:
>
> * I fully support that you work that way and am not suggesting
> your workflow change at all. I 100% support complete email-based
> communication. I only ask that some users such as myself be able to
> opt out.
>
> So, I'd like to propose something. Ted said:
>
>
>> Now, we could create a wiki@ mailing list and an issue@ mailing list,
>> to match the commit@ list, but now when people opt-in, they have to
>> opt into five lists instead of three. If we add a Roller blog to the
>> mix, then there would be six.
>>
>
> I offer two suggestions, either is perfectly fine with me. Any
> other suggestions that provide more alternatives are also of course
> welcome:
>
> 1) Why not create a simple web-based form to manage all the lists.
> By default, all 5, 6, or 7 lists are checked when the user clicks
> the "subscribe" button, but each list can be independently
> subscribed and unsubscribed. You can even set the Reply-To header
> for some of the lists (bugs, wiki, etc) to point back to the dev@
> list.
>
> and/or
>
> 2) Using a Forums-based approach and different mailing lists for
> each type of content (wiki@, dev@, bug@, etc), create a single
> Struts category with several sub-forms that sync to the lists. Now
> users can search the Struts category and get a unified archive.
>
> Thoughts? I understand that this does involve some work, and for
> those of you who are quite happy with how things are now, it may
> seem like a waste of time. As such, I'm more than willing to do the
> actual work for any proposed solution.
>
> Patrick
> ---------------------------------------------------------------------
> Posted via Jive Forums
> http://forums.opensymphony.com/thread.jspa?
> threadID=14616&messageID=29027#29027
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by niallp <fo...@opensymphony.com>.
Committers obviously need to have oversight of everything - wiki, bugs, commits and posted messages, but thats a limited number of us and easy to ensure that we're fully subscribed up to everything.
For other community members Jive is excellent and I think this is a great addition to support community participation. People who don't want to be permanently subscribed and receieve all the emails can pop in and out posting on an adhoc basis.
> I offer two suggestions, either is perfectly fine
> with me. Any other suggestions that provide more
> alternatives are also of course welcome:
>
> 1) Why not create a simple web-based form to manage
> all the lists. By default, all 5, 6, or 7 lists are
> checked when the user clicks the "subscribe" button,
> but each list can be independently subscribed and
> unsubscribed. You can even set the Reply-To header
> for some of the lists (bugs, wiki, etc) to point back
> to the dev@ list.
> and/or
>
> 2) Using a Forums-based approach and different
> mailing lists for each type of content (wiki@, dev@,
> bug@, etc), create a single Struts category with
> several sub-forms that sync to the lists. Now users
> can search the Struts category and get a unified
> archive.
>
> Thoughts? I understand that this does involve some
> work, and for those of you who are quite happy with
> how things are now, it may seem like a waste of time.
> As such, I'm more than willing to do the actual work
> for any proposed solution.
I like both these ideas +1 from me.
Niall
> Patrick
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=29031#29031
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Non-discussion emails
Posted by Patrick Lightbody <fo...@opensymphony.com>.
Wow, seems like there is a lot of push back on this topic. All I ask Please respect that Jason and I (as well as the WebWork community) come from a very well-established open source community and have a lot of alternative experience in this area. We both have different perspectives, but this merger is more than dumping code in the Struts codebase. It is working with the teams too.
To Ted's specific points:
* I am very well aware the emails are a direct result of a peron's action. To my original point: I don't care. I personally review the wiki and bug tracker at a different time than when I check email.
* Jive Forums certainly can filter the email, and I may turn that on, but then I've bypassed the team rather than working with them. I don't like that approach at all.
To Sean's points:
* I am not proposing that we get rid of email lists. I am only suggesting that there be ways to opt out of certain lists/types of mail. Why is offering more options such a problem? I fail to see how everything being list-based leads to the conclusion that "The result is a single archive that is publicly searchable and contains all relevant decisions (no matter how trivial) in one place." Why can't there be multiple archives that can all be searched at once? We provide that with WebWork by allowing users to search the WebWork _category_, which includes the Dev, User, and CVS lists.
To James:
* I fully support that you work that way and am not suggesting your workflow change at all. I 100% support complete email-based communication. I only ask that some users such as myself be able to opt out.
So, I'd like to propose something. Ted said:
> Now, we could create a wiki@ mailing list and an issue@ mailing list,
> to match the commit@ list, but now when people opt-in, they have to
> opt into five lists instead of three. If we add a Roller blog to the
> mix, then there would be six.
I offer two suggestions, either is perfectly fine with me. Any other suggestions that provide more alternatives are also of course welcome:
1) Why not create a simple web-based form to manage all the lists. By default, all 5, 6, or 7 lists are checked when the user clicks the "subscribe" button, but each list can be independently subscribed and unsubscribed. You can even set the Reply-To header for some of the lists (bugs, wiki, etc) to point back to the dev@ list.
and/or
2) Using a Forums-based approach and different mailing lists for each type of content (wiki@, dev@, bug@, etc), create a single Struts category with several sub-forms that sync to the lists. Now users can search the Struts category and get a unified archive.
Thoughts? I understand that this does involve some work, and for those of you who are quite happy with how things are now, it may seem like a waste of time. As such, I'm more than willing to do the actual work for any proposed solution.
Patrick
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=14616&messageID=29027#29027
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org