incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <gst...@gmail.com>
Subject Re: Oversight of non-mailinglist-ful podlings
Date Wed, 04 Jan 2012 23:51:59 GMT
On Jan 4, 2012 4:01 PM, "sebb" <sebbaz@gmail.com> wrote:
>
> On 4 January 2012 19:45, Greg Stein <gstein@gmail.com> wrote:
> > On Wed, Jan 4, 2012 at 14:33, Daniel Shahaf <d.s@daniel.shahaf.name>
wrote:
> >> Someone created
> >>
https://svn.apache.org/repos/asf/incubator/devicemap/site/trunk/?p=1227271
> >> before the devicemap-commits@ list was created.  I expect no list
> >> received a commit mail about it.
> >>
> >> This PMC may want to review its mailer config and/or podling creation
> >> policies to ensure that no changes slip unnoticed.  Saying "once the
> >> commits mail flow, check the svn tree to see what it contained prior to
> >> the first commit that was emailed about" might suffice.
> >
> > Couldn't we just have a default rule for asf/incubator/ go to
> > private@incubator? Once a podling is constructed and configured, then
> > its commit emails would go to the correct place.
>
> Seems like a good idea, but why use private@ - commit mails are not
> normally private are they?
>
> Would it not be better to send them to public-commits@incubator.apache.orgor
> general@incubator?

I worry that something not configured to go somewhere specific, might be
private.

Since this kind of misconfig should be rare, it shouldn't flood private@.
It also puts them in front of the PMC itself, many who I hypothesize are
*not* subscribed to general@ or public-commits@ (I never even heard of the
latter!)

Cheers,
-g

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