incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Richards <mricha...@gmail.com>
Subject Re: Bugzilla e-mail is bouncing and other e-mail issues
Date Wed, 28 Sep 2011 02:09:13 GMT
heh, when did that happen? Must have missed the email about the ooo-issues
list.

On Tue, Sep 27, 2011 at 8:54 PM, Rob Weir <robweir@apache.org> wrote:

> Follow up to my follow up from a few weeks ago.   Can someone open an
> JIRA issue with Infra and work with them to make these BZ changes?
>
> https://issues.apache.org/jira/browse/INFRA
>
> As it is now, we have an ooo-issues list, but are receiving no
> notifications.
>
> Thanks!
>
> -Rob
>
>
> On Fri, Sep 9, 2011 at 10:10 AM, Rob Weir <robweir@apache.org> wrote:
> > It sounds like there was general agreement to make all notifications
> > go to ooo-issues@i.a.o.  But did anyone follow through (or is anyone
> > intending to follow through) with a JIRA issue, as Mark requested?
> >
> > I'm happy to do this myself, but I think it would be better for
> > someone with more background in how BZ was working before to engage
> > with Infra@ on this.
> >
> > -Rob
> >
> > On Mon, Sep 5, 2011 at 3:51 AM, Mark Thomas <markt@apache.org> wrote:
> >> Over the weekend, the ASF infra team noticed some e-mail from the ooo BZ
> >> instance was bouncing. Specifically, e-mail to
> >> issues@www.openoffice.org. There also are 142 other
> >> issues@xxx.openoffice.org accounts.
> >>
> >> The delivery failure may be a temporary issue but it highlights a two
> >> tasks for the ooo podling.
> >>
> >> 1. These accounts need to be switched to ASF mailing lists. Please
> >> identify the required changes and open a Jira ticket with the
> >> infrastructure team to implement the changes.
> >>
> >> Note: These accounts were enabled. ASF Infra security policy requires
> >> that BZ accounts representing mailing lists are disabled. All 143
> >> accounts have been disabled. This does not stop update notifications
> >> being sent but it does stop people requesting password resets for these
> >> accounts or logging on using these accounts.
> >>
> >> 3. The assigned to field is set to just about anything other than
> >> ooo-dev@incubator.a.o. In the main ASF Bugzilla instance, this field is
> >> hard-coded to the relevant project's dev list and is read-only. This
> >> ensures that any updates to any issue are sent to the dev list. ASF
> >> policy requires that all issue tracker updates are sent to a project
> >> mailing list (usually dev@ or issues@) so that the community is aware
> of
> >> updates to the issues. Please decide how you want to handle this and
> >> then open a Jira ticket with the infrastructure team to make the
> changes.
> >>
> >> Please note I am not subscribed to this list and will not be monitoring
> >> it for replies. If you need to contact the infrastructure team please
> >> use the usual channels.
> >>
> >> Mark
> >>
> >
>



-- 
--Matt

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message