Re: Notes and Policies and Stuff...Re: [PHP-NOTES] note 9179 modified in time by jmcastagnetto

--- Ron Chmara <ron@opus1.com> wrote: > jmcastagnetto@php.net wrote: > > [Editor's note. Yes. That is a fact that is well > known and tied to the OS. If this is not solved by > then, a malfunctioning in a script might be the > least of your troubles. BTW, using fake emails, in > particular the ones for the PHP list is a bad > thing.] > > > > Wouldn't relying on this function to do time > comparision will eventually bump into the Unix clock > overflow problem in year 2033? > > Uh... > > If there is no email submitted, it *defaults* to > php-general. Idea being that > this address would become sprinkled throughout the > manual, and when > people wanted to ask a question, maybe they'd click > on the php-general > email and start interacting with the list. So they > aren't forging, they're > simply not submitting their email address. OIC, I did not check the code for the note submission, so I assumed that it was a forge not a default that is was being added. My mistake, I'll remove that note, and add the comment to the description of the function, for those who do not know about the problem. > Also, > when we get the post on > PHP-notes, it isn't padded with the lovely path > information, or however the > different mail servers handle it respectively....(I > get full headers in > the body). Indeed. This is a good thing. > I also wonder if "adding" editors notes onto > questions is a good thing. It > seems to imply that not only is asking questions in > the errata okay, but > that PHP folks will personally answer, online. So it > *encourages* asking > questions, rather than discouraging it. What I've > been doing, (when it seems > to be an issue that needs answering, and I have an > answer), is adding a > separate contribution and then deleting the first > question. We *want* the > questions, and anything that appear to be questions, > to simply cease to > exist in the manual. Usually I tend to add comments to postings that are not questions, e.g. in cases of code that might not be secure or could have a secondary effect. I've been trying to be consistent, but this is not one of the cases. > Otherwise, people will see that questions are asked, > and somehow answered, > and assume that it must be okay behavior. Even if an > editor responds with > an answer in email it may invite additional > questions, because even though > their question was deleted, they got their answer... > so next time, rather > than ask the list, they can post an errata note and > get a "personal > response from the PHP team". Perhaps, we could agree on a boilerplate text that basically says: "wrong place to post this, send it to one of the support lists or the bug database". We could just copy/paste that when replying to the emails we get in the list, or we could have a "Reject" option in the on-line notes that will email back the person submitting the note w/ the boilerplate text, and remove the note. I would like the second option better. So we could have 3 options for an individual note: - Delete it w/o a notification (what we can do right now) - Reject it (email the submitter and remove it) - Edit it I agree w/ Ron's approach of consolidating submissions once in a while. I've done it only 2 or 3 times I think. Will take a look later at the notes admin code and see how easy would be to add a "Reject" option. > Thoughts? Comments? Flames? > > -Bop > > -- > Brought to you from boop!, the dual boot Linux/Win95 > Compaq Presario 1625 > laptop, currently running RedHat 6.1. Your bopping > may vary. > > -- > PHP Notes Mailing List (http://www.php.net/) > To unsubscribe, e-mail: > php-notes-unsubscribe@lists.php.net > For additional commands, e-mail: > php-notes-help@lists.php.net > To contact the list administrators, e-mail: > php-list-admin@lists.php.net > ===== --- Jesus M. Castagnetto (jcastagnetto@yahoo.com) __________________________________________________ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/