[engit/enperl-site.git] / enlightenedperl.org / grants / grants001.html

<html>
  <head>
  <title>Enlightened Perl Organisation</title>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
    <meta name="description" content="Enlightened Perl Organisation: Not-for-profit guaranteed limited company" />
    <meta name="keywords" content="enlightened perl, epo, perl" />
    <meta name="author" content="Mark Keating" />
    <meta name="copyright" content="2008 Enlightened Perl Organisation" />

    <link rel="stylesheet" type="text/css" href="http://www.enlightenedperl.org/style/reset.css" />
    <link rel="stylesheet" type="text/css" href="http://www.enlightenedperl.org/style/basic.css" />
    <link rel="stylesheet" type="text/css" href="http://www.enlightenedperl.org/style/layout.css" />
    <link rel="stylesheet" type="text/css" href="http://www.enlightenedperl.org/style/forms.css" />

    <link rel="shortcut icon" href="favicon.ico" />

<!--[if lt IE 8]>
	<link rel="stylesheet" href="style/lt_ie7.css" />
<![endif]-->
</head>

  <body>

    <div id="wrap">

      <div id="header-left">
        <p class="pad">
          &nbsp;&nbsp;
        </p>
      </div>


      <div id="header-middle">
        <p class="pad">&nbsp;
          
        </p>
      </div>
 
      <div id="header-text">
         <h1 class="title">
            enlightened perl organisation
          </h1>
          <p class="dict">
          <strong>enlightened</strong> |en'litnd|: <em>adjective</em>:<br />
          having or showing a rational, 
          modern, and well-informed outlook </p>
      </div>

      <div id="header-right">
        <p class="pad">
          &nbsp;&nbsp;
        </p>
      </div>

      <div id="nav">
        <a href="http://www.enlightenedperl.org/index.html">Home</a> |
        <a href="http://www.enlightenedperl.org/about.html">About</a> |
        <a href="http://www.enlightenedperl.org/project.html"> Projects</a> |
        <a href="http://www.enlightenedperl.org/grants.html"> Grants</a> |
        <a href="http://www.enlightenedperl.org/form/"> Membership</a> |
        <a href="http://www.enlightenedperl.org/rules.html"> Rules</a> |
        <a href="http://www.enlightenedperl.org/donate.html"> Donations</a> |
        <a href="http://www.enlightenedperl.org/logos.html"> Logos/Buttons</a> |
        <a href="http://www.enlightenedperl.org/board.html"> Board</a> |
        <a href="http://www.enlightenedperl.org/contact.html"> Contact</a>
      </div>


      <div id="main"> 

          <div id="content">

            <h1>
              Document Bounties #1
            </h1>

            <p>
              The Membership voted on the series of proposals for Document Bounties. 
              The results are listed below on a chart, the original proposals follow.<br /><br />
            </p>
            
            <p>
              <img src="http://spreadsheets.google.com/pub?key=ri-jlG1BzaoSdHGNYCgl1pA&oid=4&output=image" /><br /><br />
              <img src="http://spreadsheets.google.com/pub?key=ri-jlG1BzaoSdHGNYCgl1pA&oid=5&output=image" /><br /><br />
              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.
            <p>
            
            <p>
              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.
            </p>
            
            <p>
              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
              &pound;450, &pound;450 and &pound;300 (GBP) respectively.
            </p>
            
            <p>
              <b>[Proposal One]</b><br />
              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.
            </p>
            
            <p>
              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.<br /><br />
            </p>
            
            <p>
              <b>[Proposal Two]</b><br />
              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.<br /><br />
            </p>
            
            <p>
              <b>[Proposal Three]</b><br />
              HTTP::Engine - brilliant project, lousy english docs. Could really do with a clean overview, 
              reworked references docs, and maybe a cookbook.<br /><br />
            </p>
            
            <p>
              <b>[Proposal Four]</b><br />
              Enlightened Moose - using MooseX::Declare, MooseX::Types, Moose::Autobox and friends 
              together to get the most out of Moose and the nicest syntax.<br /><br />
            </p>
            
            <p>
              <b>[Proposal Five]</b><br />
              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.<br /><br />
            </p>
            
            <p>
              <b>[Proposal Six]</b><br />
              A "Why Enlightened Perl" white paper aimed at either tech managers or perhaps even C-level.<br /><br />
            </p>
            
            <p>
              <b>[Propoal Seven]</b><br />
              DBIx::Class Tutorial (introductory)<br /><br />
            </p>
            
            <p>
              <b>[Proposal Eight]</b><br />
              Moose Tutorial (introductory)<br /><br />
            </p>
            
            <p>
              <b>[Proposal Nine]</b><br />
              Embedding workflow in Catalyst using WPDL<br /><br />
            </p>
            
            <p>
              <b>[Proposal Ten]</b><br />
              Padre - Perl IDE<br /><br />
            </p>
            
            <p>
              <b>[Proposal Eleven]</b><br />
              Write a set of pages for developer.yahoo.com/perl/ (and feed any discoveries 
              into the Extended Core project)<br /><br />
            </p>
            
            <p>
              <b>[Proposal Twelve]</b><br />
              A set of examples - walkthroughs on projects using the Extended Core as tutorial material.<br /><br />
            </p>
            
            <p>
              <b>[Proposal Thirteen]</b><br />
              Performance optimization and scalability for Catalyst.<br /><br />
            </p>
            
            <p>
              <b>[Proposal Fourteen]</b><br />
              a roadmap on the bigger landmarks inside perl core, and introduce people to the code base
            </p>
                       
          </div>

          <div id="linknews">
 <!--            <div id="latest">
             <h4>
                Grants
              </h4>
              <ul>
                <li>
                  ?
                </li>

            <hr /> -->
              <h4>
                Links
              </h4>
            <script type="text/javascript"  src="http://adserver.szabgab.com/ads/direct_link_selflink.js?cnt=8">
            </script>
          </div>

        <div id="footer">
          Copyright &copy;2008-09 Enlightened Perl Organisation
        </div>
      </div>


    </div>


    <!-- GOOGLE ANALYTICS CODE -->
<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-2382391-3";
urchinTracker();
</script>
    
  </body>
</html>
Commit	Line	Data
abf82377	1	<html>
	2	<head>
	3	<title>Enlightened Perl Organisation</title>
	4	<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
	5	<meta name="description" content="Enlightened Perl Organisation: Not-for-profit guaranteed limited company" />
	6	<meta name="keywords" content="enlightened perl, epo, perl" />
	7	<meta name="author" content="Mark Keating" />
	8	<meta name="copyright" content="2008 Enlightened Perl Organisation" />
	9
	10	<link rel="stylesheet" type="text/css" href="http://www.enlightenedperl.org/style/reset.css" />
	11	<link rel="stylesheet" type="text/css" href="http://www.enlightenedperl.org/style/basic.css" />
	12	<link rel="stylesheet" type="text/css" href="http://www.enlightenedperl.org/style/layout.css" />
	13	<link rel="stylesheet" type="text/css" href="http://www.enlightenedperl.org/style/forms.css" />
	14
	15	<link rel="shortcut icon" href="favicon.ico" />
	16
	17	<!--[if lt IE 8]>
	18	<link rel="stylesheet" href="style/lt_ie7.css" />
	19	<![endif]-->
	20	</head>
	21
	22	<body>
	23
	24	<div id="wrap">
	25
	26	<div id="header-left">
	27	<p class="pad">
	28
	29	</p>
	30	</div>
	31
	32
	33	<div id="header-middle">
	34	<p class="pad">
	35
	36	</p>
	37	</div>
	38
	39	<div id="header-text">
	40	<h1 class="title">
	41	enlightened perl organisation
	42	</h1>
	43	<p class="dict">
	44	<strong>enlightened</strong> \|en'litnd\|: <em>adjective</em>:<br />
	45	having or showing a rational,
	46	modern, and well-informed outlook </p>
	47	</div>
	48
	49	<div id="header-right">
	50	<p class="pad">
	51
	52	</p>
	53	</div>
	54
	55	<div id="nav">
	56	<a href="http://www.enlightenedperl.org/index.html">Home</a> \|
	57	<a href="http://www.enlightenedperl.org/about.html">About</a> \|
	58	<a href="http://www.enlightenedperl.org/project.html"> Projects</a> \|
	59	<a href="http://www.enlightenedperl.org/grants.html"> Grants</a> \|
	60	<a href="http://www.enlightenedperl.org/form/"> Membership</a> \|
	61	<a href="http://www.enlightenedperl.org/rules.html"> Rules</a> \|
	62	<a href="http://www.enlightenedperl.org/donate.html"> Donations</a> \|
	63	<a href="http://www.enlightenedperl.org/logos.html"> Logos/Buttons</a> \|
	64	<a href="http://www.enlightenedperl.org/board.html"> Board</a> \|
65	<a href="http://www.enlightenedperl.org/contact.html"> Contact</a>
66	</div>
67
68
69
70	<div id="main">
71
72	<div id="content">
73
74	<h1>
75	Document Bounties #1
76	</h1>
77
78	<p>
79	The Membership voted on the series of proposals for Document Bounties.
80	The results are listed below on a chart, the original proposals follow.<br /><br />
81	</p>
82
83	<p>
84	<img src="http://spreadsheets.google.com/pub?key=ri-jlG1BzaoSdHGNYCgl1pA&oid=4&output=image" /><br /><br />
85	<img src="http://spreadsheets.google.com/pub?key=ri-jlG1BzaoSdHGNYCgl1pA&oid=5&output=image" /><br /><br />
86	As you can see from the above chart the voting between Ordinary members and Special Members was
87	very similar. Special members voted proposal 5 as most useful with proposals 4, 3 and 1 occupying
88	joint second place. Ordinary members voted proposals 1 and 4 as joint first followed by 13 and the 5
89	in second and third place. Combined totals place us at 1, 4 and 5 all occupying joint first place,
90	followed by 3, then by 13.
91	<p>
92
93	<p>
94	Organisational rules dictate that the vote from ther Ordinary membership carries. The Special membership
95	vote was used to help break ties in voting, in this case it is clear that the Special members vote
96	does not break the tie between proposals 1 and 4.
97	</p>
98
99	<p>
100	When the decision was placed before the Directors it was noted that Proposals 5 and 7 were very similar in nature.
101	If the scores were combined for proposals 5 and 7 it would place this into equal first place with proposals
102	1 and 4. The Directors therefore decided to award three grants to proposals 1, 4 and 5 for the sums of
103	£450, £450 and £300 (GBP) respectively.
104	</p>
105
106	<p>
107	<b>[Proposal One]</b><br />
108	An update to POE docs. With the rise of Moose, I can see a lot of uses to mix and blend the two
109	to form servers with OO-based dispatch, better event driven GUI applications with clear separation
110	of concerns and other things.
111	</p>
112
113	<p>
114	The way things are now it's kind of spread all over the place and it would be nice if someone
115	could structure it better, from the standpoint of a newcomer to POE. Event driven architecture
116	is very different from procedural (and for that matter OO-based) programming, so some introductory
117	information about terminology and potential articles/books on the subject would be nice to include.<br /><br />
118	</p>
119
120	<p>
121	<b>[Proposal Two]</b><br />
122	I would also suggest maybe to add another layer on top of the website that identifies you based
123	on competency level, this way it's easier to get started. I'm pretty sure there's a lot of docs
124	there, they just need better organization.<br /><br />
125	</p>
126
127	<p>
128	<b>[Proposal Three]</b><br />
129	HTTP::Engine - brilliant project, lousy english docs. Could really do with a clean overview,
130	reworked references docs, and maybe a cookbook.<br /><br />
131	</p>
132
133	<p>
134	<b>[Proposal Four]</b><br />
135	Enlightened Moose - using MooseX::Declare, MooseX::Types, Moose::Autobox and friends
136	together to get the most out of Moose and the nicest syntax.<br /><br />
137	</p>
138
139	<p>
140	<b>[Proposal Five]</b><br />
141	DBIx::Class for people who like SQL - working back from SQL queries to DBIC usage step
142	by step to demonstrate you can produce the exact same queries with DBIc that you would by hand.<br /><br />
143	</p>
144
145	<p>
146	<b>[Proposal Six]</b><br />
147	A "Why Enlightened Perl" white paper aimed at either tech managers or perhaps even C-level.<br /><br />
148	</p>
149
150	<p>
151	<b>[Propoal Seven]</b><br />
152	DBIx::Class Tutorial (introductory)<br /><br />
153	</p>
154
155	<p>
156	<b>[Proposal Eight]</b><br />
157	Moose Tutorial (introductory)<br /><br />
158	</p>
159
160	<p>
161	<b>[Proposal Nine]</b><br />
162	Embedding workflow in Catalyst using WPDL<br /><br />
163	</p>
164
165	<p>
166	<b>[Proposal Ten]</b><br />
167	Padre - Perl IDE<br /><br />
168	</p>
169
170	<p>
171	<b>[Proposal Eleven]</b><br />
172	Write a set of pages for developer.yahoo.com/perl/ (and feed any discoveries
173	into the Extended Core project)<br /><br />
174	</p>
175
176	<p>
177	<b>[Proposal Twelve]</b><br />
178	A set of examples - walkthroughs on projects using the Extended Core as tutorial material.<br /><br />
179	</p>
180
181	<p>
182	<b>[Proposal Thirteen]</b><br />
183	Performance optimization and scalability for Catalyst.<br /><br />
184	</p>
185
186	<p>
187	<b>[Proposal Fourteen]</b><br />
188	a roadmap on the bigger landmarks inside perl core, and introduce people to the code base
189	</p>
190
191	</div>
192
193	<div id="linknews">
194	<!-- <div id="latest">
195	<h4>
196	Grants
197	</h4>
198	<ul>
199	<li>
200	?
201	</li>
202
203	<hr /> -->
204	<h4>
205	Links
206	</h4>
207	<script type="text/javascript" src="http://adserver.szabgab.com/ads/direct_link_selflink.js?cnt=8">
208	</script>
209	</div>
210
211	<div id="footer">
212	Copyright ©2008-09 Enlightened Perl Organisation
213	</div>
214	</div>
215
216
217
218	</div>
219
220
221
222	<!-- GOOGLE ANALYTICS CODE -->
223	<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
224	</script>
225	<script type="text/javascript">
226	_uacct = "UA-2382391-3";
227	urchinTracker();
228	</script>
229
230	</body>
231	</html>