Re: Sending Wiki Notifications to Mailing Lists
In light of this conversation I am changing the proposal to this: For both the Community Forum (OOOUSER) and the Developer Forum (OOODEV) I now propose sending an email with a daily digest to ooo-commits@incubator.a.o. This way those who want to oversee changes can do so, and in the same place where svn change emails go. (FYI -a website change sends three emails to that list.) For those who want to see recent changes in confluence, this is possible. Here is how: (1) Go to the Dashboard. (2) On the left find Spaces: and click on the Team tab. (3) On the View Spaces for Team pop-up menu select ooo Recent changes for both Wikis appear on the right - a few, not 100. For those who want to get their own notifications - https://cwiki.apache.org/confluence/users/viewmyemailsettings.action Since the proposal has changed I will wait an additional 36 hours (for a total of 72) to see if Consensus is achieved. Regards, Dave On Jun 23, 2011, at 1:17 AM, Marcus (OOo) wrote: I second this to send all notifications to the commits mailing list. Marcus Am 06/23/2011 03:42 AM, schrieb Raphael Bircher: Hi Oh yes, I don't love wiki change mails on the discouss list. I think we have enough mails there. Greetings Raphael Am 23.06.11 03:29, schrieb Greg Stein: I would suggest ooo-commits instead. That seems a better list for change notifications. The digest/each setup sounds great. Cheers, -g On Jun 22, 2011 8:26 PM, Dave Fisherdave2w...@comcast.net wrote: At the Apache Software Foundation everything should happen on a public mailing list. [1] Since the wikis are not mailing lists we need take advantage of confluences ability to email notifications. This will make Wiki changes transparent to the whole community. [2] There are two options. An email with every change or a daily digest. For the Community Forum (OOOUSER) I propose that a daily digest be sent to ooo-dev@incubator.a.o. For the Developer Forum (OOODEV) I propose sending an email with every change to ooo-commits@incubator.a.o. Lazy Consensus [3] will apply. In consideration of our world wide audience I'll wait at least 36 hours before asking Infrastructure and the Incubator to help implement a wiki to email policy. It can be a different policy. Regards, Dave [1] http://incubator.apache.org/guides/lists.html [2] https://cwiki.apache.org/CWIKI/#Index-Postingemailalertstoamailinglist [3] http://www.apache.org/foundation/voting.html#LazyConsensus
Re: Sending Wiki Notifications to Mailing Lists
Sounds fine to me ... I do like to review the commit archives, even when I don't subscribe there directly. Pedro. --- On Thu, 6/23/11, Dave Fisher dave2w...@comcast.net wrote: ... In light of this conversation I am changing the proposal to this: For both the Community Forum (OOOUSER) and the Developer Forum (OOODEV) I now propose sending an email with a daily digest to ooo-commits@incubator.a.o. This way those who want to oversee changes can do so, and in the same place where svn change emails go. (FYI -a website change sends three emails to that list.) For those who want to see recent changes in confluence, this is possible. Here is how: (1) Go to the Dashboard. (2) On the left find Spaces: and click on the Team tab. (3) On the View Spaces for Team pop-up menu select ooo Recent changes for both Wikis appear on the right - a few, not 100. For those who want to get their own notifications - https://cwiki.apache.org/confluence/users/viewmyemailsettings.action Since the proposal has changed I will wait an additional 36 hours (for a total of 72) to see if Consensus is achieved. Regards, Dave On Jun 23, 2011, at 1:17 AM, Marcus (OOo) wrote: I second this to send all notifications to the commits mailing list. Marcus Am 06/23/2011 03:42 AM, schrieb Raphael Bircher: Hi Oh yes, I don't love wiki change mails on the discouss list. I think we have enough mails there. Greetings Raphael Am 23.06.11 03:29, schrieb Greg Stein: I would suggest ooo-commits instead. That seems a better list for change notifications. The digest/each setup sounds great. Cheers, -g On Jun 22, 2011 8:26 PM, Dave Fisherdave2w...@comcast.net wrote: At the Apache Software Foundation everything should happen on a public mailing list. [1] Since the wikis are not mailing lists we need take advantage of confluences ability to email notifications. This will make Wiki changes transparent to the whole community. [2] There are two options. An email with every change or a daily digest. For the Community Forum (OOOUSER) I propose that a daily digest be sent to ooo-dev@incubator.a.o. For the Developer Forum (OOODEV) I propose sending an email with every change to ooo-commits@incubator.a.o. Lazy Consensus [3] will apply. In consideration of our world wide audience I'll wait at least 36 hours before asking Infrastructure and the Incubator to help implement a wiki to email policy. It can be a different policy. Regards, Dave [1] http://incubator.apache.org/guides/lists.html [2] https://cwiki.apache.org/CWIKI/#Index-Postingemailalertstoamailinglist [3] http://www.apache.org/foundation/voting.html#LazyConsensus hk
Re: Sending Wiki Notifications to Mailing Lists
Dave Fisher wrote: In light of this conversation I am changing the proposal to this: For both the Community Forum (OOOUSER) and the Developer Forum (OOODEV) I now propose sending an email with a daily digest to ooo-commits@incubator.a.o. This way those who want to oversee changes can do so, and in the same place where svn change emails go. (FYI -a website change sends three emails to that list.) For those who want to see recent changes in confluence, this is possible. Here is how: (1) Go to the Dashboard. (2) On the left find Spaces: and click on the Team tab. (3) On the View Spaces for Team pop-up menu select ooo Recent changes for both Wikis appear on the right - a few, not 100. For those who want to get their own notifications - https://cwiki.apache.org/confluence/users/viewmyemailsettings.action Since the proposal has changed I will wait an additional 36 hours (for a total of 72) to see if Consensus is achieved. Regards, Dave I feel that this is the best idea. It will keep from flooding this list with information that not all are interested in. Andy
Re: Sending Wiki Notifications to Mailing Lists
On Thu, Jun 23, 2011 at 1:50 PM, Dave Fisher dave2w...@comcast.net wrote: In light of this conversation I am changing the proposal to this: For both the Community Forum (OOOUSER) and the Developer Forum (OOODEV) I now propose sending an email with a daily digest to ooo-commits@incubator.a.o. This way those who want to oversee changes can do so, and in the same place where svn change emails go. (FYI -a website change sends three emails to that list.) +1 -Rob
Re: Sending Wiki Notifications to Mailing Lists
On Thu, Jun 23, 2011 at 1:50 PM, Dave Fisher dave2w...@comcast.net wrote: In light of this conversation I am changing the proposal to this: For both the Community Forum (OOOUSER) and the Developer Forum (OOODEV) I now propose sending an email with a daily digest to ooo-commits@incubator.a.o. This way those who want to oversee changes can do so, and in the same place where svn change emails go. (FYI -a website change sends three emails to that list.) +1 -- DiGro Windows 7 and OpenOffice.org 3.3 Scanned with Ziggo uitgebreide Internetbeveiliging (F-Secure)
Re: Sending Wiki Notifications to Mailing Lists
Pedro F. Giffuni wrote: I personally would prefer not to receive them. Please make sure they are easy to filter: some header like [Wiki digest] ..., at least. cheers, Pedro. Agreed. Andy
Re: Sending Wiki Notifications to Mailing Lists
I appreciate that. But I also suspect that with 1,000 change notifications per day, no oversight at all will occur. So given the scale of the anticipated wiki, how do we get the maximum actual oversight? -Rob On Wed, Jun 22, 2011 at 10:20 PM, Sam Ruby ru...@intertwingly.net wrote: On Wed, Jun 22, 2011 at 10:09 PM, Andy Brown a...@the-martin-byrd.net wrote: Pedro F. Giffuni wrote: I personally would prefer not to receive them. Please make sure they are easy to filter: some header like [Wiki digest] ..., at least. cheers, Pedro. Agreed. Not directed an anyone in particular, but the essential difference between the role of committer and the role of a member of a PMC is that a committer does his or her own thing, but a PMC member is responsible for oversight: http://www.apache.org/dev/pmc.html#audience Andy - Sam Ruby
