Hi, Your English is great, don't let that stop you from expressing your opinions ;)
Yoav Shapira Millennium Research Informatics >-----Original Message----- >From: Paulo Simao [mailto:[EMAIL PROTECTED] >Sent: Friday, March 19, 2004 3:29 PM >To: [EMAIL PROTECTED] >Subject: RE: Jakarta embracing the JCP? > >In my opinion, JCP and ASF should keep working just as they are. >JCP has a more conceptual work, defining patterns and standards, while ASF >has a more "hands on" to implement JSRS. > >It is the biz of JCP define what ASF is to do, while is about ASF know HOW >to do it. >Sun needs to keep some order in Java comunity, and that´s why JCP exists >under her flag. ASF, in contrast is completely free, having no Boss, but >ourselves. > >Naturally, ASF´s process is much ligther in terms of burocracy focusing in >real world implementation of some spec defined. (specs are aways >specs...hard to define, hard to rollback, better, no rollback, just a >deprecated javadoc tag. Have you seen a refactoring in a JSR before? :-) ) > >things are working this way, and I think they should be kept this way. > >Sorry if this hurted someone, but my english is not so rich as I wished, to >express my ideas. > >regards, >Paulo. > >>From: "Noel J. Bergman" <[EMAIL PROTECTED]> >>Reply-To: "Jakarta General List" <[EMAIL PROTECTED]> >>To: "Jakarta General List" <[EMAIL PROTECTED]> >>Subject: RE: Jakarta embracing the JCP? >>Date: Fri, 19 Mar 2004 13:44:32 -0500 >> >> > How about if Jakarta [or Apache-Java as a whole] embraced the latest >JCP >> > process? >> >>In what way? Can you be specific? As I understand the JCP, what you are >>asking makes little sense. >> >>We don't have "spec leads", nor do we want them. We don't have ownership >>of >>a project/specification. Everything here is communal and consensual. >That >>is not true of the JCP. Actually, I would prefer to see the JCP continue >>to >>evolve to become more like the ASF. >> >> > What I'm largely interested in are the reasons why not, as these would >>be >> > perfect reasons why something like groovy, or ant or httpclient, should >> > not become jsr's. >> >>A JSR is a specification. It should have a TCK and an RI, but at heart it >>is a specification. Some people have talked about proposing the Apache >>Repository Specification, which I understand Maven will evolve to use, as >a >>JSR. If that happened, I'd prefer to see us run a JCP Expert Group more >in >>line with an ASF project, not run ASF projects like an JCP Expert Group. >> >>Geir? Your thoughts? >> >> --- Noel >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [EMAIL PROTECTED] >>For additional commands, e-mail: [EMAIL PROTECTED] >> > >_________________________________________________________________ >MSN Hotmail, o maior webmail do Brasil. http://www.hotmail.com > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
