On 01/31/2011 11:16 PM, Charles Morris wrote:
On Sat, Jan 22, 2011 at 3:39 AM, brian d foy<brian.d....@gmail.com> wrote:
[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article
<954223cb-548f-4908-87f8-4007b84c9...@f20g2000prn.googlegroups.com>,
gray<g...@cpan.org> wrote:
I am requesting ownership of the namespace Digest::CubeHash as the
current assignee has owned it for 3 months [1] and it is still unused.
This is a bit sticky because the author has very recently (three months
ago) noted interest in this module. That's not a very long time to have
disappeared, in my opinion. Charles, if you're listening, speak up even
to say "yes" or "no".
Is there another name that you might use for your distribution, even if
temporarily?
We typically don't make these judgements on anything other than
respecting the intent of the person who got there first. We don't
select on better, etc. We just try to make peacable transfers when
necessary, but in most cases try to get the people involved to work it
out themselves. :)
--
brian d foy (one of many PAUSE admins), http://pause.perl.org
PAUSE instructions: http://pause.perl.org/pause/query?ACTION=pause_04about
Archives: http://www.xray.mpe.mpg.de/mailing-lists/modules
Please send all messages back to modules@perl.org with no CC to me.
Hello :)
There are some problems in my opinion with transferring that namespace.
The module was intended to include a Pure-Perl implementation of the
CubeHash digest,
as well as the XS functionality implemented by Gray's module, and as
such it's taken
me more than 3 months to write; considering the responsibilities of
life and etc.
If I were to just hand the namespace over, I feel that the intended
implementation would never
be complete, and I am a bit dissatisfied with this outcome. Most
crypto stuff on CPAN is
lacking a PP implementation, I wanted CubeHash to be the first in a
long string of PP crypto
projects; due to its simplicity. People without C compilers should
have (slow) crypto too :)
On one hand, I registered the module to avoid this issue in the first place.
On the other hand, I understand Mr. Gray's conundrum as well,
it's hard to rename a module when it's sitting next to 14 others with
the same naming scheme.
Perhaps Mr. Gray has a solution to this problem?
If he will not rename his module,
I'd be willing to hand the namespace over if Gray included a Pure-Perl
implementation.
How about cooperation on a shared code base in a shared repository?
There'd be some initial redundancy as you merge your work, but in the
end, everybody wins.
Just saying :)
Best regards,
Steffen
