[wp-meta] [Making WordPress.org] #4159: Short echo tag ("<?=") tag must be allowed for use in templates

[Making WordPress.org]

#4159: Short echo tag ("<?=") tag must be allowed for use in templates
-------------------------------------+-----------------------
 Reporter:  KestutisIT               |       Owner:  (none)
     Type:  defect                   |      Status:  reopened
 Priority:  normal                   |   Milestone:
Component:  Handbooks                |  Resolution:
 Keywords:  needs-codex 2nd-opinion  |
-------------------------------------+-----------------------
Changes (by KestutisIT):

 * keywords:  needs-codex => needs-codex 2nd-opinion
 * status:  closed => reopened
 * resolution:  invalid =>


Comment:

 @Otto42 , I understand that you are many years commiter here, but for
 other people you can give more support/help. I took **A LOT** of time to
 create this ticket and write it's content, as well as I did read the
 manual about meta trac and core track, and I did not found any better
 place to fit this request. I don't use chat apps, and it is hard for me to
 be on **scheduled time**.

 So you say:
 >> " on the relevant make blogs "
 Which blogs exactly. There is no blog for coding standards. The is posts
 that are couple years old, will anybody read the 'comment' out there?

 I also check the **core trac** - it allows me to add a tag on 'coding-
 standards' but that place is for report of some kind of WordPress feature
 that is not compliant to given standard, it is not about issues that are
 in between PHP.net, where Rasmus endorses something, and W.org, where the
 coding standards page was last updated probably before PHP 5.4.0 release
 date, and that's why that scope is outdated.

 I don't mind that you would close the ticket once again, but please the
 clearly give me a link of exact place where should I create this exact
 ticket with **ALL** the resolution described with all these steps.

 Thank you.

 P.S. Just feeling a bit depressed after putting so much effort to suggest
 something, when that gots rejected by 1 sentence without any links or so.

 P.P.S. I've added "2nd Opinion" keyword, if you don't mind, as I
 personally don't see a place where would the ticket about issues with
 coding standards would fit perfectly, what would sum up to solution, that
 you may need to be more flexible and allow this ticket to be in a place,
 where it is closest for that task (but may not be a perfect fit for it).

 Replying to [comment:2 Otto42]:
 > This is the meta.trac, where we track tickets related to changes on
 WordPress.org or other properties. We don't determine the standards used
 here.
 >
 > Core standards and such should be discussed on the relevant make blogs
 or in team chats.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4159#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org