Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:34766
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.146.181 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=S3O9r3Lo3HC1aUSMJ2QdkWwshsYIQrBJkyHIF0nDZ7rH7YiKHlLtkShCMRJv9jirbYBRv+W9JwHI3U10hkIGGPLefcQZNZzXcymD+zikbZKaM1spI5qkAJyssfFiDkHXsQ4mVkIg7LBgrAK5OA4z4cfrFmpfzSTNEtTGqFUGTiY=
Message-ID: <b5f7bf6c0801121625s500bf24fufa8ca53bf05a2b73@mail.gmail.com>
Date: Sat, 12 Jan 2008 19:25:48 -0500
Sender: david.coallier@gmail.com
To: "Gregory Beaver" <greg@chiaraquartet.net>
Cc: "Lukas Kahwe Smith" <smith@pooteeweet.org>, 
	"PHP Developers Mailing List" <internals@lists.php.net>
In-Reply-To: <4788D546.10108@chiaraquartet.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <B7554978-DB8C-4D41-BF2A-38C9C8F16965@pooteeweet.org>
	 <4788D546.10108@chiaraquartet.net>
Subject: Re: [PHP-DEV] Re: voting
From: davidc@php.net ("David Coallier")

On Jan 12, 2008 9:57 AM, Gregory Beaver <greg@chiaraquartet.net> wrote:
> Lukas Kahwe Smith wrote:
> > Hi,
> >
> > I think its painfully obvious that a system to manage the voting is
> > needed. Like I said, ideally it should also have an email interface.
> > People should be able to vote from +1 to -1 and be able to add a
> > comment. Notifications should be send to this list about the start and
> > final result of the vote.
> >
> > Voting itself should be split by people with access to cvs.php.net and
> > those that do not. This is open source, everybody can voice their
> > opinions, but the developers of the project should have final say.
> > However if the end user and developer votes diverge greatly it will
> > still be an important hint to take into account. That being said, end
> > user polling imho belongs somewhere else and before the final developer
> > vote.
> >
> > The features of PEPr in PEAR cover all of this quite well, except for
> > the email interface. I personally would not need that and maybe its too
> > much of a hassle to get this done in a reliable and secure way.
>
> PEPr, unfortunately, is very tightly bound to the pearweb code, and
> would be a big hassle to separate as it currently stands.  We have been
> working (by we, I mostly mean Helgi) for over a year now trying to clean
> up pearweb and still are only about halfway through the codebase, but
> when PEPr is tackled, I will let you all know.  Of course, if there is
> someone enterprising who wants to assist with that specific part of the
> cleanup, the code is in cvs at pearweb/.  PEPr-specific code is located
> in pearweb/include/pepr, pearweb/public_html/pepr, and
> pearweb/cron/pepr.php.
>

And if that entrepreneur-person needs tips about the pearweb code or
"mentoring", I'll be glad to help.


> Thanks,
> Greg
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



-- 
David Coallier,
Founder & Software Architect,
Agora Production (http://agoraproduction.com)
51.42.06.70.18