Re: FW: [pear-webmaster] proposal: PEAR Who's Who on zend.com
| From: | Helgi Þormar | Date: | Tue, 11 May 2004 14:17:24 +0000 |
| Subject: | Re: FW: [pear-webmaster] proposal: PEAR Who's Who on zend.com | ||
| References: | 1 | Groups: | php.pear.webmaster |
| Request: | Send a blank email to pear-webmaster+get-2251@lists.php.net to get a copy of this message | ||
On Tue, 2004-05-11 at 14:14, Steph wrote:
> oops, missed the list - re-sending, sorry.
>
>
> Hi Helgi,
>
> Thanks for the quick response :)
>
> I agree that direct access to the database is a bad idea 'even for Zend',
> but would it be possible to set up (for example) a cron job that sends out a
> weekly email giving the information we need here?
>
> The secondary problem is that if we use the information from the user
> database without having any indication of activity we'll get people like
> myself on there - it seems that everyone with a php.net account was given a
> PEAR account regardless of whether they were involved in making PEAR
> contributions...
That's were the maintains table comes in :) I my self made a little bug
stats for pear (yet to public) and there you can find bugs in all pages
where X developer is in maintain of some sort (lead, developer, helper,
contribuer etc.) so really in stead of getting all the users .... I get
the users that have their ID in the maintain table :)
Not sure with that all php.net account == pear account but indeed seems
so :)
The cron job stuff can infact be done (I myself can even do that if I
get the info what you need, but well martin will have to add the cron
stuff but I can code the php part, shouldn't be a problem.)
But would email be the way to go ? Not so sure about that one :) Unless
you people at zend want to go through ~100 users per email :) hehe or
well you could of cause make some parser for that job, any way that is
in you best needs really, we can probly make something that you can use
to make Who's Who page :)
Maybe would be a good idea to list up all the needed info and etc., and
we can see what we can do about that :)
--
Regards
Helgi