I'm very grateful to Joan for sharing this. It must have been difficult
and time consuming to write this experience down. It required courage to
put this information in the public, in the context of my original post
which was very critical of offlist development. I learned a lot from your
story
Hi,
On Sat, Nov 3, 2018 at 8:37 PM Joan Touzet wrote:
> ...In a way, it feels a bit like having had bypass surgery, I
> guess :)
Indeed, thank you very much for sharing this!
I think the conclusion at this point is that large code drops are not
*necessarily* damaging to a community but handling
a bit like having had bypass surgery, I
guess :)
-Joan
- Original Message -
> From: "Myrle Krantz"
> To: dev@community.apache.org, "dev"
> Sent: Thursday, October 18, 2018 7:18:07 AM
> Subject: Why are large code drops damaging to a community?
>
> H
On Wed, 31 Oct 2018 at 08:44, Myrle Krantz wrote:
>
> On Fri, Oct 19, 2018 at 10:32 PM James Dailey wrote:
> >
> > +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 g
On 31 Oct 2018 17:03, "Jim Jagielski" wrote:
Ahh... I missed the "so if y'all would like to
elaborate" part of your email... Let me pull
together some thoughts and expand/extend the story :)
> On Oct 31, 2018, at 4:44 AM, Myrle Krantz wrote:
>
> I haven't given up hope that Jim
> will provide
Ahh... I missed the "so if y'all would like to
elaborate" part of your email... Let me pull
together some thoughts and expand/extend the story :)
> On Oct 31, 2018, at 4:44 AM, Myrle Krantz wrote:
>
> I haven't given up hope that Jim
> will provide more details.
>
On Fri, Oct 19, 2018 at 10:32 PM James Dailey wrote:
>
> +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 suspect that Jim's example of Robert Thau's htt
Thank you for sharing your experiences with offlist development Alex.
Even single-developer large code drops can be damaging to the
community in some cases. Malcolm Upayavira gave a good example. But
single developers may find it easier to remedy the situation in the
same way Upayavira did: by c
Hi all,
well of course there will be off-list development, if something new is donated
to the ASF.
I guess Myrle's point is, that for an existing project, features that are
communicated and implemented off-list and are brought back after some time is
damaging.
I fully agree with that assumpti
This is just a nitpick, but it is the subject line that is bothering me.
Having a "no large code drops" mantra is not the same as a "limit off-list
collaboration" mantra which is different from a "no off-list development"
mantra.
For Flex, Adobe made something like 5 large code drops. It simp
Hey all,
I'd like to invite anyone with relevant positive or negative
experiences with off-list development or large code drops to share
those experiences. The ASF policy of "no off-list development" is
implemented in a wide variety of ways in various communities, but
there are still may be some
ook for Android<https://aka.ms/ghei36> herunterladen
From: mike peoni
Sent: Saturday, October 20, 2018 7:01:47 AM
To: dev@community.apache.org
Subject: Re: Why are large code drops damaging to a community?
In talking about https MyOpj.VisibleEh would this be appropriate for a
large Apl so you w
In talking about https MyOpj.VisibleEh would this be appropriate for a
large Apl so you wouldn't raise flags and further more i put 2 Apl on face
book just anonymized on my page then they put up a developers page and i
liked it and i went to close my
account and my Apl where there
In the dev, page
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
-Original Message-
> From: Shane Curcuru
> Sent: Thursday, October 18, 2018 8:26 PM
> To: Apache Community Development ; Apache
> Fineract Dev
> Subject: Re: Why are large code drops damaging to a community?
>
> Myrle Krantz wrote on 10/18/18 7:18 A
arts of your software solution.
Ross
-Original Message-
From: Shane Curcuru
Sent: Thursday, October 18, 2018 8:26 PM
To: Apache Community Development ; Apache Fineract
Dev
Subject: Re: Why are large code drops damaging to a community?
Myrle Krantz wrote on 10/18/18 7:18 AM:
> H
Hi again ! Yes endeed ! As I have spoken I Am Always on dispositon gladly
could help if I would be able to do that. Of course without any obligation.
I could have oportunity learning from peoples who are highly, educated and
skillful on their Job. You can contact me whenever you want. Thank you ver
Myrle Krantz wrote on 10/18/18 7:18 AM:
> Hey all,
>
> There are many forms of offlist development. One form of offlist
> development is working on large code drops in private and then
> contributing them all at once. Threshold size is probably arguable,
> and varies by project; put that aside f
Something about this topic Firstly cause of practical reasons. As I have
noticed I Am opened to every colaboration and I would Like to give hand if
I could help withouth any obligations. Just friendly and freely. I do
appreciate you and your working. Sincerely yours.--Zeljko Leskur.
Dana 18. 10. 20
Hi ! Thank you very much for your mail and friendly and very I might Said
expert explanation . I do know that you're doing your Job but anyway I Am
highly respecting you and your knowledge. So I'll try to explain my
position and at the same time descrobe my position. I will do that
honestly and re
Hey all,
There are many forms of offlist development. One form of offlist
development is working on large code drops in private and then
contributing them all at once. Threshold size is probably arguable,
and varies by project; put that aside for the moment. I've been
working on an explanation
27 matches
Mail list logo
