Brock Rozen wrote:
>
> On Fri, 29 Sep 2000 at 01:00, Roger B.A. Klorese wrote about "Re: The...":
>
> > > Asking for enhancements, bug fixes, new features, etc. is not a
> > > contribution. Asking for them to be included with the package
> > > because you have already written, tested, debugged, and proven
> > > it works IS contributing.
> >
> > Perhaps it's because of what I do for a living -- product management --
> > but I truly believe asking for features, AND helping to determine if they
> > would be popular and/or beneficial and to whom, *IS* a major contribution.
>
> I happen to agree. And I've proved it with the last of the Mj1 versions
> that Jason worked on.
Ideas are great contributions to a product or project that is actively being
worked on. In the case of open source, I had not considered the possibility
of sparking the interest of a new developer picking up where the previous
left off. In the case of majordomo 1.x, there could be issues with the
license agreement, preventing others from enhancing the code. This is/was
the case with RedHat/Debian offering bug fixed versions of majordomo with
their OS bundle.
>
> Those versions of Mj1 that Jason worked on had lots of idea contributions
> from me. In fact, the way Mj1 allows messages to be approved was the fruit
> of my hand. No, not my code -- that was Jason's -- but what Jason had in
> front of him while he was coding.
>
> > > I feel sympathy for those that won't contribute. (notice I did not say
> > > can't) Mostly because they will always be the leeches that I used to
> > > be.
>
> Why answering questions, even if you don't contribute code or ideas, isn't
> considered contributing is beyond me.
You misunderstood me here. Possibly because of the definition I used for
contribute. I was definitely saying free tech support is a major
contribution. Answering questions in this list is the majority of "my"
contribution.
Dan Liston
|
|
