Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 10218 invoked from network); 22 Aug 2002 21:53:45 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 22 Aug 2002 21:53:45 -0000 Received: (qmail 8989 invoked by uid 97); 22 Aug 2002 21:53:59 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 8912 invoked by uid 97); 22 Aug 2002 21:53:58 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 8810 invoked by uid 98); 22 Aug 2002 21:53:57 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) From: Ola Berg To: commons-dev@jakarta.apache.org Reply-To: Ola Berg MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: Tripnet Webmail (IMP/PHP) Sender: ola.berg@arkitema.se Subject: Re: [OT] Newcomers Message-Id: Date: Thu, 22 Aug 2002 23:53:24 +0200 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N costinm writes: >What I resent is people forgeting the goal of commons - to provide a way >for jakarta projects to share code - and writing code \'for the sake of >writing code\'. Not having a real use for the code in a project... [snip] >It is perfectly reasonable for \'newcomers\' who need a piece of >commons software to behave in a way that makes it useable for >them to make those changes. It is expected that those using the >code in real projects will use their votes to make sure the >changes are not breaking their stuff. bayard writes: >I apologise. I was working under the misunderstanding that I was helping >to build a nice common library that enhance the existing JDK, I got the same impression as Henri did, from the commons charter. After all these flames back and forth, I have re-read the charter and proposal and found that if you know that \"commons\" originally meant \"common to jakarta projects\", you will have one impression of the meaning of the charter; and if you come from the outside without the background history, Henri\'s and mine interpretation (\"common code for the whole world\") isn\'t illogical. No wonder you elders gets pissed off sometimes when we come in with an attitude that seems to break what you know was the original intention of commons. Sorry. I thought that what we was doing here was unifying the utilities that we all, by experience, have collected during the years, or missed in JDK, from existing jakarta projects as well as from other places. Reuse in a wider scope than just within other jakarta projects. In that scenario, breaking backwards compatibility with jakarta projects is bad, but not worse than breaking backwards compatibility with anything else. Unifying on what the community by collective experience feels is the best way means sacrificing how one used to do things sometimes. I suggest that: 1) I and other newcomers change our attitude 2) The wording in the guidelines for the commons project are changed as to more clearly reflect the original intention of the project. Since I wasn\'t the only one misunderstanding this, I think a clarification is justified. /O -------------------- ola.berg@arkitema.se 0733 - 99 99 17 -- To unsubscribe, e-mail: For additional commands, e-mail: