Re: candidates for PEAR Group: why should we vote for you? Tell us your plans and your history
| From: | David Coallier | Date: | Sat, 20 Jun 2009 17:05:21 +0000 |
| Subject: | Re: candidates for PEAR Group: why should we vote for you? Tell us your plans and your history | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-52002@lists.php.net to get a copy of this message | ||
2009/6/20 Dmitri Snytkine <d.snytkine@gmail.com>
> Does the pear president get paid? If not, then what are the benefits for
> being pear president? Is it just a bragging rights?
>
>
Hi there Dmitri and everyone, first of all sorry for not replying sooner,
the last few weeks have been simply overbooked and overworked :)
So I'll reply first to your question Dmitri by saying that the job of the
PEAR President is not to "brag with rights" in fact, the president doesn't
have any right until there's a tie within the PEAR Group. They are the ones
with rights and real "PEAR" work to do.
The job of the president is to represent PEAR socially and virtually.
Basically to give you an idea, last year I was going around barcamps and
non-php conferences across Europe and chatting to people about PEAR. Mainly
trying to identify their fears and dissolve the myths that hang around PEAR
while informing as many people as possible about the upcoming PEAR2 and
Pyrus.
The reason for me for choosing non php conferences last year was to work on
getting new developers from other languages to bring in their inputs and
knowledge to PHP. There hasn't been many yet but a few did come around and
asked questions about standards, distributing, etc. Which is imho a good
start.
Another task of the president is to keep good relations with the PHP
internals. This year there has been a few issues and I have done the best of
my capacities to keep the best relations with internals. I'd like to take
the opportunity to thank Christian Weiske for the amazing work done to keep
the relations going with the PHP Doc team and everyone else that was
involved as well.
What I would like to do in the next year (And already have started this by
discussing with other frameworks) is to bring back the idea that PEAR is a
"component" repository and that any general purpose code should be in PEAR.
Many of those companies/frameworks have strict politics so it's a long and
overwhelming process but I'm confident that we can clean PEAR's image and
bring in fresh talent.
Hope this helps you a bit understanding what is the president's role :)
--
Slan,
David