Meeting summary for March 18, 2010: Agen…

Meeting summary for March 18, 2010:

Agenda:

  • Menu management feature scope creepscope creep The tendency for requirements to increase during a release's development cycle beyond those originally approved for the upcoming release. Something to be avoided. Also known as feature creep. and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) – Jane – Postponed at Jane’s request
  • Manual vs. automated POT generation for 2010 – Nikolay
  • Link Update checker (https://core.trac.wordpress.org/ticket/12437) – dd32 – Update checker removed
  • Project schedule update – All

Summary:

  • There will be a bot that regularly commits an updated POT file for twentyten.
  • BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. was bumped to the 22nd, because menus needed more time and to allow for SXSW recovery.
  • Jane is doing usability testing on menu management.
  • #12142 (cookie issues related to keys/salts and multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site) was brought up as a good one to handle before beta.
  • A MacOS-related filesystem ticketticket Created for both bug reports and feature development on the bug tracker. (#12637) was also brought up, at which point the dev chat more or less trailed off, and conversations about specific tickets continued.