Hey Jim,
I’d say they are a symptom *and* a problem. But putting that aside, can you
unroll what you mean please?
What was that code drop from SGI a symptom of?
What did Robert Thau do (or not do), before during or after to ensure the
success of httpd?
Best Regards,
Myrle
On Sat 20. Oct 2018 a
I would say that, in general, large code drops are more a *symptom* of a
problem, rather than a problem, in and of itself...
> On Oct 19, 2018, at 5:12 PM, Alex Harui wrote:
>
> IMO, the issue isn't about large code drops. Some will be ok.
>
> The issue is about significant collaboration off-
IMO, the issue isn't about large code drops. Some will be ok.
The issue is about significant collaboration off-list about anything, not just
code.
My 2 cents,
-Alex
On 10/19/18, 1:32 PM, "James Dailey" wrote:
+1 on this civil discourse.
I would like to offer that sometimes larg
+1 on this civil discourse.
I would like to offer that sometimes large code drops are unavoidable and
necessary. Jim's explanation of httpd contribution of type 1 is a good
example.
I think we would find that many projects started with a large code drop
(maybe more than one) - a sufficient amoun
It be disheartening if one has pulled to fix one thing and another
committer fixes it under another huge fix without collaborating with one.
This happens occasionally with superstars and it is enough to stop new
committers contributing at all.
Steph
On Fri, Oct 19, 2018 at 9:44 AM Malcolm Upayavi
My wayback was to 2002/3, when I was playing with Cocoon. Their CLI was
implemented as a large monolithic Java class, and quite impenetrable. I had
spent an age working on a large refactoring that made it much clearer and more
usable. Unfortunately, it also broke backwards compatibility.
Vadim
Large code drops are almost always damaging, since inherent in that process is
the concept of "throwing the code over a wall". But sometimes it does work out,
assuming that continuity and "good intentions" are followed.
To show this, join me in the Wayback Machine as Sherman and I travel to the
Would like to come nov. 30th please forward detailed message of event times
and travel & accomadations thanks mpeoni
On Fri, Oct 19, 2018, 4:05 AM Ignasi Barrera wrote:
> The talk is on November 30th, at 15:00. If you can make it for that time,
> that would be perfect :)
>
> On Fri, 19 Oct 2018
The talk is on November 30th, at 15:00. If you can make it for that time,
that would be perfect :)
On Fri, 19 Oct 2018 at 08:23, Mike Yuxxxp wrote:
> On Thu, Oct 18, 2018, 11:11 PM Santiago Gala
> wrote:
>
> > I will be able to stay early afternoon.
> >
> > Let me know if it works for you, so t
+1
>
> On October 19, 2018 at 4:18 AM r...@gardler.org wrote:
>
> +1 to both Shane and Myrle's input here.
>
> The Apache Way is all about consensus building in order to maximize the
> potential for collaboration between partners. It is impossible to drive
> consensus within a com
Hi,
No answers here, but I got positive feedback at the-asf #general (1:
yes, it's open for everyone, 2: an auto invite would be great)
1.) I will create an INFRA ticket to install an auto-invite system
(similar to http://slack.k8s.io/) if no objection in the next 3 working
days. And help if it
11 matches
Mail list logo
