RE: [pear-webmaster] proposal: PEAR Who's Who on zend.com

Hi Steph! You wrote: > OK I'm back on it! > We've had an internal discussion and think, with you, that xml-rpc would be > a better way of going about things. > I made up (below) a rough list of the content we'd expect to see on there > (with the jobseeking aspect of this kind of list very much in mind). Base > info would be Name, PEAR packages and PEAR url; I have to admit that I've no > clue yet how the rest of the information's going to get in there as it's > obviously down to the individual developer, whether or not they want such > information online at all and when they would like to update it. Either > your database needs to be extended to accommodate this, or ours does. It > probably makes more sense for it to be ours, leaving the xml-rpc feed > consisting of the base information and the only issue the one of filtering > out those who aren't involved in developing/maintaining any package > whatsoever. The basic info can be replaced directly from PEAR through RPC. For the rest you can offer a simple editing form, which (if we implement this, what I hope) can be authenticated against the PEARWeb SSO mechanism. > Please feel free to argue with my list :) > Name > Thumbnail pic > Locale Birthdate > Occupation > Availability > Hobbies > Spoken Languages > Programming Languages --> Skill rate for languages (1-5 or so, slightly experienced - profi) > Expertise > Other Skills > PEAR packages (lead/developer/helper) --> Can be gathered from the PEAR DB also, I guess. > PEAR url --> Dito Other PEAR activities (Website, Documentation, Installer, QA,...) Job experinces? (Projects, ...) Other open source projects? Homepage URL Blog URL --> Maybe even aggregate the blogs? Just some thoughts, maybe you find them useful! Regards, Toby -- Tobias Schlitt a passion for php http://www.schlitt.info