RE: [pear-webmaster] I should maybe point out here..

> This has nothing to do with anxiety of any sort, but I can imagine that > there are people who are concerned enough about their privacy to object > against being mentioned on sites they didn't explicitely subscribe to. Googled on your own name lately? I can promise you that any php.net involvement will _guarantee_ you're mentioned on all kinds of sites you didn't explicitly subscribe to! I even used that fact to get into America earlier this year when I had trouble proving my far-fetched tale of open source, cruise ships and student poverty to a sceptical immigration officer. Although I don't think this is what you meant, I'll say it now: Zend.com is not and never has been a subscription site. It's the company site for a company that happens to have been founded by two of the three people responsible for ever making PHP happen at all, both of whom are still a major force in PHP language development 8 years down the line from writing their initial language parser. Zend's always taken the community/php.net side of its hybridness very seriously indeed. The only reason I even set out to do this project in the first place was because the existing community pages were so outdated as to be misleading, and had to be 'disappeared'. A lot of the people who had slots on there keep asking when we're going to replace it, and that's basically what I'm trying to do - replace it, expand it, and keep it updated as automagically as we can. > The reason I didn't mention it was that I've only been thinking about > this lately. But I actually don't think that adding such a feature will > have any effect on your QA process: The only code that will be changed > is on PEAR's side. The way I have things set up at present, if you click on a package link and that package doesn't have an owner in the database, the package will magically cease to exist. So yes, it _does_ affect our end too; I based my design around the initial discussions we had, not things that are coming along as I complete it (or try to), and it already sounds as if I'm going to have to rewrite a fairly chunk of it due to the table business. Thankfully it's not the logic that needs rewriting in that case, just stuff like the number of array elements going into the db and being pulled out. Missing developers will mean that part of the logic at our end has to be rewritten too. It means I have to allow for the possibility of 'anon' - i.e. the information would still need to be in our db, but there'd need to be a bool 'public' or 'private', which I'd need to access all over the shop. Is it actually worth it? given that if you click on anon's packages you'll be faced with anon's name on the package page at pear.php.net? Why would anyone refuse to allow their name to be a link on zend.com when it's already public on pear.php.net and anywhere else that copies information from there? - that's a total mystery, and one I certainly didn't take into account when designing this beastie. If it were a privacy issue the information wouldn't be publicly available at pear.php.net. So there's something I'm missing here. I'll work around it if I _have_ to, but it'd be dishonest of me to say I don't mind doing it, or even that I appreciate why it needs to be done. > I'm afraid I understood you wrong back then: When you asked me about > this sort of stuff, I was under the impression that you wanted to set up > a new database at zend.com in which people could enter their > information. (IIRC I also asked a question like "we are talking about a > database at zend.com, no" and got a positive answer. But I'm likely to > be wrong.) Ah, in that case our entire conversation was at odds - I have the logs, it's possible to read either interpretation into it so long as you know what you're looking for. I guess we were both pushed for time :I > I don't think there is anyone here who objects against the project. We > just want to make sure that it fits in our infrastructure as nicely as > possible. So do I! Can we please work together now so that we can get this done quickly? This project's well past its due date.. Would the best place to start be with the user table structure? I don't think the zendWhoIsWho() function will need rewriting as such, but the changes I sent in for it in amongst those diffs earlier _are_ needed; I'm missing everyone with a PECL package and no PEAR connection at present. Cheers! - Steph