Document Bounties #1
The Membership voted on the series of proposals for Document Bounties.
The results are listed below on a chart, the original proposals follow.
As you can see from the above chart the voting between Ordinary members and Special Members was
very similar. Special members voted proposal 5 as most useful with proposals 4, 3 and 1 occupying
joint second place. Ordinary members voted proposals 1 and 4 as joint first followed by 13 and the 5
in second and third place. Combined totals place us at 1, 4 and 5 all occupying joint first place,
followed by 3, then by 13.
Organisational rules dictate that the vote from ther Ordinary membership carries. The Special membership vote was used to help break ties in voting, in this case it is clear that the Special members vote does not break the tie between proposals 1 and 4.
When the decision was placed before the Directors it was noted that Proposals 5 and 7 were very similar in nature. If the scores were combined for proposals 5 and 7 it would place this into equal first place with proposals 1 and 4. The Directors therefore decided to award three grants to proposals 1, 4 and 5 for the sums of £450, £450 and £300 (GBP) respectively.
[Proposal One]
An update to POE docs. With the rise of Moose, I can see a lot of uses to mix and blend the two
to form servers with OO-based dispatch, better event driven GUI applications with clear separation
of concerns and other things.
The way things are now it's kind of spread all over the place and it would be nice if someone
could structure it better, from the standpoint of a newcomer to POE. Event driven architecture
is very different from procedural (and for that matter OO-based) programming, so some introductory
information about terminology and potential articles/books on the subject would be nice to include.
[Proposal Two]
I would also suggest maybe to add another layer on top of the website that identifies you based
on competency level, this way it's easier to get started. I'm pretty sure there's a lot of docs
there, they just need better organization.
[Proposal Three]
HTTP::Engine - brilliant project, lousy english docs. Could really do with a clean overview,
reworked references docs, and maybe a cookbook.
[Proposal Four]
Enlightened Moose - using MooseX::Declare, MooseX::Types, Moose::Autobox and friends
together to get the most out of Moose and the nicest syntax.
[Proposal Five]
DBIx::Class for people who like SQL - working back from SQL queries to DBIC usage step
by step to demonstrate you can produce the exact same queries with DBIc that you would by hand.
[Proposal Six]
A "Why Enlightened Perl" white paper aimed at either tech managers or perhaps even C-level.
[Propoal Seven]
DBIx::Class Tutorial (introductory)
[Proposal Eight]
Moose Tutorial (introductory)
[Proposal Nine]
Embedding workflow in Catalyst using WPDL
[Proposal Ten]
Padre - Perl IDE
[Proposal Eleven]
Write a set of pages for developer.yahoo.com/perl/ (and feed any discoveries
into the Extended Core project)
[Proposal Twelve]
A set of examples - walkthroughs on projects using the Extended Core as tutorial material.
[Proposal Thirteen]
Performance optimization and scalability for Catalyst.
[Proposal Fourteen]
a roadmap on the bigger landmarks inside perl core, and introduce people to the code base