Consider that requirement a mandate from "on high". Not that I disagree with it, but it is one a few requirements "above the paygrade" of the WPTRT. :)<div><br></div><div>Chip<br><br><div class="gmail_quote">
On Thu, Nov 10, 2011 at 10:39 AM, Rick Anderson <span dir="ltr"><<a href="mailto:rick@byobwebsite.com">rick@byobwebsite.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Newbie question - I can't find the imperative against the use of fopen() type functions. Can you point me in the direction of a conversation about that?<div class="HOEnZb"><div class="h5"><br><br><div class="gmail_quote">
On Thu, Nov 10, 2011 at 7:34 AM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But that's the point: it *is* an imperative. That's the difference between being REQUIRED to do/not to do something, versus something being RECOMMENDED to do/not to do, or OPTIONAL.<div>
<br></div><div>For example: use of fopen() type functions: the requirement is imperative. They MUST NOT be used.</div>
<div><br></div><div><font color="#888888">Chip</font><div><div></div><div><br><br><div class="gmail_quote">On Thu, Nov 10, 2011 at 9:31 AM, Mario Peshev <span dir="ltr"><<a href="mailto:mario@peshev.net" target="_blank">mario@peshev.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would not like 'must not' as too imperative - 'should not' or<br>
'required to' + some other verb indicating negative sound better in my<br>
language at least.<br>
<br>
Best regards,<br>
<div><br>
Mario Peshev<br>
Training and Consulting Services @ DevriX<br>
<a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br>
<a href="http://devrix.com" target="_blank">http://devrix.com</a><br>
<a href="http://peshev.net/blog" target="_blank">http://peshev.net/blog</a><br>
<br>
<br>
<br>
<br>
</div><div><div>On Thu, Nov 10, 2011 at 5:29 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>> wrote:<br>
> We use the terminology from RFC 2119, in order to ensure consistency; so:<br>
> "required", "recommended", or "optional".<br>
> I suppose we could replace "required not" with "must not"?<br>
> Chip<br>
><br>
> On Thu, Nov 10, 2011 at 9:26 AM, Angelo Bertolli <<a href="mailto:angelo.bertolli@gmail.com" target="_blank">angelo.bertolli@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Maybe the word FORBIDDEN could be used instead if it makes it clearer.<br>
>><br>
>> On 11/10/2011 10:24 AM, Mario Peshev wrote:<br>
>> > Please do apologize my English, but as a foreign language 'REQUIRED<br>
>> > NOT to' written this way looks exactly like "NOT REQUIRED to'" (with<br>
>> > this exact casing).<br>
>> ><br>
>> > Could be my bad, but these are guidelines and the cleaner, the better.<br>
>> ><br>
>> > Mario Peshev<br>
>> > Training and Consulting Services @ DevriX<br>
>> > <a href="http://www.linkedin.com/in/mpeshev" target="_blank">http://www.linkedin.com/in/mpeshev</a><br>
>> > <a href="http://devrix.com" target="_blank">http://devrix.com</a><br>
>> > <a href="http://peshev.net/blog" target="_blank">http://peshev.net/blog</a><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > On Thu, Nov 10, 2011 at 5:17 PM, Chip Bennett <<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>><br>
>> > wrote:<br>
>> >> Good morning, Theme developers and reviewers!<br>
>> >> Now is the time to begin discussing and finalizing the changes to the<br>
>> >> Theme<br>
>> >> Review Guidelines pursuant to the release of WordPress 3.3. Please read<br>
>> >> and<br>
>> >> discuss, here:<br>
>> >><br>
>> >> <a href="http://make.wordpress.org/themes/2011/11/10/wordpress-3-3-proposed-guidelines-revisions/" target="_blank">http://make.wordpress.org/themes/2011/11/10/wordpress-3-3-proposed-guidelines-revisions/</a><br>
>> >> Note that, until WordPress 3.3 is released, these proposed revisions<br>
>> >> are a<br>
>> >> work-in-progress. Consider the above link as a "Request For Comment";<br>
>> >> if you<br>
>> >> have anything to add, or disagree with anything proposed, please<br>
>> >> comment<br>
>> >> accordingly. We post these, because we value your input and feedback as<br>
>> >> Theme developers.<br>
>> >> Thanks!<br>
>> >> Chip<br>
>> >> _______________________________________________<br>
>> >> theme-reviewers mailing list<br>
>> >> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
>> >> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
>> >><br>
>> >><br>
>> > _______________________________________________<br>
>> > theme-reviewers mailing list<br>
>> > <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
>> > <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
>> _______________________________________________<br>
>> theme-reviewers mailing list<br>
>> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
>> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
><br>
> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
><br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><b><font size="4">Rick Anderson</font></b><div><b><i>WordPress Trainer/Web Developer</i></b></div><div>
<a href="http://www.byobwebsite.com" target="_blank">www.byobwebsite.com</a></div>
<div>935 Daley Street</div><div>Edmonds, WA 98020</div><div><a href="tel:%28206%29%20801-5209" value="+12068015209" target="_blank">(206) 801-5209</a></div><div>Skype - tailoringtheweb</div><br>
</font></span><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>