Apache Jakarta Project Board Report, June 2009
Apache Jakarta Project Board Report, June 2009 Status == Note: The board determined that the Jakarta report provided in May was lacking in detail. This report seeks to address this criticism. _From outgoing Chair, Martin van den Bemt_ It has been a while since I reported the last time. In june 2008 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 relief 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. -- EOM -- _New chair?_ We are in the process of electing a new chair (voting is in progress). Apart from the need to elect a new chair the Jakarta has no board level issues at this time. Releases * Cactus-1.8.1 - January 26, 2009 * BSF-3.0-b3 - April 5, 2009 * JMeter 2.3.3 - May 24, 2009 Subproject news === _BCEL_ No activity - maintenance mode. _BSF_ Did a 3.0 beta3 release to fix a bug for a user. Otherwise very quiet. -- sebb, antelder _Cactus_ Cactus version 1.8.1 was released in January. This version fixes a number of bugs, provides a maven2 plugin to cactify WAR and EAR files and a sample application showing how to test EJB3 projects. -- ptahchiev _ECS_ No activity - maintenance mode. _JCS_ There were a bunch of new features added at the end of last year. I'm in the process of fixing a few bugs and plan to cut a tag for a new release in the next month or so. -- asmuts _JMeter_ Lots of fixes and incremental improvements have been made to the JMeter code. JMeter user list is quite busy. There are a good few experienced JMeter users who help out with user questions. JMeter 2.3.3 was released on May 24. -- sebb _ORO_ No activity - maintenance mode. _Regexp_ No activity - maintenance mode. _Taglibs_ Standard Taglib (implementation of JSTL) migrated to Maven2. All non-deprecated Taglibs have migrated to Maven2. Discussing possibility of Taglibs moving to Tomcat with the Tomcat PMC. Random, Datetime and I18N taglibs deprecated (aka retired). An RDC 1.1 release is planned next month. -- bayard, rahul _Retired Projects_ * Slide [Report edited and submitted by Scott Eade with contributions by many.] - To unsubscribe, e-mail: general-unsubscr...@jakarta.apache.org For additional commands, e-mail: general-h...@jakarta.apache.org
Re: Jakarta site directory no longer contains .svn directories
Henri Yandell wrote: Sorry - I was doing the POI one on www.apache and jakarta.apache and cleaned up the remaining velocity/turbine bits on jakarta.apache while doing that. The download page points to closer.cgi, so I figured things were good. Do you need me to roll back? If it is not too much trouble. I would rather have the leisure of doing this as time becomes available rather than having to drop everything else I am working on in order to address this today. Thanks, Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta site directory no longer contains .svn directories
Roland Weber wrote: Danny Angus wrote: On 6/7/07, Thomas Vandahl <[EMAIL PROTECTED]> wrote: Danny Angus wrote: Yes.. http://jakarta.apache.org/site/jakarta-site2.html I've never seen this before. What link would have taken me there? From jakarta.apache.org, I mean? Oh I don't know the answer to *that* question! I just knew the page was there. :-) Maybe the idea is that you will find the page while you're browsing the file system before your first update? I know why I never tried ;-) The README.txt in jakarta-site refers to it :-) Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta site directory no longer contains .svn directories
I set Turbine to redirect yesterday. I will delete the turbine directory once I am happy that everything is okay with the new Turbine TLP site. We still have Turbine on the Jakarta downloads page - we will sort this out when we have the Turbine download page working. In summary: We are taking care of Turbine as part of the TLP move and will tidy up after ourselves towards the end of this process. Thanks, Scott Martin van den Bemt wrote: Good one :) Didn't fix Velocity yet (better to put that in the root .htaccess and get rid of subdirs) So Turbine can be redirected too ? Mvgr, Martin Henning Schmiedehausen wrote: Once, the sites are up, feel free to copy /www/jakarta.apache.org/velocity/.htaccess and /www/velocity.apache.org/moving.html Best regards Henning On Thu, 2007-06-07 at 22:24 +0200, Martin van den Bemt wrote: Thanx for clearing it up, I was starting to doubt myself, since I did some cleanup of old Jakarta projects a couple of days ago (no worries, didn't touch POI and Turbine yet !) Mvgr, Martin Thomas Vandahl wrote: sebb wrote: Thanks; that's also fixed the missing updates. I wonder how it happened? That was me. I could have *sworn* that I copied these over by accident and as busy to remove them as fast as possible. Is this procedure "svn update - edit - ant - svn commit - svn update site" documented somewhere? I've never seen anything like this. Bye, Thomas. - 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] - 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 site directory no longer contains .svn directories
sebb wrote: Not sure what's happened, but the .svn directories seem to have disappeared from the directory tree: /www/jakarta.apache.org/site It means that "svn update site" no longer works... What would the fix be - to check out the site again? Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
Thomas Vandahl wrote: Thomas Vandahl wrote: Actually, it's more than that. But so be it. I will update the files on my site and kindly ask for a re-vote. Done. I chose the separate LICENSE file. The maven2-POM is also part of the distribution. The maven2 pom is what I was holding out for and I believe the license issue has been dealt with correctly. So... +1 for the release from me. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release JCS 1.3
sebb wrote: On 26/05/07, Thomas Vandahl <[EMAIL PROTECTED]> wrote: sebb wrote: > Project Team: both tv and jvanzyl are committers Actually my contributions are very small, so I'm fine with the contributor status. But you _are_ still a committer... Surely it is up to Thomas to decide how he wants to be listed? Also what about jvanzyl? So as a committer Jason is welcome to make this change. I don't see this as the responsibility of the release manager. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commons moving to TLP
Henri Yandell wrote: * Slide. There's some sign of activity here. Not enough yet. * Cactus. Tiny bit of activity, again not enough for a TLP. * JMeter. Lots of commits from Sebb, but not a big community. For all three of these the best solution I can think of is to move them to the Incubator. Keep the lists where they are, move the svn, move the websites. They need to be thinking TLP, they need to get community. I think the people that work on and use these projects would feel somewhat marginalized if they were pushed over to Incubator. How about we have four categories in "Jakarta Commons becomes Jakarta": * proper * sandbox * dormant * jakarta-holdouts (replace this with a better name of your choosing) The last one being a home for these projects until they can find a home elsewhere (tlp or otherwise). Would it be correct to say that one of the reasons for a commons to go tlp was that a more focused PMC is required going forward? This would still be possible with a few holdouts in the mix. Scott (crawls back under rock) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Commons moving to TLP
+1 Scott Henri Yandell wrote: Sadly a bit too late to make the next board meeting I suspect. However, here's a vote for Commons to officially request that it move to TLP. http://wiki.apache.org/jakarta-commons/TLPResolution Please add your name if you're a Commons developer and haven't added your name yet. [ ] +1 I support the proposal [ ] +0 I don't care [ ] -1 I'm opposed to the proposal because... Voting will close in one week. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[RESULT][VOTE] Move Turbine to TLP
Voting has ended. The following votes were case: +1: 19 votes * Will Glass-Husain (pmc) * Henning P. Schmiedehausen (pmc) * Juergen Hoffmann * Peter Courcoux * Thomas Vandahl * Jeff Brekke (pmc) * Henri Yandell (pmc) * Scott Eade (pmc) * Roland Weber (pmc) * Dion Gillard * Niall Pemberton (pmc) * Nathan Bubna (pmc) * Mark Thomas (pmc) * Rahul Akolkar (pmc) * Davanum Srinivas (pmc) * Jörg Schaible (pmc) * Martin van den Bemt (pmc) * Jesse Kuhnert * Rony G. Flatscher (pmc) +0: None -1: None Thank you to those that participated. I will ask Martin to take the proposal to the board. Scott Scott Eade wrote: The Turbine project has been discussing a proposal to the board that the Turbine projects leave the Jakarta umbrella and become their own top level project. We are now at the point in the process that calls for a vote to take place. The proposal is available at: http://wiki.apache.org/jakarta-turbine/TLPTurbine For the interested, most of the discussion took place in the following thread: http://www.nabble.com/-DISCUSS--TLP--tf3574436.html Here are the vote options: [ ] +1 I support the proposal [ ] +0 I don't care [ ] -1 I'm opposed to the proposal because... Voting will close in one week. Thanks, Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Move POI to TLP
+1. Scott Nick Burch wrote: Hi All After lots of discussion within POI, and Jakarta in general, we think POI is ready to graduate to its own TLP. Thanks to the magic of ApacheCon, lots of people have been on-hand to help finalise the proposal for this, which is attached below. So, now is the time to vote on the proposal: [ ] +1 I support the proposal [ ] +0 I don't care [ ] -1 I'm opposed to the proposal because... Voting will close in one week. Cheers Nick - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Move Turbine to TLP
+1 from me (duh). Scott Scott Eade wrote: The Turbine project has been discussing a proposal to the board that the Turbine projects leave the Jakarta umbrella and become their own top level project. We are now at the point in the process that calls for a vote to take place. The proposal is available at: http://wiki.apache.org/jakarta-turbine/TLPTurbine For the interested, most of the discussion took place in the following thread: http://www.nabble.com/-DISCUSS--TLP--tf3574436.html Here are the vote options: [ ] +1 I support the proposal [ ] +0 I don't care [ ] -1 I'm opposed to the proposal because... Voting will close in one week. Thanks, Scott - 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]
[VOTE] Move Turbine to TLP
The Turbine project has been discussing a proposal to the board that the Turbine projects leave the Jakarta umbrella and become their own top level project. We are now at the point in the process that calls for a vote to take place. The proposal is available at: http://wiki.apache.org/jakarta-turbine/TLPTurbine For the interested, most of the discussion took place in the following thread: http://www.nabble.com/-DISCUSS--TLP--tf3574436.html Here are the vote options: [ ] +1 I support the proposal [ ] +0 I don't care [ ] -1 I'm opposed to the proposal because... Voting will close in one week. Thanks, Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Move Jakarta Cactus/JMeter to new Testing TLP
Felipe Leme wrote: [ ] +1 I am favorable to the move and would like to contribute to the new TLP [ X ] +1 I am favorable to the move but would not be participating in the new TLP [ ] +0 it does not matter to me [ ] -1 I am against it because - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: VOTE: Tomcat -> TLP
+1 Scott Eade (Jakarta PMC Member) Ian F. Darwin wrote: As has been discussed on this list & on tomcat-dev, the Tomcat people are interested in "moving up". Attached please find a Resolution to this effect from the proposed new Tomcat PMC to the Board. This is a binding procedural vote to be decided by a simple majority of those eligible and casting votes (as per http://www.apache.org/foundation/voting.html). All current members of the Jakarta PMC have binding votes. Since this involves creation of a new project I believe we should give people a week to vote; votes must therefore be registered by midnight Eastern time on Wednesday, 13 April 2005. At that point we will tally the votes and, if the vote is in the affirmative, forward the Resolutions to the Board. The question: I vote in support of the proposal to move Tomcat to an Apache Top Level Project as detailed in the attached Resolution. [ ] +1 Vote in support [ ] 0 Abstain [ ] -1 Vote against Thanks. Ian Darwin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Eyebrowse down?
It seems that Eyebrowse is down, or more likely MySQL, e.g. going to http://mail-archives.apache.org/eyebrowse/ViewLists results in: VelocityServlet: Error processing the template Unable to instantiate concrete database mapper org.tigris.eyebrowse.MySQLEyebrowseDb: Cannot connect to Database jdbc:mysql://localhost:3306/eyebrowse as eyebrowse org.apache.velocity.exception.VelocityException: Unable to instantiate concrete database mapper org.tigris.eyebrowse.MySQLEyebrowseDb: Cannot connect to Database jdbc:mysql://localhost:3306/eyebrowse as eyebrowse Is someone on this list able to resurrect this or do we need to contact infrastructure? Thanks in advance to whoever gets it going again, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wiki page tampered.
Shinobu Kawai Yoshida wrote: What's happened to the wiki page? Can we get it back? http://wiki.apache.org/general Someone can just login and revert the page. The sooner we can get the following implemented the better: http://www.google.com/googleblog/2005/01/preventing-comment-spam.html Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Turbine wiki migration
Can we please have Turbine wiki set up on http://wiki.apache.org/general so that we can migrate the content over from the old wiki. According to http://wiki.apache.org/general/HowToMakeWikiAdminRequests at least one person on the Jakarta PMC ought to be able to so this. requesting project: jakarta wiki name: jakarta-turbine human readable wiki name: Jakarta Turbine Wiki change notification mailing list: [EMAIL PROTECTED] Thanks in advance, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migration to Ajax from Nagoya (fwd)
Scarab is used by Turbine, DB Torque and a couple of other sub projects. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au Henri Yandell wrote: Anyone going to have problems if Jive, Scarab and Faqs go away? Hen -- Forwarded message -- Date: Thu, 23 Dec 2004 14:45:50 -0500 From: Noel J. Bergman <[EMAIL PROTECTED]> Reply-To: Jakarta Project Management Committee List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Migration to Ajax from Nagoya We are in the process of migrating from nagoya to ajax. There are a number of applications that no longer appear to be in use. Please let infrastructure know ASAP if you need: jive faqs scarab migrated. Thanks. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Updating PMC bylaws
[X] +1 - let's do it Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AndrewCates - wiki pruner [Was: Re: [Apache JMeter Wiki] Updated: WikiName]
I agree with Mike's analysis. Initially I removed this guys pages on all of the ASF wikis that I work on as he is all over the place in terms of wikis (both ASF and non-ASF) and is not subscribed to any of the related project lists. I didn't bother responding to his comments after I deleted his pages as I couldn't be bothered fanning the flames. At the end of the day he *has* fixed up a few typos here and there so unless someone feels strongly about it there is probably little harm in letting things be just as long as we keep an eye on them. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au Mike Verdone wrote: It looks like he's all over the Apache Wikis, not just the JMeter one. From his home page, it looks like he's just a fan of Wiki technology, and strives to study and promote it. Apparently he's cleaning up the Wiki documentation and such... obsessively: http://wiki.apache.org/general/RecentChanges However, he also seems to be removing spam. He's like a Wiki bonsai tree pruner or something. Seems pretty harmless to me. I don't see any scams or spams relating to him except a few links to a children's charity. http://www.sos-uk.org.uk/children-charity.htm Mike. Peter Lin wrote: Over the last couple months, there's been multple entries in our wiki by AndrewCates. Anyone else feel this is a bit odd? I don't see the purpose of these entries. Should we be reporting this to the apache sys admins? peter On Thu, 29 Jul 2004 13:25:08 -, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Date: 2004-07-29T06:25:08 Editor: AndrewCates <[EMAIL PROTECTED]> Wiki: Apache JMeter Wiki Page: WikiName URL: http://wiki.apache.org/jakarta-jmeter/WikiName no comment Change Log: -- @@ -1,2 +1,6 @@ ##language:en -A WikiName is a word that uses capitalized words. WikiName''''''s automagically become hyperlinks to the WikiName's page. See also HelpForBeginners, "Arbitrary Page Names". +Any word with at least two capital letters and two lower case letters automatically generates a new page with that name, linked from under the word whereever it appears. + +In general a WikiName is a such a word made by running together two capitalized words with no space. + +See also HelpForBeginners, "Arbitrary Page Names". - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Karma request
Scott Eade wrote: Can someone please grant Aaron Smuts (asmuts at apache dot org) karma to update the jakarta-turbine-jcs site? Scratch this request - Daniel Rall is looking into it. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Karma request
Can someone please grant Aaron Smuts (asmuts at apache dot org) karma to update the jakarta-turbine-jcs site? Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Importing SourceForge code that uses ASL
A while back someone forked JCS to a SourceForge project (http://ehcache.sourceforge.net/) to fix some bugs and to simplify the code base by reducing the scope of the functionality it provides. The SF project is listed as being ASL. Someone has now back ported the bug fixes to JCS (http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=403) and I am wondering if there might be any licensing issues with this. I assume not, but thought I would double check anyway. Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wiki Migration
Scott Eade wrote: According to http://nagoya.apache.org/wiki/apachewiki.cgi?MigrateFromThisWiki and http://wiki.apache.org/general/UseModMigration we eventually need to migrate the existing Usemod wiki content over to the new MoinMoin wiki. For jakarta I would imagine that we will want a subwiki per subproject. I would like to migrate the turbine project pages across as a subwiki called turbine under a Jakarta heading (with change diffs going to the turbine-dev mailing list). I am only volunteering to migrate the turbine project pages, but if others want to put their hands up for other subprojects then perhaps a single request to infrastructure could be used to request multiple subwikis. As I understand it there needs to be a consensus in the jakarta PMC that this is the way forward before a request can be made to infrastructure to create any subwikis. Do any PMC members object to this approach? Given no negative comments and the apparent acceptance of the establishment of a number of subwikis by several other jakarta sub-projects can I proceed with asking infrastructure to establish a turbine subwiki? Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wiki Migration
Geir Magnusson Jr. wrote: Does this mean we can have ./jakarta ./jakarta/turbine ./jakarta/whatever Where turbine and whatever are distinct and separate, not just parts of /jakarta? Not quite - the wiki urls would all be at the same level. Using separate wikis thus: ./jakarta ./turbine ./jakarta-commons has a few advantages: 1. Oversight can be improved by sending change diffs to the list most appropriate to the wiki concerned. 2. Potential migration of subprojects to top level projects could simplified (especially if we use, for example, "turbine" rather than "jakarta-turbine" as the name of the turbine wiki). 3. Separate wikis means independent namespaces for WikiWords. Including links between separate wikis is easily achieved through the use of InterWiki links. Would anyone like to comment on a preferred naming convention - i.e. "turbine" vs "jakarta-turbine" (I see we now have "jakarta-cactus" and "jakarta-tapestry"). I don't know if it is difficult to change the name of a wiki from say "jakarta-cactus" to just "cactus" if say cactus were to become a top level project in the future, so perhaps just "cactus" might have been a more future-proof choice. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wiki Migration
Mark R. Diggory wrote: So would I for jakarta stuff, but this stuff goes above and beyond Jakarta. Okay then make your case to the wiki admins to provide for these on the general (i.e. top level) wiki - perhaps under section 3 General Documentation. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wiki Migration
According to http://nagoya.apache.org/wiki/apachewiki.cgi?MigrateFromThisWiki and http://wiki.apache.org/general/UseModMigration we eventually need to migrate the existing Usemod wiki content over to the new MoinMoin wiki. For jakarta I would imagine that we will want a subwiki per subproject. I would like to migrate the turbine project pages across as a subwiki called turbine under a Jakarta heading (with change diffs going to the turbine-dev mailing list). I am only volunteering to migrate the turbine project pages, but if others want to put their hands up for other subprojects then perhaps a single request to infrastructure could be used to request multiple subwikis. As I understand it there needs to be a consensus in the jakarta PMC that this is the way forward before a request can be made to infrastructure to create any subwikis. Do any PMC members object to this approach? Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wiki Migration
Mark R. Diggory wrote: What about non-project related wiki content like the following, where would that go in the new wiki? http://nagoya.apache.org/wiki/apachewiki.cgi?GettingInvloved http://nagoya.apache.org/wiki/apachewiki.cgi?ToolChest http://nagoya.apache.org/wiki/apachewiki.cgi?IrcChannels If the PMC is agreeable the Jakarta heading (I see it is there now with a jakarta-cactus subwiki) could itself be a subwiki to provide a place for these non-project documents (with change diffs emailed to this list). The Incubator and Logging projects seem to take this approach. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Future Of Turbine-JCS
robert burrell donkin wrote: (we've done some talking on the pmc list and turbineers have discussed this in the past but since it's not really confidential i'm starting this thread to give everyone a chance to participate.) some information about Turbine-JCS: * JCS has no release * other apache products depend on JCS * JCS is not really directly related to turbine concerns: * JCS is a sub-sub-project with it's own mailing list (this kind of structure has proved difficult to properly supervise) * JCS's health * want to find the 'right' place for JCS -->8 Andy: There most definitely are Turbine people (count me in) - but as Robert suggests above, with it's own mailing list many of us are unaware of JCS. The connection between Turbine and JCS is Torque, which was spun out into db.apache.org some time ago. JCS could well receive more attention if it was located somewhere more appropriate - more attention leads to more users and developers. Without knowing too much, should perhaps "JCS to db top level" and "JCS to db commons" also be considered options? Of the available options below I have selected jakarta commons more by excluding the other options than because of some perceived positive fit in jakarta commons (though commons is a good place to be no doubt). -->8 [ ] leave JCS within turbine [ ] JCS to apache commons [x] JCS to jakarta commons [ ] JCS to jakarta top level [ ] JCS to incubator [ ] something else (please specify)... Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: website (was RE: [PATCH] promoted sub-projects)
On 21/03/2003 2:31 AM, "Stefan Bodewig" <[EMAIL PROTECTED]> wrote: > - maybe DB as well. OJB should probably be replaced in the Related list by DB which includes Torque (formerly part of Turbine) in addition to OJB. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
karma for jakarta-site2
Could someone grant me karma to jakarta-site2? I want to alter the mailing list details for the projects that have moved to db.apache.org. Thanks in advance, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Example committer acknowledgement - RESEND
On 5/02/2003 2:24 PM, "Pier Fumagalli" <[EMAIL PROTECTED]> wrote: > On 5/2/03 2:59 "Scott Eade" <[EMAIL PROTECTED]> wrote: > >>> The example committer acknowledgement on >>> http://jakarta.apache.org/site/roles.html indicates that a new committer >>> should send an email to asf at jaguNET.com. What is the purpose of this, ^^ >>> and assuming there is a purpose, what is the address that should actually be >>> used. > > The email address you have to use is the one you normally use (in your case > Scott Eade <[EMAIL PROTECTED]>)... The purpose is to let know the > ASF secretary that you can actually write code in our CVS, and therefore > legally bound to the Foundation itself (in good and bad times)... > > Pier Thanks for the response Pier. I should have been more careful with my wording. What I was actually wanting to query was: 1. The address [EMAIL PROTECTED] - this does not seem to be operable (it bounces mail) 2. For what purpose is the public key required. Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FW: Example committer acknowledgement - RESEND
Does anyone have an answer to my query below? Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com -- Forwarded Message > From: Scott Eade <[EMAIL PROTECTED]> > Reply-To: "Jakarta General List" <[EMAIL PROTECTED]> > Date: Tue, 28 Jan 2003 14:45:49 +1100 > To: Jakarta General List <[EMAIL PROTECTED]> > Subject: Example committer acknowledgement > > The example committer acknowledgement on > http://jakarta.apache.org/site/roles.html indicates that a new committer > should send an email to asf at jaguNET.com. What is the purpose of this, > and assuming there is a purpose, what is the address that should actually be > used. > > Thanks, > > Scott > -- > Scott Eade > Backstage Technologies Pty. Ltd. > http://www.backstagetech.com.au > .Mac Chat/AIM: seade at mac dot com -- End of Forwarded Message - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Example committer acknowledgement
The example committer acknowledgement on http://jakarta.apache.org/site/roles.html indicates that a new committer should send an email to asf at jaguNET.com. What is the purpose of this, and assuming there is a purpose, what is the address that should actually be used. Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
jmeter-dev commit message
Hi, It seems that the jmeter-dev commit message are backed up again. Can someone please give these a kick along. Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
cvs commit messages for jmeter-dev
It seems that jakarta-jmeter cvs commit messages are no longer being sent to the JMeter Developers List <[EMAIL PROTECTED]>. The last commit message was on December 14 2002, but there have most definitely been commits since then. Can someone please either fix this, provide the details necessary to fix this or point me to the information about how to fix this (it appears that the method used to configure this is well beyond what is covered in the cvs manual). Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: [Fwd: Wiki Wiki (has been set up)]
On 25/12/2002 4:46 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > A little wiki bird left a posting on the "JProjectPages" about how to change > it to "Log4JProjectPages". On the page, put it as "[[Log4JProjectPages]]". > It works. Thank you little wiki bird. I have updated the relevant links. Tweet tweet! > > Of course, it would eventually be even better if the wiki could let you do > the equivalent of Some text for the link so that we don't > NeedToHaveTextAllJumbledTogetherForALink. Um, the whole point of a wiki is that it should be abnormally easy to create things such as new pages and links to them - the very basis of this is the concept of a WikiWord. > > Also, is there any way to delete pages from the wiki? I'd like to remove > the "JProjectPages" so that it does not show up in searches. Just remove > all the contents? No way to delete - you need to be able to recover if someone anonymously deletes something you want to keep. Just delete the content. > > -Mark Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: [Fwd: Wiki Wiki (has been set up)]
On 22/12/2002 2:15 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Thanks for setting this up! > > Any idea why the "Log4JProjectPages" show us as "JProjectPages"? > > -Mark According to my interpretation of http://www.usemod.com/cgi-bin/wiki.pl?WikiWord Log4JProjectPages should be fine. To force it to work you can surround it with double square brackets. You will in effect be creating a replacement page for JProjectPages, so make sure you copy the content over. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: ACTION not WORDS Re: A Jakarta wiki?
Thanks Pier and Andrew - you made Andrew's suggested deadline with a week to spare ;-) Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com On 21/12/2002 5:51 PM, "Pier Fumagalli" <[EMAIL PROTECTED]> wrote: > On 21/12/02 2:34 "Sam Ruby" <[EMAIL PROTECTED]> wrote: > >> Andrew C. Oliver wrote: >>> >>> Sam, do you or someone have the abillity/will to give me sufficient >>> rights to install a small cgi script on an apache webserver somewhere >>> with filesystem access? >> >> Your definition of "ACTION" is "AskSam"? >> >> AFAIK, your authority and mine with respect to being able to execute cgi >> scripts on a machine like cvs.apache.org are the same. I just did a few >> tests, and apparently I don't have permission. > > That's called defensive programming (ehem... Administration) :-) > >>> If not, what about servlet engine + database access? >> >> Not on any BSD machine. You will find a more receptive set of sysadmins >> on nagoya. >> >> In any case, the right place to pursue this is [EMAIL PROTECTED] > > Done... http://nagoya.apache.org/wiki/ > > I'd still prefer a Java/MySQL based approach, but It's up and running... > > Pier > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: ACTION not WORDS Re: A Jakarta wiki?
Andrew, ACTION is good mm'kay. I think we should at least consider a Java based wiki: - JSPWiki at http://www.ecyrd.com/JSPWiki/Wiki.jsp is used by Cocoon (I installed this locally and had it running in about 5 minutes). - Micael mentioned Chiki (http://chiki.emaho.org/) - this looks pretty good too (but I haven't tried installing it yet). Rodney Waldhoff's comment concerning namespaces is very important. For JSPWiki I think we would need to go down the "federation of wikis with intra-wiki links" path (prefixing with project names becomes a PITA fairly quickly IMO). It looks like Chiki's "nodes" provide independent namespaces, but it wasn't obvious how to go about creating a node (it is worth looking into this though as the "federation" model may require more effort to set up new sub-wikis, but perhaps this is not such a bad thing). Twiki is an excellent cgi based wiki (http://www.twiki.org), but I think we are better off adopting a solution that we can more easily contribute to if we so desire (note that both JSPWiki and Chiki are GPL). I am unsure of the legal ramifications that Tim O'Brien raises, but the whole point of wanting a wiki is to allow update access by non-committers. A more subtle point is whether or not to allow anonymous postings - I myself prefer people to register before they can make changes, it only takes a few seconds, and provides at least some form of (albeit easily circumvented) author trail. It is excellent to see that you are so keen - targeting the end of next week sounds great. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com On 21/12/2002 6:25 AM, "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote: > +1 > > Sam, do you or someone have the abillity/will to give me sufficient > rights to install a small cgi script on an apache webserver somewhere > with filesystem access? > > If not, what about servlet engine + database access? > > If so. I will select one based on ease of maintenence, setup, > "security" and set it up by the end of next week. > > Thank you, > > -Andy > > Tom Copeland wrote: > >> Love 'em. Let's pick one and set it up... they're very cool >> >> tom >> >> >> >>> -Original Message- >>> From: Rodney Waldhoff [mailto:[EMAIL PROTECTED]] >>> Sent: Friday, December 20, 2002 12:36 PM >>> To: Jakarta General List >>> Subject: Re: A Jakarta wiki? >>> >>> >>> On Sat, 21 Dec 2002, Scott Eade wrote: >>> >>> >>> >>>> So how about some feedback: >>>> 1. Wiki's - love 'em or hate 'em? >>>> >>>> >>> Love 'em, and think they would provide (a) a good way to write ad hoc >>> documentation, (b) a good way to host certain discussions. >>> At my day job >>> we use an internal wiki for documentation almost exclusively, and >>> sometimes as an effective public brainstorming tool. (And >>> we're fairly >>> centrally located--for distributed, asynchronous discussion a >>> wiki is even >>> more useful.) >>> >>> >>> >>>> 2. JSPWiki - good choice or bad choice? >>>> >>>> >>> Never used it, so no real opinion, although there seem to be >>> a number of >>> wiki's that are much more popular (perhaps not in java >>> though). There's a >>> big list of wiki impls on Ward's Wiki at >>> <http://c2.com/cgi/wiki?WikiEngines>, of course. >>> >>> (Most wiki clones, JSPWiki included, seem to be GPLed, if >>> that matters to >>> anyone.) >>> >>> >>> >>>> 3. Scope of the wiki(s) - ((Turbine) and (Avalon)), Jakarta >>>> >>>> >>> or Apache? >>> >>> I'd like to see a wiki with at least jakarta scope. >>> >>> One option might be to use a wiki that supports "namespaces", or a >>> federation of wikis with intra-wiki links, so that one could create a >>> "sub-wiki" per project but still support "global" cross-linking. >>> >>> For example, a intra-wiki link might look like >>> Turbine:OracleHowTo versus >>> plain ol' OracleHowTo. >>> >>> Alternatively, a simple convention of prefixing the project >>> name might be >>> sufficient for a shared wiki namespace, but might need >>> support from some >>
A Jakarta wiki?
About a month ago a discussion occurred over on turbine-user/dev about the possibility of setting up a wiki to use for creating ad hoc documentation as well as a place to develop more formal documentation that might perhaps later be converted to xdoc for direct inclusion in the actual project site. We discussed setting something up on a non-apache server, but thought we would first seek an opinion as to whether or not an apache hosted solution might be a possibility. To this end, I posted a query to [EMAIL PROTECTED] (quoted below). The brief discussion that ensued between Brian Behlendorf, Pier Fumagalli and myself concluded that I was to liaise with Pier to set up a JSPWiki instance on nagoya. I provided Pier with some information and asked him what the next steps might be, but unfortunately Pier has become overloaded with work and has been unable to get back to me (I'm not complaining Pier - all things take time and time is a limited resource). Anyway, I have two motivations for mailing the general list: 1. To raise the profile of this request in hope of sparking some action. 2. To gain some feedback as to the desirability of widening the scope of the wiki beyond turbine. As mentioned below, Cocoon already have an external (non-apache hosted) wiki. Leo Simons has also indicated that a similar discussion has recently taken place over on the Avalon lists with the conclusion being that they too would like to set up a wiki. So how about some feedback: 1. Wiki's - love 'em or hate 'em? 2. JSPWiki - good choice or bad choice? 3. Scope of the wiki(s) - ((Turbine) and (Avalon)), Jakarta or Apache? 4. Hosting - apache.org or external 5. Timing - now, soon, later or never Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com On Fri, 15 Nov 2002, Scott Eade wrote: > On turbine-user & turbine-dev (jakarta) we have been discussing the > possibility of setting up a wiki to use for creating ad hoc documentation as > well as a place to develop more formal documentation (perhaps we will > convert it to xdoc and make it part of the "real" docs once we are happy > with it). > > To this end, we are wondering if it would be possible to establish a wiki > somewhere on an apache server. > > At this stage our desire is for a wiki that provides information about > turbine and its related projects (torque, fulcrum, etc.), but perhaps the > entire jakarta or even apache community could benefit from the free flow of > information that is facilitated by a wiki. > > We are open minded about the wiki implementation to be used. There is a > maven plugin that provides quite a nice customisation of the UseMod wiki. I > myself have used twiki and am fairly happy with it. Cocoon uses an > externally hosted JSPWiki which looks pretty good (being a Java person I > would probably have used this in preference to twiki had I found it > earlier). > > Anyway, what are the chances of getting something set up on an apache > server? > > What would I need to do to get something happening? > > Thanks, > > Scott > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: [scarab] problems with scarab server
> From: Jon Scott Stevens <[EMAIL PROTECTED]> > > I just need to make it clear that it isn't Scarab that is slow, it is > nagoya. > I didn't expect that it would be Scarab. Pier is looking into a problem with mysql on nagoya. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:general-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>
Re: [scarab] problems with scarab server
> From: Daniel Rall <[EMAIL PROTECTED]> > > Mahler Thomas <[EMAIL PROTECTED]> writes: > >> - Sessions are disrupted, so you have login several times to get done even >> most simple actions. >> It took us hours to enter 10 new issues. > > Rarely, I restart Catalina on nagoya a few times in a row well pushing > new Eyebrowse changes live. This could possibly account for some > session disruptions (though I thought that session information was > persisted in a file by Catalina). During the past week or so, I've > monkeyed with the server once or twice. It's remotely possible we > could've coincided. No, Scarab on nagoya is always very slow, almost to the point of being unusable. I'll post a question to the infrastructure address asking if the machine is resource bound. Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:general-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:general-help@;jakarta.apache.org>
Re: Differences between Structs and Turbine ???
> From: [EMAIL PROTECTED]
>
> #if (..)
> #end
>
> in Velocity...?
>
>> "Andrew C. Oliver" <[EMAIL PROTECTED]> wrote on 08/10/2002 09:50:15 AM:
>>
>> <%
>> if (you.have(this).in.your(html)) {
>>out.println("Andy doesn't think its good");
>> }
>> %>
But the Velocity is much easier to teach to a web designer (non-programmer)
than the JSP.
http://jakarta.apache.org/velocity/ymtd/ymtd.html
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
[ANNOUNCEMENT] Turbine issue tracking now on nagoya Scarabinstance
As from today, issues for Turbine related projects can no longer be entered into bugzilla. >From now on, issues that pertain to the following Turbine related projects should be submitted into the fully maintained Scarab instance at http://nagoya.apache.org/scarab/issues: * Turbine site * Turbine-2 * Turbine-3 * Fulcrum * TDK * JCS Note: The list above includes all Turbine related projects with the exception of Maven - Maven issues are being maintained in a Jira instance at http://jira.werken.com/BrowseProject.jspa?id=10030 Regards, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: Issue tracking
> From: Pier Fumagalli <[EMAIL PROTECTED]> > > Sorry, if you had troubles accessing Nagoya, it has been most definitely my > fault. The original idea to set up Scarab on Nagoya was that once some > projects had the confidence of the install, all other projects would have > moved as well, so, I still think that installing it on a central location is > a good idea... > > If you, Jason and Bob want to maintain that instance, just let me know and > I'll grant appropriate karma, otherwise, I believe that at the end we'll > have 3 bug tracking systems: two on nagoya, and one wherever you guys want > to put it... :-/ I'll ask back on turbine-dev and see if there is a general consensus. It is actually John McNally and Stephen Haberman that have volunteered to maintain the install, so it is in large part up to them (Bob and Jason were just our gracious hosts). The trouble is of course that we already have an active project on each of the two scarab installs :-( Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Re: Issue tracking
> From: Pier Fumagalli <[EMAIL PROTECTED]> >> On 26/9/02 3:04, "Scott Eade" <[EMAIL PROTECTED]> wrote: > >> This instance was set up >> as it apparently proved difficult to gain the necessary access to maintain >> the Scarab instance at issues.apache.org/scarab. > > We already have a setup of Scarab on nagoya.apache.org, which of course is > _already_ has an alias as issues.apache.org > > If you want to use scarab, use nagoya and update that installation, let's > not redo the whole thing again and again and again... As stated in the original message, it was deemed to difficult to obtain the necessary access to maintain the instance on nagoya. As things currently stand we have the nagoya instance that is un-maintained with only one project using it and we have the up-to-date werken instance with one project actively using it (and four more that have agreed to) and two people committed to maintaining it. The newer instance is hosted at a very ASF friendly location who are happy to provide their resources and the access necessary to maintain it. Why not follow the path of least resistance? Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Issue tracking
Hi, I am in the process of tidying up the issue tracking systems used by the turbine projects. The biggest change is that we are predominantly going to use an instance of the turbine based Scarab issue tracking system (from tigris.org) that is installed at werken.com (Bob McWhirter's site on a box belonging to Bob and Jason van Zyl - thanks guys). This instance was set up as it apparently proved difficult to gain the necessary access to maintain the Scarab instance at issues.apache.org/scarab. Bob has suggested that we set up an apache.org hostname for the box to make it easier if it becomes necessary to migrate to another system in the future. I thought it would be a good idea to run this past the general Jakarta list prior to making a request to [EMAIL PROTECTED] In summary here is what we want to do: 1. Request the host name scarab.apache.org be set up to point to the same address as scarab.werken.com 2. Update http://issues.apache.org/ to de-emphasise the issues.apache.org/scarab install (now used only by OJB) and to include a reference to the new scarab.apache.org instance (note that OBJ guys are being invited to migrate over to the maintained Scarab instance). 3. Organize for bugzilla to no longer accept turbine issues. Please speak up if you have any comments or concerns about this. It has been discussed on the turbine-dev list with no objections. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
