You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Greg Stein <gs...@gmail.com> on 2017/04/06 03:03:47 UTC

Re: Creating a podlings@incubator.apache.org mailing list

Hi John, et al,

From an Infrastructure position, I have several points w.r.t to this
request, and its associated Jira ticket [1] :

* The spam potential is large for this, so I suggest it gets treated like
announce@apache, which requires sending from @apache and forced moderation
of *all* messages. I hope we can have a mailing list to use those features
(a simple fan-out alias won't do it), with subscribers being other lists.
We'll note in the ticket if a problem arises.

* As I've raised elsewhere, Infrastructure work/costs have a direct
correlation to podling entry, and podling graduation. Adjusting the
podlings@ fan-out at entry/graduation is heaping on. more work. I've spoken
with John on HipChat, and asked that the IPMC provide a script to fetch and
print the desired set of target dev@ lists (I don't want Infra to guess;
y'all need a script to define the set). We'll incorporate that into a daily
cron job. Whether the script uses LDAP or pulls podling.xml ... *shrug*

If there are any questions/concerns, then please continue here or in the
ticket.

Cheers,
Greg Stein
Infrastructure Administrator, ASF

[1] https://issues.apache.org/jira/browse/INFRA-13823


On Mon, Mar 20, 2017 at 1:52 PM, John D. Ament <jo...@apache.org>
wrote:

> All,
>
> Before I go ahead with it, wanted to see if others had any opinions.  I'm
> planning to ask infra to create a podlings@i.a.o mailing list, which would
> go to all podlings dev@ list.  There may be some scenarios where we need
> to
> communicate out to all podlings.  For instance, the logo change and how it
> impacts the podlings.
>
> John
>

Re: Creating a podlings@incubator.apache.org mailing list

Posted by "P. Taylor Goetz" <pt...@gmail.com>.
+1 for moderation.

-Taylor

> On Apr 6, 2017, at 5:21 AM, John D. Ament <jo...@apache.org> wrote:
> 
> I agree to both points.  I've already started on the script, based on the
> existing python scripts we use to generate our reports.
> 
> How do others feel about the moderation?  Its only for "official"
> communication so..
> 
> John
> 
>> On Wed, Apr 5, 2017 at 11:03 PM Greg Stein <gs...@gmail.com> wrote:
>> 
>> Hi John, et al,
>> 
>> From an Infrastructure position, I have several points w.r.t to this
>> request, and its associated Jira ticket [1] :
>> 
>> * The spam potential is large for this, so I suggest it gets treated like
>> announce@apache, which requires sending from @apache and forced moderation
>> of *all* messages. I hope we can have a mailing list to use those features
>> (a simple fan-out alias won't do it), with subscribers being other lists.
>> We'll note in the ticket if a problem arises.
>> 
>> * As I've raised elsewhere, Infrastructure work/costs have a direct
>> correlation to podling entry, and podling graduation. Adjusting the
>> podlings@ fan-out at entry/graduation is heaping on. more work. I've
>> spoken
>> with John on HipChat, and asked that the IPMC provide a script to fetch and
>> print the desired set of target dev@ lists (I don't want Infra to guess;
>> y'all need a script to define the set). We'll incorporate that into a daily
>> cron job. Whether the script uses LDAP or pulls podling.xml ... *shrug*
>> 
>> If there are any questions/concerns, then please continue here or in the
>> ticket.
>> 
>> Cheers,
>> Greg Stein
>> Infrastructure Administrator, ASF
>> 
>> [1] https://issues.apache.org/jira/browse/INFRA-13823
>> 
>> 
>> On Mon, Mar 20, 2017 at 1:52 PM, John D. Ament <jo...@apache.org>
>> wrote:
>> 
>>> All,
>>> 
>>> Before I go ahead with it, wanted to see if others had any opinions.  I'm
>>> planning to ask infra to create a podlings@i.a.o mailing list, which
>> would
>>> go to all podlings dev@ list.  There may be some scenarios where we need
>>> to
>>> communicate out to all podlings.  For instance, the logo change and how
>> it
>>> impacts the podlings.
>>> 
>>> John
>>> 
>> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Creating a podlings@incubator.apache.org mailing list

Posted by "John D. Ament" <jo...@apache.org>.
I agree to both points.  I've already started on the script, based on the
existing python scripts we use to generate our reports.

How do others feel about the moderation?  Its only for "official"
communication so..

John

On Wed, Apr 5, 2017 at 11:03 PM Greg Stein <gs...@gmail.com> wrote:

> Hi John, et al,
>
> From an Infrastructure position, I have several points w.r.t to this
> request, and its associated Jira ticket [1] :
>
> * The spam potential is large for this, so I suggest it gets treated like
> announce@apache, which requires sending from @apache and forced moderation
> of *all* messages. I hope we can have a mailing list to use those features
> (a simple fan-out alias won't do it), with subscribers being other lists.
> We'll note in the ticket if a problem arises.
>
> * As I've raised elsewhere, Infrastructure work/costs have a direct
> correlation to podling entry, and podling graduation. Adjusting the
> podlings@ fan-out at entry/graduation is heaping on. more work. I've
> spoken
> with John on HipChat, and asked that the IPMC provide a script to fetch and
> print the desired set of target dev@ lists (I don't want Infra to guess;
> y'all need a script to define the set). We'll incorporate that into a daily
> cron job. Whether the script uses LDAP or pulls podling.xml ... *shrug*
>
> If there are any questions/concerns, then please continue here or in the
> ticket.
>
> Cheers,
> Greg Stein
> Infrastructure Administrator, ASF
>
> [1] https://issues.apache.org/jira/browse/INFRA-13823
>
>
> On Mon, Mar 20, 2017 at 1:52 PM, John D. Ament <jo...@apache.org>
> wrote:
>
> > All,
> >
> > Before I go ahead with it, wanted to see if others had any opinions.  I'm
> > planning to ask infra to create a podlings@i.a.o mailing list, which
> would
> > go to all podlings dev@ list.  There may be some scenarios where we need
> > to
> > communicate out to all podlings.  For instance, the logo change and how
> it
> > impacts the podlings.
> >
> > John
> >
>