On Fri, Nov 11, 2011 at 01:30:38PM -0800, Bill Ward wrote:
How about just do it by author - if any of the author's distros are idle
for 6 months, send them an email?
No. It's pointless. We already have a system that works, so let's not
try to fix it.
--
David Cantrell | Cake Smuggler
On 11-11-11 06:29 PM, Aristotle Pagaltzis wrote:
Considering the nature of CPAN, I tend to agree. Trying to force it
everyone's throat would be the best way to quickly and utterly doom
the project. And probably ensure to wake up one morning with a camel's
head in our bed.:-)
Or a severed
On Nov 10, 2011, at 4:41 PM, Neil Bowers wrote:
I hereby give modu...@perl.org permission to grant co-maintainership
to any of my modules, if the following conditions are met:
(1) I haven't released the module for a year or more
(2) There are outstanding issues on RT which need
On 11/10/2011 9:33 PM, David Nicol wrote:
I think this is not necessary at all. I think you have pretty much
described the current standards for granting takeover. I think the
barrier to making local forks is already very low and there is no
reason to switch the whole thing to Git.
Yeah,
On Nov 11, 2011, at 9:20 AM, John M. Gamble wrote:
I think the barrier to making local forks is already very low and there is no
reason to switch the whole thing to Git.
I usually use gitpan when I want to fork a module and can't find it's source
history. https://github.com/gitpan
On 2011-11-11, at 10:52, Todd Rinaldo to...@cpanel.net wrote:
On Nov 11, 2011, at 9:20 AM, John M. Gamble wrote:
I think the barrier to making local forks is already very low and there is
no reason to switch the whole thing to Git.
I usually use gitpan when I want to fork a module and
On Fri, Nov 11, 2011 at 11:53:15AM -0500, Olaf Alders wrote:
Gitpan is no longer actively maintained AFAIK. See the issues list for how to
revive it.
And that's my cue to point out that while Gitpan isn't updated,
you can still use Git::CPAN::Patch, the module Gitpan is using under
On 2011-11-10, at 6:27 PM, Neil Bowers wrote:
2. Maintainer wants help
The other case is when a maintainer is still around, but either doesn't want
to maintain a distribution anymore, or wouldn't mind a wee bit of help.
[...]
Maybe the solution to (1) and (2) lies with a site that
On Fri, Nov 11, 2011 at 2:43 PM, yan...@babyl.dyndns.org wrote:
On Thu, Nov 10, 2011 at 11:27:04PM +, Neil Bowers wrote:
Interesting thought. How about:
- if a distribution author appears to be inactive, then the author
would receive an email to their registered
CPAN
* yan...@babyl.dyndns.org yan...@babyl.dyndns.org [2011-11-11 22:30]:
On Thu, Nov 10, 2011 at 11:27:04PM +, Neil Bowers wrote:
I think this would still have to be a mechanism that an author has
to sign up to, rather than it automatically being applied.
Considering the nature of CPAN, I
I am against the 'if I die' part. As we are all communication over the net,
it is very difficult to know why a person have stopped responding.
And it make the statement a bit scary.
Shmuel.
On Wed, Nov 9, 2011 at 1:22 AM, Neil Bowers n...@bowers.com wrote:
One of the problems I see with CPAN
Original-Nachricht
Datum: Tue, 8 Nov 2011 16:22:02 +
Von: Neil Bowers n...@bowers.com
An: module-authors@perl.org
Betreff: The module authors pledge
One of the problems I see with CPAN is that there are many modules
which have been left unattended. Many of these have
Il 08/11/2011 17:22, Neil Bowers ha scritto:
Should I die, then the time-limits in (1) and (3) do not apply.
Drop this, as difficult to verify (for various reasons), and +1 from me.
-- bronto
On Thu, 2011-11-10 at 18:50 +0900, Shmuel Fomberg wrote:
I am against the 'if I die' part. As we are all communication over the
net, it is very difficult to know why a person have stopped
responding.
And it make the statement a bit scary.
The real problem with 'if I die' is that there is no
On 11/08/2011 04:22 PM, Neil Bowers wrote:
One of the problems I see with CPAN is that there are many modules
which have been left unattended. Many of these have outstanding bugs,
and a good number have patches and forked versions, some of which you can
find on RT. You'll also find people
On Thursday 10 November 2011 09:50:08 Shmuel Fomberg wrote:
I am against the 'if I die' part. As we are all communication over the net,
it is very difficult to know why a person have stopped responding.
And it make the statement a bit scary.
Hmm - if it's someone reasonably well known in the
On Tue, Nov 8, 2011 at 5:22 PM, Neil Bowers n...@bowers.com wrote:
One of the problems I see with CPAN is that there are many modules
which have been left unattended. Many of these have outstanding bugs,
and a good number have patches and forked versions, some of which you can
find on RT.
On 11/10/2011 11:11 AM, Neil Bowers wrote:
If someone comes along and thinks hey, this would be useful, and I can
improve it,
we should make it easier for the baton to be passed on, as it will improve
the overall quality
of CPAN.
All the while still respecting the original author [1]
My
I've been having the same idea. I'd say the right place is a clearly
named file your CPAN home dir, preferably something explicit and
standardized about when you're ok with it and when not.
Metadata can already be attached to distributions in an extensible
fashion. It's really about the code,
On Thu, Nov 10, 2011 at 1:32 PM, Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 da...@cpan.org wrote:
Metadata can already be attached to distributions in an extensible
fashion. It's really about the code, not the author/maintainer - one
can have different opinions on/policies for different distros.
True, though most of
On Tue, Nov 08, 2011 at 04:22:02PM +, Neil Bowers wrote:
I hereby give modu...@perl.org permission to grant co-maintainership
to any of my modules, if the following conditions are met:
(1) I haven't released the module for a year or more
(2) There are outstanding issues
I think the Should I die (though I think in the event of my death would
be better) can only really work if a family member replies to the email
saying that the maintainer has passed away, which isn't too likely but
could happen. Since those time limits would expire eventually anyway, it's
probably
On 11-11-08 11:22 AM, Neil Bowers wrote:
To make life easier for the perl modules cabal, how about a voluntary
pledge
Nice idea. I like.
I've been mulling about the same problem in my corner, so here are my 2
canadian cents' worth on the topic:
As I see it, there are two aspects to
Shmuel wrote:
I am against the 'if I die' part. As we are all communication over the net,
it is very difficult to know why a person have stopped responding.
And it make the statement a bit scary.
And Raphael wrote:
The real problem with 'if I die' is that there is no way of knowing: the
TL;DR: yeah, what they said.
Boyd wrote:
In essence, you're trying to elicit from the authors how they feel about
their module, either:
* I'm easy. I just want it to be useful to people.
* That's my _baby_ you're talking about!
which hides the ugly and bureaucratic detail you're
Being on the patch submitting side of this, I'll put in my 2 pence.
For the last 2 years, I've been bugging one CPAN author to apply my patch
that fixes a bug in RT. He says, I've moved to GitHub. Fork my project and
issue a pull request. [...]
I've got a few of those going on.
But in
I hereby give modu...@perl.org permission to grant co-maintainership
to any of my modules, if the following conditions are met:
(1) I haven't released the module for a year or more
(2) There are outstanding issues on RT which need addressing
(3) Email to my CPAN email address
On 2011-11-10, at 5:36 AM, Neil Bowers wrote:
Shmuel wrote:
I am against the 'if I die' part. As we are all communication over the net,
it is very difficult to know why a person have stopped responding.
And it make the statement a bit scary.
And Raphael wrote:
The real problem with 'if
28 matches
Mail list logo
