[packagers] RE: retty - naming conflict in rpmforge

[Stefan Radman]

Hi Oliver,

> > There has never been a lot of interest in my program, and 
At least now there's a bit ;-)

> since I am not using it anymore myself, 
What are you using instead?

> know of any user who uses the tool actively, I'll be glad to 
> change the name, 

If it does what it is supposed to I'll be using it actively.
Please consider this a request from an active user. :-) 

> So a rename of the tool (maybe 0.2 with just the rename), a 
> new freshmeat announcement and maybe a statement on the website 

Having browsed for alternative (unused) names I would suggest:

  remtty-0.2  (Obsoletes: retty-0.1)

There does not seem to be any commercial or open source software or
trademark associated with that name.
http://www.google.com/search?q=remtty

> Stefan would 
> be a good candidate for maintainership. *hint* *hint* :)

I cannot promise anything at this point in time but let's see ...

Thank you in advance
Kind regards
Stefan

> -----Original Message-----
> From: Dag Wieers [mailto:dag at wieers.com] 
> Sent: Tuesday, 22 May, 2007 11:42
> To: Oliver Hitz
> Cc: Stefan Radman; packagers at lists.rpmforge.net
> Subject: Re: retty - naming conflict in rpmforge
> 
> On Tue, 22 May 2007, Oliver Hitz wrote:
> 
> > On 21 May 2007, Stefan Radman wrote:
> > > I am a user of RPMforge with an interest of using both 
> packages and
> > > would therefore like to propose that you rename your 
> retty software to
> > > something similar e.g. rettyd or remtty or rtty.
> > > 
> > > Such a step would help a larger community to a 
> hazzle-free concurrent
> > > use of both software packages.
> > 
> > There has never been a lot of interest in my program, and 
> since I am not
> > using it anymore myself, there has never been any never 
> version. If you
> > know of any user who uses the tool actively, I'll be glad 
> to change the
> > name, otherwise I propose we leave it as it is until 
> somebody asks about
> > it. What do you think?
> 
> Hey Oliver,
> 
> I think Stefan is the requesting party here :)
> 
> My opinion is that even when the program is currently no 
> longer maintained 
> (or lets call it 'finished'), people may want to extend it after your 
> maintainership. For that reason it needs to be available.
> 
> Our current problem is that we cannot make it available as 
> such, as we 
> have another tool in the repository named retty v1.0.
> 
> So a rename of the tool (maybe 0.2 with just the rename), a 
> new freshmeat 
> announcement and maybe a statement on the website that you do 
> no longer 
> maintain it but anyone is free to take over maintainership or 
> co-maintainership, is probably the best for the community in general.
> 
> Nobody is going to take interest in maintaining retty if it 
> is not known.
> 
> PS Of course, for maintainership, you'd need to be a user. So 
> Stefan would 
> be a good candidate for maintainership. *hint* *hint* :)
> 
> Kind regards,
> --   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
> [all I want is a warm bed and a kind word and unlimited power]
>