Re: [Jakarta Wiki] Update of Migrating to Subversion by HenriYandell

2005-07-15 Thread Daniel L. Rall
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: [svn] Alexandria: migrate or archive?

2005-06-24 Thread Daniel L. Rall
On Fri, 2005-06-24 at 17:41 +1200, Simon Kitching wrote:
 On Fri, 2005-06-24 at 01:35 -0400, Henri Yandell wrote:
  I can't remember, are we going to migrate Alexandria over to SVN, or treat 
  it like jakarta-site, jakarta-site-old and other obviously dead modules.
  
  If we want to migrate it, does anyone mind me just going ahead and doing 
  so?
 
 I'm in favour of migrating it. There may well be stuff that people want
 to go back and look into over the next few years. That will be difficult
 when Apache no longer provides CVS access
 
 The site stuff is different; there's no obvious reason for looking at
 the history of any of that, or retrieving any old versions.

For Alexandria, migration would be an appropriate scheme.  I can't say
that this is true for all effective dead projects, however.



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



RE: [Jakarta Wiki] Trivial Update of Migrating to Subversion byDanielRall

2005-06-22 Thread Daniel L. Rall
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: [ANNOUNCEMENT] Proposal For Jakarta Sub Project For Web Application Components

2005-06-22 Thread Daniel L. Rall
On Wed, 2005-06-22 at 16:11 -0700, Martin Cooper wrote:
 
 On Wed, 22 Jun 2005, robert burrell donkin wrote:
 
  i considered posting this to one or more of the announcement lists in an
  attempt to widen the audience but i didn't feel confident that it would
  be appropriate or wise.
 
  opinions?
 
 IMO, it doesn't need to go to announcements lists at this point. People 
 who are only on those lists are likely interested only in things that have 
 become real. When (if) the subproject is created, it might be more 
 appropriate, but I don't feel a proposal is right for [EMAIL PROTECTED]
 
 I did, however, forward the message to taglibs-dev and taglibs-user, since 
 they may end up with a vested interest in this.

I sent it over to Web Services as well.



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



RE: [Jakarta Wiki] Trivial Update of Migrating to Subversion by DanielRall

2005-06-21 Thread Daniel L. Rall
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

2005-06-21 Thread Daniel L. Rall
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: mod_dav_svn for SuSe 9.2 Professional

2005-05-08 Thread Daniel L. Rall
On Thu, 2005-05-05 at 15:27 -0400, Noel J. Bergman wrote:
  I'd like to know whether anyone would know where I can find the
 mod_dav_svn
 
 That'd be a question for httpd.apache.org, not Jakarta (Java stuff).

Or even better, [EMAIL PROTECTED]

http://subversion.tigris.org/project_packages.html#binary-packages



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



Re: SSH access to jakarta.apache.org

2005-05-08 Thread Daniel L. Rall
On Thu, 2005-05-05 at 19:01 +0200, Oliver Zeigermann wrote:
 Folks!
 
 As already said it seems I will need SSH access to jakarta.apache.org
 to update the jakarta commons transaction website - which I am a
 committer for.
 
 Is that right? If so who can grant that for me?

infrastructure@



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