welcome to the Mojolicious core team Marcus Ramberg and Glen Hinkle

mojolicious · Dec 9, 2011 · 5628dfb · 5628dfb
1 parent 0776a44
commit 5628dfb
Show file tree

Hide file tree

Showing 5 changed files with 20 additions and 7 deletions.
diff --git a/Changes b/Changes
@@ -1,6 +1,9 @@
 This file documents the revision history for Perl extension Mojolicious.
 
-2.37    2011-12-07 00:00:00
+2.37    2011-12-09 00:00:00
+        - Welcome to the Mojolicious Core Team Marcus Ramberg and Glen
+          Hinkle.
+        - Improved documentation.
         - Improved unicode tests.
         - Fixed inline template double encoding bug.
 

diff --git a/Makefile.PL b/Makefile.PL
@@ -29,7 +29,7 @@ WriteMakefile(
           license     => 'http://dev.perl.org/licenses/',
           MailingList => 'http://groups.google.com/group/mojolicious',
           repository  => 'http://github.com/kraih/mojo',
-          bugtracker  => 'http://groups.google.com/group/mojolicious'
+          bugtracker  => 'http://github.com/kraih/mojo/issues'
         },
         no_index => {directory => [qw/t/]}
       },

diff --git a/lib/Mojolicious.pm b/lib/Mojolicious.pm
@@ -711,6 +711,12 @@ that have been used in the past.
 
 Sebastian Riedel, C<sri@cpan.org>.
 
+=head1 CORE DEVELOPERS
+
+Glen Hinkle, C<tempire@cpan.org>.
+
+Marcus Ramberg, C<mramberg@cpan.org>.
+
 =head1 CREDITS
 
 In alphabetical order:
@@ -785,8 +791,6 @@ Eugene Toropov
 
 Gisle Aas
 
-Glen Hinkle
-
 Graham Barr
 
 Henry Tang
@@ -819,8 +823,6 @@ Magnus Holm
 
 Maik Fischer
 
-Marcus Ramberg
-
 Mark Stosberg
 
 Matthew Lineen

diff --git a/lib/Mojolicious/Guides/CodingGuidelines.pod b/lib/Mojolicious/Guides/CodingGuidelines.pod
@@ -44,6 +44,13 @@ Code should be written with a Perl6 port in mind.
 
 No refactoring unless a very important feature absolutely depends on it.
 
+The addition and modification of features is decided by majority vote or the
+pumpking.
+
+New core developers must be accepted by a 2/3 majority vote.
+
+The pumpking has veto rights and may select his successor.
+
 It's not a feature without a test and documentation.
 
 A feature is only needed when the majority of the userbase benefits from it.

diff --git a/lib/Mojolicious/Guides/FAQ.pod b/lib/Mojolicious/Guides/FAQ.pod
@@ -98,7 +98,8 @@ right.
 Writing a test is usually the hardest part of fixing a bug, so the better
 your test case the faster it can be fixed. ;)
 
-Once that's done you can contact the developers via mailing list
+Once that's done you can contact the developers via via GitHub
+(https://github.com/kraih/mojo/issues), mailing list
 (L<http://groups.google.com/group/mojolicious>) or IRC
 (C<#mojo> on C<irc.perl.org>).