Re: elections for PEAR Group commence in 1 day

From: Date: Thu, 19 Apr 2007 05:34:20 +0000
Subject: Re: elections for PEAR Group commence in 1 day
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-46288@lists.php.net to get a copy of this message
On 4/19/07, Gregory Beaver <greg@chiaraquartet.net> wrote:
Hello, The first elections for the new PEAR Group will commence in about 24 hours, and last until May 1. The candidates, listed at http://pear.php.net/election/info.php?election=7&vote=1, are: David Coallier http://pear.php.net/user/davidc
Bertrand Mansion        http://pear.php.net/user/mansion
Christian Weiske        http://pear.php.net/user/cweiske
Helgi Þormar    http://pear.php.net/user/dufuz
Arnaud Limbourg         http://pear.php.net/user/arnaud
Martin Jansen http://pear.php.net/user/mj Paul M. Jones http://pear.php.net/user/pmjones
Joe Stump       http://pear.php.net/user/jstump
Joshua Eichorn http://pear.php.net/user/jeichorn
Brett Bieber    http://pear.php.net/user/saltybeagle
Stefan Neufeind         http://pear.php.net/user/neufeind
If you wish to run, you have about 24 hours left to declare candidacy. If each candidate would be willing to describe their ideals (or specific plans) for moving PEAR forward, this may be helpful for those who are going to be voting. 7 candidates will be selected for the PEAR Group. This election is the big one: the PEAR Group will make decisions that affect every single developer, including defining what a collective is, which packages belong to which collectives, assigning CVS karma for developers, and other vitally important tasks. Thanks, Greg
Well well well, I am pretty sure this is the beginning of a long threaded-mail-campaign but I would still like to mention a few points why I am running and why you should vote for me *shrug*. 1. I am and have been devoted to pear for the past years and working a lot on both the outside world (Promoting PEAR in companies and PHP communities) and development of different PEAR packages as well as helping other people with their packages. I am an easy going person that is a good communicator and likes to work in teams, hence the pear-group interactions and communications. 2. I have many great ideas to improve both developers experience within the usage and deployment of PEAR packages, and the reputation of pear itself by having a repository of packages with better quality of the code in PEAR, bug fixing/bug reporting. 3. I am planning on defining and driving the future of PEAR; how we can evolve, improve RFCs, improve Coding Standards, improve Naming Conventions, etc. 4. Moreover, PEAR is not only a repository, with the channeling system we have now, I believe this can bring much more coverage and power to PEAR as a whole and as a community and this is another point I am planning on working on in order to make it evolve further than it already is! 5. With the upcoming PEAR2 (PHP5 Only) I believe there will be a lot of work and decisions that have to be made in order to bring this to another level, I have been present since the first days of the word PEAR2 (which was actively refused a year or two back) but now, we have the chance to make this happen with a decent decision power. 6. I am also the mentor of the jaws project in google summer of code which is being developed using PHP6, therefore the point was that I am not only involved in PEAR, but I am also involved in PHP itself, and other open source softwares. Moreover, I am not only a PHP Person, I have and still work a lot with javascript, I have reviewed a few books for instance HTML_AJAX (By Joshua Eichorn), and other books for jQuery, Prototype/Scriptaculous, etc. I am very involved and I strongly believe in Open Source Software and it's Model. I want to make a difference and I can as I work with/on PEAR daily. I am present on both the mailing lists and on IRC. 7. I want to make an improvement to the documentation system! Anyone who worked with PEAR knows that many many packages don't have end-user documentation, and it could be a good time to bring and implement a way of doing documentation that wouldn't be too much of a hassle (and also make developers realize that the documentation is as important as the code and shouldn't be a small task, but it isn't something as boring as it can seem. This is something we have to improve greatly; Making the documentation writing attractive to PEAR developers. You probably noticed that I didn't list the packages I am working on as you can all see this on http://pear.php.net/user/davidc so if you want to look at them, be my guest and go ahead :). I am ready to do some work, and I am not scared of the problems it might involve! I hope you'll make the right choice :) -- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18

« previous php.pear.dev (#46288) next »