develooper Front page | perl.perl5.porters | Postings from July 2014

Re: Criteria for becoming/dropping a core module [was: Re:maintainer wanted: Time::Piece]

Thread Previous | Thread Next
From:
Abigail
Date:
July 30, 2014 15:41
Subject:
Re: Criteria for becoming/dropping a core module [was: Re:maintainer wanted: Time::Piece]
Message ID:
20140730154117.GA17802@almanda.fritz.box
On Wed, Jul 30, 2014 at 11:09:54AM -0400, Jarkko Hietaniemi wrote:
> On Wednesday-201407-30, 5:26, Neil Bowers wrote:
>>   1. Needed to install perl. Eg various Test::*
>>   2. Modules (especially pragmata) that are considered to be part of the language. strict/warnings/Carp
>>   3. Toolchain modules needed to bootstrap your environment. Eg CPAN
>>   4. Modules for talking to your environment / glue. Eg Cwd, Fcntl, File::Spec*
>>   5. Codifies best practice in a way that's seen as a good thing ("everyone will/should want to use it"). autodie?
>>   6. "Batteries included" - stuff that "everyone" does, so makes sense to come in the box. Eg Getopt::Std, HTTP::Tiny
>
> Nice hierarchy.  Yes, Time::Piece was an attempt in #5.
>
> Though I'd like to squeeze in #4.5... "modules where tight bundling with  
> core is necessary/useful", like the B::
>
> I'd be all for squeezing out all that do not pass #1-#4.  But backward  
> compat: at what release would we set the "grandfather line"?
>


I'd say, drop those when it becames a hassle to keep. But as long as
they're keep passing tests (or can be made to pass them without much
fuss), I don't see a reason to drop them. (I think this is similar to
what Rjbs suggested).



Abigail

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About