Re: Intent to maintainer change: canna

1999-05-20 Thread Sven LUTHER
On Wed, May 19, 1999 at 11:48:34PM -0400, Brian Almeida wrote:
> On Wed, May 19, 1999 at 08:19:47PM -0400, Adam Di Carlo wrote:
> > I'm not sure I agree with Brian.  The old maintain put out a "looking
> > for new maintainer" request on this list. Therefore, it is appropriate
> > that the agreed upon new maintainer would announce that here to.  This
> > is to prevent others from possibly investigating the source with an
> > eye towards taking over maintenance.
> Ah, I see.  I must have missed that message.  In this case, yes, I'd say
> "Ok, this guy has it now, thanks for the help", which most people do right 
> now anyways (most often just a "It's yours."). 

Just one message for all packages he was taking over would have been
enough, not one for each package ?

Friendly,

Sven LUTHER



Re: Intent to maintainer change: canna

1999-05-20 Thread Brian Almeida
On Wed, May 19, 1999 at 08:19:47PM -0400, Adam Di Carlo wrote:
> I'm not sure I agree with Brian.  The old maintain put out a "looking
> for new maintainer" request on this list. Therefore, it is appropriate
> that the agreed upon new maintainer would announce that here to.  This
> is to prevent others from possibly investigating the source with an
> eye towards taking over maintenance.
Ah, I see.  I must have missed that message.  In this case, yes, I'd say
"Ok, this guy has it now, thanks for the help", which most people do right 
now anyways (most often just a "It's yours."). 

-- 
Brian Almeida <[EMAIL PROTECTED]>  
Debian Linux Developer - http://www.debian.org
finger [EMAIL PROTECTED] for GPG/PGP public keys
Don't hate yourself in the morning - sleep till noon. 



Re: Intent to maintainer change: canna

1999-05-20 Thread John Lapeyre
*Adam Di Carlo wrote:
> ISHIKAWA Mutsumi <[EMAIL PROTECTED]> writes:
> I'm not sure I agree with Brian.  The old maintain put out a "looking
> for new maintainer" request on this list. Therefore, it is appropriate
> that the agreed upon new maintainer would announce that here to.  This
> is to prevent others from possibly investigating the source with an
> eye towards taking over maintenance.
I thought the same thing. An announcement of change of
maintainership is appropriate for  this list.


-- 
John Lapeyre <[EMAIL PROTECTED]>,  [EMAIL PROTECTED]
Tucson,AZ http://www.physics.arizona.edu/~lapeyre



Re: Intent to maintainer change: canna

1999-05-20 Thread Adam Di Carlo
ISHIKAWA Mutsumi <[EMAIL PROTECTED]> writes:

>  Brian Almeida <[EMAIL PROTECTED]> wrote
>>> Usually, you don't need to announce a maintainer change to the
>>> lists if it's already been agreed to by both the old and new
>>> maintainers, just mark something like '* New maintainer' in the
>>> changelog.

>  I had read "Developpers' Reference". But I can't find description of
> this case, so I send "Maintainer Change announce mail" ,just in case.
> 
>  OK, I understand this process for these case. Thank you.

I'm not sure I agree with Brian.  The old maintain put out a "looking
for new maintainer" request on this list. Therefore, it is appropriate
that the agreed upon new maintainer would announce that here to.  This
is to prevent others from possibly investigating the source with an
eye towards taking over maintenance.

Of course, you can change maintainership without involving this
list. For instance, it's pretty common, I think, for old maintainers
looking to drop packages to solicit actuve bug reporters , asking them
if they wanna take over the pkg.

Anyhow, I'll take a look at adding a section about this to the
developers-reference.

--
.Adam Di [EMAIL PROTECTED]http://www.onShore.com/>



Re: Intent to maintainer change: canna

1999-05-19 Thread ISHIKAWA Mutsumi
 Brian Almeida <[EMAIL PROTECTED]> wrote
   Subject: Re: Intent to maintainer change: canna
   Message-ID: <[EMAIL PROTECTED]>

>> Usually, you don't need to announce a maintainer change to the lists if it's
>> already been agreed to by both the old and new maintainers, just mark
>> something like '* New maintainer' in the changelog.  

 Thanks for your advice :-)

 I had read "Developpers' Reference". But I can't find description of
this case, so I send "Maintainer Change announce mail" ,just in case.

 OK, I understand this process for these case. Thank you.

-
Wed May 19 23:41:38 JST 1999
  ISHIKAWA Mutsumi <[EMAIL PROTECTED]>
  a trustee of Japan Linux Association <[EMAIL PROTECTED]>
  a member of Debian project   <[EMAIL PROTECTED]>
  a member of Debian JP project<[EMAIL PROTECTED]>
  a member of X-TrueType project (TrueType fonts support for X)



Re: Intent to maintainer change: canna

1999-05-19 Thread Brian Almeida
On Wed, May 19, 1999 at 11:14:18PM +0900, ISHIKAWA Mutsumi wrote:
> Package: canna
> 
>  canna package's mainainer Yoshiaki Yanagihara <[EMAIL PROTECTED]> is
> very very busy in his main work. He can't maintain some
> packages. Canna is one of them.
> 
>  We disccussed this point, and I will take over kterm's maintainer.
> 
>  Canna is a japanese input system.
> 
>  I will upload the package in this week end.
Usually, you don't need to announce a maintainer change to the lists if it's
already been agreed to by both the old and new maintainers, just mark
something like '* New maintainer' in the changelog.  

-- 
Brian Almeida <[EMAIL PROTECTED]>  -  Systems Administrator
CICAT Networks - The New Brand of Telecommunications Service
Web: http://www.cicat.com/   V: 703-383-1408
email: [EMAIL PROTECTED]   F: 703-385-3788
Life's unfair - but root password helps!