"Wade" might be a little OTT. ;) I think the doc is too terse, if anything.
(But actually, I think it strikes the balance very well.)
On 3 July 2013 17:51, Eric Johnson wrote:
> My one suggestion would be to group all the historical patterns/commentary
> at the end of the document. That way, pe
My one suggestion would be to group all the historical
patterns/commentary at the end of the document. That way, people looking
for specific information about current practices will not have to wade
through historical information.
Eric
On 7/2/13 6:59 PM, Marvin Humphrey wrote:
On Thu, May 9,
Nice. Thanks Marvin!
On 3 July 2013 06:00, Craig L Russell wrote:
> Marvin,
>
> Nice work. +1
>
> Craig
>
> On Jul 2, 2013, at 6:59 PM, Marvin Humphrey wrote:
>
> > On Thu, May 9, 2013 at 7:29 PM, Noah Slater wrote:
> >> Hey Marvin,
> >>
> >> Did you get anywhere with this?
> >
> > Finally, ye
Marvin,
Nice work. +1
Craig
On Jul 2, 2013, at 6:59 PM, Marvin Humphrey wrote:
> On Thu, May 9, 2013 at 7:29 PM, Noah Slater wrote:
>> Hey Marvin,
>>
>> Did you get anywhere with this?
>
> Finally, yes. I've written up the subject on the Incubator wiki and linked to
> it from the proposal g
Stein
Reply-To: "general@incubator.apache.org"
Date: Tuesday, July 2, 2013 7:32 PM
To: "general@incubator.apache.org"
Subject: Re: Creating announce@ lists by default
>On Tue, Jul 2, 2013 at 9:59 PM, Marvin Humphrey
>wrote:
>> On Thu, May 9, 2013 at 7:29 PM, No
On Tue, Jul 2, 2013 at 9:59 PM, Marvin Humphrey wrote:
> On Thu, May 9, 2013 at 7:29 PM, Noah Slater wrote:
>> Hey Marvin,
>>
>> Did you get anywhere with this?
>
> Finally, yes. I've written up the subject on the Incubator wiki and linked to
> it from the proposal guide.
>
> https://wiki.apac
On Thu, May 9, 2013 at 7:29 PM, Noah Slater wrote:
> Hey Marvin,
>
> Did you get anywhere with this?
Finally, yes. I've written up the subject on the Incubator wiki and linked to
it from the proposal guide.
https://wiki.apache.org/incubator/MailingListOptions
http://incubator.apache.org/gui
On Tue, Mar 26, 2013, at 12:21 PM, Luciano Resende wrote:
> If I was the press/analyst folks or security/sysadmin folks, I'd
> probably prefer to receive all these announcements over one list, then
> having to figure out every announcement list for each apache project
> in use in my infrastructure
Hey Marvin,
Did you get anywhere with this?
Thanks,
On 30 March 2013 15:39, Marvin Humphrey wrote:
> On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater wrote:
> > Thanks Greg. Sane advice. I'll add this to my todo list and see if I can
> > come up with a patch for the docs.
>
> The obvious place t
I really like this idea, Marvin. If you're gonna run with it, I'll take a
step back.
On 30 March 2013 15:39, Marvin Humphrey wrote:
> On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater wrote:
> > Thanks Greg. Sane advice. I'll add this to my todo list and see if I can
> > come up with a patch for th
On Sat, Mar 30, 2013 at 8:06 AM, Noah Slater wrote:
> Thanks Greg. Sane advice. I'll add this to my todo list and see if I can
> come up with a patch for the docs.
The obvious place to patch is the descriptive paragraph here:
http://incubator.apache.org/guides/proposal.html#template-mailing-li
Thanks Greg. Sane advice. I'll add this to my todo list and see if I can
come up with a patch for the docs.
On 28 March 2013 06:50, Greg Stein wrote:
> On Wed, Mar 27, 2013 at 2:46 PM, Noah Slater wrote:
> >...
> > I don't believe we should force an announce@ list on anybody. But I do
> > thin
On Wed, Mar 27, 2013 at 2:46 PM, Noah Slater wrote:
>...
> I don't believe we should force an announce@ list on anybody. But I do
> think it might be a good idea to mention a few of the standard lists that
> projects might consider requesting.
No strong opinion. Generally, I don't think podlings
On 27 March 2013 18:37, Mark Struberg wrote:
> My personal experience: There are a few people registered to
> annou...@apache.org, but there is a low registration rate for the
> respective subproject lists. At least not for most projects.
>
That's to be expected, though, right? We have something
ubject: Re: Creating announce@ lists by default
>
> On Wed, Mar 27, 2013 at 10:23 AM, Luciano Resende
> wrote:
>> On Wed, Mar 27, 2013 at 10:19 AM, Noah Slater
> wrote:
>>> So we just set out a policy for podlings to follow that says something
>>> like: if you
On Wed, Mar 27, 2013 at 10:23 AM, Luciano Resende wrote:
> On Wed, Mar 27, 2013 at 10:19 AM, Noah Slater wrote:
>> So we just set out a policy for podlings to follow that says something
>> like: if you use a project-specific announce@ list, anything you send to it
>> must also be copied to annou.
On 27 March 2013 17:23, Luciano Resende wrote:
> On Wed, Mar 27, 2013 at 10:19 AM, Noah Slater wrote:
>> So we just set out a policy for podlings to follow that says something
>> like: if you use a project-specific announce@ list, anything you send to it
>> must also be copied to annou...@apache.
Putting it in policy is probably as close as we can get to automation. ;)
On 27 March 2013 17:23, Luciano Resende wrote:
> On Wed, Mar 27, 2013 at 10:19 AM, Noah Slater wrote:
> > So we just set out a policy for podlings to follow that says something
> > like: if you use a project-specific ann
On Wed, Mar 27, 2013 at 10:19 AM, Noah Slater wrote:
> So we just set out a policy for podlings to follow that says something
> like: if you use a project-specific announce@ list, anything you send to it
> must also be copied to annou...@apache.org, and vice-versa.
>
> This is how I expect all ann
On 27 March 2013 17:15, sebb wrote:
>
> Well, I found that sending a separate e-mail to announce@a.o was
> useful for two reasons:
> - more likely to get bounces; wanted to distinguish those from TLP list
> bounces
> - people sometime reply all
> - announce@a.o requires an ASF address; I use GMai
On 27 March 2013 16:48, Noah Slater wrote:
> On 27 March 2013 16:28, Luciano Resende wrote:
>>
>>
>> Do the general announce list lag behind because there are individual lists
>> ?
>>
>
> I see no reason why they would.
Well, I found that sending a separate e-mail to announce@a.o was
useful for
On 27 March 2013 16:28, Luciano Resende wrote:
>
>
> Do the general announce list lag behind because there are individual lists
> ?
>
I see no reason why they would.
On 27 March 2013 16:31, Luciano Resende wrote:
>
> The minute that is in the guides, I'm positive that 100% of new
> podlings p
On Wed, Mar 27, 2013 at 7:45 AM, Noah Slater wrote:
> Bertrand, yes, I am not sold on the idea of doing it by default. But
> perhaps sort of advisory, highlighting it as an option, and giving reasons
> why it might be a good idea for some projects?
>
> What would I have to do to add that? If I pre
On Tue, Mar 26, 2013 at 6:14 PM, Marvin Humphrey wrote:
> On Tue, Mar 26, 2013 at 4:05 AM, Noah Slater wrote:
>
>> I am under the impression that having a low-volume, high-signal
>> announcement channel is generally beneficial to most projects that try it.
>
> I agree that such lists are useful.
On Wed, Mar 27, 2013 at 3:45 PM, Noah Slater wrote:
> Bertrand, yes, I am not sold on the idea of doing it by default. But
> perhaps sort of advisory, highlighting it as an option, and giving reasons
> why it might be a good idea for some projects?
Yes, sounds good to me if it's just a suggestion
Bertrand, yes, I am not sold on the idea of doing it by default. But
perhaps sort of advisory, highlighting it as an option, and giving reasons
why it might be a good idea for some projects?
What would I have to do to add that? If I prepare a patch to the docs,
would it be CTR or RTC?
On 27 Marc
On Wed, Mar 27, 2013 at 2:14 AM, Marvin Humphrey wrote:
> ...As to whether such lists should be encouraged for new podlings (probably by
> putting a stub in the proposal template alongside the other lists), I can't
> say that I have a strong opinion
IIUC Noah's proposal goes further and sugge
On Tue, Mar 26, 2013 at 4:05 AM, Noah Slater wrote:
> I am under the impression that having a low-volume, high-signal
> announcement channel is generally beneficial to most projects that try it.
I agree that such lists are useful. I like to subscribe to individual
announce lists for security pu
On Tuesday, March 26, 2013, Andrei Savu wrote:
> I think we should see this as option and let the podling decide.
>
> In some cases it's useful but most of time it's enough if you filter
> the dev / user lists for messages that contain ANNOUNCE in the subject
> line.
+1
>
> -- Andrei Savu / ax
I think we should see this as option and let the podling decide.
In some cases it's useful but most of time it's enough if you filter
the dev / user lists for messages that contain ANNOUNCE in the subject
line.
-- Andrei Savu / axemblr.com
On Tue, Mar 26, 2013 at 7:50 PM, Noah Slater wrote:
>
Why would you want to subscribe to the announce list of every new incubator
project? If you wanted to do that, you'd just subscribe to
general@incubator.apache.org, or even annou...@apache.org.
Please note, I am not suggesting we disband annou...@apache.org. We already
have plenty of TLPs using an
On Tue, Mar 26, 2013 at 10:38 AM, Noah Slater wrote:
> Yep. Obviously, I'm aware we have a foundation-wide announce list. :)
>
> It's not very helpful for people who are only interested in one or two
> projects, however.
>
> If I am using Hadoop, and only care about knowing about new Hadoop releas
Yep. Obviously, I'm aware we have a foundation-wide announce list. :)
It's not very helpful for people who are only interested in one or two
projects, however.
If I am using Hadoop, and only care about knowing about new Hadoop releases
or security disclosures, I do not want to:
a) subscribe to a
On Tue, Mar 26, 2013 at 6:21 PM, Luciano Resende wrote:
> ...We already have a Apache wide announce list, which is used for release
> announcements and probably can or is already used for the other things
> you mentioned
Yes, see http://www.apache.org/foundation/mailinglists.html#foundation-a
On Tue, Mar 26, 2013 at 10:14 AM, Noah Slater wrote:
> Luciano, release announcements and security disclosures.
>
> Jordan, can you clarify what you understand by "be maintained"? Just to be
> clear, this is a one time operation, and as far as I know, comes with no
> maintenance costs whatsoever.
Luciano, release announcements and security disclosures.
Jordan, can you clarify what you understand by "be maintained"? Just to be
clear, this is a one time operation, and as far as I know, comes with no
maintenance costs whatsoever. So the "too much" part of "too much for
little gain" doesn't ap
There are already 3 public and 1 private lists that have to be maintained.
Another list just for announcements seems like too much for little gain. The
users list should suffice for announcements (with [ANN] in the subject).
-JZ
On Mar 26, 2013, at 4:05 AM, Noah Slater wrote:
> Incubator,
>
On Tue, Mar 26, 2013 at 4:05 AM, Noah Slater wrote:
> Incubator,
>
> Is there a reason we don't recommend podlings create an announce@ list by
> default?
>
> I am under the impression that having a low-volume, high-signal
> announcement channel is generally beneficial to most projects that try it.
38 matches
Mail list logo
