test

2003-07-02 Thread Franck POCHET
 
 

__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: The vendors page

2003-07-02 Thread Santiago Gala
Andrew C. Oliver escribió:
The original intent of the vendors.xml page was:

 1. Because I got sick of hearing people say Jakarta projects are not
supported and wanted a page to send people to during presentations.
 2. So a certain unnamed committer would not feel the need to spam the lists
(because I though if he got away with it, others would start doing it and
then I'd get lists full of consultancy spam).
Now that Open Source is no longer a commercial cussword and I doubt even an
economic turnaround will kill the momentum, I think that the policy for that
page ought to be just have one of the committers you employ on the Jakarta
projects you support make the change.  Thus tightening it from people who
support Jakarta projects to people who support Jakarta projects.
Thoughts/Objections?

+1 It is a simple test of reasonable support, not just lurking.

I would not say you employ, but just convince one jakarta commiter to 
make the change. This would ensure at least some level of communication 
(like sending it to the project -dev list and discussing it there, etc.)

It the spirit of Open Source, if a Company is not able to have a fluid 
relation with at least one committer of one of the projects they 
support, I can't see how they can claim support of the projects.

Note I'm saying less than Andy. Not employing a committer, but 
channelling the change through one committer. The company maybe 
contributed some patches or docs, or just good answers in the -user 
list, but the project committers should be aware of them existing and 
supporting the project.


-Andy
Regards
--
Santiago Gala
High Sierra Technology, S.L. (http://hisitech.com)
http://memojo.com?page=SantiagoGalaBlog


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


[ºÎÀçÁ߸ÞÀÏ] [ANNOUNCE] Release of Commons HttpClient 2.0 Beta 2

2003-07-02 Thread nylons
This mail address is obsolete!

_
Çѹ̸£ ¸ÞÀÏ  ( http://mail.hanmir.com/ )
¿ì¸®³¢¸® ÅëÇÏ´Â ÀÎÅÍ³Ý ¾ÆÁöÆ® Çѹ̸£ ( http://www.hanmir.com/ )
---BeginMessage---
The Jakarta Commons HttpClient team is proud to announce the release of 
HttpClient 2.0 beta 2.  Most likely this will be the last beta before 
the final 2.0 release.  Please visit the HttpClient website 
http://jakarta.apache.org/commons/httpclient/ and download this 
latest release.

The following changes have been made since Release 2.0 Beta 1:

 * 20240 - Cookies with null path are no longer rejected in the
   browser compatibility mode.
 * 20481 - Query parameters set via 
HttpMethodBase.setQueryString(NameValuePair[])
   now correctly use 'application/x-www-form-urlencoded' encoding.

 * 20481 - POST method correctly applies 
'application/x-www-form-urlencoded'
   encoding.

 * 20569 - Duplicate connection headers are now handled.

 * 20646 - Fixed NTLM proxy authentication via SSL.

 * 20665 - Changed URI to correctly handle path resolution according to
   http://www.apache.org/~fielding/uri/rev-2002/issues.html.  In
   particular dot-segments are removed when not necessary.
 * 20938 - Connections are now closed when the request is missing a 
content
   length and is not chunked.

 * 20942 - Requests with DIGEST authentication are now correctly handled
   when redirected.
 * 21130 - DEFAULT_MAX_HOST_CONNECTIONS and 
DEFAULT_MAX_TOTAL_CONNECTIONS are
   now public in MultiThreadedHttpConnectionManager.

 * 21201 - URIs are now correctly rebuilt following a call to 
URI.normalize().

 * 21202 - WireLogInputStream.read(byte[]) now logs the correct number 
of bytes.

 * Fixed path parsing in RFC2109 cookie spec.

 * Fixed possible NPE when reading an empty response body.

 * The various to*Charset() methods of URIUtil have been deprecated.

Thank you,

Commons HttpClient Development Team

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---End Message---
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: The vendors page

2003-07-02 Thread Steven Noels
On 2/07/2003 11:13 Santiago Gala wrote:

I would not say you employ, but just convince one jakarta commiter to 
make the change. This would ensure at least some level of communication 
(like sending it to the project -dev list and discussing it there, etc.)
+1 on being present on the list and discussing things

snip/

the project committers should be aware of them existing and 
supporting the project.
Yep - so basically this should be decided on a subproject-level in 
Jakarta's case. I doubt *anyone* is able to support *all* Jakarta 
subprojects on a level that he/she serves his customers well. 
Suggestion: move this page away from the Jakarta main site, and 
stimulate subprojects to host their own vendor pages.

/Steven
--
Steven Noelshttp://outerthought.org/
Outerthought - Open Source, Java  XML Competence Support Center
Read my weblog athttp://blogs.cocoondev.org/stevenn/
stevenn at outerthought.orgstevenn at apache.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: The vendors page

2003-07-02 Thread Howard M. Lewis Ship
I'm tending towards the argument that if you can convince someone who has the right 
access to update
the vendors.xml
page, then you deserve to be on the list.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry



 -Original Message-
 From: Steven Noels [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, July 02, 2003 8:37 AM
 To: Jakarta General List
 Subject: Re: The vendors page
 
 
 On 2/07/2003 11:13 Santiago Gala wrote:
 
  I would not say you employ, but just convince one 
 jakarta commiter 
  to
  make the change. This would ensure at least some level of 
 communication 
  (like sending it to the project -dev list and discussing it 
 there, etc.)
 
 +1 on being present on the list and discussing things
 
 snip/
 
  the project committers should be aware of them existing and
  supporting the project.
 
 Yep - so basically this should be decided on a subproject-level in 
 Jakarta's case. I doubt *anyone* is able to support *all* Jakarta 
 subprojects on a level that he/she serves his customers well. 
 Suggestion: move this page away from the Jakarta main site, and 
 stimulate subprojects to host their own vendor pages.
 
 /Steven
 -- 
 Steven Noelshttp://outerthought.org/
 Outerthought - Open Source, Java  XML Competence Support Center
 Read my weblog athttp://blogs.cocoondev.org/stevenn/
 stevenn at outerthought.orgstevenn at apache.org
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[JAKARTA NEWSLETTER] News on Jakarta from May to June, 2003

2003-07-02 Thread Tetsuya Kitahata
Hello, All


We are now preparing the 'Jakarta Newsletter Issue 9',
news from May to June 2003, which would be published
in the middle of July 2003.

The 'Jakarta Newsletter Issue 9' will be appeared at
http://jakarta.apache.org/site/news/200305.html
and the editorial deadline would be 00:00 GMT, 6th July.

We lowered the barrier to entry - users and developers will
be able to easily contribute, as prepared the
ApacheWiki (http://nagoya.apache.org/wiki/apachewiki.cgi).

If you have anything to be added to the ApacheWiki, please go to
http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue9
and fill in up what you want to append.
If there's nothing news-worthy on the projects, then please just
write *N/A*.

If you have been voted in as a new committer in jakarta or
jakarta-related projects within these 2 months, please add your
name to the list on ApacheWiki.

Probably, the former newsletter draft (Jakarta Newsletter Issue8)
would give you some hints in writing the articles.
cf. 
http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue8March2003


If you have any questions about this, please send your messages to
[EMAIL PROTECTED]

Sincerely,

-- Tetsuya ([EMAIL PROTECTED])

P.S. I wanna post these above to each projects' dev list sooner or later.


-
Tetsuya Kitahata --  Terra-International, Inc.
E-mail: [EMAIL PROTECTED]: [EMAIL PROTECTED]
http://www.terra-intl.com/
(Apache Jakarta Translation, Japanese)
http://jakarta.terra-intl.com/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: The vendors page

2003-07-02 Thread Andrew C. Oliver
Okay, then I shall for now on dutifully ignore patches to the page from
names I do not recognize.  I, personally, am unlikely to commit patches at
all (figuring most should be able to commit them themselves with the rare
exceptions mentioned) from this point on.

-Andy

On 7/2/03 9:51 AM, Howard M. Lewis Ship [EMAIL PROTECTED] wrote:

 I'm tending towards the argument that if you can convince someone who has the
 right access to update
 the vendors.xml
 page, then you deserve to be on the list.
 
 --
 Howard M. Lewis Ship
 Creator, Tapestry: Java Web Components
 http://jakarta.apache.org/tapestry
 
 
 
 -Original Message-
 From: Steven Noels [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, July 02, 2003 8:37 AM
 To: Jakarta General List
 Subject: Re: The vendors page
 
 
 On 2/07/2003 11:13 Santiago Gala wrote:
 
 I would not say you employ, but just convince one
 jakarta commiter
 to
 make the change. This would ensure at least some level of
 communication 
 (like sending it to the project -dev list and discussing it
 there, etc.)
 
 +1 on being present on the list and discussing things
 
 snip/
 
 the project committers should be aware of them existing and
 supporting the project.
 
 Yep - so basically this should be decided on a subproject-level in
 Jakarta's case. I doubt *anyone* is able to support *all* Jakarta
 subprojects on a level that he/she serves his customers well.
 Suggestion: move this page away from the Jakarta main site, and
 stimulate subprojects to host their own vendor pages.
 
 /Steven
 -- 
 Steven Noelshttp://outerthought.org/
 Outerthought - Open Source, Java  XML Competence Support Center
 Read my weblog athttp://blogs.cocoondev.org/stevenn/
 stevenn at outerthought.orgstevenn at apache.org
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

-- 
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI

http://jakarta.apache.org/poi
For Java and Excel, Got POI?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: The vendors page

2003-07-02 Thread Michael Davey
Howard M. Lewis Ship wrote:

I'm tending towards the argument that if you can convince someone who has the right 
access to update
the vendors.xml
page, then you deserve to be on the list.
My motivation for attempting to add Collabra to the list was with the 
long-term plan of moving one of my engineers to a full time open source 
role in response to the additional business that the entry produced. 
Right now we make the occasional contribution to other Open Source 
projects but virtually no contributions to Apache (and those were done 
in employees' own time).  If there is enough paid Jakarta work to keep 
one of my engineers busy for 3 or 4 days a week, the decision to ask him 
to find other Jakarta stuff to do for the rest of his time is an easy 
one to make.

Perhaps over time, he would get known and accepted in the community and 
someone would choose to nominate him for committer priviledges. 
Obviously, that is something that Collabra would have very little 
control over.

An alternative would be to employ an existing committer (perhaps 
poaching them from their existing employer).  A side-effect would be 
that they would then be obligated for the most part to work on features 
that Collabra deems important, rather than what the wider community 
wants, thus actually reducing the capacity of the Jakarta project to 
achieve its aims.  This goes completely against our corporate philosophy 
and, IMHO, the spirit of the communtiy and I won't do it.

I guess what I am saying is that we are a small company with limited 
resources (heck, even Sendmail, Inc. only contributes ~50 man-hours per 
week to freeware sendmail). We want to help out and give something back 
to the community (beyond increasing the install base and training 
users), but we need you to help us help you.

--
Michael Davey
Technical Director
Collabra Ltd.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: The vendors page

2003-07-02 Thread Howard M. Lewis Ship
 Perhaps over time, he would get known and accepted in the 
 community and 
 someone would choose to nominate him for committer priviledges. 
  Obviously, that is something that Collabra would have very little 
 control over.
 

If you have someone with talent and a decent amount of time to spend, my experience is 
that they can
become a committer pretty quickly.  If they are providing quality mentoring and 
patches, it quickly
becomes easier to vote them in as a committer than to manually apply their patches.  
So if your
primary goal is to establish Collabra's rep and your incidental goal is to be listed 
on the vendors
page, start now and see results soon.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: The vendors page

2003-07-02 Thread Brian McCallister
It might be useful for projects who *need* help to let that be known in 
some easy-to-find way. Some projects are well staffed, some are 
understaffed. If you are involved with several of the project mailing 
lists it becomes more clear, but if you are say, a company who wants to 
contribute effort and talent it might be tough to figure out which 
projects need manpower.

While no project is going to be accepted into Jakarta without a 
development community around it, there are always places that need more 
help than others.

Just my 2 cents.

-Brian

On Wednesday, July 2, 2003, at 02:00 PM, Howard M. Lewis Ship wrote:

Perhaps over time, he would get known and accepted in the
community and
someone would choose to nominate him for committer priviledges.
 Obviously, that is something that Collabra would have very little
control over.
If you have someone with talent and a decent amount of time to spend, 
my experience is that they can
become a committer pretty quickly.  If they are providing quality 
mentoring and patches, it quickly
becomes easier to vote them in as a committer than to manually apply 
their patches.  So if your
primary goal is to establish Collabra's rep and your incidental goal 
is to be listed on the vendors
page, start now and see results soon.

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


cvs commit: jakarta-site2/xdocs/site news.xml

2003-07-02 Thread rdonkin
rdonkin 2003/07/02 14:36:44

  Modified:docs index.html
   docs/site news.html
   xdocsindex.xml
   xdocs/site news.xml
  Log:
  Added news about Jakarta Commons press coverage
  
  Revision  ChangesPath
  1.263 +1 -1  jakarta-site2/docs/index.html
  
  Index: index.html
  ===
  RCS file: /home/cvs/jakarta-site2/docs/index.html,v
  retrieving revision 1.262
  retrieving revision 1.263
  diff -u -r1.262 -r1.263
  --- index.html2 Jul 2003 02:13:31 -   1.262
  +++ index.html2 Jul 2003 21:36:44 -   1.263
  @@ -231,6 +231,7 @@
   h4Other news from a 
href=site/news.htmlJakarta/a 
   and a href=site/elsewhere.htmlElsewhere/a/h4
   ul
  +lia href=site/news.html#20030702.202 July 2003 - bJakarta 
Commons/b featured in OnJava article, open source conference and (forthcoming) 
book/a/li
   lia href=site/elsewhere.html#20030625.125 June 2003 - 
   bAnt/b and bXercesJ/b win 2003 JavaWorld Awards/a 
/li
   lia href=site/elsewhere.html#20030628.124 June 2003 - bSOAP 
Version 1.2/b Recommendation Issued by W3C/a/li
  @@ -239,7 +240,6 @@
   lia href=site/news.html#20030603.203 June 2003 - bJakarta 
Lucene/b and bCommons Digester/b
   featured on bIBM developerWorks/b/a /li
lia href=site/elsewhere.html#20030528.128 May 2003 - bApache 
HTTPD 2.0.46/b Released/a/li
  -lia href=site/news.html#20030522.122 May 2003 - bJakarta 
Newsletter Issue 8/b Released/a/li
   /ul
   /blockquote
   /p
  
  
  
  1.332 +10 -1 jakarta-site2/docs/site/news.html
  
  Index: news.html
  ===
  RCS file: /home/cvs/jakarta-site2/docs/site/news.html,v
  retrieving revision 1.331
  retrieving revision 1.332
  diff -u -r1.331 -r1.332
  --- news.html 2 Jul 2003 02:13:31 -   1.331
  +++ news.html 2 Jul 2003 21:36:44 -   1.332
  @@ -178,7 +178,16 @@
 /td/tr
 trtd
   blockquote
  -a name=20030702.1
  +a name=20030702.2
  +h302 July 2003 - Jakarta Commons Finds Fame At Last ;)/h3
  +/a
  +pOnJava has an a 
href=http://www.onjava.com/pub/a/onjava/2003/06/25/commons.html;article/a 
  +introducing components in Jakarta Commons./p
  +pJakarta Commons will also be 
featuring in a a 
href=http://conferences.oreillynet.com/cs/os2003/view/e_sess/3760;session/a at the 
  +O'Reilly Open Source Conversion. It will also be covered in 
  +a href=http://www.apress.com/book/bookDisplay.html?bID=197;this book/a./p
  +hr size=1 noshade=noshade /
  +a name=20030702.1
   h302 July 2003 - Commons HttpClient 2.0 Beta 2 Released/h3
   /a
   pThe Commons team is pleased to 
announce the second, and hopefully final, beta release
  
  
  
  1.210 +1 -1  jakarta-site2/xdocs/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/jakarta-site2/xdocs/index.xml,v
  retrieving revision 1.209
  retrieving revision 1.210
  diff -u -r1.209 -r1.210
  --- index.xml 2 Jul 2003 02:13:32 -   1.209
  +++ index.xml 2 Jul 2003 21:36:44 -   1.210
  @@ -56,6 +56,7 @@
   h4Other news from a href=site/news.htmlJakarta/a 
   and a href=site/elsewhere.htmlElsewhere/a/h4
   ul
  +lia href=site/news.html#20030702.202 July 2003 - bJakarta 
Commons/b featured in OnJava article, open source conference and (forthcoming) 
book/a/li
   lia href=site/elsewhere.html#20030625.125 June 2003 - 
   bAnt/b and bXercesJ/b win 2003 JavaWorld Awards/a 
/li
   lia href=site/elsewhere.html#20030628.124 June 2003 - bSOAP 
Version 1.2/b Recommendation Issued by W3C/a/li
  @@ -64,7 +65,6 @@
   lia href=site/news.html#20030603.203 June 2003 - bJakarta 
Lucene/b and bCommons Digester/b
   featured on bIBM developerWorks/b/a /li
lia href=site/elsewhere.html#20030528.128 May 2003 - bApache 
HTTPD 2.0.46/b Released/a/li
  -lia href=site/news.html#20030522.122 May 2003 - bJakarta 
Newsletter Issue 8/b Released/a/li
   /ul
   /section
   
  
  
  
  1.283 +13 -0 jakarta-site2/xdocs/site/news.xml
  
  Index: news.xml
  ===
  RCS file: 

cvs commit: jakarta-site2/xdocs/site newbie.xml

2003-07-02 Thread rdonkin
rdonkin 2003/07/02 14:52:54

  Modified:docs/site newbie.html
   xdocs/site newbie.xml
  Log:
  Added link to main apache site to newbie html
  
  Revision  ChangesPath
  1.26  +24 -4 jakarta-site2/docs/site/newbie.html
  
  Index: newbie.html
  ===
  RCS file: /home/cvs/jakarta-site2/docs/site/newbie.html,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- newbie.html   8 Jun 2003 04:05:10 -   1.25
  +++ newbie.html   2 Jul 2003 21:52:54 -   1.26
  @@ -171,6 +171,28 @@
   table 
border=0 cellspacing=0 cellpadding=2 width=100%
 trtd bgcolor=#525D76
   font color=#ff face=arial,helvetica,sanserif
  +  a name=But First...strongBut First.../strong/a
  +/font
  +  /td/tr
  +  trtd
  +blockquote
  +p
  +Jakarta is just one Apache project. As a newbie Jakarta committer you might not be 
aware of it but 
  +you're part of a bigger community. So, start by taking some time to read about 
  +a href=http://www.apache.org/foundation;Apache Software Foundation/a and 
familiarize yourself 
  +with the a href=http://www.apache.org/dev/;Developers Resources/a.
  +/p
  +p
  +Next, take a look at the a href=http://www.apache.org/dev/committers.html;Apache 
Committers FAQ/a.
  +/p
  +/blockquote
  +/p
  +  /td/tr
  +  trtdbr//td/tr
  +/table
  +table border=0 cellspacing=0 
cellpadding=2 width=100%
  +  trtd bgcolor=#525D76
  +font color=#ff face=arial,helvetica,sanserif
 a name=Newbie Committer FAQstrongNewbie Committer FAQ/strong/a
   /font
 /td/tr
  @@ -183,11 +205,9 @@
 li
   a href=#How do I login to the CVS? /How do I login to the CVS?
   /li
  -  li
  -a href=#What are the project guidelines? /What are the project guidelines?
  +  lia href=#What are the project guidelines? /What are the project guidelines?
 /li
  -  li
  -a href=#What are my responsibilities as a Committer?What are my 
responsibilities as a Committer?/a
  +  lia href=#What are my responsibilities as a Committer?What are my 
responsibilities as a Committer?/a
 /li
 li
   a href=#Is there a set term for acting as a Committer? Will I have to be 
elected again?Is there a set term for acting as a Committer? Will I have to be 
elected again?/a
  
  
  
  1.5   +13 -5 jakarta-site2/xdocs/site/newbie.xml
  
  Index: newbie.xml
  ===
  RCS file: /home/cvs/jakarta-site2/xdocs/site/newbie.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- newbie.xml6 Nov 2002 19:54:19 -   1.4
  +++ newbie.xml2 Jul 2003 21:52:54 -   1.5
  @@ -7,7 +7,17 @@
 /properties
   
   body
  -
  +section name=But First...
  +p
  +Jakarta is just one Apache project. As a newbie Jakarta committer you might not be 
aware of it but 
  +you're part of a bigger community. So, start by taking some time to read about 
  +a href='http://www.apache.org/foundation'Apache Software Foundation/a and 
familiarize yourself 
  +with the a href='http://www.apache.org/dev/'Developers Resources/a.
  +/p
  +p
  +Next, take a look at the a href='http://www.apache.org/dev/committers.html'Apache 
Committers FAQ/a.
  +/p
  +/section
 section name=Newbie Committer FAQ
   
 ul
  @@ -17,11 +27,9 @@
 li
   a href=#How do I login to the CVS?/aHow do I login to the CVS?
   /li
  -  li
  -a href=#What are the project guidelines?/aWhat are the project guidelines?
  +  lia href=#What are the project guidelines?/aWhat are the project 
guidelines?
 /li
  -  li
  -a href=#What are my responsibilities as a Committer?What are my 
responsibilities as a Committer?/a
  +  lia href=#What are my responsibilities as a Committer?What are my 
responsibilities as a Committer?/a
 /li
 li
   a href=#Is there a set term for acting as a Committer? Will I have to be 
elected again?Is there a set term for acting as a Committer? Will I have to be 
elected again?/a
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-site2/xdocs/site/news editor.xml

2003-07-02 Thread rdonkin
rdonkin 2003/07/02 15:55:34

  Added:   xdocs/site/news editor.xml
  Log:
  Added new how-to-be-newsletter-editor page
  
  Revision  ChangesPath
  1.1  jakarta-site2/xdocs/site/news/editor.xml
  
  Index: editor.xml
  ===
  ?xml version=1.0?
  document
  properties
  author email=[EMAIL PROTECTED]Jakarta Newsletter Team/author
  titleEditing The Newsletter/title
  /properties
  body
  section name=Introduction
  subsection name=About This Document
  p
  This document is intended to be(come) a self help manual for newsletter editors. 
  Please feel free to add, ammend and update this document. Not only will it be easier
  for you next time if you keep this updated but also you'll be doing a huge favour to 
  emThose Who Will Come After/em.
  /p
  /subsection
  
  subsection name=How The Newsletter Is Created
  p
  The newsletter is created on the 
  a 
href='http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts'Apache 
Wiki/a.
  This should lower the barrier to enter and allow more people to participate.
  The next issue of the newsletter is open for business from the time that the last 
one is closed.
  The proposed scope of the next newsletter is set when the last newsletter is cut.
  Traditionally, the last editor will either continue in office or request a new 
volunteer editor in 
  good time before the deadline for the next issue approaches.
  /p
  /subsection 
  
  subsection name=Preparations
  p
  Review the older newsletter. Familiarize yourself with their contents
  and seek inspiration from their ideas. 
  /p
  p
  To edit the newsletter you'll need free time around the time that the newsletter is 
published.
  You'll also need karma for the jakarta-site2 CVS module. Committers can obtain karma 
from the Jakarta pmc 
  on request.
  /p
  p
  Make sure you know how to create the xml that the Jakarta site is written in and how 
to generate the site. 
  Instructions can be found 
  a href='http://jakarta.apache.org/site/jakarta-site2'here/a and 
  a href='http://jakarta.apache.org/site/jakarta-site2b'here/a.
  /p
  /subsection 
  /section
  
  section name='Step By Step Guide'
  subsection name='Start The Countdown'
  p
  There is nothing to stop entries being added at any time after the last issue has 
been created. 
  But nothing concentrates the mind like an approaching deadline. So, in order to fill 
the newsletter,
  it's necessary to fix a deadline for contributions, annouce the fact (to the various 
development lists)
  and then remind people as the deadline approaches.
  /p
  pHere's an example of a (good) annoucement:
  codepre
  Dear Jakarta BCEL Development Team, 
  (http://jakarta.apache.org/bcel/)
  
  We are now preparing the 'Jakarta Newsletter Issue 9',
  news from May to June 2003, which would be published 
  in the middle of July 2003.
  
  The 'Jakarta Newsletter Issue 9' will be appeared at 
  http://jakarta.apache.org/site/news/200305.html
  and the editorial deadline would be 00:00 GMT, 6th July.
  
  We lowered the barrier to entry - users and developers
  will be able to easily contribute, as prepared the
  ApacheWiki(http://nagoya.apache.org/wiki/apachewiki.cgi).
  
  If you have anything to be added to the ApacheWiki, please go to
  http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue9
  and fill up what you want to append.
  If there's nothing news-worthy on 'Jakarta BCEL', then please just write *N/A*.
  
  If you have been voted in as a new committer in 'Jakarta BCEL' project
  within these 2 months, please add your name to the list on ApacheWiki.
  
  Probably, the former newsletter draft (Jakarta Newsletter Issue8)
  would give you some hints in writing the articles.
  cf. 
http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue8March2003
  
  If you have time enough to contribute to 
  http://nagoya.apache.org/wiki/apachewiki.cgi?BCELProjectPages
  please modify, fill in the ApacheWiki to create more precise and useful pages.
  
  We really appreciate your contribution.
  If you have any questions about this, please subscribe to 
  mailto:[EMAIL PROTECTED]
  and send your messages to 
  mailto:[EMAIL PROTECTED]
  
  Sincerely,
  
  -- Tetsuya ([EMAIL PROTECTED])
  /pre/code
  
  /p
  /subsection
  
  subsection name='Closing The Last And Opening The New'
  p
  The first step in preparing the material is to post an announcement to 
  code[EMAIL PROTECTED]/code telling 

cvs commit: jakarta-site2/docs/site/news editor.html

2003-07-02 Thread rdonkin
rdonkin 2003/07/02 15:55:46

  Added:   docs/site/news editor.html
  Log:
  Added new how-to-be-newsletter-editor page
  
  Revision  ChangesPath
  1.1  jakarta-site2/docs/site/news/editor.html
  
  Index: editor.html
  ===
  !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN 
http://www.w3.org/TR/html4/loose.dtd;
  
  !-- Content Stylesheet for Site --
  
  
  !-- start the processing --
  !-- == --
  !-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! --
  !-- Main Page Section --
  !-- == --
  html
  head
  meta http-equiv=Content-Type content=text/html; charset=iso-8859-1/
  
  meta name=author 
value=Jakarta Newsletter Team
  meta name=email value=[EMAIL PROTECTED]
  
 
  
  
  titleThe Jakarta Site - Editing The Newsletter/title
  /head
  
  body bgcolor=#ff text=#00 link=#525D76
  table border=0 width=100% cellspacing=0
  !-- TOP IMAGE --
  tr
  td colspan=2
  a href=http://jakarta.apache.org;img 
src=http://jakarta.apache.org/images/jakarta-logo.gif; align=left border=0//a
  /td
  /tr
  /table
  table border=0 width=100% cellspacing=4
  trtd colspan=2
  hr noshade= size=1/
  /td/tr
  
  tr
  !-- LEFT SIDE NAVIGATION --
  td width=20% valign=top nowrap=true
  pstrongAbout Jakarta/strong/p
  ul
  lia href=../../index.htmlWelcome/a
  /li
  lia href=http://www.apache.org/foundation/;About The 
ASF/a
  /li
  lia 
href=http://jakarta.apache.org/site/news/index.html;News  Status/a
  /li
  lia href=http://www.apache.org/;Apache Website/a
  /li
  lia 
href=http://www.google.com/advanced_search?q=+site:jakarta.apache.orghl=enas_qdr=all;Search
 Jakarta/a
  /li
  lia 
href=http://jakarta.apache.org/site/contact.html;Contacting Us/a
  /li
  lia 
href=http://jakarta.apache.org/site/mission.html;Our Mission/a
  /li
  lia 
href=http://jakarta.apache.org/site/whoweare.html;Who We Are/a
  /li
  lia 
href=http://jakarta.apache.org/site/acknowledgements.html;Acknowledgements/a
  /li
  lia 
href=http://jakarta.apache.org/site/legal.html;Legal/a
  /li
  /ul
  pstrongReference/strong/p
  ul
  lia href=http://jakarta.apache.org/site/faqs.html;Our 
FAQs/a
  /li
  lia 
href=http://jakarta.apache.org/site/getinvolved.html;Get Involved/a
  /li
  lia 
href=http://jakarta.apache.org/site/vendors.html;Vendor Support/a
  /li
  lia 
href=http://jakarta.apache.org/site/guidelines.html;Project Guidelines/a
  /li
  lia 
href=http://jakarta.apache.org/site/library.html;Reference Library/a
  /li
  lia 
href=http://jakarta.apache.org/site/newproject.html;New Subprojects/a
  /li
  lia 
href=http://jakarta.apache.org/site/jakarta-site2.html;Website Maintenance/a
  /li
  lia 
href=http://incubator.apache.org/drafts/glossary.html;ASF Glossary/a
  /li
  lia href=http://www.apache.org/dev/;Developer 
Resources/a
  /li
  lia 
href=http://jakarta.apache.org/site/jspa-position.html;Apache on the JSPA/a
  /li
  /ul
  pstrongSupport/strong/p
  ul
  lia 
href=http://jakarta.apache.org/site/mail.html;Mailing Lists/a
  /li
  lia href=http://jakarta.apache.org/site/bugs.html;Bug 
Database/a
  /li
  lia href=http://nagoya.apache.org/wiki;Wiki/a
  /li
  /ul
  pstrongDownloads/strong/p
  ul
  lia 
href=http://jakarta.apache.org/site/binindex.cgi;Binaries/a
  /li
  lia 
href=http://jakarta.apache.org/site/sourceindex.cgi;Source Code/a
  /li
  lia 
href=http://jakarta.apache.org/site/cvsindex.html;CVS Repositories/a
  /li
  /ul
  pstrongProducts/strong/p
  ul
  lia href=../../alexandria/index.htmlAlexandria/a
  /li
 

cvs commit: jakarta-site2/xdocs/site/news index.xml

2003-07-02 Thread rdonkin
rdonkin 2003/07/02 15:55:55

  Modified:docs/site/news index.html
   xdocs/site/news index.xml
  Log:
  Added new how-to-be-newsletter-editor page
  
  Revision  ChangesPath
  1.30  +2 -0  jakarta-site2/docs/site/news/index.html
  
  Index: index.html
  ===
  RCS file: /home/cvs/jakarta-site2/docs/site/news/index.html,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -r1.29 -r1.30
  --- index.html8 Jun 2003 04:05:15 -   1.29
  +++ index.html2 Jul 2003 22:55:54 -   1.30
  @@ -205,6 +205,8 @@
   pstrongI've got an item for the 
next issue/strong - the best thing to do is to post a copy on the a 
href=../mail.htmlappropriate subproject mailing list/a, if people like what 
you've written then send it onto the current newsletter editor for inclusion 
indicating clearly which subproject the contribution relates to./p
   pstrongI want to discuss a 
topic from issue #X/strong - join the a href=../mail.htmlappropriate mailing 
list/a and continue the thread there./p
   pstrongI have a general 
newsletter comment/strong - send an email to the a href=../mail.htmlJakarta 
General/a list/p
  +pstrongHelp! I've Volunteered 
to be the Editor - What Do I Do?/strong - 
  +a href=./editor.htmlhere/a are some words from those who've done 
it before./p
   /blockquote
   /p
 /td/tr
  
  
  
  1.11  +4 -1  jakarta-site2/xdocs/site/news/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/jakarta-site2/xdocs/site/news/index.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- index.xml 24 May 2003 10:28:41 -  1.10
  +++ index.xml 2 Jul 2003 22:55:55 -   1.11
  @@ -27,7 +27,10 @@
   pstrongI want to discuss a topic from issue #X/strong - join the a 
href=../mail.htmlappropriate mailing list/a and continue the thread there./p
   
   pstrongI have a general newsletter comment/strong - send an email to 
the a href=../mail.htmlJakarta General/a list/p
  -
  +
  +pstrongHelp! I've Volunteered to be the Editor - What Do I Do?/strong 
- 
  +a href='./editor.html'here/a are some words from those who've done 
it before./p
  +
   /section
   section name=Archive
   ul
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: jakarta-site2/xdocs/site/news 200305.xml

2003-07-02 Thread tetsuya
tetsuya 2003/07/02 16:51:33

  Added:   docs/site/news 200305.html
   xdocs/site/news 200305.xml
  Log:
  Jakarta NewsLetter Issue9: Just a beginning
  
  Revision  ChangesPath
  1.1  jakarta-site2/docs/site/news/200305.html
  
  Index: 200305.html
  ===
  !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN 
http://www.w3.org/TR/html4/loose.dtd;
  
  !-- Content Stylesheet for Site --
  
  
  !-- start the processing --
  !-- == --
  !-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! --
  !-- Main Page Section --
  !-- == --
  html
  head
  meta http-equiv=Content-Type content=text/html; charset=iso-8859-1/
  
  meta name=author 
value=Tetsuya Kitahata
  meta name=email value=[EMAIL PROTECTED]
  
 
  
  
  titleThe Jakarta Site - Jakarta Newsletter - May-June 2003 - #9/title
  /head
  
  body bgcolor=#ff text=#00 link=#525D76
  table border=0 width=100% cellspacing=0
  !-- TOP IMAGE --
  tr
  td colspan=2
  a href=http://jakarta.apache.org;img 
src=http://jakarta.apache.org/images/jakarta-logo.gif; align=left border=0//a
  /td
  /tr
  /table
  table border=0 width=100% cellspacing=4
  trtd colspan=2
  hr noshade= size=1/
  /td/tr
  
  tr
  !-- LEFT SIDE NAVIGATION --
  td width=20% valign=top nowrap=true
  pstrongAbout Jakarta/strong/p
  ul
  lia href=../../index.htmlWelcome/a
  /li
  lia href=http://www.apache.org/foundation/;About The 
ASF/a
  /li
  lia 
href=http://jakarta.apache.org/site/news/index.html;News  Status/a
  /li
  lia href=http://www.apache.org/;Apache Website/a
  /li
  lia 
href=http://www.google.com/advanced_search?q=+site:jakarta.apache.orghl=enas_qdr=all;Search
 Jakarta/a
  /li
  lia 
href=http://jakarta.apache.org/site/contact.html;Contacting Us/a
  /li
  lia 
href=http://jakarta.apache.org/site/mission.html;Our Mission/a
  /li
  lia 
href=http://jakarta.apache.org/site/whoweare.html;Who We Are/a
  /li
  lia 
href=http://jakarta.apache.org/site/acknowledgements.html;Acknowledgements/a
  /li
  lia 
href=http://jakarta.apache.org/site/legal.html;Legal/a
  /li
  /ul
  pstrongReference/strong/p
  ul
  lia href=http://jakarta.apache.org/site/faqs.html;Our 
FAQs/a
  /li
  lia 
href=http://jakarta.apache.org/site/getinvolved.html;Get Involved/a
  /li
  lia 
href=http://jakarta.apache.org/site/vendors.html;Vendor Support/a
  /li
  lia 
href=http://jakarta.apache.org/site/guidelines.html;Project Guidelines/a
  /li
  lia 
href=http://jakarta.apache.org/site/library.html;Reference Library/a
  /li
  lia 
href=http://jakarta.apache.org/site/newproject.html;New Subprojects/a
  /li
  lia 
href=http://jakarta.apache.org/site/jakarta-site2.html;Website Maintenance/a
  /li
  lia 
href=http://incubator.apache.org/drafts/glossary.html;ASF Glossary/a
  /li
  lia href=http://www.apache.org/dev/;Developer 
Resources/a
  /li
  lia 
href=http://jakarta.apache.org/site/jspa-position.html;Apache on the JSPA/a
  /li
  /ul
  pstrongSupport/strong/p
  ul
  lia 
href=http://jakarta.apache.org/site/mail.html;Mailing Lists/a
  /li
  lia href=http://jakarta.apache.org/site/bugs.html;Bug 
Database/a
  /li
  lia href=http://nagoya.apache.org/wiki;Wiki/a
  /li
  /ul
  pstrongDownloads/strong/p
  ul
  lia 
href=http://jakarta.apache.org/site/binindex.cgi;Binaries/a
  /li
  lia 
href=http://jakarta.apache.org/site/sourceindex.cgi;Source Code/a
  /li
  lia 
href=http://jakarta.apache.org/site/cvsindex.html;CVS Repositories/a
  /li
  /ul
  pstrongProducts/strong/p
  ul
  lia 

cvs commit: jakarta-site2/xdocs/site/news 200305.xml

2003-07-02 Thread tetsuya
tetsuya 2003/07/02 16:57:19

  Modified:docs/site/news 200305.html
   xdocs/site/news 200305.xml
  Log:
  Jakarta NewsLetter Issue9: Just a beginning
  
  Revision  ChangesPath
  1.2   +6 -1  jakarta-site2/docs/site/news/200305.html
  
  Index: 200305.html
  ===
  RCS file: /home/cvs/jakarta-site2/docs/site/news/200305.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- 200305.html   2 Jul 2003 23:51:33 -   1.1
  +++ 200305.html   2 Jul 2003 23:57:18 -   1.2
  @@ -179,9 +179,14 @@
   p
   bIssue:/b 9
   br /
  -bDate:/b March-April 2003
  +bDate:/b May-June 2003
   br /
   bStatus:/b Now in a status of *OPEN FOR BUSINESS*: a 
href=http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue9;http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue9/a
  +br /
  +Please edit Apachewiki in order to create more precise and useful newsletter.
  +br /
  +Editorial deadline would be 00:00 GMT, 6th July.
  +br /
   /p
   /blockquote
   /p
  
  
  
  1.2   +6 -1  jakarta-site2/xdocs/site/news/200305.xml
  
  Index: 200305.xml
  ===
  RCS file: /home/cvs/jakarta-site2/xdocs/site/news/200305.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- 200305.xml2 Jul 2003 23:51:33 -   1.1
  +++ 200305.xml2 Jul 2003 23:57:19 -   1.2
  @@ -14,10 +14,15 @@
   p
   bIssue:/b 9
   br/
  -bDate:/b March-April 2003
  +bDate:/b May-June 2003
   br/
   bStatus:/b Now in a status of *OPEN FOR BUSINESS*: a
   
href=http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue9;http://nagoya.apache.org/wiki/apachewiki.cgi?JakartaNewsletterDrafts/Issue9/a
  +br/
  +Please edit Apachewiki in order to create more precise and useful newsletter.
  +br/
  +Editorial deadline would be 00:00 GMT, 6th July.
  +br/
   /p
   /section
   /body
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Proposal: XMLBeans

2003-07-02 Thread Howard M. Lewis Ship


 -Original Message-
 From: Cliff Schmidt [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, July 02, 2003 9:42 PM
 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 
 [EMAIL PROTECTED]
 Subject: Proposal: XMLBeans
 
 
 Hi,
 
 I would like to propose a new subproject to further develop 
 XMLBeans, which is a Java-XML binding tool that also allows 
 low-level access to the full XML instance Infoset.  The 
 technology was developed by BEA, but we believe this work 
 could potentially be a good fit for either the Jakarta or the 
 XML communities.  
 
 Please see 
 http://nagoya.apache.org/wiki/apachewiki.cgi?XmlBeansProposal 
 for a detailed proposal, which I've also copied below.
 
 Thanks,
 Cliff
 
 ---
 '''Proposal for an XMLBeans subproject in Apache XML or Jakarta'''
 
 ''2 July 2003, Cliff Schmidt ([EMAIL PROTECTED])''
 
 '''(0) rationale'''
 
 XMLBeans is an XML-Java binding tool that uses XML Schema as 
 a basis for generating Java classes to be used to easily 
 access XML instance data. It was designed to provide both 
 easy access to XML information via convenient Java classes as 
 well as complete access to the underlying XML, combining the 
 best of low-level, full access APIs like SAX and DOM with the 
 convenience of Java binding.
 
 See [http://workshop.bea.com/xmlbeans/quickStart.jsp BEA's 
 quick start page] for more information.

There's a commons module, Betwixt, that very much overlaps what you describe here.  I 
would like to
look over both APIs before noodling further.  Please take these thoughts as cursory 
and initial
until I've had a better look-see.

What's compelling about XMLBeans compared to some of the other front runners, such as 
JDOM and XOM,
Castor and JAXB?

 
 
 
 '''(0.1) criteria'''
 
 ''Meritocracy: ''
 We would very much like to see XMLBeans evolve under the 
 meritocracy model that is used within Apache.

The advice I got is still good ... get your meritocracy working RIGHT NOW.  I 
personally found big
benefits to reoganizing along these lines; it would
have been worth the effort even if Tapestry hadn't made it all the way in.  The 
meritocracy really
works to get people motivated and contributing.

 
 ''Community: ''
 Over the last six months, we have developed a thriving 
 developer community to provide feedback directly to the 
 development team through a discussion forum.  We have invited 
 three of the members of the community to join us as 
 committers, based on their contributions to the development 
 of the product.  We've also had thousands of users experiment 
 with the technology.  Part of the reason for this success has 
 been the availability of 
 [http://workshop.bea.com/xmlbeans/docindex.html sample code 
 and thorough documentation].
 
 ''Core Developers:''
 In addition to key members of the XMLBeans development team, 
 the initial committers include developers from outside BEA 
 who have spent several months using XMLBeans to solve their 
 particular development needs.  


Be prepared to document a bit more about outside developers' contributions.

 
 ''Alignment:''
 While XMLBeans does not currently have major dependencies on 
 other Apache Jakarta or XML products, we are very interested 
 in pursuing integration.  For instance, we are looking into 
 enabling Xerces to be used as our XML parser.  One reason for 
 doing this is due to the fact that we currently use the 
 [http://piccolo.sourceforge.net/ Piccolo parser], and I 
 realize that the LGPL terms of this parser would be 
 problematic for an Apache project.  Therefore, if it is 
 eventually agreed that an XMLBeans subproject in Apache would 
 be a Good Thing, we will replace our current parser with an 
 alternative that uses an Apache license.

I've learned the hard way to get rid of all [L]GPL dependencies before you attempt to 
move to
Jakarta.


 
 We are also aware that there is some overlap of functionality 
 with JAXB, specifically regarding object binding.  We would 
 very much like to see the convergence of these two 
 technologies.  In fact, one of the committers has recently 
 joined the JAXB v.2 Expert Group, in order to facilitate this.
 
 Finally, we are aware that the proposed WS-Commons subproject 
 might include a JAXB proposal.  If this subproject is 
 approved, we would want to work closely together on any 
 future JAXB-XMLBeans convergence.  
 
 
 '''(0.2) warning signs'''
 
 ''Orphaned products: ''
 BEA has been receiving very positive press and customer 
 feedback about XMLBeans and only wishes to invest further in 
 the development and support of this technology.

Do you have a roadmap of where you would like this project to be in 6 months?  A year? 
 Two years?

 
 ''Inexperience with open source:''
 While we do not yet have any committers who are currently 
 active in the XML or Jakarta projects, several of them have 
 previous experience working with open source communities.  
 For example, the architect behind XMLBeans, David Bau, has 
 built a strong community