You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Wendy Smoak <ws...@gmail.com> on 2007/05/13 21:09:10 UTC
[PROPOSAL] Create a notifications mailing list
I'd like to create notifications@myfaces.apache.org for automated
messages from Continuum.
I feel that more people are interested in watching commits than
notifications. Particularly in the case of new contributors who may
start as users, then watch the dev list, then perhaps want to (just)
review commits. Continuum notifications may just be noise at this
point.
Also, having separate lists gives each person control over the
incoming info. For example, you might want to receive commits in
email, but watch the notifications on an RSS feed.
Thoughts?
Thanks,
Wendy
Re: [PROPOSAL] Create a notifications mailing list
Posted by Matthias Wessendorf <ma...@apache.org>.
cool
On 5/20/07, Wendy Smoak <ws...@gmail.com> wrote:
> On 5/13/07, Wendy Smoak <ws...@gmail.com> wrote:
>
> > I'd like to create notifications@myfaces.apache.org for automated
> > messages from Continuum.
>
> The list has been requested: https://issues.apache.org/jira/browse/INFRA-1248
>
> --
> Wendy
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [PROPOSAL] Create a notifications mailing list
Posted by Wendy Smoak <ws...@gmail.com>.
On 5/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> I'd like to create notifications@myfaces.apache.org for automated
> messages from Continuum.
The list has been requested: https://issues.apache.org/jira/browse/INFRA-1248
--
Wendy
Re: [PROPOSAL] Create a notifications mailing list
Posted by Adam Winer <aw...@gmail.com>.
+1
-- Adam
On 5/14/07, Manfred Geiler <ma...@gmail.com> wrote:
> +1
>
> --Manfred
>
> On 5/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> > I'd like to create notifications@myfaces.apache.org for automated
> > messages from Continuum.
> >
> > I feel that more people are interested in watching commits than
> > notifications. Particularly in the case of new contributors who may
> > start as users, then watch the dev list, then perhaps want to (just)
> > review commits. Continuum notifications may just be noise at this
> > point.
> >
> > Also, having separate lists gives each person control over the
> > incoming info. For example, you might want to receive commits in
> > email, but watch the notifications on an RSS feed.
> >
> > Thoughts?
> >
> > Thanks,
> > Wendy
> >
>
>
> --
> http://www.irian.at
> Your JSF powerhouse - JSF Consulting,
> Development and Courses in English and
> German
>
> Professional Support for Apache MyFaces
>
Re: [PROPOSAL] Create a notifications mailing list
Posted by Manfred Geiler <ma...@gmail.com>.
+1
--Manfred
On 5/13/07, Wendy Smoak <ws...@gmail.com> wrote:
> I'd like to create notifications@myfaces.apache.org for automated
> messages from Continuum.
>
> I feel that more people are interested in watching commits than
> notifications. Particularly in the case of new contributors who may
> start as users, then watch the dev list, then perhaps want to (just)
> review commits. Continuum notifications may just be noise at this
> point.
>
> Also, having separate lists gives each person control over the
> incoming info. For example, you might want to receive commits in
> email, but watch the notifications on an RSS feed.
>
> Thoughts?
>
> Thanks,
> Wendy
>
--
http://www.irian.at
Your JSF powerhouse - JSF Consulting,
Development and Courses in English and
German
Professional Support for Apache MyFaces
Re: [PROPOSAL] Create a notifications mailing list
Posted by Martin van den Bemt <ml...@mvdb.net>.
Quite a symbolic act :)
Mvgr,
Martin
Matthias Wessendorf wrote:
> yes,
>
> -0
>
> :-)
>
> On 5/14/07, Manfred Geiler <ma...@gmail.com> wrote:
>> Good point!
>>
>> I revise my vote to
>> -0
>>
>> regards,
>> Manfred
>>
>> On 5/14/07, Mario Ivankovits <ma...@ops.co.at> wrote:
>> > Hi!
>> > > I am -0 on placing Continuum messages on a different mailing list
>> > > because I like seeing the commit message(s) followed by a Continuum
>> > > success/failure message. The Continuum message is a nice
>> confirmation
>> > > that the commit(s) did or did not break the build. Email clients can
>> > > be configured to filter messages if the user prefers to not see the
>> > > Continuum message or see the message in a different folder. The
>> > > converse can also be said, filtering commit and Continuum messages
>> > > into the same folder.
>> > Yep, these are my thoughts too.
>> >
>> > When Continuum is running stable I really prefer its messages
>> showing up
>> > after the commit. Even a newbie developer should see that every commit
>> > triggers an (nearly) immediate action.
>> > In the end every developer should subscribe to the continuum
>> > notification list too ... so no need to split them.
>> >
>> > Ciao,
>> > Mario
>> >
>> >
>>
>>
>> --
>> http://www.irian.at
>> Your JSF powerhouse - JSF Consulting,
>> Development and Courses in English and
>> German
>>
>> Professional Support for Apache MyFaces
>>
>
>
Re: [PROPOSAL] Create a notifications mailing list
Posted by Matthias Wessendorf <ma...@apache.org>.
yes,
-0
:-)
On 5/14/07, Manfred Geiler <ma...@gmail.com> wrote:
> Good point!
>
> I revise my vote to
> -0
>
> regards,
> Manfred
>
> On 5/14/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> > Hi!
> > > I am -0 on placing Continuum messages on a different mailing list
> > > because I like seeing the commit message(s) followed by a Continuum
> > > success/failure message. The Continuum message is a nice confirmation
> > > that the commit(s) did or did not break the build. Email clients can
> > > be configured to filter messages if the user prefers to not see the
> > > Continuum message or see the message in a different folder. The
> > > converse can also be said, filtering commit and Continuum messages
> > > into the same folder.
> > Yep, these are my thoughts too.
> >
> > When Continuum is running stable I really prefer its messages showing up
> > after the commit. Even a newbie developer should see that every commit
> > triggers an (nearly) immediate action.
> > In the end every developer should subscribe to the continuum
> > notification list too ... so no need to split them.
> >
> > Ciao,
> > Mario
> >
> >
>
>
> --
> http://www.irian.at
> Your JSF powerhouse - JSF Consulting,
> Development and Courses in English and
> German
>
> Professional Support for Apache MyFaces
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [PROPOSAL] Create a notifications mailing list
Posted by Manfred Geiler <ma...@gmail.com>.
Good point!
I revise my vote to
-0
regards,
Manfred
On 5/14/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
> > I am -0 on placing Continuum messages on a different mailing list
> > because I like seeing the commit message(s) followed by a Continuum
> > success/failure message. The Continuum message is a nice confirmation
> > that the commit(s) did or did not break the build. Email clients can
> > be configured to filter messages if the user prefers to not see the
> > Continuum message or see the message in a different folder. The
> > converse can also be said, filtering commit and Continuum messages
> > into the same folder.
> Yep, these are my thoughts too.
>
> When Continuum is running stable I really prefer its messages showing up
> after the commit. Even a newbie developer should see that every commit
> triggers an (nearly) immediate action.
> In the end every developer should subscribe to the continuum
> notification list too ... so no need to split them.
>
> Ciao,
> Mario
>
>
--
http://www.irian.at
Your JSF powerhouse - JSF Consulting,
Development and Courses in English and
German
Professional Support for Apache MyFaces
Re: [PROPOSAL] Create a notifications mailing list
Posted by Grant Smith <wo...@gmail.com>.
On 5/15/07, David Jencks <da...@yahoo.com> wrote:
>
>
> On May 15, 2007, at 8:36 AM, Grant Smith wrote:
>
> I'm +1 for the new list. For those of you who use the continuum success
> notifications as a validation that your commits didn't break anything, shame
> on you! :) You should DEFINITELY compile locally before committing your
> code, and not rely on continuum.
>
>
> Sure, everyone should compile before committing, but I think you are being
> unrealistic :-) While I don't work much on myfaces, on the projects I do
> work on consistently I often have several modifications going at once and
> commit stuff related to only one of them at a time. Having an automated
> build system is a lot more reliable to catch problems than waiting for
> people to complain on the mailing list or trying to remember to check out
> the changes into another copy of the project and build it there.
>
However, due to the time lag between committing and the automated build
system compiling the project, there exists the possibility that some poor
soul checks out a non-compilable version. This is not acceptable, and
usually the cause of much elevated blood pressure :)
I don't dispute the value of an automated build system as a means to provide
snapshots of the most up-to-date development. I agree, too, that we should
commit logical units of work at a time into the repository. I'm just saying
we should make certain what we commit doesn't break compilation.
thanks
> david jencks
>
>
>
> On 5/15/07, Bruno Aranda <br...@gmail.com> wrote:
> >
> > Hi, I can moderate it too if needed. Thanks Wendy,
> >
> > Bruno
> >
> > On 15/05/07, Wendy Smoak <ws...@gmail.com> wrote:
> > > On 5/15/07, Manfred Geiler < manfred.geiler@gmail.com> wrote:
> > >
> > > > currently there are 91 subscribers to the commits list (4 of them
> > with
> > > > digest option).
> > > > don't know if there is a way to do a mass subscribe.
> > >
> > > There is. I'll request that infrastructure seed the notifications
> > > list with the current list of subscribers to the commits list.
> > > Existing subscribers will notice a change in the 'to' address and may
> > > need to adjust mail filters.
> > >
> > > I'll moderate it, and need one more volunteer. No one except
> > > Continuum should be writing to it directly, so moderation messages can
> > > largely be ignored. The reply-to on both the commits and
> > > notifications lists should be set to the dev list.
> > >
> > > --
> > > Wendy
> > >
> >
>
>
>
> --
> Grant Smith
>
>
>
--
Grant Smith
Re: [PROPOSAL] Create a notifications mailing list
Posted by David Jencks <da...@yahoo.com>.
On May 15, 2007, at 8:36 AM, Grant Smith wrote:
> I'm +1 for the new list. For those of you who use the continuum
> success notifications as a validation that your commits didn't
> break anything, shame on you! :) You should DEFINITELY compile
> locally before committing your code, and not rely on continuum.
Sure, everyone should compile before committing, but I think you are
being unrealistic :-) While I don't work much on myfaces, on the
projects I do work on consistently I often have several modifications
going at once and commit stuff related to only one of them at a
time. Having an automated build system is a lot more reliable to
catch problems than waiting for people to complain on the mailing
list or trying to remember to check out the changes into another copy
of the project and build it there.
thanks
david jencks
>
>
> On 5/15/07, Bruno Aranda <br...@gmail.com> wrote:
> Hi, I can moderate it too if needed. Thanks Wendy,
>
> Bruno
>
> On 15/05/07, Wendy Smoak <ws...@gmail.com> wrote:
> > On 5/15/07, Manfred Geiler < manfred.geiler@gmail.com> wrote:
> >
> > > currently there are 91 subscribers to the commits list (4 of
> them with
> > > digest option).
> > > don't know if there is a way to do a mass subscribe.
> >
> > There is. I'll request that infrastructure seed the notifications
> > list with the current list of subscribers to the commits list.
> > Existing subscribers will notice a change in the 'to' address and
> may
> > need to adjust mail filters.
> >
> > I'll moderate it, and need one more volunteer. No one except
> > Continuum should be writing to it directly, so moderation
> messages can
> > largely be ignored. The reply-to on both the commits and
> > notifications lists should be set to the dev list.
> >
> > --
> > Wendy
> >
>
>
>
> --
> Grant Smith
Re: [PROPOSAL] Create a notifications mailing list
Posted by Grant Smith <wo...@gmail.com>.
I'm +1 for the new list. For those of you who use the continuum success
notifications as a validation that your commits didn't break anything, shame
on you! :) You should DEFINITELY compile locally before committing your
code, and not rely on continuum.
On 5/15/07, Bruno Aranda <br...@gmail.com> wrote:
>
> Hi, I can moderate it too if needed. Thanks Wendy,
>
> Bruno
>
> On 15/05/07, Wendy Smoak <ws...@gmail.com> wrote:
> > On 5/15/07, Manfred Geiler <ma...@gmail.com> wrote:
> >
> > > currently there are 91 subscribers to the commits list (4 of them with
> > > digest option).
> > > don't know if there is a way to do a mass subscribe.
> >
> > There is. I'll request that infrastructure seed the notifications
> > list with the current list of subscribers to the commits list.
> > Existing subscribers will notice a change in the 'to' address and may
> > need to adjust mail filters.
> >
> > I'll moderate it, and need one more volunteer. No one except
> > Continuum should be writing to it directly, so moderation messages can
> > largely be ignored. The reply-to on both the commits and
> > notifications lists should be set to the dev list.
> >
> > --
> > Wendy
> >
>
--
Grant Smith
Re: [PROPOSAL] Create a notifications mailing list
Posted by Bruno Aranda <br...@gmail.com>.
Hi, I can moderate it too if needed. Thanks Wendy,
Bruno
On 15/05/07, Wendy Smoak <ws...@gmail.com> wrote:
> On 5/15/07, Manfred Geiler <ma...@gmail.com> wrote:
>
> > currently there are 91 subscribers to the commits list (4 of them with
> > digest option).
> > don't know if there is a way to do a mass subscribe.
>
> There is. I'll request that infrastructure seed the notifications
> list with the current list of subscribers to the commits list.
> Existing subscribers will notice a change in the 'to' address and may
> need to adjust mail filters.
>
> I'll moderate it, and need one more volunteer. No one except
> Continuum should be writing to it directly, so moderation messages can
> largely be ignored. The reply-to on both the commits and
> notifications lists should be set to the dev list.
>
> --
> Wendy
>
Re: [PROPOSAL] Create a notifications mailing list
Posted by Wendy Smoak <ws...@gmail.com>.
On 5/15/07, Manfred Geiler <ma...@gmail.com> wrote:
> currently there are 91 subscribers to the commits list (4 of them with
> digest option).
> don't know if there is a way to do a mass subscribe.
There is. I'll request that infrastructure seed the notifications
list with the current list of subscribers to the commits list.
Existing subscribers will notice a change in the 'to' address and may
need to adjust mail filters.
I'll moderate it, and need one more volunteer. No one except
Continuum should be writing to it directly, so moderation messages can
largely be ignored. The reply-to on both the commits and
notifications lists should be set to the dev list.
--
Wendy
Re: [PROPOSAL] Create a notifications mailing list
Posted by Volker Weber <v....@inexso.de>.
Hi,
i can't remember subscribing the committers list, but i get the mails,
i think this was done at the account creation. This is what i expect
also for the notifications list.
For current committers (if they are not reading here) it should
suffice to sent a notification about the new list to the committers
list.
Regards,
Volker
2007/5/15, Manfred Geiler <ma...@gmail.com>:
> currently there are 91 subscribers to the commits list (4 of them with
> digest option).
> don't know if there is a way to do a mass subscribe.
>
> at least it is possible for a moderator to manually subscribe a person
> by sending a mail like this:
> mailinglist-subscribe-john=example.net@example.org
>
> anyone stepping forward and willing to be the new notifications
> moderator and manually send and confirm (at least) 32 mails to the new
> list?
> ;-)
>
> perhaps some script geek can write a unix script that does this:
> loop over the list of committer emails and send a mail to
> notifications-subscribe-<committer-email-with-at-replaced-by-equal>@myfaces.apache.org
>
> Well. All in all perhaps we should not overact here. Is there really a
> need to coerce all committers? We could add it to our bylaws that
> every (active) committer must be subscribed to at least the 3 lists:
> dev, commits and notifications.
> If a committer does not: what the heck! This is ASF open source land.
> Collaboration is voluntary.
>
> --Manfred
>
>
>
> On 5/15/07, Volker Weber <v....@inexso.de> wrote:
> > Hi,
> >
> > can we ensure that every committer gets this mails without need to
> > subscribe this new list?
> > Even for in future added committers?
> >
> > Otherwise im at least -0.5 for this.
> >
> >
> > Regards,
> > Volker
> >
> >
> > 2007/5/15, Manfred Geiler <ma...@gmail.com>:
> > > Wendy,
> > > Thanks for taking the time for all that stuff. Thanks for the
> > > additional explanation.
> > > If the separation is an approvement for all people using atom feeds:
> > > so much the better.
> > > There was no veto yet (only symbolic -0's), so please proceed like you
> > > originally planned.
> > > --Manfred
> > >
> > > On 5/15/07, Wendy Smoak <ws...@gmail.com> wrote:
> > > > On 5/14/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> > > > > Hi!
> > > > > > I am -0 on placing Continuum messages on a different mailing list
> > > > > > because I like seeing the commit message(s) followed by a Continuum
> > > > > > success/failure message. The Continuum message is a nice confirmation
> > > > > > that the commit(s) did or did not break the build. Email clients can
> > > > > > be configured to filter messages if the user prefers to not see the
> > > > > > Continuum message or see the message in a different folder. The
> > > > > > converse can also be said, filtering commit and Continuum messages
> > > > > > into the same folder.
> > > > > Yep, these are my thoughts too.
> > > > >
> > > > > When Continuum is running stable I really prefer its messages showing up
> > > > > after the commit. Even a newbie developer should see that every commit
> > > > > triggers an (nearly) immediate action.
> > > > > In the end every developer should subscribe to the continuum
> > > > > notification list too ... so no need to split them.
> > > >
> > > > Somehow, I feel the need to restate my case. :)
> > > >
> > > > People who want to see commits and notifications right next to each
> > > > other should absolutely have that option. And you will, just filter
> > > > both lists into the same folder (or give them the same tag.) And
> > > > active developers should certainly be watching both commits and
> > > > notifications.
> > > >
> > > > Howver, _how_ you watch them should be up to you -- the Atom feed on
> > > > the official archives is a great resource, as are Nabble forums.
> > > > Separate streams of information can be combined and consumed in
> > > > whatever way makes sense for you, personally.
> > > >
> > > > Also _whether_ you watch both of them should be up to the reader. Not
> > > > everyone who reads the commits list is a developer. One of the
> > > > reasons I argue for descriptive commit messages is that I learn a
> > > > great deal from reading code and understanding what the change was
> > > > meant to do. I do this for projects I'm only a casual user of. At
> > > > that level, notifications are just noise -- soon enough, I'll see the
> > > > next commit with the correction and another explanation.
> > > >
> > > > So, carry on...
> > > >
> > > > --
> > > > Wendy
> > > >
> > >
> > >
> > > --
> > > http://www.irian.at
> > > Your JSF powerhouse - JSF Consulting,
> > > Development and Courses in English and
> > > German
> > >
> > > Professional Support for Apache MyFaces
> > >
> >
>
>
> --
> http://www.irian.at
> Your JSF powerhouse - JSF Consulting,
> Development and Courses in English and
> German
>
> Professional Support for Apache MyFaces
>
Re: [PROPOSAL] Create a notifications mailing list
Posted by Manfred Geiler <ma...@gmail.com>.
currently there are 91 subscribers to the commits list (4 of them with
digest option).
don't know if there is a way to do a mass subscribe.
at least it is possible for a moderator to manually subscribe a person
by sending a mail like this:
mailinglist-subscribe-john=example.net@example.org
anyone stepping forward and willing to be the new notifications
moderator and manually send and confirm (at least) 32 mails to the new
list?
;-)
perhaps some script geek can write a unix script that does this:
loop over the list of committer emails and send a mail to
notifications-subscribe-<committer-email-with-at-replaced-by-equal>@myfaces.apache.org
Well. All in all perhaps we should not overact here. Is there really a
need to coerce all committers? We could add it to our bylaws that
every (active) committer must be subscribed to at least the 3 lists:
dev, commits and notifications.
If a committer does not: what the heck! This is ASF open source land.
Collaboration is voluntary.
--Manfred
On 5/15/07, Volker Weber <v....@inexso.de> wrote:
> Hi,
>
> can we ensure that every committer gets this mails without need to
> subscribe this new list?
> Even for in future added committers?
>
> Otherwise im at least -0.5 for this.
>
>
> Regards,
> Volker
>
>
> 2007/5/15, Manfred Geiler <ma...@gmail.com>:
> > Wendy,
> > Thanks for taking the time for all that stuff. Thanks for the
> > additional explanation.
> > If the separation is an approvement for all people using atom feeds:
> > so much the better.
> > There was no veto yet (only symbolic -0's), so please proceed like you
> > originally planned.
> > --Manfred
> >
> > On 5/15/07, Wendy Smoak <ws...@gmail.com> wrote:
> > > On 5/14/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> > > > Hi!
> > > > > I am -0 on placing Continuum messages on a different mailing list
> > > > > because I like seeing the commit message(s) followed by a Continuum
> > > > > success/failure message. The Continuum message is a nice confirmation
> > > > > that the commit(s) did or did not break the build. Email clients can
> > > > > be configured to filter messages if the user prefers to not see the
> > > > > Continuum message or see the message in a different folder. The
> > > > > converse can also be said, filtering commit and Continuum messages
> > > > > into the same folder.
> > > > Yep, these are my thoughts too.
> > > >
> > > > When Continuum is running stable I really prefer its messages showing up
> > > > after the commit. Even a newbie developer should see that every commit
> > > > triggers an (nearly) immediate action.
> > > > In the end every developer should subscribe to the continuum
> > > > notification list too ... so no need to split them.
> > >
> > > Somehow, I feel the need to restate my case. :)
> > >
> > > People who want to see commits and notifications right next to each
> > > other should absolutely have that option. And you will, just filter
> > > both lists into the same folder (or give them the same tag.) And
> > > active developers should certainly be watching both commits and
> > > notifications.
> > >
> > > Howver, _how_ you watch them should be up to you -- the Atom feed on
> > > the official archives is a great resource, as are Nabble forums.
> > > Separate streams of information can be combined and consumed in
> > > whatever way makes sense for you, personally.
> > >
> > > Also _whether_ you watch both of them should be up to the reader. Not
> > > everyone who reads the commits list is a developer. One of the
> > > reasons I argue for descriptive commit messages is that I learn a
> > > great deal from reading code and understanding what the change was
> > > meant to do. I do this for projects I'm only a casual user of. At
> > > that level, notifications are just noise -- soon enough, I'll see the
> > > next commit with the correction and another explanation.
> > >
> > > So, carry on...
> > >
> > > --
> > > Wendy
> > >
> >
> >
> > --
> > http://www.irian.at
> > Your JSF powerhouse - JSF Consulting,
> > Development and Courses in English and
> > German
> >
> > Professional Support for Apache MyFaces
> >
>
--
http://www.irian.at
Your JSF powerhouse - JSF Consulting,
Development and Courses in English and
German
Professional Support for Apache MyFaces
Re: [PROPOSAL] Create a notifications mailing list
Posted by Volker Weber <v....@inexso.de>.
Hi,
can we ensure that every committer gets this mails without need to
subscribe this new list?
Even for in future added committers?
Otherwise im at least -0.5 for this.
Regards,
Volker
2007/5/15, Manfred Geiler <ma...@gmail.com>:
> Wendy,
> Thanks for taking the time for all that stuff. Thanks for the
> additional explanation.
> If the separation is an approvement for all people using atom feeds:
> so much the better.
> There was no veto yet (only symbolic -0's), so please proceed like you
> originally planned.
> --Manfred
>
> On 5/15/07, Wendy Smoak <ws...@gmail.com> wrote:
> > On 5/14/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> > > Hi!
> > > > I am -0 on placing Continuum messages on a different mailing list
> > > > because I like seeing the commit message(s) followed by a Continuum
> > > > success/failure message. The Continuum message is a nice confirmation
> > > > that the commit(s) did or did not break the build. Email clients can
> > > > be configured to filter messages if the user prefers to not see the
> > > > Continuum message or see the message in a different folder. The
> > > > converse can also be said, filtering commit and Continuum messages
> > > > into the same folder.
> > > Yep, these are my thoughts too.
> > >
> > > When Continuum is running stable I really prefer its messages showing up
> > > after the commit. Even a newbie developer should see that every commit
> > > triggers an (nearly) immediate action.
> > > In the end every developer should subscribe to the continuum
> > > notification list too ... so no need to split them.
> >
> > Somehow, I feel the need to restate my case. :)
> >
> > People who want to see commits and notifications right next to each
> > other should absolutely have that option. And you will, just filter
> > both lists into the same folder (or give them the same tag.) And
> > active developers should certainly be watching both commits and
> > notifications.
> >
> > Howver, _how_ you watch them should be up to you -- the Atom feed on
> > the official archives is a great resource, as are Nabble forums.
> > Separate streams of information can be combined and consumed in
> > whatever way makes sense for you, personally.
> >
> > Also _whether_ you watch both of them should be up to the reader. Not
> > everyone who reads the commits list is a developer. One of the
> > reasons I argue for descriptive commit messages is that I learn a
> > great deal from reading code and understanding what the change was
> > meant to do. I do this for projects I'm only a casual user of. At
> > that level, notifications are just noise -- soon enough, I'll see the
> > next commit with the correction and another explanation.
> >
> > So, carry on...
> >
> > --
> > Wendy
> >
>
>
> --
> http://www.irian.at
> Your JSF powerhouse - JSF Consulting,
> Development and Courses in English and
> German
>
> Professional Support for Apache MyFaces
>
Re: [PROPOSAL] Create a notifications mailing list
Posted by Manfred Geiler <ma...@gmail.com>.
Wendy,
Thanks for taking the time for all that stuff. Thanks for the
additional explanation.
If the separation is an approvement for all people using atom feeds:
so much the better.
There was no veto yet (only symbolic -0's), so please proceed like you
originally planned.
--Manfred
On 5/15/07, Wendy Smoak <ws...@gmail.com> wrote:
> On 5/14/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> > Hi!
> > > I am -0 on placing Continuum messages on a different mailing list
> > > because I like seeing the commit message(s) followed by a Continuum
> > > success/failure message. The Continuum message is a nice confirmation
> > > that the commit(s) did or did not break the build. Email clients can
> > > be configured to filter messages if the user prefers to not see the
> > > Continuum message or see the message in a different folder. The
> > > converse can also be said, filtering commit and Continuum messages
> > > into the same folder.
> > Yep, these are my thoughts too.
> >
> > When Continuum is running stable I really prefer its messages showing up
> > after the commit. Even a newbie developer should see that every commit
> > triggers an (nearly) immediate action.
> > In the end every developer should subscribe to the continuum
> > notification list too ... so no need to split them.
>
> Somehow, I feel the need to restate my case. :)
>
> People who want to see commits and notifications right next to each
> other should absolutely have that option. And you will, just filter
> both lists into the same folder (or give them the same tag.) And
> active developers should certainly be watching both commits and
> notifications.
>
> Howver, _how_ you watch them should be up to you -- the Atom feed on
> the official archives is a great resource, as are Nabble forums.
> Separate streams of information can be combined and consumed in
> whatever way makes sense for you, personally.
>
> Also _whether_ you watch both of them should be up to the reader. Not
> everyone who reads the commits list is a developer. One of the
> reasons I argue for descriptive commit messages is that I learn a
> great deal from reading code and understanding what the change was
> meant to do. I do this for projects I'm only a casual user of. At
> that level, notifications are just noise -- soon enough, I'll see the
> next commit with the correction and another explanation.
>
> So, carry on...
>
> --
> Wendy
>
--
http://www.irian.at
Your JSF powerhouse - JSF Consulting,
Development and Courses in English and
German
Professional Support for Apache MyFaces
Re: [PROPOSAL] Create a notifications mailing list
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi!
> People who want to see commits and notifications right next to each
> other should absolutely have that option. And you will, just filter
> both lists into the same folder (or give them the same tag.) And
> active developers should certainly be watching both commits and
> notifications.
You can apply the same filter to move the Continuum messages to another
folder - or even trash them.
> Howver, _how_ you watch them should be up to you -- the Atom feed on
> the official archives is a great resource, as are Nabble forums.
I do not use atom feeds to monitor any mailing-list ... so don't know if
they will be of any value for me.
Ciao,
Mario
Re: [PROPOSAL] Create a notifications mailing list
Posted by Wendy Smoak <ws...@gmail.com>.
On 5/14/07, Mario Ivankovits <ma...@ops.co.at> wrote:
> Hi!
> > I am -0 on placing Continuum messages on a different mailing list
> > because I like seeing the commit message(s) followed by a Continuum
> > success/failure message. The Continuum message is a nice confirmation
> > that the commit(s) did or did not break the build. Email clients can
> > be configured to filter messages if the user prefers to not see the
> > Continuum message or see the message in a different folder. The
> > converse can also be said, filtering commit and Continuum messages
> > into the same folder.
> Yep, these are my thoughts too.
>
> When Continuum is running stable I really prefer its messages showing up
> after the commit. Even a newbie developer should see that every commit
> triggers an (nearly) immediate action.
> In the end every developer should subscribe to the continuum
> notification list too ... so no need to split them.
Somehow, I feel the need to restate my case. :)
People who want to see commits and notifications right next to each
other should absolutely have that option. And you will, just filter
both lists into the same folder (or give them the same tag.) And
active developers should certainly be watching both commits and
notifications.
Howver, _how_ you watch them should be up to you -- the Atom feed on
the official archives is a great resource, as are Nabble forums.
Separate streams of information can be combined and consumed in
whatever way makes sense for you, personally.
Also _whether_ you watch both of them should be up to the reader. Not
everyone who reads the commits list is a developer. One of the
reasons I argue for descriptive commit messages is that I learn a
great deal from reading code and understanding what the change was
meant to do. I do this for projects I'm only a casual user of. At
that level, notifications are just noise -- soon enough, I'll see the
next commit with the correction and another explanation.
So, carry on...
--
Wendy
Re: [PROPOSAL] Create a notifications mailing list
Posted by Mario Ivankovits <ma...@ops.co.at>.
Hi!
> I am -0 on placing Continuum messages on a different mailing list
> because I like seeing the commit message(s) followed by a Continuum
> success/failure message. The Continuum message is a nice confirmation
> that the commit(s) did or did not break the build. Email clients can
> be configured to filter messages if the user prefers to not see the
> Continuum message or see the message in a different folder. The
> converse can also be said, filtering commit and Continuum messages
> into the same folder.
Yep, these are my thoughts too.
When Continuum is running stable I really prefer its messages showing up
after the commit. Even a newbie developer should see that every commit
triggers an (nearly) immediate action.
In the end every developer should subscribe to the continuum
notification list too ... so no need to split them.
Ciao,
Mario
Re: [PROPOSAL] Create a notifications mailing list
Posted by Paul Spencer <pa...@apache.org>.
Wendy,
I am -0 on placing Continuum messages on a different mailing list
because I like seeing the commit message(s) followed by a Continuum
success/failure message. The Continuum message is a nice confirmation
that the commit(s) did or did not break the build. Email clients can be
configured to filter messages if the user prefers to not see the
Continuum message or see the message in a different folder. The
converse can also be said, filtering commit and Continuum messages into
the same folder.
Paul Spencer
Wendy Smoak wrote:
> I'd like to create notifications@myfaces.apache.org for automated
> messages from Continuum.
>
> I feel that more people are interested in watching commits than
> notifications. Particularly in the case of new contributors who may
> start as users, then watch the dev list, then perhaps want to (just)
> review commits. Continuum notifications may just be noise at this
> point.
>
> Also, having separate lists gives each person control over the
> incoming info. For example, you might want to receive commits in
> email, but watch the notifications on an RSS feed.
>
> Thoughts?
>
> Thanks,
> Wendy
>
Re: [PROPOSAL] Create a notifications mailing list
Posted by Simon Lessard <si...@gmail.com>.
+1
On 5/14/07, Matthias Wessendorf <ma...@apache.org> wrote:
>
> +1
>
> On 5/14/07, Paul McMahan <pa...@gmail.com> wrote:
> > +1
> >
> >
> > On May 13, 2007, at 3:09 PM, Wendy Smoak wrote:
> >
> > > I'd like to create notifications@myfaces.apache.org for automated
> > > messages from Continuum.
> > >
> > > I feel that more people are interested in watching commits than
> > > notifications. Particularly in the case of new contributors who may
> > > start as users, then watch the dev list, then perhaps want to (just)
> > > review commits. Continuum notifications may just be noise at this
> > > point.
> > >
> > > Also, having separate lists gives each person control over the
> > > incoming info. For example, you might want to receive commits in
> > > email, but watch the notifications on an RSS feed.
> > >
> > > Thoughts?
> > >
> > > Thanks,
> > > Wendy
> >
> >
>
>
> --
> Matthias Wessendorf
> http://tinyurl.com/fmywh
>
> further stuff:
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
Re: [PROPOSAL] Create a notifications mailing list
Posted by Matthias Wessendorf <ma...@apache.org>.
+1
On 5/14/07, Paul McMahan <pa...@gmail.com> wrote:
> +1
>
>
> On May 13, 2007, at 3:09 PM, Wendy Smoak wrote:
>
> > I'd like to create notifications@myfaces.apache.org for automated
> > messages from Continuum.
> >
> > I feel that more people are interested in watching commits than
> > notifications. Particularly in the case of new contributors who may
> > start as users, then watch the dev list, then perhaps want to (just)
> > review commits. Continuum notifications may just be noise at this
> > point.
> >
> > Also, having separate lists gives each person control over the
> > incoming info. For example, you might want to receive commits in
> > email, but watch the notifications on an RSS feed.
> >
> > Thoughts?
> >
> > Thanks,
> > Wendy
>
>
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: [PROPOSAL] Create a notifications mailing list
Posted by Paul McMahan <pa...@gmail.com>.
+1
On May 13, 2007, at 3:09 PM, Wendy Smoak wrote:
> I'd like to create notifications@myfaces.apache.org for automated
> messages from Continuum.
>
> I feel that more people are interested in watching commits than
> notifications. Particularly in the case of new contributors who may
> start as users, then watch the dev list, then perhaps want to (just)
> review commits. Continuum notifications may just be noise at this
> point.
>
> Also, having separate lists gives each person control over the
> incoming info. For example, you might want to receive commits in
> email, but watch the notifications on an RSS feed.
>
> Thoughts?
>
> Thanks,
> Wendy
Re: [PROPOSAL] Create a notifications mailing list
Posted by Cagatay Civici <ca...@gmail.com>.
+1, this will simplify things
Cagatay
On 5/14/07, Bernd Bohmann <be...@atanion.com> wrote:
>
> +1
>
> Regards
>
> Bernd
>
> Bruno Aranda wrote:
> > +1 I am ok with that. Although I have everything filtered and ordered
> > I guess it will reduce the amount of mails in the dev list, hence
> > everything will be more clear,
> >
> > Cheers,
> >
> > Bruno
> >
> > On 13/05/07, Wendy Smoak <ws...@gmail.com> wrote:
> >> I'd like to create notifications@myfaces.apache.org for automated
> >> messages from Continuum.
> >>
> >> I feel that more people are interested in watching commits than
> >> notifications. Particularly in the case of new contributors who may
> >> start as users, then watch the dev list, then perhaps want to (just)
> >> review commits. Continuum notifications may just be noise at this
> >> point.
> >>
> >> Also, having separate lists gives each person control over the
> >> incoming info. For example, you might want to receive commits in
> >> email, but watch the notifications on an RSS feed.
> >>
> >> Thoughts?
> >>
> >> Thanks,
> >> Wendy
> >>
> >
>
Re: [PROPOSAL] Create a notifications mailing list
Posted by Bernd Bohmann <be...@atanion.com>.
+1
Regards
Bernd
Bruno Aranda wrote:
> +1 I am ok with that. Although I have everything filtered and ordered
> I guess it will reduce the amount of mails in the dev list, hence
> everything will be more clear,
>
> Cheers,
>
> Bruno
>
> On 13/05/07, Wendy Smoak <ws...@gmail.com> wrote:
>> I'd like to create notifications@myfaces.apache.org for automated
>> messages from Continuum.
>>
>> I feel that more people are interested in watching commits than
>> notifications. Particularly in the case of new contributors who may
>> start as users, then watch the dev list, then perhaps want to (just)
>> review commits. Continuum notifications may just be noise at this
>> point.
>>
>> Also, having separate lists gives each person control over the
>> incoming info. For example, you might want to receive commits in
>> email, but watch the notifications on an RSS feed.
>>
>> Thoughts?
>>
>> Thanks,
>> Wendy
>>
>
Re: [PROPOSAL] Create a notifications mailing list
Posted by Bruno Aranda <br...@gmail.com>.
+1 I am ok with that. Although I have everything filtered and ordered
I guess it will reduce the amount of mails in the dev list, hence
everything will be more clear,
Cheers,
Bruno
On 13/05/07, Wendy Smoak <ws...@gmail.com> wrote:
> I'd like to create notifications@myfaces.apache.org for automated
> messages from Continuum.
>
> I feel that more people are interested in watching commits than
> notifications. Particularly in the case of new contributors who may
> start as users, then watch the dev list, then perhaps want to (just)
> review commits. Continuum notifications may just be noise at this
> point.
>
> Also, having separate lists gives each person control over the
> incoming info. For example, you might want to receive commits in
> email, but watch the notifications on an RSS feed.
>
> Thoughts?
>
> Thanks,
> Wendy
>