One of the suggestions which came out of the Governance Sprint Proposal is the formation of a 'Technical Working Group', which would be responsible for setting and maintaining policies around the technical aspects of our community, including things such as the Git repository usage policies, full project approval process, and coding standards.

One role of this group would be to evaluate and sanction proposed policy changes, as a safeguard against policy definition through a single user editing the appropriate drupal.org page.

This issue is intended as a placeholder to log various topics which may need to be discussed by the Technical Working Group, once it is formed. Include here any items which you might suggest the Technical Working Group could look at, either because i) the existing policy is unclear or does not have wide community consensus, ii) the existing policy is somehow broken, or iii) the community could benefit from the establishment of a new policy.

Comments

jthorson’s picture

Based on discussion in IRC tonight, it appears that there is a fair bit of confusion regarding the existence (or non-existence) of a policy recommending when one should use db_query() versus db_select(). A policy discussion issue has been opened at #1881146: [policy] Decide when to use db_select() and when db_query() (or the appropriate connection commands) for this particular item.

xjm’s picture

In the case of #1, there is disagreement between the component maintainers on the point. Another individual edited the handbook page at http://drupal.org/node/310072 contracting one of the component maintainers. I reverted that and added a link to the policy issue instead.

For coding standards, we create core issues and then update the handbook pages when the core issues have consensus. (E.g., http://drupal.org/node/1354 uses a restricted input format. http://drupal.org/node/310072 is mostly documentation with just one line regarding the best practice recommendation, so it is not.)

Dave Reid’s picture

@xjm: Your most recent fix/change on that page has yet again been reverted: http://drupal.org/node/310072/revisions

Gábor Hojtsy’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Closing as outdated. This queue and specifically this issue especially is not used by the technical working group anymore.