Re: [Jakarta Wiki] Update of FrontPage by PhilSteitz
2011/12/22 Apache Wiki wikidi...@apache.org: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The FrontPage page has been changed by PhilSteitz: http://wiki.apache.org/jakarta/FrontPage?action=diffrev1=23rev2=24 Comment: Deleted spam links. see the list of top-level projects at [[http://www.apache.org|the main apache website]] and [[http://wiki.apache.org|the main Apache Wiki]] for information on these. The main Jakarta web site can be found at http://jakarta.apache.org/. [[Reference_Library]] and [[Vendor Support]] are two pages from the web site that can now be found here on the wiki. + - * [[http://www.buzzbacklinks.com|buy backlinks]] - * [[http://www.buzzbacklinks.com|backlink services]] - [[http://www.windows8update.com|windows 8]] This wiki contains information pertaining to the Jakarta project as a whole (mostly management and administration information). Links to the wiki pages for the various Jakarta sub-projects may be found [[http://wiki.apache.org/general|here]]. - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org -- Marcin Miotk Phone: +48 885 704 140 Email: mmiot...@gmail.com SKYPE: mmiotk84 - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
FrontPage reverted to revision 14 on Jakarta Wiki
Dear wiki user, You have subscribed to a wiki page Jakarta Wiki for change notification. The page FrontPage has been reverted to revision 14 by ScottEade. The comment on this change is: spam. http://wiki.apache.org/jakarta/FrontPage?action=diffrev1=15rev2=16 -- * [[Adding_To_The_PMC]] * [[JakartaPMCPropsedChanges]] (deprecated-draft) * [[JakartaPMCVotingProcedures]] (deprecated-draft) - * [[http://www.juziku.com/|聚资库]] TLP proposals - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Page JakartaBoardReport-current renamed to JakartaBoardReport-J uly2010 on Jakarta Wiki
Dear wiki user, You have subscribed to a wiki page Jakarta Wiki for change notification. The page JakartaBoardReport-July2010 has been renamed from JakartaBoardReport-current by RahulAkolkar. The comment on this change is: July report submitted, renaming page.. http://wiki.apache.org/jakarta/JakartaBoardReport-July2010 - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Page 8855 deleted from Jakarta Wiki
Dear wiki user, You have subscribed to a wiki page Jakarta Wiki for change notification. The page 8855 has been deleted by ScottEade. The comment on this change is: spam. http://wiki.apache.org/jakarta/8855 - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Page maryjones035 deleted from Jakarta Wiki
Dear wiki user, You have subscribed to a wiki page Jakarta Wiki for change notification. The page maryjones035 has been deleted by SebastianBazley. The comment on this change is: Spam. http://wiki.apache.org/jakarta/maryjones035 - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Page JakartaBoardReport-current renamed to JakartaBoardReport-A pril2010 on Jakarta Wiki
Dear wiki user, You have subscribed to a wiki page Jakarta Wiki for change notification. The page JakartaBoardReport-April2010 has been renamed from JakartaBoardReport-current by RahulAkolkar. The comment on this change is: Sent.. http://wiki.apache.org/jakarta/JakartaBoardReport-April2010 - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Page JakartaBoardReport-current deleted from Jakarta Wiki
Dear wiki user, You have subscribed to a wiki page Jakarta Wiki for change notification. The page JakartaBoardReport-current has been deleted by RahulAkolkar. The comment on this change is: Page seems to be in bad state due to 500.. http://wiki.apache.org/jakarta/JakartaBoardReport-current - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
FrontPage reverted to revision 8 on Jakarta Wiki
Dear wiki user,
You have subscribed to a wiki page Jakarta Wiki for change notification.
The page FrontPage has been reverted to revision 8 by SebastianBazley.
The comment on this change is: DeSpam.
http://wiki.apache.org/jakarta/FrontPage?action=diffrev1=11rev2=12
--
##language:en
#pragma section-numbers off
= Welcome to the Jakarta Wiki =
- || {{http://jakarta.apache.org/images/jakarta-community.png}} ||This is the
[[http://wiki.apache.org/general/|Apache Wiki]] for the
[[http://jakarta.apache.org/|Jakarta]] community. To edit pages, visit
[[UserPreferences|login]] near the top right corner of any page to create a
user profile or to login. Notifications of all changes you make will be sent to
the gene...@jakarta mailing list, so we will be aware of your changes and we
will happily correct any small mistakes that you might make. ||
+ || {{http://jakarta.apache.org/images/jakarta-community.png}} || This is the
[[http://wiki.apache.org/general/|Apache Wiki]] for the
[[http://jakarta.apache.org/|Jakarta]] community. To edit pages, visit
[[UserPreferences|login]] near the top right corner of any page to create a
user profile or to login. Notifications of all changes you make will be sent to
the gene...@jakarta mailing list, so we will be aware of your changes and we
will happily correct any small mistakes that you might make. ||
+ The Jakarta project is a collection of sub-projects that provide server-side
solutions using the Java language.
+ The Apache Software Foundation also hosts projects written in Java which are
not managed as part of the Jakarta project;
+ see the list of top-level projects at [[http://www.apache.org|the main apache
website]] and [[http://wiki.apache.org|the main Apache Wiki]] for information
on these.
- The Jakarta project is a collection of sub-projects that provide server-side
solutions using the Java language script. The Apache Software Foundation also
hosts projects written in Java which are not managed as part of the Jakarta
project; see the list of top-level projects at [[http://www.apache.org|the
main apache website]] and [[http://wiki.apache.org|the main Apache Wiki]] for
information on these.
+ The main Jakarta web site can be found at http://jakarta.apache.org/.
[[Reference_Library]] and [[Vendor Support]] are two pages from the web site
that can now be found here on the wiki.
+ This wiki contains information pertaining to the Jakarta project as a whole
(mostly management and administration information).
+ Links to the wiki pages for the various Jakarta sub-projects may be found
[[http://wiki.apache.org/general|here]].
- The main Jakarta web site can be found at http://jakarta.apache.org/.
[[Reference_Library]] and [[Vendor Support]] are two pages from the web site
that can now be found here on this wiki.
-
- This wiki contains information pertaining to the Jakarta project as a whole
(mostly management and administration information). Links to the wiki pages for
the various Jakarta sub-projects may be found
[[http://www.besttermpaper.com|research paper here]].
There is an external unofficial
[[http://www.nabble.com/Jakarta-f288.html|Jakarta Forum]] that currently
archives the mailing lists from all the Jakarta sub projects. You can browse or
search the messages, and find out what the entire Jakarta community is talking
about.
=== Jakarta project management ===
The Jakarta project exists as part of the Apache Software Foundation (ASF).
The ASF board delegates responsibility for overseeing all the Jakarta products
to a committee known as the Jakarta PMC.
- * [[JakartaPMC]]
+ * [[JakartaPMC]]
-
- * [[JakartaPMCTopLevelProjectApplication]]
+ * [[JakartaPMCTopLevelProjectApplication]]
-
- * [[Adding_To_The_PMC]]
+ * [[Adding_To_The_PMC]]
-
- * [[JakartaPMCPropsedChanges]] (deprecated-draft)
+ * [[JakartaPMCPropsedChanges]] (deprecated-draft)
-
- * [[JakartaPMCVotingProcedures]] (deprecated-draft)
+ * [[JakartaPMCVotingProcedures]] (deprecated-draft)
TLP proposals
* [[TLPCactusAndJMeter]]
- * [[TLPCactusAndJMeter/Notes]]
+* [[TLPCactusAndJMeter/Notes]]
-
* [[TLPSlide]]
-
* [[TLPHttpComponents]]
=== Jakarta PMC Chair thoughts ===
(Hen) For want of anywhere else to place this, a scratchpad in which I can
record some ideas.
- * RoleOfChair
+ * [[RoleOfChair]]
-
- * JakartaReport
+ * [[JakartaReport]]
-
- * JakartaIssues
+ * [[JakartaIssues]]
-
- * LicenceIssues
+ * [[LicenceIssues]]
=== Jakarta Infrastructure ===
- * WikiInfo
+ * [[WikiInfo]]
- * MailListInfo
+ * [[MailListInfo]]
-
- * BugzillaInfo
+ * [[BugzillaInfo]]
-
- * JiraInfo
+ * [[JiraInfo]]
-
* [[Migrating_to_Subversion]]
-
- * NewCommittersInfo
+ * [[NewCommittersInfo]]
-
- * NewSubprojectInfo
+ * [[NewSubprojectInfo]]
-
- * KarmaInfo
+ * [[KarmaInfo]]
-
- * SiteInfo
+ * [[SiteInfo
FrontPage reverted to revision 5 on Jakarta Wiki
Dear wiki user,
You have subscribed to a wiki page Jakarta Wiki for change notification.
The page FrontPage has been reverted to revision 5 by SebastianBazley.
The comment on this change is: DeSpam.
http://wiki.apache.org/jakarta/FrontPage?action=diffrev1=7rev2=8
--
##language:en
#pragma section-numbers off
= Welcome to the Jakarta Wiki =
- || {{http://jakarta.apache.org/images/jakarta-community.png}} ||This is the
[[http://wiki.apache.org/general/|Apache Wiki]] for the
[[http://jakarta.apache.org/|Jakarta]] community. To edit pages, visit
[[UserPreferences|login]] near the top right corner of any page to create a
user profile or to login. Notifications of all changes you make will be sent to
the gene...@jakarta mailing list, so we will be aware of your changes and we
will happily correct any small mistakes that you might make. ||
+ || {{http://jakarta.apache.org/images/jakarta-community.png}} || This is the
[[http://wiki.apache.org/general/|Apache Wiki]] for the
[[http://jakarta.apache.org/|Jakarta]] community. To edit pages, visit
[[UserPreferences|login]] near the top right corner of any page to create a
user profile or to login. Notifications of all changes you make will be sent to
the gene...@jakarta mailing list, so we will be aware of your changes and we
will happily correct any small mistakes that you might make. ||
+ The Jakarta project is a collection of sub-projects that provide server-side
solutions using the Java language.
+ The Apache Software Foundation also hosts projects written in Java which are
not managed as part of the Jakarta project;
+ see the list of top-level projects at [[http://www.apache.org|the main apache
website]] and [[http://wiki.apache.org|the main Apache Wiki]] for information
on these.
- The Jakarta project is a collection of sub-projects that provide server-side
solutions using the Java language. The Apache Software Foundation also hosts
projects written in Java which are not managed as part of the Jakarta project;
see the list of top-level projects at [[http://www.apache.org|the main apache
website]] and [[http://wiki.apache.org|the main Apache Wiki]] for information
on these.
+ The main Jakarta web site can be found at http://jakarta.apache.org/.
[[Reference_Library]] and [[Vendor Support]] are two pages from the web site
that can now be found here on the wiki.
+ This wiki contains information pertaining to the Jakarta project as a whole
(mostly management and administration information).
+ Links to the wiki pages for the various Jakarta sub-projects may be found
[[http://wiki.apache.org/general|here]].
- The main Jakarta web site can be found at http://jakarta.apache.org/.
[[Reference_Library]] and [[Vendor Support]] are two pages from the web site
that can now be found here on the wiki.
-
- This wiki contains information pertaining to the Jakarta project as a whole
(mostly management and administration information). Links to the wiki pages for
the various Jakarta sub-projects may be found
[[http://wiki.apache.org/general|here]].
There is an external unofficial
[[http://www.nabble.com/Jakarta-f288.html|Jakarta Forum]] that currently
archives the mailing lists from all the Jakarta sub projects. You can browse or
search the messages, and find out what the entire Jakarta community is talking
about.
-
- Also some details are written in [[http://www.besttermpaper.com|Paper writing
service]] , only for user attention.
=== Jakarta project management ===
The Jakarta project exists as part of the Apache Software Foundation (ASF).
The ASF board delegates responsibility for overseeing all the Jakarta products
to a committee known as the Jakarta PMC.
- * [[JakartaPMC]]
+ * [[JakartaPMC]]
- * [[JakartaPMCTopLevelProjectApplication]]
+ * [[JakartaPMCTopLevelProjectApplication]]
- * [[Adding_To_The_PMC]]
+ * [[Adding_To_The_PMC]]
- * [[JakartaPMCPropsedChanges]] (deprecated-draft)
+ * [[JakartaPMCPropsedChanges]] (deprecated-draft)
- * [[JakartaPMCVotingProcedures]] (deprecated-draft)
+ * [[JakartaPMCVotingProcedures]] (deprecated-draft)
TLP proposals
* [[TLPCactusAndJMeter]]
- * [[TLPCactusAndJMeter/Notes]]
+* [[TLPCactusAndJMeter/Notes]]
* [[TLPSlide]]
* [[TLPHttpComponents]]
=== Jakarta PMC Chair thoughts ===
(Hen) For want of anywhere else to place this, a scratchpad in which I can
record some ideas.
- * RoleOfChair
+ * [[RoleOfChair]]
- * JakartaReport
+ * [[JakartaReport]]
- * JakartaIssues
+ * [[JakartaIssues]]
- * LicenceIssues
+ * [[LicenceIssues]]
=== Jakarta Infrastructure ===
+
- * WikiInfo
+ * [[WikiInfo]]
- * MailListInfo
+ * [[MailListInfo]]
- * BugzillaInfo
+ * [[BugzillaInfo]]
- * JiraInfo
+ * [[JiraInfo]]
* [[Migrating_to_Subversion]]
- * NewCommittersInfo
+ * [[NewCommittersInfo]]
- * NewSubprojectInfo
+ * [[NewSubprojectInfo]]
- * KarmaInfo
+ * [[KarmaInfo
Re: [Jakarta Wiki] Update of JakartaBoardReport-current by MartinvandenBemt
If everyone is ok with it, I will send the current state of this page as the board report ? Mvgr, Martin - Original Message - From: Apache Wiki wikidi...@apache.org To: general@jakarta.apache.org Sent: Monday, May 18, 2009 9:45:42 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: [Jakarta Wiki] Update of JakartaBoardReport-current by MartinvandenBemt Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by MartinvandenBemt: http://wiki.apache.org/jakarta/JakartaBoardReport-current -- === Status === - Chair to summarize Jakarta-wide news + the current state of affairs. + It has been a while since I reported the last time. In june 2009 I announced + that I wanted to be replaced because of time constraints, with no one + volunteering. After that however I got caught up with what was happening in my + personal life and also was shutdown for over 3 months, which ended up in a + long period of silence. + Now all major personal events (positive I might add, so please don't worry) + have passed, I however still find myself fighting to find time (and energy) to + spend at Apache. + + In the light of this, I hand in my resignation as VP Apache Jakarta. + To my relieve a discussion about the (in reality already effective) vacancy + started and some people stood up to volunteer to take over the position. + + I myself regret the long absence and silence and I hope it didn't cause to + much worry and problems. + === Releases === - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [Jakarta Wiki] Update of JakartaBoardReport-current by MartinvandenBemt
Martin van den Bemt wrote: If everyone is ok with it, I will send the current state of this page as the board report ? Reconsider the June 2009 ;-) - Jörg Mvgr, Martin - Original Message - From: Apache Wiki wikidi...@apache.org To: general@jakarta.apache.org Sent: Monday, May 18, 2009 9:45:42 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: [Jakarta Wiki] Update of JakartaBoardReport-current by MartinvandenBemt Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by MartinvandenBemt: http://wiki.apache.org/jakarta/JakartaBoardReport-current -- === Status === - Chair to summarize Jakarta-wide news + the current state of affairs. + It has been a while since I reported the last time. In june 2009 I announced + that I wanted to be replaced because of time constraints, with no one + volunteering. After that however I got caught up with what was happening in my + personal life and also was shutdown for over 3 months, which ended up in a + long period of silence. + Now all major personal events (positive I might add, so please don't worry) + have passed, I however still find myself fighting to find time (and energy) to + spend at Apache. + + In the light of this, I hand in my resignation as VP Apache Jakarta. + To my relieve a discussion about the (in reality already effective) vacancy + started and some people stood up to volunteer to take over the position. + + I myself regret the long absence and silence and I hope it didn't cause to + much worry and problems. + === Releases === - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: [Jakarta Wiki] Update of Using LGPL'd code by HenriYandell
Hi! The following page has been changed by HenriYandell: http://wiki.apache.org/jakarta/Using_LGPL'd_code Does this mean the door to have LGPL dependencies as described below has been closed again? - = Latest [EMAIL PROTECTED] informations (2006) = - - Lately we discussed that it might be possible that the PMC is able to vote to add LGPL stuff to a project as long as the following rule will be fulfilled. - - We still need the ok from legal@ before we start with this procedure. - - At least the jakarta PMC voted that these rules are acceptable. - - == Rules== - - * ask the original library author to change its license or provide a double licensing model - * look for an alternative implementation with an ASF friendly license - * the build script BY DEFAULT excludes java classes depending on LGPL - * a special parameter will enable building these classes - * its not allowed to bundle the LGPL library with any distribution\\(nightly, release) - * the function the library gains from the LGPL stuff is fully optional - * a bridging api (which can reside within the same project - so can be hosted at apache) will be used to access these LGPL stuff to clearly show its optional behaviour - * a vote for adding a LGPL dependency to a project on pmc@ - - The technical stuff how to setup the build has to be figured out. Ciao, Mario - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of Using LGPL'd code by HenriYandell
Ah - now I see. Must be the Optional Add-ons section. Thanks! Ciao, Mario I don't think so - the 3rd party draft I link to says pretty much the same thing. On 10/4/07, Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! The following page has been changed by HenriYandell: http://wiki.apache.org/jakarta/Using_LGPL'd_code Does this mean the door to have LGPL dependencies as described below has been closed again? - = Latest [EMAIL PROTECTED] informations (2006) = - - Lately we discussed that it might be possible that the PMC is able to vote to add LGPL stuff to a project as long as the following rule will be fulfilled. - - We still need the ok from legal@ before we start with this procedure. - - At least the jakarta PMC voted that these rules are acceptable. - - == Rules== - - * ask the original library author to change its license or provide a double licensing model - * look for an alternative implementation with an ASF friendly license - * the build script BY DEFAULT excludes java classes depending on LGPL - * a special parameter will enable building these classes - * its not allowed to bundle the LGPL library with any distribution\\(nightly, release) - * the function the library gains from the LGPL stuff is fully optional - * a bridging api (which can reside within the same project - so can be hosted at apache) will be used to access these LGPL stuff to clearly show its optional behaviour - * a vote for adding a LGPL dependency to a project on pmc@ - - The technical stuff how to setup the build has to be figured out. Ciao, Mario - 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]
Re: [Jakarta Wiki] Update of Using LGPL'd code by HenriYandell
I don't think so - the 3rd party draft I link to says pretty much the same thing. On 10/4/07, Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! The following page has been changed by HenriYandell: http://wiki.apache.org/jakarta/Using_LGPL'd_code Does this mean the door to have LGPL dependencies as described below has been closed again? - = Latest [EMAIL PROTECTED] informations (2006) = - - Lately we discussed that it might be possible that the PMC is able to vote to add LGPL stuff to a project as long as the following rule will be fulfilled. - - We still need the ok from legal@ before we start with this procedure. - - At least the jakarta PMC voted that these rules are acceptable. - - == Rules== - - * ask the original library author to change its license or provide a double licensing model - * look for an alternative implementation with an ASF friendly license - * the build script BY DEFAULT excludes java classes depending on LGPL - * a special parameter will enable building these classes - * its not allowed to bundle the LGPL library with any distribution\\(nightly, release) - * the function the library gains from the LGPL stuff is fully optional - * a bridging api (which can reside within the same project - so can be hosted at apache) will be used to access these LGPL stuff to clearly show its optional behaviour - * a vote for adding a LGPL dependency to a project on pmc@ - - The technical stuff how to setup the build has to be figured out. Ciao, Mario - 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] Update of Carolina+Coast+ by NathanBubna
Hi Nathan, Is this an officially sanctioned (by the ASF) text for deleted wiki pages? Thanks, Matt --- Apache Wiki [EMAIL PROTECTED] wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/jakarta/Carolina+Coast+ The comment on the change is: delete spam -- - spam deleted + deleted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of Carolina+Coast+ by NathanBubna
Never mind--with the current barrage I see that this is apparently a Moin convention. :) -Matt --- Matt Benson [EMAIL PROTECTED] wrote: Hi Nathan, Is this an officially sanctioned (by the ASF) text for deleted wiki pages? Thanks, Matt --- Apache Wiki [EMAIL PROTECTED] wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by NathanBubna: http://wiki.apache.org/jakarta/Carolina+Coast+ The comment on the change is: delete spam -- - spam deleted + deleted - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of JakartaBoardReport-current by RolandWeber
I've added it to the board template :)
Mvgr,
Martin
Apache Wiki wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Jakarta Wiki for
change notification.
The following page has been changed by RolandWeber:
http://wiki.apache.org/jakarta/JakartaBoardReport-current
The comment on the change is:
Martin, you might want to update your template
--
''!FileUpload''
- ''!HttpClient''
-
''IO''
''Jelly''
@@ -105, +103 @@
ECS
HttpComponents
+ ''including !HttpClient''
JCD
-
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] Update of JakartaBoardReport-current by HenriYandell
Apache Wiki wrote: + * Inactive - No activity, no one watching it. Candidate for dormancy. + * Maintenance - No activity, someone watching it. Henri, Regexp + See ORO. + According to your definition, Regexp should be in Maintenance state. Vadim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Trivial Update of JakartaBoardReport-March2007 by RolandWeber
Feel free to remove it from commons and add it to HttpComponents. It was just a dumb copy paste from the commons webpage :) While you are at it, you could also add this to the template (+ httpcode and httpasync) Mvgr, Martin Apache Wiki wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by RolandWeber: http://wiki.apache.org/jakarta/JakartaBoardReport-March2007 The comment on the change is: HttpComponents project is responsible for maintaining Commons HttpClient -- ''!FileUpload'' - ''!HttpClient'' + ''!HttpClient'' - see !HttpComponents project below ''IO'' - 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] Update of JakartaBoardReport-June2006 by FelipeLeme
You're right - good catch! Dennis Lundberg wrote: Cactus 1.17.2 was released on March 26th, 2006. Shouldn't that be 1.7.2? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of JakartaBoardReport-June2006 by FelipeLeme
Apache Wiki wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by FelipeLeme: http://wiki.apache.org/jakarta/JakartaBoardReport-June2006 The comment on the change is: Note sure if I used the proper release format; please feel free to fix it if nec New page: == Month Year Board Report == === Status === Chair to summarize Jakarta-wide news + the current state of affairs. === Releases === Cactus 1.17.2 was released on March 26th, 2006. Shouldn't that be 1.7.2? === Community changes === New committers, pmc persons, asf members and departures. === Infrastructure news === Changes to the projects infrastructure. Migrations to Subversion, new vmware instances etc. === Subproject news === News related to various subprojects, if they have news. Volunteers for subproject news are desired, otherwise the Chair is responsible for finding out said news (and should mark that they had to do so). Subproject A Committer lands on Moon Subproject B Sending committer to Mars - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of TLPSlide by RahulAkolkar
Thanks for catching that Rahul :) Hen On Fri, 24 Mar 2006, Apache Wiki wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by RahulAkolkar: http://wiki.apache.org/jakarta/TLPSlide The comment on the change is: Removed cut and paste error. -- RESOLVED, that the initial Slide PMC be and hereby is tasked with the migration and rationalization of the Apache Jakarta Slide subproject; and be it further - RESOLVED, that all responsibility pertaining to the Jakarta Tapestry subproject and encumbered upon the Apache Jakarta PMC are hereafter discharged. + RESOLVED, that all responsibility pertaining to the Jakarta Slide subproject and encumbered upon the Apache Jakarta PMC are hereafter discharged. - 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] Update of OneCommunityProposals by StephenColebourne
On Sun, 2006-03-12 at 23:32 +0100, Andrew C. Oliver wrote: I'd like to note my opposition. I don't have the same vision as you do and do not wish to be distracted by 100 irrelavant emails a day about Commons ABCD. I'm glad Henri posted that reorganization things were being discussed. I would have preferred that he posted a more detailed message as I think others would likely be opposed to such forms of social engineering. Things evolve the way the evolve for a reason. That POI has relatively little to do with Commons-DB is not really a good reason to force us to listen to noise/interference. In radio, you tend to try and pick bands that aren't real close together so that you don't overlap and trample on each other's bandwidth. I had to do this with my wireless network because my neighbor's stuff kept interferring. No I don't think it would be great if we both shared channel 6 and I don't feel like vetting some non-technical irrelevant change by someone who wanted to get their API used by more projects (nevermind that it performs half as well as the JDK implementation and sucks down 100 other dependencies). And I bet [EMAIL PROTECTED] would be REALLY popular...so popular that ALL questions about POI would go to [EMAIL PROTECTED] with CC to every email address I've ever had and appologies for not posting on the list but half the time you can't unsubscribe and I really don't want 1 emails a day about stuff I'm not using. you've just an excellent argument for moving poi to top level :) like it or not, it's the jakarta pmc which has the binding votes. henri's proposal only formalises and organises the actual current state of affairs. if you don't trust my judgement enough to allow me a veto on poi commits then you need to talk to the other poi committers about graduating poi to top level status. If projects share obvious common technical ties then it makes sense, otherwise lets let darwin decide rather than radical social engineering. The PMC should ASK the individual projects if they would like to share a common list and set of committers rather than a top down decision proposed on a list that most committers don't subscribe to (which might indicate...duh...that they don't want to be on a list mostly not about their project). This proposal and any that resemble it are non-starters for me. A lot of this sounds like Commons trying to remake Jakarta in its image. As an alternative why can't commons be top level? The namespace is now free (http://commons.apache.org/). hmmm... commons, taglibs, http components and whatnot going to commons.apache.org that'd only leaves POI in jakarta: does that really make more sense than apache poi? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of OneCommunityProposals by StephenColebourne
On Mon, 2006-03-13 at 23:48 +0100, Andrew C. Oliver wrote: that'd only leaves POI in jakarta did you have a point there? :-) thanks for highlighting my bad grammar (it's past my bed time) the point was the bit you snipped :) preserving jakarta as a special umbrella for poi seems more than a little odd to me. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of OneCommunityProposals by StephenColebourne
I'd like to note my opposition. I don't have the same vision as you do and do not wish to be distracted by 100 irrelavant emails a day about Commons ABCD. I'm glad Henri posted that reorganization things were being discussed. I would have preferred that he posted a more detailed message as I think others would likely be opposed to such forms of social engineering. Things evolve the way the evolve for a reason. That POI has relatively little to do with Commons-DB is not really a good reason to force us to listen to noise/interference. In radio, you tend to try and pick bands that aren't real close together so that you don't overlap and trample on each other's bandwidth. I had to do this with my wireless network because my neighbor's stuff kept interferring. No I don't think it would be great if we both shared channel 6 and I don't feel like vetting some non-technical irrelevant change by someone who wanted to get their API used by more projects (nevermind that it performs half as well as the JDK implementation and sucks down 100 other dependencies). And I bet [EMAIL PROTECTED] would be REALLY popular...so popular that ALL questions about POI would go to [EMAIL PROTECTED] with CC to every email address I've ever had and appologies for not posting on the list but half the time you can't unsubscribe and I really don't want 1 emails a day about stuff I'm not using. If projects share obvious common technical ties then it makes sense, otherwise lets let darwin decide rather than radical social engineering. The PMC should ASK the individual projects if they would like to share a common list and set of committers rather than a top down decision proposed on a list that most committers don't subscribe to (which might indicate...duh...that they don't want to be on a list mostly not about their project). This proposal and any that resemble it are non-starters for me. A lot of this sounds like Commons trying to remake Jakarta in its image. As an alternative why can't commons be top level? The namespace is now free (http://commons.apache.org/). That is all, -Andy Apache Wiki wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by StephenColebourne: http://wiki.apache.org/jakarta/OneCommunityProposals The comment on the change is: Create page for one community proposals New page: This document proposes ways that we as Jakarta can move towards becoming one community rather than many. ''Note that there is a counter-argument that states that multiple communities within Jakarta is fine. However, at present this conflicts with the ASF board opinion and legal structure.'' == Mission == Jakarta has a less than completely clear mission at the moment. Here is a proposed 'mission statement', please feel free to make alternate suggestions: ''Jakarta provides a diverse set of Java-based components which aim to make day-to-day development easier. The focus is on reusable, small-scale, single-purpose libraries that can be used directly by your application or by larger frameworks.'' It would seem appropriate for whatever mission we choose to be on the top of the Jakarta home page. == Maililng lists == Jakarta has about 16 current project mailing lists. One is very active (commons) and the rest vary from some activity to very little. Mailing lists are significant as they represent the primary means of communication in a project, and thus the primary form of community. Any change to mailing list structure needs careful consideration. The aim of any change is to create better oversight of the mature components. A 'one community' proposal must provide a technique to reduce the mailing list silo effect, where developers are not interested in other lists (and thus other parts of the same community). == Subversion access == Jakarta currently gives out SVN access to individual subprojects. A 'one community' proposal almost certainly involves removing this barrier. Any Jakarta committer can thus commit anywhere in Jakarta. Social norms will still act as a barrer to undesirable behaviour. == Subprojects == As developers we tend to abstract and form hierarchies naturally. Subprojects are a natural outcome of this. However, Jakarta as 'one community' must mean the end to the term 'subprojects'. Instead, a focus on many, many components directly at the Jakarta level is the best viewpoint. == Practicalities == The single-level groupings proposal. Theory - One community split into groups for practicality purposes (everyone together would be chaos!) * Move all commons proper projects up to the jakarta level in SVN and on the website. * Commons level infrastructure/pages is dismantled and moved to jakarta-level * Agree on 4 to 5 groupings for the current subprojects (this is hard!!! it should ideally be driven by the current component owners
Re: [Jakarta Wiki] Update of OneCommunityProposals by StephenColebourne
For the record, I wrote this to try to sum up where discussions have got to and to provide some vision as to where the end result might be. Checking mailing lists tonight indicates that POI has quite a healthy set of messages as is. I didn't see much development discussion (an indicator of community) but I could be mistaken. IMO, a *forced* merger of POI with another group would have very negative consequences, both for POI and the other group. Sorry I wasn't clear on that. At the moment, I see this debate as not affecting POI. (It also probably excludes Hivemind and possibly some other subprojects). IMHO, this debate is about commons and the inactive/mature Jakarta subprojects. Andrew C. Oliver wrote: A lot of this sounds like Commons trying to remake Jakarta in its image. As an alternative why can't commons be top level? The namespace is now free (http://commons.apache.org/). or why not http://poi.apache.org/ ;-) Then you don't have to listen to our debates. Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of OneCommunityProposals by StephenColebourne
On Sun, 12 Mar 2006, Andrew C. Oliver wrote: I'm glad Henri posted that reorganization things were being discussed. I would have preferred that he posted a more detailed message as I think others would likely be opposed to such forms of social engineering. Things evolve the way the evolve for a reason. That POI has relatively little to do with I didn't post more because I didn't want to falsely represent Martin, Stephen and many others' viewpoints. Best to read the originals I figure. If projects share obvious common technical ties then it makes sense, otherwise lets let darwin decide rather than radical social engineering. This is a point many have brought up (Martin, Stephen, yourself). Let evolution take care of it. It's a cool saying to use. Unfortunately it's a terrible metaphor. Evolution happens in spontaneous bursts, and via mutations that allow some to be better suited to environmental change. Not because the whole decide to change their ways. This is evolution happening right now. What you mean to say is let's not change. [I fully accept I don't get evolution, it's a moving target of a subject - but I'm closer than the previous metaphor] The PMC should ASK the individual projects if they would like to share a common list and set of committers rather than a top down decision proposed on a list that most committers don't subscribe to (which might indicate...duh...that they don't want to be on a list mostly not about their project). This proposal and any that resemble it are non-starters for me. What it indicates is that they are not a part of the Jakarta community. The viewpoint that I am an ECS committer, not a Jakarta committer has only one answer to my view - ecs.apache.org. A lot of this sounds like Commons trying to remake Jakarta in its image. As Nope, much of this is me trying to turn Jakarta into a normal Apache project - rather than the corpse of something that was determined to be unwanted by the ASF as a whole many years ago. Jakarta was considered in need of change back then and thus the TLPs started happening, and we're less healthy now than we were then. Given that Commons defines a much healthier umbrella concept than Jakarta does, I'm seeking to bring those ideas up into Jakarta while flattening the whole so we're less of a 3 to 4 tier umbrella. an alternative why can't commons be top level? The namespace is now free (http://commons.apache.org/). It's definitely another option - and one I've mentioned. The namespace is pretty much free - a few views that we shouldn't be re-using an old name but I'm confident we'd be able to use the name. One point likely to cause trouble is over whether commons.apache.org would be Java focused or not. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of OneCommunityProposals by StephenColebourne
On Sun, 12 Mar 2006, Stephen Colebourne wrote: Checking mailing lists tonight indicates that POI has quite a healthy set of messages as is. I didn't see much development discussion (an indicator of community) but I could be mistaken. There's not a lot of conversation on poi-dev; though there is a healthy flow via bugzilla comments and occasional svn commits. IMO, a *forced* merger of POI with another group would have very negative consequences, both for POI and the other group. Sorry I wasn't clear on that. Agreed. At the moment, I see this debate as not affecting POI. (It also probably excludes Hivemind and possibly some other subprojects). IMHO, this debate is about commons and the inactive/mature Jakarta subprojects. Yup. Tapestry - TLP Slide - TLP (if they get active enough to do it) Cactus/JMeter - TLP (need to write a proposal) Turbine - Against TLP HiveMind - Just brought an email on TLP alive again. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
:/ On 11 Mar 2006 22:57:36 +0300, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Please send email at [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Unsubscribed. Not a huge effort for nayeem to resubscribe once they've figured out what's going on with the spamming :) Hen On Sat, 11 Mar 2006, Jesse Kuhnert wrote: :/ On 11 Mar 2006 22:57:36 +0300, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Please send email at [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]
Re: Re: Re: [Jakarta Wiki] Update of JakartaBoardReport-March2006 by DanielSavarese
Scratch that, my unsubscribe reply came back empty. Neither gulfnetksa or zajil on the subscriber list. Bizarre :) Hen On Sat, 11 Mar 2006, Henri Yandell wrote: Unsubscribed. Not a huge effort for nayeem to resubscribe once they've figured out what's going on with the spamming :) Hen On Sat, 11 Mar 2006, Jesse Kuhnert wrote: :/ On 11 Mar 2006 22:57:36 +0300, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Please send email at [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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of JakartaBoardReport-December2005 by JürgenHermann
Nope, it should be December. My time machine is simple, to get to time T from time N, you sit in the machine for T - N and then get out :) Idea is to have the report being written over the next 3 months and not at the end, it worked a fair bit last quarter. Hen On Sat, 1 Oct 2005, Apache Wiki wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by J??rgenHermann: http://wiki.apache.org/jakarta/JakartaBoardReport-December2005 -- == December 2005 Board Report == + + ? Hmm, can you lend me your time machine? ;) I guess this should be September... === Status === - 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] Update of JakartaBoardReport-September2005 by SebastianBazley
Need a bit more than that Seb :) Take a look at the previous board reports, we're looking for a bit of colour as to what's happened to your sub-community during the previous quarter, usually driven by what the release meant to the community. Is it a bug release, major release etc, are there plans for big changes etc. http://jakarta.apache.org/site/pmc/board-reports.html Hen On Sun, 4 Sep 2005, Apache Wiki wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by SebastianBazley: http://wiki.apache.org/jakarta/JakartaBoardReport-September2005 The comment on the change is: Update JMeter -- JMeter + 24 August 2005 - JMeter 2.1 released + Taglibs (RDC) 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]
Re: [Jakarta Wiki] Update of JakartaBoardReport-September2005 by SebastianBazley
OK - I was just going by the other entries on the Wiki ...
We'll try and add something more shortly.
S.
On 04/09/05, Henri Yandell [EMAIL PROTECTED] wrote:
Need a bit more than that Seb :)
Take a look at the previous board reports, we're looking for a bit of
colour as to what's happened to your sub-community during the previous
quarter, usually driven by what the release meant to the community. Is it
a bug release, major release etc, are there plans for big changes etc.
http://jakarta.apache.org/site/pmc/board-reports.html
Hen
On Sun, 4 Sep 2005, Apache Wiki wrote:
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Jakarta Wiki for
change notification.
The following page has been changed by SebastianBazley:
http://wiki.apache.org/jakarta/JakartaBoardReport-September2005
The comment on the change is:
Update JMeter
--
JMeter
+ 24 August 2005 - JMeter 2.1 released
+
Taglibs (RDC)
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of Migrating to Subversion by HenriYandell
Hey guys, I'm up for making this happen when ever the active Turbine committers give the thumbs up (I myself haven't been active lately). Henning, let me know. - Dan On Thu, 2005-07-14 at 03:15 +, Apache Wiki wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by HenriYandell: http://wiki.apache.org/jakarta/Migrating_to_Subversion -- * JMeter- Nudge sent. * POI - Nudged. Is OS X support good enough? amongst other questions. * Tapestry - Nudged. Is [http://sublicpse.tigris.org/ Subclipse] good enough? - * Turbine - Henning Schmiedehausen, Daniel Rall + * Turbine - Henning Schmiedehausen, Daniel Rall (Discussing on Tuesday 19th at ApacheCon) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of Migrating to Subversion by HenriYandell
Hi Daniel, (will you be @ ApacheCon EU?) Thomas Fischer of DB Torque and I have agreed to migrate DB Torque at ApacheCon and we will also do the Turbine conversion. If you are around (physically or at IRC), your help will be very much appreciated. Regards Henning On Fri, 2005-07-15 at 03:40 -0700, Daniel L. Rall wrote: Hey guys, I'm up for making this happen when ever the active Turbine committers give the thumbs up (I myself haven't been active lately). Henning, let me know. - Dan On Thu, 2005-07-14 at 03:15 +, Apache Wiki wrote: Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by HenriYandell: http://wiki.apache.org/jakarta/Migrating_to_Subversion -- * JMeter- Nudge sent. * POI - Nudged. Is OS X support good enough? amongst other questions. * Tapestry - Nudged. Is [http://sublicpse.tigris.org/ Subclipse] good enough? - * Turbine - Henning Schmiedehausen, Daniel Rall + * Turbine - Henning Schmiedehausen, Daniel Rall (Discussing on Tuesday 19th at ApacheCon) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new Standard/JSTL subproject? [WAS Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin]
Henri Yandell wrote: are there any committers involved with JSTL around? Sorry, I raised the question then entered in JavaOne-sleep-mode :( if not, would anyone like to volunteer to sound them out about a move to subproject status? I vote for Standard being a separate Jakarta sub-project. I've mentioned the idea on the taglibs-dev mailing list, no reply as yet. There hasn't being too many messages by the committers lately, specially on votes. So, tomorrow (I'm too tired now :-) I will send a big message summarizing all of these pending votes and hopefully we will get enough committer answers now... -- Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
new Standard/JSTL subproject? [WAS Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin]
On Thu, 2005-06-23 at 20:14 -0400, Henri Yandell wrote: On Thu, 23 Jun 2005, robert burrell donkin wrote: On Thu, 2005-06-23 at 00:49 -0300, Felipe Leme wrote: Apache Wiki wrote: Please do not edit comments into this text: please use the CharterForWebCommonsRequestForComments or post to [http://jakarta.apache.org/site/mail.html General At Jakarta]. OK, here I am posting :-) 3.What about the Standard Taglibs? Should it be part of this new project or should it be a separate project. The reasoning here is that, because that sub-project provide the codebase for JSTL's implementation (and maybe other JSR taglibs in the future as well, such as the Web Services taglib), its development activities/cycles might be different from the non-standard ones (we could even try to apply the TCK on such projects in the future, for instance). if the new subproject is anything like the commons then each component will have it's own development rhythm. it might be easier to raise extra hands when needed for these efforts if these share the same infrastructure (mailing lists, subproject organization and so on). opinions? My vote is for the active Taglibs to roll into the web component subproject, but for the Standard/JSTL taglib to move to Jakarta subproject status. Taglibs-user is dominated by JSTL questions and the JSTL committers don't have any obvious overlap with the other taglib committers (that I've noticed). Also in terms of codebase, Standard is the relative behemoth. Lastly it has a much higher profile than other parts of web-component-subproject will have and as a spec implementation it has a different set of issues to deal with. +1 are there any committers involved with JSTL around? if not, would anyone like to volunteer to sound them out about a move to subproject status? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: new Standard/JSTL subproject? [WAS Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin]
On 6/26/05, robert burrell donkin [EMAIL PROTECTED] wrote: are there any committers involved with JSTL around? if not, would anyone like to volunteer to sound them out about a move to subproject status? I've mentioned the idea on the taglibs-dev mailing list, no reply as yet. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of CreatingCommonsForWebComponents by FelipeLeme
On Thu, 2005-06-23 at 00:38 -0300, Felipe Leme wrote: I also fixed the alphabetic order of the existing proposals (but accidently typed enter before adding that comment). thanks - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin
On Thu, 2005-06-23 at 00:49 -0300, Felipe Leme wrote: Apache Wiki wrote: Please do not edit comments into this text: please use the CharterForWebCommonsRequestForComments or post to [http://jakarta.apache.org/site/mail.html General At Jakarta]. OK, here I am posting :-) I'd like to suggest 2 things: 1.We prefereably use Maven for the builds, as it helps a lot handling the dependencies (if we stick to Ant, we should at least use Ivy or M2 Ant stuff for dependency management). For instance, I haven't applied some patches to the Jakarta Taglibs because my computers are not set for building them anymore (and I don't have the time/patience to fix it). jakarta commons is agnostic (but uses maven for the website). i'd recommend official agnosticism with unofficial encouragement to maven. it is a good idea to provide ant scripts generated by maven in SVN. 2.Regarding the Jakarta Taglibs, we should create the new taglibs from scratch. I mean, of course we should reuse the code, but we better do some refactoring first (for instance, eliminating redundant taglibs, defining a role for TLD names, etc...) - the current Jakarta Taglibs would then be frozen in time. IMHO it would probably be more convenient to maintain these frozen taglibs (from an official perspective) within the new subproject. with subversion, it's really nice and easy to have cool directory structures... 3.What about the Standard Taglibs? Should it be part of this new project or should it be a separate project. The reasoning here is that, because that sub-project provide the codebase for JSTL's implementation (and maybe other JSR taglibs in the future as well, such as the Web Services taglib), its development activities/cycles might be different from the non-standard ones (we could even try to apply the TCK on such projects in the future, for instance). if the new subproject is anything like the commons then each component will have it's own development rhythm. it might be easier to raise extra hands when needed for these efforts if these share the same infrastructure (mailing lists, subproject organization and so on). opinions? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin
On Thu, 2005-06-23 at 00:52 -0300, Felipe Leme wrote: Felipe Leme wrote: I'd like to suggest 2 things: ... 3 Damn, beaten by the ENTER key again :-( shades of monty python's flying circus ;) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin
robert burrell donkin wrote: if the new subproject is anything like the commons then each component will have it's own development rhythm. I think this is a cogent point... if the idea is that this is like a Commons project, than I have to ask the question: why not just have a few new Commons projects, as was my original proposal? I originally started by suggesting a Commons Filters, because I had some filters I wanted to contribute. So far I think we've brainstormed something like 4-6 sort of sub-packages of this... If they are going to develop to their own rhythm as you say, then why not make each a Commons project, where there already largely is the infrastructure (in the larger sense) build up? That would seem to me the path of least (or at least lower) resistance, and maybe even a more appropriate fit. It's a question of what the vision is of course... if everyone is thinking along the commons lines anyway, why not just do it in Commons? Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin
On Thu, 2005-06-23 at 17:55 -0400, Frank W. Zammetti wrote: robert burrell donkin wrote: if the new subproject is anything like the commons then each component will have it's own development rhythm. I think this is a cogent point... if the idea is that this is like a Commons project, than I have to ask the question: why not just have a few new Commons projects, as was my original proposal? The relevant questions are: * what percentage of the existing commons developers are interested in working on web components * what percentage of the prospective web developers are interested in participating in other commons projects * what percentage of users and interested in both web and normal commons projects. If the answer to any of these is high then the benefits of a combined community outweigh the nuisance of excessive emails, overly-large subproject lists and general distraction. I would guess the critical threshold to be about 25% - but I don't think that will be reached, ie I believe that less than 25% of existing commons committers would be interested in web commons components of the sort proposed. Therefore having such components in the existing commons will just annoy people without having any significant benefits (other than allowing this startup hassle for web commons to be skipped). Already we have people (both developers and users) agitating for separate per-component mail lists due to the volume of emails in commons. Some people have stated that they refuse to subscribe or be part of the community while there is a shared list. I would hate to see separate lists, but they have a point - there is an upper limit to the amount of mail people can handle (esp. people on dial-up connections; filtering by mail subject doesn't reduce the bandwidth needed to download all the mails). There is also the issue of community size. Commons has a couple of dozen regular committers, which means we all recognise each other's names. That's quite important I think, and brings some sense of team membership. Diluting this with another dozen developers (I hope web commons will grow to that size!) may change that sense of community (esp. if we don't have many interests in common). And likewise for new web commons committers - I think the sense of a team will be stronger with a separate project/mail-list etc. I admit it's all guesswork and a little crystal-ball-gazing. If web-commons is a failure, ie only a couple of projects get off the ground, then the existing commons would be a better home. But I hope that's not the case - there does seem to be a reasonable number of ideas and people willing to push them forward. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin
On Thu, 23 Jun 2005, robert burrell donkin wrote: On Thu, 2005-06-23 at 00:49 -0300, Felipe Leme wrote: Apache Wiki wrote: Please do not edit comments into this text: please use the CharterForWebCommonsRequestForComments or post to [http://jakarta.apache.org/site/mail.html General At Jakarta]. OK, here I am posting :-) 3.What about the Standard Taglibs? Should it be part of this new project or should it be a separate project. The reasoning here is that, because that sub-project provide the codebase for JSTL's implementation (and maybe other JSR taglibs in the future as well, such as the Web Services taglib), its development activities/cycles might be different from the non-standard ones (we could even try to apply the TCK on such projects in the future, for instance). if the new subproject is anything like the commons then each component will have it's own development rhythm. it might be easier to raise extra hands when needed for these efforts if these share the same infrastructure (mailing lists, subproject organization and so on). opinions? My vote is for the active Taglibs to roll into the web component subproject, but for the Standard/JSTL taglib to move to Jakarta subproject status. Taglibs-user is dominated by JSTL questions and the JSTL committers don't have any obvious overlap with the other taglib committers (that I've noticed). Also in terms of codebase, Standard is the relative behemoth. Lastly it has a much higher profile than other parts of web-component-subproject will have and as a spec implementation it has a different set of issues to deal with. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Jakarta Wiki] Trivial Update of Migrating to Subversion byDanielRall
Well Dean, it _was_ a wording tweak, meaning that the actual content didn't change much, merely the verbiage. - verbiage \VUR-bee-ij\, noun: The use of many words without necessity - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Jakarta Wiki] Trivial Update of Migrating to Subversion byDanielRall
On Wed, 2005-06-22 at 11:49 +0200, Dean Pickersgill wrote: Well Dean, it _was_ a wording tweak, meaning that the actual content didn't change much, merely the verbiage. - verbiage \VUR-bee-ij\, noun: The use of many words without necessity - manner of expressing oneself in words - m-w.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of CreatingCommonsForWebComponents by FelipeLeme
I also fixed the alphabetic order of the existing proposals (but accidently typed enter before adding that comment). Apache Wiki wrote: The comment on the change is: - added my suggestions - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin
Apache Wiki wrote: Please do not edit comments into this text: please use the CharterForWebCommonsRequestForComments or post to [http://jakarta.apache.org/site/mail.html General At Jakarta]. OK, here I am posting :-) I'd like to suggest 2 things: 1.We prefereably use Maven for the builds, as it helps a lot handling the dependencies (if we stick to Ant, we should at least use Ivy or M2 Ant stuff for dependency management). For instance, I haven't applied some patches to the Jakarta Taglibs because my computers are not set for building them anymore (and I don't have the time/patience to fix it). 2.Regarding the Jakarta Taglibs, we should create the new taglibs from scratch. I mean, of course we should reuse the code, but we better do some refactoring first (for instance, eliminating redundant taglibs, defining a role for TLD names, etc...) - the current Jakarta Taglibs would then be frozen in time. 3.What about the Standard Taglibs? Should it be part of this new project or should it be a separate project. The reasoning here is that, because that sub-project provide the codebase for JSTL's implementation (and maybe other JSR taglibs in the future as well, such as the Web Services taglib), its development activities/cycles might be different from the non-standard ones (we could even try to apply the TCK on such projects in the future, for instance). -- Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of DraftCharterForWebComponentCommons by RobertBurrellDonkin
Felipe Leme wrote: I'd like to suggest 2 things: ... 3 Damn, beaten by the ENTER key again :-( - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Jakarta Wiki] Trivial Update of Migrating to Subversion by DanielRall
On Sun, 2005-06-19 at 01:56 +0200, Dean Pickersgill wrote: The following page has been changed by DanielRall: http://wiki.apache.org/jakarta/Migrating_to_Subversion The comment on the change is: wording tweak ... Look, what IS the point of making comments which generate mail which says NOTHING?? 'Wording tweak'. Tells me a lot. Whats wrong with a sensible description that actually means something to the reader? Well Dean, it _was_ a wording tweak, meaning that the actual content didn't change much, merely the verbiage. - Line 12: The CVS repositories of dead projects are not targeted for migration (e.g. jakarta-site). The CVS repositories of dead projects are not targeted for immediate migration (e.g. jakarta-site). - If there's some way to update the change log message, be my guest. Otherwise, you're swinging the signal-to-noise ratio in the wrong direction. I get enough email. Thanks, Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Jakarta Wiki] Update of Migrating to Subversion by DanielRall
I'd like to suggest that your contributions might be more valuable in patch form, but given the quality of your review comments, I'll instead advise a little shut-the-hell-up. On Sun, 2005-06-19 at 01:53 +0200, Dean Pickersgill wrote: The comment on the change is: Noted Velocity completely done. Updated Subversion plan/+'s/questions/-'s ... Obviously not because people are still adding to it ... -- * Every sub-project of Jakarta gets a subdirectory in the Jakarta SVN repo. * They use a tags/trunk/branches structure within said subdirectory, though they could further componentise and then use the tags/trunk/branches structure if it fits them better. - + * The CVS repositories of dead projects are not targeted for migration (e.g. jakarta-site). == Positives == - One major plus is that it simplifies the life of the infrastructure team. They no longer need UNIX accounts for each user, but can maintain users in htaccess files (behind SSL). + Subversion provides many advantages over CVS, smoothing out its excessive character while providing the same approximate level of functionality, and a much better designed platform on which to develop tools. Sampling of improvements over CVS: + * move files within the repository and maintain the history + * delete directories (which are treated no different than any other versioned resource) + * treat groups of files in one commit as a single transaction (change set-like) + * significantly faster branching and tagging - There are many developer pluses too. Subversion gives us the ability to move files within the repository and maintain the history, to treat groups of files in one commit as a single transaction and has faster speed on tagging. + Another major benefit is that administration of Subversion simplifies the life of the Infrastructure team. UNIX accounts need not be created for each user; user accounts are instead maintained in htaccess files, with authentication occuring over SSL. == Questions == - * What do we do with legal issues? If a non-ASF allowed licensed file appears in the repository, can we obliterate it? Is it a problem if we can't? * Is the community's toolset fully supported? - * How do we educate the community? - * Do we need to migrate dead cvs modules? ie) jakarta-site? == Negatives == - * Tagging is just a directory copy. Tags which are more than a simple directory tree get trickier. ie) tagging without tagging all the files, or tagging plus a set of files in a sibling directory. The trick of doing 'cvs status -v build.xml' to list known tags for a module is no longer available as well. - * Installation. An SVN client, especially with SSL support, seems trickier to install than CVS. + * The tagging and branching model varies from that of CVS, and is only a cheap directory copy. Tags which are more than a simple directory tree get trickier. ie) tagging without tagging all the files, or tagging plus a set of files in a sibling directory. The trick of doing 'cvs status -v build.xml' to list known tags for a module is no longer available as well. Instead, the tags/ directory in the repository may be browsed using a 'svn ls' or a [http://svn.apache.org/viewcvs.cgi/ web browser]. + * Obliteration of files which should have never made their way into the VC repository (e.g. files with a non-ASF allowed license) can currently only be accomplished through a dump/edit/load of the entire repository by the Infrastructure team (resulting in a repository-wide maintenance window). == Migration Plan == @@ -39, +40 @@ * POI - Nudged. Is OS X support good enough? amongst other questions. * Slide - Stefan LCtzkendorf. Migration applied for. * Taglibs - Tim O'Brien. Martin Cooper. Renudged. - * Tapestry - Nudged. Is Subclipse good enough? + * Tapestry - Nudged. Is [http://sublicpse.tigris.org/ Subclipse] good enough? * Turbine - Henning Schmiedehausen, Daniel Rall === Archivals === @@ -49, +50 @@ === DONE === * BCEL - Henri Yandell - * BSF - Done. + * BSF - (done) * Commons - Martin Cooper + Tim O'Brien - [http://wiki.apache.org/jakarta-commons/SubversionConversion Conversion Instructions] * ECS - Robert Burell Donkin + Henri Yandell. jakarta-ecs and jakarta-ecs2. - * HiveMind - Done. + * HiveMind - (done) * Lucene- Erik Hatcher - * ORO - Daniel Savarese. + * ORO - Daniel Savarese * Regexp- Henri Yandell * Site2 - Tim O'Brien + Henri Yandell - [Site2 Conversion Instructions] - * Velocity - Needs folding of 3 dirs into 1. Daniel Rall. + * Velocity
RE: [Jakarta Wiki] Update of JakartaBoardReport-June2005 by DanielRall
Oh dear -Original Message- From: Apache Wiki [mailto:[EMAIL PROTECTED] Sent: 18 June 2005 22:30 To: general@jakarta.apache.org Subject: [Jakarta Wiki] Update of JakartaBoardReport-June2005 by DanielRall Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by DanielRall: http://wiki.apache.org/jakarta/JakartaBoardReport-June2005 -- Velocity - Migration from Bugzilla to Jira approved. + Migration from Bugzilla to Jira approved. OSGi bundle submitted. - 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] Update of Migrating to Subversion by DanielRall
The comment on the change is: Noted Velocity completely done. Updated Subversion plan/+'s/questions/-'s ... Obviously not because people are still adding to it ... -- * Every sub-project of Jakarta gets a subdirectory in the Jakarta SVN repo. * They use a tags/trunk/branches structure within said subdirectory, though they could further componentise and then use the tags/trunk/branches structure if it fits them better. - + * The CVS repositories of dead projects are not targeted for migration (e.g. jakarta-site). == Positives == - One major plus is that it simplifies the life of the infrastructure team. They no longer need UNIX accounts for each user, but can maintain users in htaccess files (behind SSL). + Subversion provides many advantages over CVS, smoothing out its excessive character while providing the same approximate level of functionality, and a much better designed platform on which to develop tools. Sampling of improvements over CVS: + * move files within the repository and maintain the history + * delete directories (which are treated no different than any other versioned resource) + * treat groups of files in one commit as a single transaction (change set-like) + * significantly faster branching and tagging - There are many developer pluses too. Subversion gives us the ability to move files within the repository and maintain the history, to treat groups of files in one commit as a single transaction and has faster speed on tagging. + Another major benefit is that administration of Subversion simplifies the life of the Infrastructure team. UNIX accounts need not be created for each user; user accounts are instead maintained in htaccess files, with authentication occuring over SSL. == Questions == - * What do we do with legal issues? If a non-ASF allowed licensed file appears in the repository, can we obliterate it? Is it a problem if we can't? * Is the community's toolset fully supported? - * How do we educate the community? - * Do we need to migrate dead cvs modules? ie) jakarta-site? == Negatives == - * Tagging is just a directory copy. Tags which are more than a simple directory tree get trickier. ie) tagging without tagging all the files, or tagging plus a set of files in a sibling directory. The trick of doing 'cvs status -v build.xml' to list known tags for a module is no longer available as well. - * Installation. An SVN client, especially with SSL support, seems trickier to install than CVS. + * The tagging and branching model varies from that of CVS, and is only a cheap directory copy. Tags which are more than a simple directory tree get trickier. ie) tagging without tagging all the files, or tagging plus a set of files in a sibling directory. The trick of doing 'cvs status -v build.xml' to list known tags for a module is no longer available as well. Instead, the tags/ directory in the repository may be browsed using a 'svn ls' or a [http://svn.apache.org/viewcvs.cgi/ web browser]. + * Obliteration of files which should have never made their way into the VC repository (e.g. files with a non-ASF allowed license) can currently only be accomplished through a dump/edit/load of the entire repository by the Infrastructure team (resulting in a repository-wide maintenance window). == Migration Plan == @@ -39, +40 @@ * POI - Nudged. Is OS X support good enough? amongst other questions. * Slide - Stefan LCtzkendorf. Migration applied for. * Taglibs - Tim O'Brien. Martin Cooper. Renudged. - * Tapestry - Nudged. Is Subclipse good enough? + * Tapestry - Nudged. Is [http://sublicpse.tigris.org/ Subclipse] good enough? * Turbine - Henning Schmiedehausen, Daniel Rall === Archivals === @@ -49, +50 @@ === DONE === * BCEL - Henri Yandell - * BSF - Done. + * BSF - (done) * Commons - Martin Cooper + Tim O'Brien - [http://wiki.apache.org/jakarta-commons/SubversionConversion Conversion Instructions] * ECS - Robert Burell Donkin + Henri Yandell. jakarta-ecs and jakarta-ecs2. - * HiveMind - Done. + * HiveMind - (done) * Lucene- Erik Hatcher - * ORO - Daniel Savarese. + * ORO - Daniel Savarese * Regexp- Henri Yandell * Site2 - Tim O'Brien + Henri Yandell - [Site2 Conversion Instructions] - * Velocity - Needs folding of 3 dirs into 1. Daniel Rall. + * Velocity - Daniel Rall - 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
RE: [Jakarta Wiki] Trivial Update of Migrating to Subversion by DanielRall
The following page has been changed by DanielRall: http://wiki.apache.org/jakarta/Migrating_to_Subversion The comment on the change is: wording tweak ... Look, what IS the point of making comments which generate mail which says NOTHING?? 'Wording tweak'. Tells me a lot. Whats wrong with a sensible description that actually means something to the reader? Deano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Jakarta Wiki] Update of InterWiki by ManikSurtani
I hate to do this as I know this is not an admin list but in the last few days I've started receiving these notifications that the wiki has changed. I haven't subscribed to this list so I'm assuming I was added 'accidentally', how do I get off the list? Kevin Jones http://public.xdi.org/=kevin.jones skype (www.skype.com): kevinrjones -Original Message- From: Apache Wiki [mailto:[EMAIL PROTECTED] Sent: 30 March 2005 23:32 To: Apache Wiki Subject: [Jakarta Wiki] Update of InterWiki by ManikSurtani Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by ManikSurtani: http://wiki.apache.org/jakarta/InterWiki -- List of valid InterWiki names this wiki knows of: [[InterWiki]] - Subprojects under Jakarta that have wiki pages: + Subprojects under Jakarta that do not have wiki sites of their own (under http://wiki.apache.org) but have a few wiki pages under this wiki: JakartaRegexp MoinMoin marks the InterWiki links in a way that works for the MeatBall:ColourBlind and also is MeatBall:LynxFriendly by using a little icon with an ALT attribute. If you hover above the icon in a graphical browser, you'll see to which Wiki it refers. If the icon has a border, that indicates that you used an illegal or unknown BadBadBad:InterWiki name (see the list above for valid ones). BTW, the reasoning behind the icon used is based on the idea that a Wiki:WikiWikiWeb is created by a team effort of several people. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Update of InterWiki by ManikSurtani
What's happened is that the wiki change notifications seem to be sent to a separate list now ([EMAIL PROTECTED]) instead of where they were sent before ([EMAIL PROTECTED]). This has also happened for some (all?) of the other wikis. I'm assuming this change happened as part of the upgrade to the newer wiki version. I've already put in a request to the infrastructure folks to change this back to the way it was. -- Martin Cooper On Wed, 30 Mar 2005 23:48:13 +0100, Kevin Jones [EMAIL PROTECTED] wrote: I hate to do this as I know this is not an admin list but in the last few days I've started receiving these notifications that the wiki has changed. I haven't subscribed to this list so I'm assuming I was added 'accidentally', how do I get off the list? Kevin Jones http://public.xdi.org/=kevin.jones skype (www.skype.com): kevinrjones -Original Message- From: Apache Wiki [mailto:[EMAIL PROTECTED] Sent: 30 March 2005 23:32 To: Apache Wiki Subject: [Jakarta Wiki] Update of InterWiki by ManikSurtani Dear Wiki user, You have subscribed to a wiki page or wiki category on Jakarta Wiki for change notification. The following page has been changed by ManikSurtani: http://wiki.apache.org/jakarta/InterWiki -- List of valid InterWiki names this wiki knows of: [[InterWiki]] - Subprojects under Jakarta that have wiki pages: + Subprojects under Jakarta that do not have wiki sites of their own (under http://wiki.apache.org) but have a few wiki pages under this wiki: JakartaRegexp MoinMoin marks the InterWiki links in a way that works for the MeatBall:ColourBlind and also is MeatBall:LynxFriendly by using a little icon with an ALT attribute. If you hover above the icon in a graphical browser, you'll see to which Wiki it refers. If the icon has a border, that indicates that you used an illegal or unknown BadBadBad:InterWiki name (see the list above for valid ones). BTW, the reasoning behind the icon used is based on the idea that a Wiki:WikiWikiWeb is created by a team effort of several people. - 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] New: ApacheBranding
What's the filtering criteria? Is it a comprehensive list or just some of the Jakarta projects? I only ask because Velocity is missing. WILL - Original Message - From: general@jakarta.apache.org To: general@jakarta.apache.org Sent: Tuesday, March 01, 2005 9:45 PM Subject: [Jakarta Wiki] New: ApacheBranding Date: 2005-03-01T21:45:26 Editor: HenriYandell Wiki: Jakarta Wiki Page: ApacheBranding URL: http://wiki.apache.org/jakarta/ApacheBranding no comment New Page: Scratchpad to create a list of suggested Apache brands to send to the PRC mailing list. * Apache Ant * Apache APR * Apache Axis * Apache Beehive * Apache Cocoon * Apache Forrest * Apache Gump * Apache HTTPD * Apache Incubator * Apache Infrastructure * Apache Jackrabbit * Apache Jakarta Commons * Jakarta Commons Xxx * Apache Excalibur * Apache Jakarta Slide * Apache Jakarta BCEL * Apache Jakarta Cactus * Apache Jakarta Hivemind * Apache Jakarta Taglibs * Apache Jakarta Tapestry * Apache Jakarta Turbine * Apache Lenya * Apache Lucene * Apache Maven * Apache Maven Plugins * Apache Nutch * Apache Tomcat * Apache Web Services * Apache WSS4J * Apache Xerces * Apache Xalan * Apache XML Xxxx * Apache OJB - 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] New: ApacheBranding
Just a list that JetBrains sent me with a request for the correct terms; it's mainly a temporary page so I could send something over to the PRC asking about branding and didn't want to sit and do it in html because that would have taken all of 5 minutes more :) The question is a good one though, what are the preferred names for each one etc. Hen On Wed, 2 Mar 2005, Will Glass-Husain wrote: What's the filtering criteria? Is it a comprehensive list or just some of the Jakarta projects? I only ask because Velocity is missing. WILL - Original Message - From: general@jakarta.apache.org To: general@jakarta.apache.org Sent: Tuesday, March 01, 2005 9:45 PM Subject: [Jakarta Wiki] New: ApacheBranding Date: 2005-03-01T21:45:26 Editor: HenriYandell Wiki: Jakarta Wiki Page: ApacheBranding URL: http://wiki.apache.org/jakarta/ApacheBranding no comment New Page: Scratchpad to create a list of suggested Apache brands to send to the PRC mailing list. * Apache Ant * Apache APR * Apache Axis * Apache Beehive * Apache Cocoon * Apache Forrest * Apache Gump * Apache HTTPD * Apache Incubator * Apache Infrastructure * Apache Jackrabbit * Apache Jakarta Commons * Jakarta Commons Xxx * Apache Excalibur * Apache Jakarta Slide * Apache Jakarta BCEL * Apache Jakarta Cactus * Apache Jakarta Hivemind * Apache Jakarta Taglibs * Apache Jakarta Tapestry * Apache Jakarta Turbine * Apache Lenya * Apache Lucene * Apache Maven * Apache Maven Plugins * Apache Nutch * Apache Tomcat * Apache Web Services * Apache WSS4J * Apache Xerces * Apache Xalan * Apache XML Xxxx * Apache OJB - 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]
Re: [Jakarta Wiki] Updated: JakartaBoardReport-December2004
On 24 Nov 2004, at 23:42, Daniel Rall wrote: On Sun, 2004-11-21 at 21:39 +, robert burrell donkin wrote: On 19 Nov 2004, at 21:19, [EMAIL PROTECTED] wrote: snip - -- --- @@ -2,7 +2,7 @@ === Status === - * ECS and ORO migrated to SVN. + * ECS, ORO, and the Velocity modules migrated to SVN. * Clover license for all of ASF. i haven't migrated ECS yet. i could probably make a start on it soon enough to have it done before the report goes to the board. That's the thing about statements like this one (albeit accidental in this case); even if they weren't true when you made'em, they often end up becoming true. ;-) But in all seriousness, let me know if that should be removed. though i'll start looking into it sometime soonish, i'm not sure whether it could be done in time now. probably wiser to take it off the list. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Subproject reports Was: [Jakarta Wiki] Updated: JakartaBoardReport-December2004
On Wed, 24 Nov 2004, Daniel Rall wrote: On Sun, 2004-11-21 at 21:40 +, robert burrell donkin wrote: On 16 Nov 2004, at 17:58, [EMAIL PROTECTED] wrote: snip @@ -27,3 +49,11 @@ === Subproject news === (** implies report based on the mailing lists by the chair) + +(These projects need to provide a status) + + * Commons Betwixt + * Commons HttpClient + * Tapestry + * Tomcat + * Turbine what sort of thing's needed...? I was wondering the same. Is there a PMC status reporting template somewhere? Sorry for slowness in replying; s'been top of the todo list. I've not had feedback that previous reports from subprojects were bad, just that our last report was lacking reports for subprojects who had obviously done things (by releasing code) and the suggestion that a release should imply a subproject report on the Jakarta report; which makes sense to me. Previous reports seem to give a good set of topics. New committers should already be listed above, but information on future plans, reasons for the new releases, death of project (Watchdog), new pieces of work are all of interest. Examples would be: HttpClient have released a bugfix (2.0.2) and are in the last steps of releasing an alpha of (3.0). Upon the release of 3.0, we plan to leave the Commons and become a Jakarta subproject, extending the scope of HttpClient to dadadada Notes about responses to Tomcat security issues are probably of a lot of interest. Releases that fix those etc. Slide's thoughts on becoming a TLP, though that'll be in my status notes as it was on the pmc/general list. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subproject reports Was: [Jakarta Wiki] Updated: JakartaBoardReport-December2004
On 25 Nov 2004, at 20:48, Henri Yandell wrote: snip HttpClient have released a bugfix (2.0.2) and are in the last steps of releasing an alpha of (3.0). Upon the release of 3.0, we plan to leave the Commons and become a Jakarta subproject, extending the scope of HttpClient to dadadada i've added something about betwixt. one thing does strike: betwixt really isn't a subproject. httpclient is a subproject in waiting but maybe there are developments in the commons (for example, the promotion of email and transaction) that are probably of more interest. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subproject reports Was: [Jakarta Wiki] Updated: JakartaBoardReport-December2004
On Thu, 25 Nov 2004, robert burrell donkin wrote: On 25 Nov 2004, at 20:48, Henri Yandell wrote: snip HttpClient have released a bugfix (2.0.2) and are in the last steps of releasing an alpha of (3.0). Upon the release of 3.0, we plan to leave the Commons and become a Jakarta subproject, extending the scope of HttpClient to dadadada i've added something about betwixt. one thing does strike: betwixt really isn't a subproject. httpclient is a subproject in waiting but maybe there are developments in the commons (for example, the promotion of email and transaction) that are probably of more interest. Good point. Promotion from sandbox-proper is hereby cause for inclusion in the report :) The betwixt release is still of interest, just there are other things beside a release which are of interest. Off to in-laws. Will add to wiki and let people on the Commons list know later. Same thing should apply for Taglibs too, will check what's going on there recently. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Subproject reports Was: [Jakarta Wiki] Updated: JakartaBoardReport-December2004
On 25 Nov 2004, at 21:56, Henri Yandell wrote: On Thu, 25 Nov 2004, robert burrell donkin wrote: On 25 Nov 2004, at 20:48, Henri Yandell wrote: snip one thing does strike: betwixt really isn't a subproject. httpclient is a subproject in waiting but maybe there are developments in the commons (for example, the promotion of email and transaction) that are probably of more interest. Good point. Promotion from sandbox-proper is hereby cause for inclusion in the report :) The betwixt release is still of interest, just there are other things beside a release which are of interest. +1 perhaps occasions where oversight have been demonstrated (thinking of the email and transaction licensing matters just dealt with) would help to reassure the board. hopefully, if some other people jump in here with other ideas, we might be able to pull a good list together... Off to in-laws. Will add to wiki and let people on the Commons list know later. Same thing should apply for Taglibs too, will check what's going on there recently. don't stay out too late ;) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Updated: JakartaBoardReport-December2004
On Sun, 2004-11-21 at 21:40 +, robert burrell donkin wrote: On 16 Nov 2004, at 17:58, [EMAIL PROTECTED] wrote: snip @@ -27,3 +49,11 @@ === Subproject news === (** implies report based on the mailing lists by the chair) + +(These projects need to provide a status) + + * Commons Betwixt + * Commons HttpClient + * Tapestry + * Tomcat + * Turbine what sort of thing's needed...? I was wondering the same. Is there a PMC status reporting template somewhere? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Updated: JakartaBoardReport-December2004
On Sun, 2004-11-21 at 21:39 +, robert burrell donkin wrote: On 19 Nov 2004, at 21:19, [EMAIL PROTECTED] wrote: snip --- --- @@ -2,7 +2,7 @@ === Status === - * ECS and ORO migrated to SVN. + * ECS, ORO, and the Velocity modules migrated to SVN. * Clover license for all of ASF. i haven't migrated ECS yet. i could probably make a start on it soon enough to have it done before the report goes to the board. That's the thing about statements like this one (albeit accidental in this case); even if they weren't true when you made'em, they often end up becoming true. ;-) But in all seriousness, let me know if that should be removed. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Updated: JakartaBoardReport-December2004
On 19 Nov 2004, at 21:19, [EMAIL PROTECTED] wrote: snip --- --- @@ -2,7 +2,7 @@ === Status === - * ECS and ORO migrated to SVN. + * ECS, ORO, and the Velocity modules migrated to SVN. * Clover license for all of ASF. i haven't migrated ECS yet. i could probably make a start on it soon enough to have it done before the report goes to the board. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Updated: JakartaBoardReport-December2004
On 16 Nov 2004, at 17:58, [EMAIL PROTECTED] wrote: snip @@ -27,3 +49,11 @@ === Subproject news === (** implies report based on the mailing lists by the chair) + +(These projects need to provide a status) + + * Commons Betwixt + * Commons HttpClient + * Tapestry + * Tomcat + * Turbine what sort of thing's needed...? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN of ECS Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
On 24 Sep 2004, at 10:48, Henning Schmiedehausen wrote: I think that Robert is the best person to answer this. He is the main responsibe developer of ECS. ;-) developer implies ongoing development. minder would be more appropriate ;) ECS is still used in many production systems and solves the problems it addresses adequately but the questions have moved on since them. i'm still subscribed to the lists but my interests have lain elsewhere for several years now. On Tue, 2004-09-21 at 22:56, Henri Yandell wrote: +Robert Burrel Donkin has volunteered to migrate ECS over to SVN as a trial migration. it went a bit quiet after i made this offer. if there's interest, i'd be willing to push this forward again. Well, do we know who would be the one to accept the offer? As far as I know, ECS doesn't really have a champion anymore. I'd vote for Robert here. i'm not sure i parse this exchange properly. what's certainly true is that ECS has no committers on the pmc. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN of ECS Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
I think that Robert is the best person to answer this. He is the main responsibe developer of ECS. ;-) On Tue, 2004-09-21 at 22:56, Henri Yandell wrote: +Robert Burrel Donkin has volunteered to migrate ECS over to SVN as a trial migration. it went a bit quiet after i made this offer. if there's interest, i'd be willing to push this forward again. Well, do we know who would be the one to accept the offer? As far as I know, ECS doesn't really have a champion anymore. I'd vote for Robert here. It seems that the community in general would need to answer: 1) Should we goto SVN (likely to be a big problem if we say no)? Yes. Up to the projects to decide when they move. E.g. I hope to use the CVS-SVN move for Turbine as a cleaning move for the project to reduce the huge number of turbine CVS repositories. 2) Should inactive projects (ECS, Watchdog, ...) goto SVN? If they find someone that maintains them: yes. 3) Any reason why ECS should not be the first to go? No. +1 Go ahead. :-) Regards Henning -- Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH [EMAIL PROTECTED]+49 9131 50 654 0 http://www.intermeta.de/ RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire Linux, Java, perl, Solaris -- Consulting, Training, Development Fighting for one's political stand is an honorable action, but re- fusing to acknowledge that there might be weaknesses in one's position - in order to identify them so that they can be remedied - is a large enough problem with the Open Source movement that it deserves to be on this list of the top five problems. --Michelle Levesque, Fundamental Issues with Open Source Software Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN of ECS Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
In message [EMAIL PROTECTED], Noel J. Bergman w rites: Done. Thanks Noel! I know these things are normally supposed to go through infrastructure, but I thought I could test it out in the test repository without troubling anyone first. Everything looks good and doing the conversion even helped me detect that at some point I'd checked in html files for the Web site that had literal character values instead of character entities like #169; in them. I can regenerate those and check them in the next time there's a release. At any rate, if Henri wants a guinea pig, he can send infrastructure a formal request to convert jakarta-oro over to SVN. The default cvs2svn values are fine. e.g., cvs2svn -v --dump-only --dumpfile=oro.svn.dump /home/cvs/jakarta-oro/ svn mkdir https://svn.apache.org/repos/asf/jakarta/oro/ svnadmin load --parent-dir jakarta/oro /x1/svn/asf oro.svn.dump Why oro instead of ECS? Only because I jumped the gun with Noel's help and tested the svn conversion. ECS can always go next. daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN of ECS Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
In message [EMAIL PROTECTED], Henri Yandell writes: Well, do we know who would be the one to accept the offer? I made a dump of jakarta-oro in ~dfs/pub/oro.svn.dump. I can't do svnadmin load --parent-dir jakarta-oro /x1/svn/test oro.svn.dump because you need to be in the svnadmin group. If someone with appropriate access wants to do the load feel free. I think it's better to move to svn sooner rather than later. daniel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: SVN of ECS Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
Daniel F. Savarese wrote: If someone with appropriate access wants to do the load feel free. Done. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
On 21 Sep 2004, at 01:50, [EMAIL PROTECTED] wrote: +(Has been sent to the board. Please do not edit.) oops didn't read this properly. sorry. (it's a pity that there isn't some way to lock down pages in the wiki once they've been created. or maybe we just need an wiki-anakia scraper so that the product can be recorded in cvs.) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
On 21 Sep 2004, at 01:39, [EMAIL PROTECTED] wrote: snip +Robert Burrel Donkin has volunteered to migrate ECS over to SVN as a trial migration. it went a bit quiet after i made this offer. if there's interest, i'd be willing to push this forward again. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SVN of ECS Re: [Jakarta Wiki] Updated: JakartaBoardReport-September2004
+Robert Burrel Donkin has volunteered to migrate ECS over to SVN as a trial migration. it went a bit quiet after i made this offer. if there's interest, i'd be willing to push this forward again. Well, do we know who would be the one to accept the offer? As far as I know, ECS doesn't really have a champion anymore. It seems that the community in general would need to answer: 1) Should we goto SVN (likely to be a big problem if we say no)? 2) Should inactive projects (ECS, Watchdog, ...) goto SVN? 3) Any reason why ECS should not be the first to go? My answers being: 1) Yes. I'm not the hugest fan of SVN, but my pains with it are largely server-side. I think we'll adapt to the different style of tagging, and the client-support is/will be good enough. 2) Yes, as they're not dead. 3) I can't see any. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Overrode an entry Was: [Jakarta Wiki] Updated: JakartaReport-July2004
Apologies for this Gary, but I think you won't mind. Release news goes higher up, so when Commons Codec is out, it can just appear at the top. It's not a big deal as it's very easy for me to collate the releases from the front page. I'm also aiming to only have subprojects listed (HttpClient will be a subproject soon I think), so Commons bits under the Commons section. Hen On Wed, 14 Jul 2004 [EMAIL PROTECTED] wrote: Date: 2004-07-14T11:16:10 Editor: GaryGregory [EMAIL PROTECTED] Wiki: Jakarta Wiki Page: JakartaReport-July2004 URL: http://wiki.apache.org/jakarta/JakartaReport-July2004 no comment Change Log: -- @@ -24,6 +24,10 @@ Commons HttpClient + Commons Codec + +The vote to release version 1.3 has passed. Gary Gregory is currently going through the signing and publish process. + ECS HiveMind - 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: Overrode an entry Was: [Jakarta Wiki] Updated: JakartaReport-July2004
No problem, I did not really know where to put it, so I placed the item
near another Commons one.
Gary
-Original Message-
From: Henri Yandell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 14, 2004 13:00
To: Verwaltung
Cc: Gary Gregory
Subject: Overrode an entry Was: [Jakarta Wiki] Updated: JakartaReport-
July2004
Apologies for this Gary, but I think you won't mind.
Release news goes higher up, so when Commons Codec is out, it can just
appear at the top. It's not a big deal as it's very easy for me to
collate
the releases from the front page.
I'm also aiming to only have subprojects listed (HttpClient will be a
subproject soon I think), so Commons bits under the Commons section.
Hen
On Wed, 14 Jul 2004 [EMAIL PROTECTED] wrote:
Date: 2004-07-14T11:16:10
Editor: GaryGregory [EMAIL PROTECTED]
Wiki: Jakarta Wiki
Page: JakartaReport-July2004
URL: http://wiki.apache.org/jakarta/JakartaReport-July2004
no comment
Change Log:
--
@@ -24,6 +24,10 @@
Commons HttpClient
+ Commons Codec
+
+The vote to release version 1.3 has passed. Gary Gregory is
currently
going through the signing and publish process.
+
ECS
HiveMind
-
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]
Re: [Jakarta Wiki] Updated: JakartaPMC
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
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
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: [Jakarta Wiki] Updated: JakartaPMC
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: [Jakarta Wiki] New: WikiBrazil
Could someone check this ? I cannot read that too well :).
To whomever is doing this: it is best to login, so we can see who did
this..
And is this specific to Brazil ? Or is this also readable by all
Portugese speakers ?
Mvgr,
Martin
On Mon, 2004-07-05 at 14:05, [EMAIL PROTECTED] wrote:
Date: 2004-07-05T05:05:26
Editor: 143.106.2.61
Wiki: Jakarta Wiki
Page: WikiBrazil
URL: http://wiki.apache.org/jakarta/WikiBrazil
no comment
New Page:
b[[Apache Software Foundation]] Wiki/b -- An experiment in emergence of
documentation. [http://nagoya.apache.org/wiki/apachewiki.cgi?action=rss RSS]
[HomePageDiscussion Talk Page]
---
http://jakarta.apache.org/images/logos/ac2003-150.gif --
http://apachecon.com/2003/US/index.html
=== Seja bem vindo, o futuro é amanhã. Obrigado por colaborar! ===
Entre aqui para conseguir [[ Motivacao ]].
* '''Apache Wiki'''- Edição simplificada de documentos.
** [http://www.usemod.com/cgi-bin/wiki.pl?RegrasFormatacaoTexto Regras de
Formatação de Texto] para este Wiki.
** ApacheNewsletterDrafts
** SandBox - é a caixa-de-areia onde você experimenta seus dons artísticos de
criação usando o ApacheWiki
** FrequentlyAskedQuestions sobre o Apache de uma forma geral e sobre o OpenSource.
** WhatsA (glossário)
** [http://nagoya.apache.org/wiki/apachewiki.cgi?action=index Indice geral]
** O que é wiki? Veja ApacheWiki. (incluindo Wiki baseado em FAQs.)
** [[WikiAdmin]]s - Aqueles que tem o poder , mas o usam raramente.
** ApacheWikiHistory - História deste wiki
* '''ASFProjects''' - Projetos da Fundação de Software Apache
** [http://apr.apache.org/ APR] - Ambiente de execução portável da Apache
** [http://commons.apache.org/ Commons] - Projeto de objetos comuns da apache . O
projeto comum da Apache não é o mesmo que o projeto comum da Jakarta. O ''Jakarta
Commons'' é somente disponível para componentes escritos em java, enquanto que o
''Apache Commons Project'' tem o objetivo de hospedar componentes para qualquer
linguagem. Adicionalmente, o ''Apache Commons'' é um projeto de topo de linha da
Fundação de Software Apache, isto significa que ele deve responder diretamente a
Diretoria em vez de a outros PMCs.
** [http://httpd.apache.org/ HTTP Server Project] - O Projeto do Servidor de HTTP da
Apache é um esforço para desenvolver e manter um servido HTTP de código-livre
para os modernos sistemas operacionais incluindo UNIX e Windows NT. O objetivo deste
projeto é fornecer um servidor seguro, eficiente e extensível que forneça
serviços de HTTP em sincronia com os padrões de HTTP atuais.
** [http://httpd.apache.org/docs-project/ HTTP Server Documentation Project] - O
projeto de documentação é um esforço para manter e melhorar a qualidade da
documentação incluída com o servidor de HTTP da Apache. A participação é
aberta a qualquer pessoa com tempo disponível, com conhecimentos mínimos sobre
HTML e sobre o servidor de HTTP da Apache. Não é necessário saber programar,
desta forma é uma boa oportunidade para aqueles que não sabem programar para
contribuir com o sucesso da Apache, e ter os seus trabalhos lidos por milhões de
usuários Apache.
** AntProjectPages - [http://ant.apache.org/ página do projeto] - o ''Apache Ant''
é uma ferramenta java para compilar um conjunto de aplicações que comporão um
projeto, de forma automatizada, sem a necessidade de fazer várias chamadas ao
compilador e a mecanismos de movimentação de arquivos a toda hora.
** AvalonProjectPages - o ''Apache Avalon'' fornece uma plataforma completa para
programação de componentes incluindo uma área de trabalho, utilitários,
ferramentas, componentes e compartimentos de aplicações(''containers''). Usando
padrões de criações chaves como a Inversão do Controle (IoC) e Separação das
Responsabilidade (SoC), o ''Avalon'' atinge um grande número de vantagens sobre a
tradicional forma de programação orientada a objetos.
** [[Incubator]] - O projeto incubador foi criado em outubro de 2002 para fornecer
caminhos de entrada para a Fundação de Software da Apache para projetos e bases de
códigos que desejam ser parte dos esforços da fundação. A doação de código de
organizações externas e projetos externos que querem migrar-se para a Apache irão
entrar através do ''Incubator''.
*** ApacheIncubatorProjectPages
** CocoonProjectPages - O projeto Cocoon é um framework de desenvolvimento web
construído em torno de conceitos de separação das responsabilidade e é baseado
em desenvolvimento de componentes. Ele é um ambiente de trabalho XML que aumenta o
uso das tecnologias XML e XSLT para as aplicações de servidores para novos
níveis. Criado para ter perfomance e escalabilidade em torno do processamento de
blocos SAX de informações.
** [http://wiki.apache.org/db DBProjectPages] - o projeto ''DB'' é encarregado pela
criação e manutenção de soluções de
Re: [Jakarta Wiki] New: WikiBrazil
Yep, would be good to know who's been adding it (though not that many
obvious brazillian names on the list, so might be easy to guess :) ).
Seems a bit odd to me. It looks like Apache Brazil and not Jakarta Brazil.
Very little there about Jakarta.
Apparantly the top line is:
Either welcome, the future is tomorrow. Debtor for collaborating!
Gotta love online translators :)
Anyway, the fact it's not about Jakarta is a worry for me. We should talk
to infrastructure about organizing localised content on the main Wiki.
Hen
On Mon, 5 Jul 2004, Martin van den Bemt wrote:
Could someone check this ? I cannot read that too well :).
To whomever is doing this: it is best to login, so we can see who did
this..
And is this specific to Brazil ? Or is this also readable by all
Portugese speakers ?
Mvgr,
Martin
On Mon, 2004-07-05 at 14:05, [EMAIL PROTECTED] wrote:
Date: 2004-07-05T05:05:26
Editor: 143.106.2.61
Wiki: Jakarta Wiki
Page: WikiBrazil
URL: http://wiki.apache.org/jakarta/WikiBrazil
no comment
New Page:
b[[Apache Software Foundation]] Wiki/b -- An experiment in emergence of
documentation. [http://nagoya.apache.org/wiki/apachewiki.cgi?action=rss RSS]
[HomePageDiscussion Talk Page]
---
http://jakarta.apache.org/images/logos/ac2003-150.gif --
http://apachecon.com/2003/US/index.html
=== Seja bem vindo, o futuro é amanhã. Obrigado por colaborar! ===
Entre aqui para conseguir [[ Motivacao ]].
* '''Apache Wiki'''- Edição simplificada de documentos.
** [http://www.usemod.com/cgi-bin/wiki.pl?RegrasFormatacaoTexto Regras de
Formatação de Texto] para este Wiki.
** ApacheNewsletterDrafts
** SandBox - é a caixa-de-areia onde você experimenta seus dons artísticos de
criação usando o ApacheWiki
** FrequentlyAskedQuestions sobre o Apache de uma forma geral e sobre o OpenSource.
** WhatsA (glossário)
** [http://nagoya.apache.org/wiki/apachewiki.cgi?action=index Indice geral]
** O que é wiki? Veja ApacheWiki. (incluindo Wiki baseado em FAQs.)
** [[WikiAdmin]]s - Aqueles que tem o poder , mas o usam raramente.
** ApacheWikiHistory - História deste wiki
* '''ASFProjects''' - Projetos da Fundação de Software Apache
** [http://apr.apache.org/ APR] - Ambiente de execução portável da Apache
** [http://commons.apache.org/ Commons] - Projeto de objetos comuns da apache . O
projeto comum da Apache não é o mesmo que o projeto comum da Jakarta. O
''Jakarta Commons'' é somente disponível para componentes escritos em java,
enquanto que o ''Apache Commons Project'' tem o objetivo de hospedar componentes
para qualquer linguagem. Adicionalmente, o ''Apache Commons'' é um projeto de
topo de linha da Fundação de Software Apache, isto significa que ele deve
responder diretamente a Diretoria em vez de a outros PMCs.
** [http://httpd.apache.org/ HTTP Server Project] - O Projeto do Servidor de HTTP
da Apache é um esforço para desenvolver e manter um servido HTTP de
código-livre para os modernos sistemas operacionais incluindo UNIX e Windows NT.
O objetivo deste projeto é fornecer um servidor seguro, eficiente e extensível
que forneça serviços de HTTP em sincronia com os padrões de HTTP atuais.
** [http://httpd.apache.org/docs-project/ HTTP Server Documentation Project] - O
projeto de documentação é um esforço para manter e melhorar a qualidade da
documentação incluída com o servidor de HTTP da Apache. A participação é
aberta a qualquer pessoa com tempo disponível, com conhecimentos mínimos sobre
HTML e sobre o servidor de HTTP da Apache. Não é necessário saber programar,
desta forma é uma boa oportunidade para aqueles que não sabem programar para
contribuir com o sucesso da Apache, e ter os seus trabalhos lidos por milhões de
usuários Apache.
** AntProjectPages - [http://ant.apache.org/ página do projeto] - o ''Apache
Ant'' é uma ferramenta java para compilar um conjunto de aplicações que
comporão um projeto, de forma automatizada, sem a necessidade de fazer várias
chamadas ao compilador e a mecanismos de movimentação de arquivos a toda hora.
** AvalonProjectPages - o ''Apache Avalon'' fornece uma plataforma completa para
programação de componentes incluindo uma área de trabalho, utilitários,
ferramentas, componentes e compartimentos de aplicações(''containers''). Usando
padrões de criações chaves como a Inversão do Controle (IoC) e Separação das
Responsabilidade (SoC), o ''Avalon'' atinge um grande número de vantagens sobre a
tradicional forma de programação orientada a objetos.
** [[Incubator]] - O projeto incubador foi criado em outubro de 2002 para fornecer
caminhos de entrada para a Fundação de Software da Apache para projetos e bases
de códigos que desejam ser parte dos esforços da fundação. A doação de
código de organizações externas e projetos externos que querem migrar-se
Re: [Jakarta Wiki] Updated: Motivacao
Understand you read/understand some Portugese ? Maybe translation spam bots have seen the light ? mvgr, Martin On Mon, 2004-07-05 at 18:37, Henri Yandell wrote: Doing an automatic translation on this page yields complete crap. Random gibberings of the insane (reminds me of the book I just read, the author's persona within the book is of a man who mistakenly believes he is pretending to be insane to avoid the murder of his mother-in-law). Going to give it a little while to see if anyone admits to it, else will delete it. Hen On Mon, 5 Jul 2004 [EMAIL PROTECTED] wrote: Date: 2004-07-05T08:05:17 Editor: 143.106.2.61 Wiki: Jakarta Wiki Page: Motivacao URL: http://wiki.apache.org/jakarta/Motivacao no comment Change Log: -- @@ -9,7 +9,8 @@ Toda ao memorvel na histria do mundo um triunfo do entusiasmo. Nada grande foi conseguido sem isto, porque isto proporciona desafios deixando o tempo bem ocupado, no importando o quo assustador ou difcil, proporcionando um novo significado. Sem entusiasmo voc est domesticado a uma vida de mediocridade, mas com entusiasmo voc pode realizar milagres. Sempre faa o melhor que puder. O que voc planta agora, voc ir colher depois. -Tome conscincia que a verdadeira felicidade mora dentro de voc. No desperdice tempo e esforo procurando por paz, contentamento e diverso no mundo exterior. Lembre que no h felicidade verdadeira em ter ou receber, mas apenas em dar. Estenda a mo. Compartilhe. Sorria. Abrace. Felicidade um perfume que voc no pode pulverizar nos outros sem conseguir uns respingos em voc mesmo. + + Tome conscincia que a verdadeira felicidade mora dentro de voc. No desperdice tempo e esforo procurando por paz, contentamento e diverso no mundo exterior. Lembre que no h felicidade verdadeira em ter ou receber, mas apenas em dar. Estenda a mo. Compartilhe. Sorria. Abrace. Felicidade um perfume que voc no pode pulverizar nos outros sem conseguir uns respingos em voc mesmo. Aprecie e de valor ao amor que voc recebeu at agora. Este amor ir sobreviver at muito depois que seu ouro e sua sade forem embora. - 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] -- Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Jakarta Wiki] Updated: Motivacao
No, I'm just copying and pasting it into a portuguese-english online translator and expecting it to be vaguely about computers, Java and Apache. I go to act now. I go to act now. I go to act now. Daqui in ahead, I go to repeat these words each hour, each day, all day It continues in much the same tradition and is hard to imagine being Apache-based. http://www.systranlinks.com/systran/cgi I've removed it (it's always in the audit trail) until someone pipes up about it. Hen On Mon, 5 Jul 2004, Martin van den Bemt wrote: Understand you read/understand some Portugese ? Maybe translation spam bots have seen the light ? mvgr, Martin On Mon, 2004-07-05 at 18:37, Henri Yandell wrote: Doing an automatic translation on this page yields complete crap. Random gibberings of the insane (reminds me of the book I just read, the author's persona within the book is of a man who mistakenly believes he is pretending to be insane to avoid the murder of his mother-in-law). Going to give it a little while to see if anyone admits to it, else will delete it. Hen On Mon, 5 Jul 2004 [EMAIL PROTECTED] wrote: Date: 2004-07-05T08:05:17 Editor: 143.106.2.61 Wiki: Jakarta Wiki Page: Motivacao URL: http://wiki.apache.org/jakarta/Motivacao no comment Change Log: -- @@ -9,7 +9,8 @@ Toda ao memorvel na histria do mundo um triunfo do entusiasmo. Nada grande foi conseguido sem isto, porque isto proporciona desafios deixando o tempo bem ocupado, no importando o quo assustador ou difcil, proporcionando um novo significado. Sem entusiasmo voc est domesticado a uma vida de mediocridade, mas com entusiasmo voc pode realizar milagres. Sempre faa o melhor que puder. O que voc planta agora, voc ir colher depois. -Tome conscincia que a verdadeira felicidade mora dentro de voc. No desperdice tempo e esforo procurando por paz, contentamento e diverso no mundo exterior. Lembre que no h felicidade verdadeira em ter ou receber, mas apenas em dar. Estenda a mo. Compartilhe. Sorria. Abrace. Felicidade um perfume que voc no pode pulverizar nos outros sem conseguir uns respingos em voc mesmo. + + Tome conscincia que a verdadeira felicidade mora dentro de voc. No desperdice tempo e esforo procurando por paz, contentamento e diverso no mundo exterior. Lembre que no h felicidade verdadeira em ter ou receber, mas apenas em dar. Estenda a mo. Compartilhe. Sorria. Abrace. Felicidade um perfume que voc no pode pulverizar nos outros sem conseguir uns respingos em voc mesmo. Aprecie e de valor ao amor que voc recebeu at agora. Este amor ir sobreviver at muito depois que seu ouro e sua sade forem embora. - 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] -- Mvgr, Martin - 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: Motivacao
I've deleted it. This is one way to delete pages: Login cd /www/wiki.apache.org/data/jakarta/data/text rm Motivacao S. - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 06, 2004 12:14 AM Subject: [Jakarta Wiki] Updated: Motivacao Date: 2004-07-05T16:14:16 Editor: HenriYandell [EMAIL PROTECTED] Wiki: Jakarta Wiki Page: Motivacao URL: http://wiki.apache.org/jakarta/Motivacao Emptying seems to not delete. Need to put some junk in it. Change Log: -- @@ -1,21 +1 @@ -Eu vou agir agora. Eu vou agir agora. Eu vou agir agora. Daqui em diante, eu vou repetir estas palavras cada hora, cada dia, todo dia, até que estas palavras se tornem hábitos como minha respiração, e a ação que irá seguir se tornem tão instintivas como o brilho dos meus olhos. Com estas palavras eu posso condicionar minha mente para executar toda ação necessária para meu sucesso. Eu vou agir agora. Eu vou repetir estas palavras novamente e novamente e novamente. Eu vou caminhar onde o erro tem medo de caminhar. Eu vou trabalhar quando o erro procurar descanso. Eu vou agir agora, pois agora é tudo que eu tenho. Amanhã é o dia reservado para o trabalho do preguiçoso. Eu não sou preguiçoso. Amanhã é o dia que o erro irá acontecer. Eu não sou um fracassado.Eu vou agir agora. O sucesso não irá esperar. Se eu esperar, o sucesso irá se tornar inclinado para outro e perdido a mim para sempre. Esta é a hora. Este é o lugar. Eu sou a pessoa. - -Não há melhor coisa que a adversidade. Cada prejuízo, cada coração partido, cada perda, contém suas próprias sementes, suas próprias lições em como melhorar meu modo de agir a próxima vez. - -A criatura mais fraca vivente, concentrando sua força num simples objeto, pode realizar bons resultados, enquanto que a mais forte, por dispersar seus esforços em muitas tarefas, pode falhar em realizar tudo. Gotas de água, caindo continuamente, perfuram passagens através das rochas mais duras, enquanto que monstruosas torrentes que passam apressadas sobre as rochas com impetuoso alvoroço não deixam vestígios atrás. - -Nunca permita que as pessoas façam chuva em seu território e lancem mortalhas de escuridão e acabem com todo o seu dia. Lembre que não há talento, não há auto-comiseração, não há raciocínio, não há caráter como pré-requisitos para construir um negócio errado. Nada exterior pode ter poder sobre você, a não ser que você permita isto. Seu tempo é muito precioso para ser sacrificado em dias perdidos combatendo as forças serventes do ódio, do ciúmes, e da inveja. Proteja sua frágil vida com cuidado. Apenas Deus pode dar forma a uma flor, mas qualquer criança tola pode despedaçá-la em partes. - -Toda ação memorável na história do mundo é um triunfo do entusiasmo. Nada grande foi conseguido sem isto, porque isto proporciona desafios deixando o tempo bem ocupado, não importando o quão assustador ou difícil, proporcionando um novo significado. Sem entusiasmo você está domesticado a uma vida de mediocridade, mas com entusiasmo você pode realizar milagres. - -Sempre faça o melhor que puder. O que você planta agora, você irá colher depois. - -Tome consciência que a verdadeira felicidade mora dentro de você. Não desperdice tempo e esforço procurando por paz, contentamento e diversão no mundo exterior. Lembre que não há felicidade verdadeira em ter ou receber, mas apenas em dar. Estenda a mão. Compartilhe. Sorria. Abrace. Felicidade é um perfume que você não pode pulverizar nos outros sem conseguir uns respingos em você mesmo. - -Aprecie e de valor ao amor que você recebeu até agora. Este amor irá sobreviver até muito depois que seu ouro e sua saúde forem embora. - -Obstáculos são necessários e importantes para se atingir o sucesso, as vitórias nos empreendimentos vêm somente depois de muitos esforços e incontáveis perdas. Cada esforço e cada perda possibilitam moldar suas habilidades e sua confiança. Assim cada obstáculo é um irmão de sangue forçando você a se tornar melhor... ou desistir. Cada retrocesso é uma oportunidade para mover para frente; livre-se deles, evite eles, e você lança longe seu futuro. - -Nunca misture novamente seus dias ou noites com tanto trabalho serviçal e coisas sem importância que você não tem tempo para aceitar um desafio real quando isto aparece ao acaso. Isto se refere tanto a jogar bem como trabalhar. Um dia meramente vivido não é motivo de celebração. Você não está aqui para desperdiçar suas preciosas horas quando você tem a habilidade para realizar tanto, apenas fazendo uma leve mudança em sua rotina. Nunca mais trabalhe apressado. Nunca mais se esconda do sucesso. Deixe tempo, deixe espaço para crescer. Agora. Agora! Não amanhã! - -O sucesso é o único caminho correto para produzir mais e sevir melhor em relação ao que é esperado de você, não importa o tipo de tarefa. +-deadpage
Re: ACTION not WORDS Re: A Jakarta wiki?
I was merely asking if anyone had given a thought to the question of legal issues and how they relate to Wiki + ASF. I think that it is a reasonable question, and I was surprised that no one had raised this issue. Audit trail...? The same issues are in the wiki as are in the CVS repository and with Bugzilla. Anyone could do the things you say. Is there an audit train, go look. hit Recent changes. The thing about the wiki is we just delete inapporpriate content. Wiki's have a long and proud history and so far as I know have NEVER gotten anyone sued. It is important to keep reminding yourself that Apache is a corporation of Delaware, and it is subject to real IP law. If you've been watching some of the dev lists I've been watching, there have been some small copyright violations of late that, luckily, have been settled amicably.This coupled with the fact that ASF wants to start raising more operational funds (Attachment A, November board minutes), makes legal questions very important. I'd ask you to look up the word indemnity, and meditate. You want FUD? Open source software has *very* well funded enemies. :-( Right, however I don't see how this is any different. Anyone can post an illegal patch into bugzilla with relative ease. If that little password thing makes you comfortable, go get a yahoo address with a fake name and post the secret sauce in a patch. I call this FUD because you're concerned with something that hasn't ever happened before (as far as I know, please point me to a case if you know otherwise), Ward Cunningham has been running a wiki for like 10 years or so, you're concerned with something highly correctable (easily deleteable content). And lastly the main threat on an Apache wiki is that someone posts something from a book on an Apache topic. Somehow I doubt the publisher of such a book would want to shut Apache down (kinda hard for them to sell books that way). Any other IP would probably be too off topic and would probably be deleted just by WTF does that have to do with anything... (Not that I think we should be too strict). So by the well funded enemies I must presume you mean Microsoft primarily. Yes if they are our enemy that is a problem indeed. It seems like something that is particularly remediable. We should seek their friendship and work on getting some .NET projects started. PS: You are right about Wiki's effective self regulation, I'm astonished that Wikipedia still adheres to the neutrality policy on topics that deal with current events - (if only major world conflicts could be settled on Wiki?). I started a Wikipedia page on Jakarta, it is sparse, and hardly accurate SO FIX IT: http://www.wikipedia.org/wiki/Jakarta_Project Notice how expansive that wikipedia is? I would presume that Britannica and friends have a vested interest in not seeing it grow. AFAIK they have yet to be sued. Bottom line, we can be sued for anyhthing, there are things that are of greater risk (hosting source code for instance, I'm sure by now 'IF' statements violate someone's patent somewhere). Wikis have a proven long track record, and I would rather NOT argue legal issues with software developers. Its a big fat waste of time. This isn't a comment on your worth as a human being or whatever, just IANAL and AFAIK you aren't either, so we both don't know WTF we're talking about which leads to a conversation of pure conjecture and speculation which has no logical conclusion. If you honestly feel this is going to be a problem (despite it never having happened in the history of the net so far google is aware of), its your right, responsibility and duty to bring it to the boards attention. -jAndy.NET Tim O'Brien -Original Message- From: Andrew C. Oliver [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 8:26 PM To: Jakarta General List Subject: Re: ACTION not WORDS Re: A Jakarta wiki? O'brien, Tim wrote: A non-member, non-commiter, doc patch submitter with three questions here, Would this Wiki be limited to those with commit status? If not, how does this jive with the whole merit-based Apache-way? Does a public wiki have any legal ramifications for ASF? If Wiki is open to the public and someone puts GPL'd or copyrighted material on Wiki, who would bear responsibility? Lets not start with the FUD.. If it happens, we'll remove them. What if someone puts the detailed information on how to produce Anthrax, and hides the secret location of Osama Bin Ladin in a patch submitted which also brilliantly makes Velocity run 300x faster than it does currently so that we have to choose between making the CIA happy or velocity running fast... Wiki's self regulate. You'll see. Lets not What if problems that don't exist. Go see http://www.wikipedia.org/ and http://c2.com/cgi/wiki to see what can happen and on what scale, without those things being a problem... Lets
Re: ACTION not WORDS Re: A Jakarta wiki?
James Mitchell wrote: No JSP does indeed suck. It just sucks less with Struts. LOL..ok, we'll leave it at that. You gotta understand Andy, he's got his own language: - it sucks == I don't get it - the idea is good but implementation sucks == I'm not able to use it - it sucks but with this and that it sucks less == I'm able to use it - it's very good == I wrote it - you should use it == it simply works, dunno why but I like it - it rocks == I've never used it but it makes me salivate ;-P -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: ACTION not WORDS Re: A Jakarta wiki?
Nicola Ken Barozzi wrote: James Mitchell wrote: No JSP does indeed suck. It just sucks less with Struts. LOL..ok, we'll leave it at that. You gotta understand Andy, he's got his own language: - it sucks == I don't get it - the idea is good but implementation sucks == I'm not able to use it - it sucks but with this and that it sucks less == I'm able to use it - it's very good == I wrote it - you should use it == it simply works, dunno why but I like it - it rocks == I've never used it but it makes me salivate Oh, I made a mistake, that's me :-) -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) - -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
