Sponsored Content
The Lounge What is on Your Mind? Please Welcome Akshay Hegde to the Moderation Team Post 303038431 by Neo on Tuesday 3rd of September 2019 05:59:26 AM
Old 09-03-2019
Quote:
Originally Posted by RavinderSingh13
Thanks Neo for doing so Smilie

Welcome to MODs group Akshay Smilie

Thanks,
R. Singh
You are welcome Ravinder!

My goal is to bring even more diversity into the moderation team over the next year. Living and working in Asia for over 12 years, I'm really into the many benefits that diversity and different cultural backgrounds brings to all of us.

It's basically my theme for 2019 - Diversity is the Best Part of Life!

Also, I want some of our very long time contributors like Don, RudiC and bakunin to focus on answering questions and have more free time for technical Q&A in their area of expertise. Those guys are all great technical superstars in their respective areas of interest and they deserve a break from adding code tags, editing posts and enforcing the same old "boring" forum rules! The technical Q&A are much more fun than mundane adding tags and editing posts or giving infractions.
These 3 Users Gave Thanks to Neo For This Post:
 
Perl::Critic::More(3)					User Contributed Perl Documentation				     Perl::Critic::More(3)

NAME
Perl::Critic::More - Supplemental policies for Perl::Critic SYNOPSIS
perl -MCPAN -e'install Perl::Critic::More' perlcritic -theme more lib/Foo.pm AFFILIATION
This file has no functionality, but instead is a placeholder for a loose collection of Perl::Critic policies. All of those policies will have an "Affiliation" section announcing their participation in this grouping. DESCRIPTION
This is a collection of Perl::Critic policies that are not included in the Perl::Critic core for a variety of reasons: o Experimental Some policies need some time to work out their kinks, test usability, or gauge community interest. A subset of these will end up in the core Perl::Critic someday. o Requires special dependencies For example, some policies require development versions of PPI (or some other CPAN module). These will likely end up in the Perl::Critic core when their dependencies are fulfilled. o Peripheral to Perl For example, the "Editor::RequireEmacsFileVariables" policy is metacode. These are not part of Perl::Critic's mission. o Special purpose For example, policies like "CodeLayout::RequireASCII" designed to scratch itches not felt by most of the community. These will always remain in a Perl::Critic supplement instead of in the core. All of these policies have the theme "more" so they can be turned off as a group via .perlcriticrc by adding this line: theme = not more The special purpose ones may be part of the "notrecommended" theme. Avoid these via: theme = not notrecommended Sorry about the double-negative... See "CONFIGURATION" in Perl::Critic for details on how to interact with themes. SEE ALSO
Perl::Critic Perl::Critic::Bangs - Andy Lester's fantastic list of code pet peeves Perl::Critic::Lax - RJBS' more-lenient versions of some core Perl::Critic policies parrot - the parrot team has developed a few specialized Perl::Critic policies of their own AUTHOR
Chris Dolan <cdolan@cpan.org> The included policies may have other authors -- please see them individually. This distribution is controlled by the Perl::Critic team. If you want to add a policy to this collection, check out our Subversion repository and mailing lists at <http://perlcritic.tigris.org>. COPYRIGHT
Copyright (c) 2006-2008 Chris Dolan This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license can be found in the LICENSE file included with this module. perl v5.16.3 2014-06-10 Perl::Critic::More(3)
All times are GMT -4. The time now is 09:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy