Ted Husted [EMAIL PROTECTED] wrote:
Conor MacNeill wrote:
I think it would be better to start with one mailing list so ensure
there is enough "mass" in discussions.
I feel strongly that there should be a combined user/dev list for
each package, and I personally stand by the statement in
Ted,
Let me give my counter point and then I will say no more.
IMHO, for a list to be useful it needs to have a certain critical mass of
subscribers. When there aren't enough people to get a discussion going,
people stop posting. If the messages are few and far between, the list
tends to
At 09:21 7/3/01 -0500, Ted Husted wrote:
Peter Donald wrote:
I will say it again - though no one really seems to listen.
No one's asking you to do anything you don't want to do, Peter. If you
are not comfortable working on a Commons package, then you should not
work on a Commons package.
I
Preface:
Before Pier calls me an ass again... ;-)
I would like to point out that despite being the chair to the PMC, I
have never had the opportunity to actually observe an election of a PMC
member. My election to the PMC was done in private as had all others
before me, and no
Say I'd propose to move the org.apache.tools.tar and
org.apache.tools.mail packages from Ant to the commons repository -
which I'll probably do - these are very small thingies that don't
really need separate mailing lists at all.
+1 !!
And maybe parts of ProjectHelper ( turned into a
on 3/7/01 5:08 AM, "Sam Ruby" [EMAIL PROTECTED] wrote:
Jon Stevens wrote:
7: Should provide an interface or implement a Sun defined interface.
s/Sun defined/standard/
- Sam Ruby
define standard.
http://jakarta.apache.org/velocity/ymtd/ymtd-implementation.html
-jon
--
If you come
on 3/7/01 5:21 AM, "Ted Husted" [EMAIL PROTECTED] wrote:
How about:
7. In general, packages should provide an interface and one or more
implementations of that interface, or implement another standard
interface (e.g. one defined by Sun).
-1
I don't like the implication that something
on 3/7/01 4:57 AM, "Ted Husted" [EMAIL PROTECTED] wrote:
I feel strongly that there should be a combined user/dev list for each
package, and I personally stand by the statement in the FAQ.
This will fail for new projects.
Reason: community building.
To create a community, you need a single
FYI, I documented the Jakarta process of asking for permission for new
account creation by the projects so that I can distribute my load a bit.
Under the Committers heading:
http://jakarta.apache.org/site/roles.html
Specifics:
"Once there are 3 positive votes, someone from the
Peter,
On Thu, 8 Mar 2001, Peter Donald wrote:
I already work on commons packages - after all I work on Avalon ;)
Avalon is not a commons package, it is a "common framework for server
applications". Why does the framework need to contain code to accomplish
specific tasks?
What Ted
At 02:53 7/3/01 -0600, Tim O'Brien wrote:
Avalon is not a commons package, it is a "common framework for server
applications". Why does the framework need to contain code to accomplish
specific tasks?
The perception that it is solely a framework is wrong. Frameworks by
themselves are useless
Pier P. Fumagalli wrote:
Was it _that_ hard to understand ? :)
Not after you explained it so politely and nicely to me... ;-)
- Sam Ruby
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
I tried to let this thread expire without getting involved but I simply
can't
stand it anymore.
His articles got me so worked up that I wrote him back personally. Probably
inundated with mail from upset readers, he never responded to me.
First of all, when someone makes a blatant claim that
13 matches
Mail list logo
