no contact with author
Hi, I am using a module from CPAN, but it lacks some functionality, so I added them. The problem is that there is no contact with author, I sent him emails twice (6months ago and 2weeks ago). A guy from [EMAIL PROTECTED] (integral), adviced to write here. signature.asc Description: OpenPGP digital signature
Re: no contact with author
Hi, Darek. Can we know who is the author? This basically because sometimes some authors have strange lives :) Cheers ambs Darek Dwornikowski wrote: Hi, I am using a module from CPAN, but it lacks some functionality, so I added them. The problem is that there is no contact with author, I sent him emails twice (6months ago and 2weeks ago). A guy from [EMAIL PROTECTED] (integral), adviced to write here. -- Alberto Simões - Departamento de Informática - Universidade do Minho Campus de Gualtar - 4710-057 Braga - Portugal Beware of bugs in the above code; I have only proved it correct, not tried it. --- Donald Knuth
Re: no contact with author
--- Darek Dwornikowski [EMAIL PROTECTED] wrote: Hi, I am using a module from CPAN, but it lacks some functionality, so I added them. The problem is that there is no contact with author, I sent him emails twice (6months ago and 2weeks ago). A guy from [EMAIL PROTECTED] (integral), adviced to write here. Thoughts: 1. I can understand your not wanting to mention the name of the module, but we might be able to provide more help if we know it, particularly if someone on this list is aware of what happened. 2. You could fork the module on the CPAN (which means maintaining it, something you might not want to do). 3. You could fork the module for your company's internal use, which I know many programmers do. 4. You could tell us what functionality you added. I do know that some authors just won't respond to what they consider unimportant or bad requests (I'm not saying your changes are unimportant or bad; the author might just see them that way.) I might add that if a fork happens, many people might be happy to see the fork on the CPAN. The theory is that many people can benefit. However, that means you have to maintain it and that can be more trouble than it's worth. More than once I've begged people for patches, only to be ignored. Plenty of other authors have had the same experience. Maintaining modules can be frustrating. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
Re: no contact with author
Thoughts: 1. I can understand your not wanting to mention the name of the module, but we might be able to provide more help if we know it, particularly if someone on this list is aware of what happened. 2. You could fork the module on the CPAN (which means maintaining it, something you might not want to do). 3. You could fork the module for your company's internal use, which I know many programmers do. 4. You could tell us what functionality you added. I do know that some authors just won't respond to what they consider unimportant or bad requests (I'm not saying your changes are unimportant or bad; the author might just see them that way.) I might add that if a fork happens, many people might be happy to see the fork on the CPAN. The theory is that many people can benefit. However, that means you have to maintain it and that can be more trouble than it's worth. More than once I've begged people for patches, only to be ignored. Plenty of other authors have had the same experience. Maintaining modules can be frustrating. sorry the module is DNS::ZoneParse. I could fork it, no problem. I am using it all the time in my company, so it is better for public that changes appear on CPAN, not only my private svn. signature.asc Description: PGP signature signature.asc Description: OpenPGP digital signature
Re: no contact with author
Darek Dwornikowski wrote: Thoughts: 1. I can understand your not wanting to mention the name of the module, but we might be able to provide more help if we know it, particularly if someone on this list is aware of what happened. 2. You could fork the module on the CPAN (which means maintaining it, something you might not want to do). 3. You could fork the module for your company's internal use, which I know many programmers do. 4. You could tell us what functionality you added. I do know that some authors just won't respond to what they consider unimportant or bad requests (I'm not saying your changes are unimportant or bad; the author might just see them that way.) I might add that if a fork happens, many people might be happy to see the fork on the CPAN. The theory is that many people can benefit. However, that means you have to maintain it and that can be more trouble than it's worth. More than once I've begged people for patches, only to be ignored. Plenty of other authors have had the same experience. Maintaining modules can be frustrating. sorry the module is DNS::ZoneParse. I could fork it, no problem. I am using it all the time in my company, so it is better for public that changes appear on CPAN, not only my private svn. Accordingly with http://search.cpan.org/~simonflk/, Simon last release date for all modules is 25 Mar 2005. I would say the best approach is to fork it... Just my 5 cents ;) Cheers -- Alberto Simões - Departamento de Informática - Universidade do Minho Campus de Gualtar - 4710-057 Braga - Portugal Beware of bugs in the above code; I have only proved it correct, not tried it. --- Donald Knuth
Re: no contact with author
On Tue, 2 Jan 2007, Alberto Simões wrote: Accordingly with http://search.cpan.org/~simonflk/, Simon last release date for all modules is 25 Mar 2005. I would say the best approach is to fork it... In this case, if the author is AWOL, the best thing is to ask for ownership of the module so that he can upload a new version. Six months is a reasonable waiting period for this, IMO. -dave /*=== VegGuide.Orgwww.BookIRead.com Your guide to all that's veg. My book blog ===*/
Re: no contact with author
Dave Rolsky napisał(a): On Tue, 2 Jan 2007, Alberto Simões wrote: Accordingly with http://search.cpan.org/~simonflk/, Simon last release date for all modules is 25 Mar 2005. I would say the best approach is to fork it... In this case, if the author is AWOL, the best thing is to ask for ownership of the module so that he can upload a new version. Six months is a reasonable waiting period for this, IMO. how can it be done? and what is AWOL ? signature.asc Description: OpenPGP digital signature
Re: no contact with author
On Tue, 2 Jan 2007, Dave Rolsky wrote: On Tue, 2 Jan 2007, Alberto Sim?es wrote: Accordingly with http://search.cpan.org/~simonflk/, Simon last release date for all modules is 25 Mar 2005. I would say the best approach is to fork it... In this case, if the author is AWOL, the best thing is to ask for ownership of the module so that he can upload a new version. Six months is a reasonable waiting period for this, IMO. Yeah, but is 2 times within in 6 months acceptable? And only via email? Like Albero said, Authors can have strange lives. Just because code hasn't updated anything in 24 months doesn't necessarily mean the guy is dead. It could just be really good code. Christopher Josephes [EMAIL PROTECTED]
Re: no contact with author
Chris napisał(a): On Tue, 2 Jan 2007, Dave Rolsky wrote: On Tue, 2 Jan 2007, Alberto Sim�es wrote: Accordingly with http://search.cpan.org/~simonflk/, Simon last release date for all modules is 25 Mar 2005. I would say the best approach is to fork it... In this case, if the author is AWOL, the best thing is to ask for ownership of the module so that he can upload a new version. Six months is a reasonable waiting period for this, IMO. Yeah, but is 2 times within in 6 months acceptable? And only via email? Like Albero said, Authors can have strange lives. Just because code hasn't updated anything in 24 months doesn't necessarily mean the guy is dead. It could just be really good code. Christopher Josephes [EMAIL PROTECTED] i wrote to him twice, trying different emails. his personal webpage is dead too.. I do not want to take over, I thought I could contact him trough this list. signature.asc Description: OpenPGP digital signature
Re: no contact with author
# from Darek Dwornikowski # on Tuesday 02 January 2007 09:49 am: i wrote to him twice, trying different emails. his personal webpage is dead too.. I do not want to take over, I thought I could contact him trough this list. Google suggests that he is still alive and updating his amazon wishlist. Even on perl.pep as recently as July. Did you try his bbc address? File a bug in rt? Are you just getting spam-trapped? (maybe try sending from a different address.) --Eric -- Those who cannot remember the past are condemned to repeat it. --George Santayana --- http://scratchcomputing.com ---
Re: no contact with author
Darek Dwornikowski writes: Dave Rolsky napisał(a): On Tue, 2 Jan 2007, Alberto Simões wrote: Accordingly with http://search.cpan.org/~simonflk/, Simon last release date for all modules is 25 Mar 2005. I would say the best approach is to fork it... In this case, if the author is AWOL, the best thing is to ask for ownership of the module so that he can upload a new version. Six months is a reasonable waiting period for this, IMO. how can it be done? Mail Simon one more time, saying that since he doesn't seem to be interested in updating the module any more you would like to upload a version with your fix in it. CC modules@perl.org on your message, to provide evidence that you've done this. If Simon hasn't responded to your message within a few weeks then write to modules@perl.org drawing their attention to this and asking to be made a co-maintainer of the module. and what is AWOL ? Absent without leave -- a military term for somebody who is missing without permission. Good luck! Simon
Re: no contact with author
Eric Wilhelm wrote: # from Darek Dwornikowski # on Tuesday 02 January 2007 09:49 am: i wrote to him twice, trying different emails. his personal webpage is dead too.. I do not want to take over, I thought I could contact him trough this list. File a bug in rt? This is a good suggestion and should be followed by anyone who is having trouble contacting a module's author or last maintainer. It documents your specific objective in trying to reach the author. Should the module's maintainership ultimately need to be transferred, it provides documentation that the people at modules@perl.org can use to make an informed decision. jimk
Re: no contact with author
Accordingly with http://search.cpan.org/~simonflk/, Simon last release date for all modules is 25 Mar 2005. I would say the best approach is to fork it... In this case, if the author is AWOL, the best thing is to ask for ownership of the module so that he can upload a new version. Six months is a reasonable waiting period for this, IMO. how can it be done? Mail Simon one more time, saying that since he doesn't seem to be interested in updating the module any more you would like to upload a version with your fix in it. CC modules@perl.org on your message, to provide evidence that you've done this. If Simon hasn't responded to your message within a few weeks then write to modules@perl.org drawing their attention to this and asking to be made a co-maintainer of the module. and what is AWOL ? Absent without leave -- a military term for somebody who is missing without permission. I wrote email to Simon. cced to modules@perl.org and module-authors@perl.org from different address, moderetors Please approve it that we have proof. signature.asc Description: OpenPGP digital signature
