headers
Peter B. West | 1 Mar 2004 01:59
Picon
Picon

Re: [VOTE] Clay Leeds for Committer

Andreas L. Delmelle wrote:
>>-----Original Message-----
>>From: Glen Mazza [mailto:grm7793 <at> yahoo.com]
>>
>>So let me start off the voting: +1.
>>
> No need to think this over: +1.

+1
--

-- 
Peter B. West <http://www.powerup.com.au/~pbwest/resume.html>
Permalink | Reply | 0 comments |
headers
Glen Mazza | 1 Mar 2004 02:38
Picon
Favicon

Re: [VOTE] Clay Leeds for Committer

--- Jeremias Maerki <dev.jeremias <at> greenmail.ch> wrote:
>
> Would you please enlighten me what the words below
> mean?
> 
> On 29.02.2004 22:10:42 Glen Mazza wrote:
> > Waxing chutzpaic, 
> 

Well, that joke didn't work. ;)

Long Answer:  There's a certain amount of chutzpah
inherent in the statement "I'd like us to try again to
make someone a committer", if *I* was the one who
-1'ed it to begin with.  Also, a lesser-used meaning
of the verb "to wax" is to "become of an emotion while
speaking" (normally, wax sentimental/ nostalgic/
patriotic, etc.)  It requires an adjective (adverb?)
to follow it, which "chutzpah" doesn't have, so I made
it up.

Short Answer:  Never mind--Just throw the rotten
tomatoes at me and forget about it!

Glen (splat!) (splat!)
Permalink | Reply | 0 comments |
headers
Peter B. West | 1 Mar 2004 04:22
Picon
Picon

Preferences

Looking at merging in the HEAD options processing into alt-design, I 
took a look at XML-Commons CLI, which seems to tidy up options 
processing quite nicely.

However, I also took another look at both the Properties and Preferences 
APIs.

It seems to me that the current CLI options processing could be replaced 
by a set of command-line property definitions.  This would be more in 
keeping with the assumptions of Java.  One immediate problem is that any 
line-length restrictions would be sooner violated if we were using 
property definitions.  Not being familiar with the requirements of 
application servers and embedded FOP, I can't comment on the 
implications in that environment.

If we do go that way, however, it brings up the issue of java.util.prefs 
again.  It seems to me that a naive implementation of the API could use 
the existing config and userconfig files to provide the system and user 
persistent stores, at least for reading.  java.util.prefs requires that 
the backing store be writable, however, and I don't know how this would 
fit in a server environment.  (This requirement can probably be 
circumvented at run-time by assuming that the backing store becomes 
unavailable after the initial read: prefs is designed to be robust in 
the face of backing-store unavailability.)

We could address the JVM version issue by wrapping the java.util.prefs 
stuff in org.apache.fop.prefs or ...configuration classes which mimic 
.util.prefs by a thin wrapper around the latter classes, and providing 
for 1.3 compatible versions to be written.  The availability of 1.4 
could easily be tested at run-time, and the appropriate switch set for
(Continue reading)

Permalink | Reply | 1 comment |
headers
Finn Bock | 1 Mar 2004 08:42
Picon
Favicon

Re: [VOTE] Clay Leeds for Committer

[Glen]

> Waxing chutzpaic, I'd like us to try again to make
> Clay a committer on this project.  

+1

regards,
finn
Permalink | Reply | 0 comments |
headers
Oleg Tkachenko | 1 Mar 2004 09:19

Re: [VOTE] Clay Leeds for Committer

Glen Mazza wrote:

> So let me start off the voting: +1.

+1

--

-- 
Oleg Tkachenko
http://blog.tkachenko.com
Multiconn Technologies, Israel
Permalink | Reply | 0 comments |
headers
Chris Bowditch | 1 Mar 2004 09:48
Picon
Favicon

Re: [VOTE] Clay Leeds for Committer

Glen Mazza wrote:

<snip/>

> The updates and issues he has brought up to us this
> week, I'm sure he would be happy to take care of for
> us, just as soon as we provide him write access.  I
> also hope he develops a psychological "concept of
> ownership" of our website over time, resulting in it
> looking increasingly top-notch.
> 
> So let me start off the voting: +1.

+1 from me too.

Chris
Permalink | Reply | 0 comments |
headers
Christian Geisert | 1 Mar 2004 09:51
Picon
Favicon

Re: [VOTE] Clay Leeds for Committer

Glen Mazza wrote:
> Team,
> 
> Waxing chutzpaic, I'd like us to try again to make
> Clay a committer on this project.  You may recall his

+1

(in the hope that we finally get those breadcrumbs fixed and a whole 
site pdf ;-)

Christian
Permalink | Reply | 0 comments |
headers
Chris Bowditch | 1 Mar 2004 10:32
Picon
Favicon

Newbie Commiter Questions

I know this subject has come up before, but I still cant quite get 
things working after trawling through the archives.

I'm using WinCVS 1.3 and Putty to connect to the cvs.apache.org. My 
understanding was that using SSH keys was optional but strongly 
encouraged. So I had a go at creating the private/public key pairs, and 
put the public key into .ssh directory on my apache home, and specified 
the private key file to Putty, but when I click "open" in Putty and 
enter userid/password I get a message saying

Trying public key authentication.
Key is of wrong type (PuTTY SSH2 private key)

Any ideas, what this means? I specified SSH2 (RSA) when I generated my 
keys. I noticed in the archives that some people have authorized_keys 
and others have authorized_keys2 file, which do I need? I tried both, 
but I still got the same message.

Thinking that SSH is not strictly required for write access, I had a go 
at updating my description on the Team page, but WinCVS says:

cvs [server aborted]: "commit" requires write access to the repository

Any help would be appreciated.

Chris
Permalink | Reply | 4 comments |
headers
Jeremias Maerki | 1 Mar 2004 10:53
Picon
Favicon

Re: Newbie Commiter Questions

I've had my problems with using SSH2. I finally tried SSH1 and it worked.
I suggest you create a SSH1 key pair and retry with this.

There are two ways you can work with putty. Either you create a tunnel
for CVS which has the benefit that the connection is always there as
soon as you have connected to the server.

The other way is to use plink which has to build a connection everytime
you access CVS. Select SSH authentication in WinCVS and specify the full
path to plink.exe as SSH client. You need to have Putty Password agent
running for that.

Tell me if you need more info. Good luck!

On 01.03.2004 10:32:28 Chris Bowditch wrote:
> I know this subject has come up before, but I still cant quite get 
> things working after trawling through the archives.
> 
> I'm using WinCVS 1.3 and Putty to connect to the cvs.apache.org. My 
> understanding was that using SSH keys was optional but strongly 
> encouraged. So I had a go at creating the private/public key pairs, and 
> put the public key into .ssh directory on my apache home, and specified 
> the private key file to Putty, but when I click "open" in Putty and 
> enter userid/password I get a message saying
> 
> Trying public key authentication.
> Key is of wrong type (PuTTY SSH2 private key)
> 
> Any ideas, what this means? I specified SSH2 (RSA) when I generated my 
> keys. I noticed in the archives that some people have authorized_keys
(Continue reading)

Permalink | Reply | 2 comments |
headers
Christian Geisert | 1 Mar 2004 11:02
Picon
Favicon

Re: Newbie Commiter Questions

Chris Bowditch wrote:

[..]

> Thinking that SSH is not strictly required for write access, I had a go 

Wrong!
You either need to make a frsh checkout with your commiiter id
or change your already checked out module as shown here: 
http://www.apache.org/dev/committers.html#general

Christian
Permalink | Reply | 0 comments |

Gmane