Hello,
Guys, don't get me wrong, but you're sounding like a bunch of old man
talking about the good old days, where you did everything on the command
line. ;-)
I'm 29 and before Apache, I hadn't heard about mailing lists. It always
felt clumsy to me. I know github and twitter. That's just the stuf
I'll certainly admit that I'm a "traditionalist". But I hope that I can be
credited with trying other things when they come along.
Unfortunately, there is no other format of communications that is standards
based and thus has all the necessary tools for being productive. If there were
I'd be ha
On Sun, Jan 18, 2015 at 8:26 AM, David Nalley wrote:
> On Sun, Jan 18, 2015 at 7:34 AM, Benedikt Ritter
> wrote:
> > Hi all,
> >
> > over at the Apache Commons Project, we have a long discussion about our
> > mailing lists. Are they to noisy? Should they be splitted up into
> sublists?
> > Shoul
With respect to search:
There's an ASF project, some of you might have heard of it, and, rumor
has it, they build a pretty good full-text search engine. So, instead
of complaining about the quality of MarkMail, perhaps we could address
this end of things by looking into more sophisticated use of,
Ross beat me to the punch
On Sunday, January 18, 2015, Ross Gardler (MS OPEN TECH) <
ross.gard...@microsoft.com> wrote:
> For me any alternative would still have to push everything into my inbox
> where I can use a my preferred tools, each developed and matured over many
> years, to help me proce
On 18.01.2015 19:23, Phil Steitz wrote:
> One thing that I agree is a shame is the deterioration of mail clients
> and archive search tools. Gmail is a disaster. I personally use
> Thunderbird for all ASF lists. I also use markmail a lot for
> searching, as it is superior to what we have internally
On 1/18/15 5:53 AM, Claude Warren wrote:
> I prefer the mailing list because it pushes new concepts to me. Git and
> such requires that I work harder to get the information. Most of the
> Apache mailing lists have a high signal to noise ratio. And even the
> signals I am not interested in don't
On 18.01.2015 18:10, Joseph Schaefer wrote:
> After all git is born out of dissatisfaction with svn, but Linus wrote the
> tool instead of simply publicly whinging about his hatred for svn.
You mean, "as well as," not "instead of." :)
-- Brane
I think Ross's consideration also applies to the many folks who cling to
technology of the 70s (i.e., the Internet versions of News Readers) to access
and contribute to ASF mailing lists.
- Dennis
-Original Message-
From: Ross Gardler (MS OPEN TECH) [mailto:ross.gard...@microsoft.com]
Hi,
I am new to this list and have been following this thread. I don't know whether
I missed this. But loomio is a free software for collaborative decision making
processes and its a free software. Do check it out.
It's easy to keep track.
On January 18, 2015 9:57:44 PM GMT+05:30, Christophe
I've seen this discussion a hundred times or so at Apache, whether it's forums
issue trackers or version control. The story is always the same: a handful of
software artisans want full uncompromising control over their toolchain. Half
the time as is true here what they want is already function
On Sun, Jan 18, 2015 at 11:19 AM, jan i wrote:
> On 18 January 2015 at 16:48, Ross Gardler (MS OPEN TECH) <
> ross.gard...@microsoft.com> wrote:
>
>> There are many reasons why the ASF requires projects to use its own
>> servers for some items. For example, we couldn't use GitHub until we had
>> b
On Sun, Jan 18, 2015 at 7:34 AM, Benedikt Ritter wrote:
> Hi all,
>
> over at the Apache Commons Project, we have a long discussion about our
> mailing lists. Are they to noisy? Should they be splitted up into sublists?
> Should individual components go TLP?
> IMHO Ben McCann summed up the core pr
On Sun, Jan 18, 2015 at 7:34 AM, Benedikt Ritter wrote:
[snip]
> Now I'm curious: Does anybody here really like the use of mailing lists? Or
> do we all simply go through the struggle of setting up filters etc. just
> because this is the way it has always been?
>
>
I absolutely loathe mailing lis
On 18 January 2015 at 16:48, Ross Gardler (MS OPEN TECH) <
ross.gard...@microsoft.com> wrote:
> There are many reasons why the ASF requires projects to use its own
> servers for some items. For example, we couldn't use GitHub until we had
> built a system that would provide adequate traceability o
There are many reasons why the ASF requires projects to use its own servers for
some items. For example, we couldn't use GitHub until we had built a system
that would provide adequate traceability of contributions.
Failure to do that would have meant it was no longer possible to provide the
leg
Hi Apache .
Every so often we get the question come up: does Apache infra allow/support
. The answer is sometimes "not yet" and related to the fact that there are
100s of projects that require uniformity at Apache, and it would be chaos of
every new project was allowed a new infrastructure
For me any alternative would still have to push everything into my inbox where
I can use a my preferred tools, each developed and matured over many years, to
help me process the volume of communications I need (filters, archives,
calendars etc.)
Ross
Sent from my Windows Phone
Perhaps there is an opportunity here for a new Apache project that can meet
the requirements outlined above. But then that might just be a "me too"
implementation of several new mail reading/processing tools from the big
companies.
On Sun, Jan 18, 2015 at 1:21 PM, jan i wrote:
> On 18 January 2
On 18 January 2015 at 14:15, Benson Margulies wrote:
> The Apache Software Foundation has a requirement of open, public,
> decision-making. The short-hand implication of those requirements is that
> 'discussions that lead to decisions are made on mailing lists.' Closely
> related is the requireme
Hi.
I don´t like github/gitlab but agree it has advantages and disadvantages to
mailing lists.
One of the biggest and most important disadvantage is that not all projects
use git and even less use github
(even though admitted the number is climbing).
I too find mailing lists outdated. Personally
The Apache Software Foundation has a requirement of open, public,
decision-making. The short-hand implication of those requirements is that
'discussions that lead to decisions are made on mailing lists.' Closely
related is the requirement that important functions take place on ASF
infrastructure.
I prefer the mailing list because it pushes new concepts to me. Git and
such requires that I work harder to get the information. Most of the
Apache mailing lists have a high signal to noise ratio. And even the
signals I am not interested in don't take that long to dispose of.
Claude
On Sun, Ja
Hi all,
over at the Apache Commons Project, we have a long discussion about our
mailing lists. Are they to noisy? Should they be splitted up into sublists?
Should individual components go TLP?
IMHO Ben McCann summed up the core problem pretty well [1]. Mailing lists
are simply a outdated tool from
24 matches
Mail list logo
