Re: Why wiki logs to [EMAIL PROTECTED] -- site-cvs@ might be better

2004-07-08 Thread Rainer Klute
Am Do, den 08.07.2004 schrieb Martin Cooper um 1:09:
 I think you are arguing against yourself here. ;-) If the people who can 
 make changes should be the same people doing the monitoring, which seems 
 to be what you are saying, then it makes perfect sense for general@ to 
 review wiki changes, since anyone on that list can make changes to the 
 wiki. Similarly, if site2 karma and site-cvs were tied (but see below), it 
 would make sense for site-cvs folks to be reviewing site2 changes.

But not everyone who can make changes does so. And not everyone who
subscribed to [EMAIL PROTECTED] interested in this particular type of messages.
If that doesn't stop it would be a very good reason
a) that non-wiki messages get visually lost and
b) for many subscribers to unsubscribe - at least for me.

Best regards
Rainer Klute

   Rainer Klute IT-Consulting GmbH
  Dipl.-Inform.
  Rainer Klute E-Mail:  [EMAIL PROTECTED]
  Körner Grund 24  Telefon: +49 172 2324824
D-44143 Dortmund   Telefax: +49 231 5349423


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



Re: Why wiki logs to [EMAIL PROTECTED] -- site-cvs@ might be better

2004-07-08 Thread Henri Yandell


On Thu, 8 Jul 2004, Rainer Klute wrote:

 Am Do, den 08.07.2004 schrieb Martin Cooper um 1:09:
  I think you are arguing against yourself here. ;-) If the people who can
  make changes should be the same people doing the monitoring, which seems
  to be what you are saying, then it makes perfect sense for general@ to
  review wiki changes, since anyone on that list can make changes to the
  wiki. Similarly, if site2 karma and site-cvs were tied (but see below), it
  would make sense for site-cvs folks to be reviewing site2 changes.

 But not everyone who can make changes does so. And not everyone who
 subscribed to [EMAIL PROTECTED] interested in this particular type of messages.
 If that doesn't stop it would be a very good reason
 a) that non-wiki messages get visually lost and
 b) for many subscribers to unsubscribe - at least for me.

For me this issue comes down to the fact that we have a general list, not
a general-dev and general-users list. I've not seen complaints on
commons-dev about the wiki notifications.

I'm not pushing for a dev and users list, just that you might want to ask
yourself which you think the list is. Obviously [EMAIL PROTECTED] is really
a community list, however usually at Apache this seems to mean the dev
list not the users list.

I'm +1 for the Wiki notifying here as the Jakarta web site seems an
important facet of the Jakarta community, and the Wiki is merely an easily
modifiable part of the web site.

CVS commits for site2 should also be coming here.

(Just a view...)

Hen


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



[Jakarta Wiki] Updated: JakartaIssues

2004-07-08 Thread general
   Date: 2004-07-08T09:26:49
   Editor: 216.26.136.155 
   Wiki: Jakarta Wiki
   Page: JakartaIssues
   URL: http://wiki.apache.org/jakarta/JakartaIssues

   no comment

Change Log:

--
@@ -8,3 +8,4 @@
  6. Wiki vandalism. Are all our wiki's monitored by a mailing list?
  7. List moderation coverage.
  8. ASF Licence 2.0. Any major work left to do?
+ 9. Obtaining a site-wide licence for Clover.

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



[Jakarta Wiki] Updated: JakartaPMC

2004-07-08 Thread general
   Date: 2004-07-08T09:55:24
   Editor: 81.248.56.222 
   Wiki: Jakarta Wiki
   Page: JakartaPMC
   URL: http://wiki.apache.org/jakarta/JakartaPMC

   no comment

Change Log:

--
@@ -2,4 +2,4 @@
 
 The role of the PMC is defined by the ASF By-Laws at section 6.3 - 
http://apache.org/foundation/bylaws.html
 
-Each Project Management Committee shall be responsible for the active management of 
one or more projects identified by resolution of the Board of Directors which may 
include, without limitation, the creation or maintenance of open-source software for 
distribution to the public at no charge. Subject to the direction of the Board of 
Directors, the chairman of each Project Management Committee shall be primarily 
responsible for project(s) managed by such committee, and he or she shall establish 
rules and procedures for the day to day management of project(s) for which the 
committee is responsible.
+Each Project Management Committee shall be responsible for the active management of 
one or more projects identified by resolution of the Board of Directors which may 
include, without limitation, the creation or maintenance of open-source software for 
distribution to the public at no charge. Subject to the direction of the Board of 
Directors, the chairman of each Project Management Committee shall be primarily 
responsible for project(s) managed by such committee, and he or she shall establish 
rules and procedures for the day to day management of project(s) for which the 
committe is responsible.

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



[Jakarta Wiki] Updated: JakartaPMC

2004-07-08 Thread general
   Date: 2004-07-08T09:56:36
   Editor: 81.248.56.222 
   Wiki: Jakarta Wiki
   Page: JakartaPMC
   URL: http://wiki.apache.org/jakarta/JakartaPMC

   no comment

Change Log:

--
@@ -2,4 +2,4 @@
 
 The role of the PMC is defined by the ASF By-Laws at section 6.3 - 
http://apache.org/foundation/bylaws.html
 
-Each Project Management Committee shall be responsible for the active management of 
one or more projects identified by resolution of the Board of Directors which may 
include, without limitation, the creation or maintenance of open-source software for 
distribution to the public at no charge. Subject to the direction of the Board of 
Directors, the chairman of each Project Management Committee shall be primarily 
responsible for project(s) managed by such committee, and he or she shall establish 
rules and procedures for the day to day management of project(s) for which the 
committe is responsible.
+Each Project Management Committee shall be responsible for the active management of 
one or more projects identified by resolution of the Board of Directors which may 
include, without limitation, the creation or maintenance of open-source software for 
distribution to the public at no charge. Subject to the direction of the Board of 
Directors, the chairman of each Project Management Committee shall be primarily 
responsible for project(s) managed by such committee, and he or she shall establish 
rules and procedures for the day to day management of project(s) for which the 
committee is responsible.

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



Re: [Jakarta Wiki] Updated: JakartaPMC

2004-07-08 Thread Rainer Klute
Hi,

the following is a good example why I am against notifications to
[EMAIL PROTECTED]:

Am Do, 2004-07-08 um 18.55 schrieb [EMAIL PROTECTED]:
 Change Log:
 
 --
 @@ -2,4 +2,4 @@
  
  The role of the PMC is defined by the ASF By-Laws at section 6.3 - 
 http://apache.org/foundation/bylaws.html
  
 -Each Project Management Committee shall be responsible for the active management 
 of one or more projects identified by resolution of the Board of Directors which may 
 include, without limitation, the creation or maintenance of open-source software 
 for distribution to the public at no charge. Subject to the direction of the Board 
 of Directors, the chairman of each Project Management Committee shall be primarily 
 responsible for project(s) managed by such committee, and he or she shall establish 
 rules and procedures for the day to day management of project(s) for which the 
 committee is responsible.
 +Each Project Management Committee shall be responsible for the active management 
 of one or more projects identified by resolution of the Board of Directors which may 
 include, without limitation, the creation or maintenance of open-source software 
 for distribution to the public at no charge. Subject to the direction of the Board 
 of Directors, the chairman of each Project Management Committee shall be primarily 
 responsible for project(s) managed by such committee, and he or she shall establish 
 rules and procedures for the day to day management of project(s) for which the 
 committe is responsible.

Am I really supposed to wade through this and find out where the
differences are?

Best regards
Rainer Klute

   Rainer Klute IT-Consulting GmbH
  Dipl.-Inform.
  Rainer Klute E-Mail:  [EMAIL PROTECTED]
  Körner Grund 24  Telefon: +49 172 2324824
D-44143 Dortmund   Telefax: +49 231 5349423


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



Re: [Jakarta Wiki] Updated: JakartaPMC

2004-07-08 Thread Henri Yandell

It's an example of complaining at people for not doing comments (I fully
admit I need to comment more myself). Took a while to notice that the one
below is a spelling fix for committe.

I wonder if we can configure wiki to make the comment mandatory :)

Hen

On Thu, 8 Jul 2004, Rainer Klute wrote:

 Hi,

 the following is a good example why I am against notifications to
 [EMAIL PROTECTED]:

 Am Do, 2004-07-08 um 18.55 schrieb [EMAIL PROTECTED]:
  Change Log:
 
  --
  @@ -2,4 +2,4 @@
 
   The role of the PMC is defined by the ASF By-Laws at section 6.3 - 
  http://apache.org/foundation/bylaws.html
 
  -Each Project Management Committee shall be responsible for the active management 
  of one or more projects identified by resolution of the Board of Directors which 
  may include, without limitation, the creation or maintenance of open-source 
  software for distribution to the public at no charge. Subject to the direction of 
  the Board of Directors, the chairman of each Project Management Committee shall be 
  primarily responsible for project(s) managed by such committee, and he or she 
  shall establish rules and procedures for the day to day management of project(s) 
  for which the committee is responsible.
  +Each Project Management Committee shall be responsible for the active management 
  of one or more projects identified by resolution of the Board of Directors which 
  may include, without limitation, the creation or maintenance of open-source 
  software for distribution to the public at no charge. Subject to the direction of 
  the Board of Directors, the chairman of each Project Management Committee shall be 
  primarily responsible for project(s) managed by such committee, and he or she 
  shall establish rules and procedures for the day to day management of project(s) 
  for which the committe is responsible.

 Am I really supposed to wade through this and find out where the
 differences are?

 Best regards
 Rainer Klute

Rainer Klute IT-Consulting GmbH
   Dipl.-Inform.
   Rainer Klute E-Mail:  [EMAIL PROTECTED]
   Körner Grund 24  Telefon: +49 172 2324824
 D-44143 Dortmund   Telefax: +49 231 5349423


 -
 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]



Re: [Jakarta Wiki] Updated: JakartaPMC

2004-07-08 Thread Craig McClanahan
Henri Yandell wrote:
I wonder if we can configure wiki to make the comment mandatory :)
 

Doubt it would help much ... like many people, I often play the game of 
what's the minimum amount of stuff needed to pass the validation on 
this field?.  Most commonly, a simple . will do the trick :-).

Hen
 

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


Re: Why wiki logs to [EMAIL PROTECTED] -- site-cvs@ might be better

2004-07-08 Thread Henri Yandell

I should make it clear that while I'd like wiki/cvs to be coming
to this list, I'm happy for the wiki/cvs to be going to the site-cvs mail
list. I just need to make sure we note that somewhere.

There's quite a lot of magic about the jakarta-level things (rather than
the individual sub-projects) and I want to make it more obvious.

Hen

On Thu, 8 Jul 2004, Henri Yandell wrote:



 On Thu, 8 Jul 2004, Rainer Klute wrote:

  Am Do, den 08.07.2004 schrieb Martin Cooper um 1:09:
   I think you are arguing against yourself here. ;-) If the people who can
   make changes should be the same people doing the monitoring, which seems
   to be what you are saying, then it makes perfect sense for general@ to
   review wiki changes, since anyone on that list can make changes to the
   wiki. Similarly, if site2 karma and site-cvs were tied (but see below), it
   would make sense for site-cvs folks to be reviewing site2 changes.
 
  But not everyone who can make changes does so. And not everyone who
  subscribed to [EMAIL PROTECTED] interested in this particular type of messages.
  If that doesn't stop it would be a very good reason
  a) that non-wiki messages get visually lost and
  b) for many subscribers to unsubscribe - at least for me.

 For me this issue comes down to the fact that we have a general list, not
 a general-dev and general-users list. I've not seen complaints on
 commons-dev about the wiki notifications.

 I'm not pushing for a dev and users list, just that you might want to ask
 yourself which you think the list is. Obviously [EMAIL PROTECTED] is really
 a community list, however usually at Apache this seems to mean the dev
 list not the users list.

 I'm +1 for the Wiki notifying here as the Jakarta web site seems an
 important facet of the Jakarta community, and the Wiki is merely an easily
 modifiable part of the web site.

 CVS commits for site2 should also be coming here.

 (Just a view...)

 Hen


 -
 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]



Re: [Jakarta Wiki] Updated: JakartaPMC

2004-07-08 Thread Rainer Klute
Am Do, 2004-07-08 um 19.33 schrieb Craig McClanahan:
 Henri Yandell wrote:
 
 I wonder if we can configure wiki to make the comment mandatory :)
 
   
 
 Doubt it would help much ... like many people, I often play the game of 
 what's the minimum amount of stuff needed to pass the validation on 
 this field?.  Most commonly, a simple . will do the trick :-).

Isn't is that wiki distinguishes between major and minor changes? It
would be nice if notices would be sent only for major changes.

Best regards
Rainer Klute

   Rainer Klute IT-Consulting GmbH
  Dipl.-Inform.
  Rainer Klute E-Mail:  [EMAIL PROTECTED]
  Körner Grund 24  Telefon: +49 172 2324824
D-44143 Dortmund   Telefax: +49 231 5349423


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



Re: [ANNOUNCEMENT] Jakarta Commons Betwixt 0.5 Released

2004-07-08 Thread robert burrell donkin
this is most definitely the wrong place to ask questions such as this. 
betwixt is a jakarta commons component and the right place to ask 
betwixt questions is on the jakarta commons user list. you'll also find 
that there are quite a few examples on the website.

but in brief: betwixt marshalls java beans to xml documents and 
unmarshalls xml documents to java beans. it is dynamic as opposed to 
generative in it's approach.

- robert
On 7 Jul 2004, at 14:16, Sako! wrote:
what is this dude? i read the about Betwixt, but still didnt 
understand what
is it good for?
give an example please.
Sako.
- Original Message -
From: robert burrell donkin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, July 03, 2004 1:31 PM
Subject: [ANNOUNCEMENT] Jakarta Commons Betwixt 0.5 Released


The Jakarta Commons team is pleased to announce the release of Betwixt
0.5.
Betwixt is a dynamic start-from-java xml-object mapper. For more 
details
see http://jakarta.apache.org/commons/betwixt/.

This release is intended to consolidate the codebase previously
released as
Betwixt-1.0-Alpha-1. It is recommended that those users who are
currently
using that release or later snapshots (of this codebase) upgrade to
this version.
Note that those users currently using a snapshot from the refactoring
branch
should wait until the 0.6 version is released.
A new release and versioning strategy for Betwixt has been adopted. 
The
version name 0.5 more accurately reflects the current state of the
released
codebase. It is stable but limited and important elements of the API
are likely
to change in the future. More frequent releases are now planning and a
0.6
release containing the improved bean reading design is planned for the
near
future.

Download the binary distribution from:
   http://jakarta.apache.org/site/binindex.cgi#commons-betwixt
and the source distribution from:
   http://jakarta.apache.org/site/sourceindex.cgi#commons-betwixt
Robert
-
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]


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


apachenews.org

2004-07-08 Thread Tetsuya Kitahata

Hi,


Well -- Now I am trying to gather the news items which would be
related to the ASF activities -- at http://www.apachenews.org/
... Since the middle of the March 2004.

I found it that there are/were keen users of asf products
who want to keep it in touch with the news of the asf activities.
-- 0.1 million unique visitors and 0.2 million page views -- there.
I think it that perhaps I can *donate* the gains (google.com! ^^;)
to the fund-raising team @ apache.org.
# very low estimated benefit, though -- 30 US$ per month, I think.

I'd like to this BLOG to be soared up more official asf
activities if allowed. -- this would be very similar to the
activities of public relations, perhaps.
Now, I do have that domain -- apachenews.org, but of course
I can (and want to) donate it to the asf and willing to if there
would be nice community which can accomodate such a news blog.

--

Ahhh -- and I'd like to recruit the editor of this news blog.
http://www.apachenews.org/
( to be honest, I registered someone who would have come
to be interested in such activities -- @ May 2004 ^^:)
I thought it that perhaps this would be an alternative
of the Apache Newsletter or something equivalent.

 Guys, are you INTERESTED?

ahhh .. this is an unofficial activitiy, perhaps. guys,
you can post news items to [EMAIL PROTECTED].
I will update as soon as possible. Nice marketing tool,
I can assure. :-) -- news items would be reflected to
http://www.apachenews.org / as soon as possible.
-- perhaps for job huntings to be enhanced in the near future.

I want to be with you, genius developers.

Thanks,

Sincerely,


-
Tetsuya Kitahata --  Terra-International (Independent)
E-mail: [EMAIL PROTECTED]  http://www.terra-intl.com/


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