Consistent and concise Boilerplate code

[bschmalhofer]

Inspired by https://www.perl.com/article/announcing-perl-7/ I thought about adapting the standard boilerplate. I propose the following:

use v5.24;
use strict;
use warnings;
use namespace::autoclean;   # for modules
use utf8;
use open qw(:std :utf8);
use autodie qw(:2.29);
use Feature::Compat::Try;

# core modules

# CPAN modules

# OTOBO modules

See http://mvp.kablamo.org/cpan/exceptions/ and https://www.nntp.perl.org/group/perl.perl5.porters/2021/01/msg258856.html regarding Feature::Compat::Try.

There are many other suggestions for boilerplates:

• https://metacpan.org/release/common-sense

• https://metacpan.org/release/Defaults-Mauke

• https://metacpan.org/pod/Defaults::Mauke

The critical questions are:

• [ ] Is OTOBO prepared for https://metacpan.org/pod/feature#The-'unicode_strings'-feature ?

• [x] Is OTOBO prepared for https://metacpan.org/pod/feature#The-'unicode_eval'-and-'evalbytes'-features ?

• [ ] Is OTOBO ready for autodie ?

[bschmalhofer]

Set milestone to 11.0, because this might have repercussions.

[bschmalhofer]

The issues with https://metacpan.org/pod/feature#The-'unicode_eval'-and-'evalbytes'-features most likely no longer apply. The test scripts now run as separate scripts, eval is no longer involved there.

[bschmalhofer]

Updated the proposal to use https://metacpan.org/pod/Feature::Compat::Try.

[svenoe]

I'm against open and autodie, not for their respective features, but because in OTOBO for open Kernel::System::Main should be used anyways, and thus this and probably also autodie are mostly two lines which won't have any effect.