Dev Chat Summary, October 29th

https://wordpress.slack.com/archives/core/p1414613658002331

Misses

  • 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. 1
  • Feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. merge window

Decisions

  • Beta 1 will happen next Wednesday.
  • One of the betas will be dropped to offset the beta 1 delay.
  • Select 2 will be punted to 4.2 due to touch problems and upstream rewrite concerns.
  • There will be an accessibility bug scrub on Friday. https://make.wordpress.org/accessibility/2014/09/17/wordpress-accessibility-ticket-priorities-for-4-1-early/

Assignments

  • @markjaquith and @avryl will make a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. to merge Focus.
  • @johnbillion will make a patch to merge Session Manager.

Links Mentioned

https://make.wordpress.org/core/version-4-1-project-schedule/
https://make.wordpress.org/core/2014/10/28/wordcamp-san-fransisco-user-testing-results/
https://github.com/johnbillion/wp-session-manager/pull/14
https://core.trac.wordpress.org/ticket/22229
https://core.trac.wordpress.org/ticket/25277
https://github.com/ivaynberg/select2/issues/1541
https://github.com/helenhousandi/wp-19867-9864/issues/11
https://github.com/ivaynberg/select2/milestones
https://github.com/helenhousandi/wp-19867-9864/
https://make.wordpress.org/core/2014/10/28/twenty-fifteen-chat-summary-october-28/
https://make.wordpress.org/accessibility/2014/09/17/wordpress-accessibility-ticket-priorities-for-4-1-early/
https://make.wordpress.org/core/

Focus 2

mark
I think Focus v2 is ready to be turned into a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. patch and be merged in. Over the last few days we have been working on making it less “twitchy” and narrowing the circumstances under which focus mode is triggered, so we are sure the user is focused on composition when it happens, instead of transiently moving through the editor or absentmindedly clicking.

Session Manager

nacin
I think the session manager is ready with some minor UIUI User interface tweaks (simplifications, really) and use of the geo IP APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways..

johnbillion
Yes the session management UI is in a similar position

johnbillion
I’m hoping to get that in patch form and ready to merge before the weekend

Select 2

johnbillion
@helen @ericlewis Do you have time to look into the touch problems before Friday? I am very tempted to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) this if we can’t get this merged by early next week, and highly visible touch support problems will prevent it being merged

johnbillion
I think we can circle back Friday during the bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub and make a decision

helen
i am having bad gut feelings myself.

jorbin
I think the work @helen and @ericlewis have done is great, but there are too many unknowns (edited)

rzen
I side with withholding it for just one release. The benefits of waiting (potentially better codebase, more room to test 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), etc) far outweigh the benefits of including now (almost certain rewrites in the very near future, for one)

eric
I’d say cut it. It’s a minor improvement, not a make-or-break feature.

nacin
And with so many other things about to come in, it’s pulling resources in different directions a bit.

helen
“just one release” – i’ve been tinkering with this since february.

rzen
Fair point, very fair point

helen
but i am not worried about cutting it for 4.1. it is frustrating, but not worrisome.

johnbillion
Ok unless the situation with touch support changes in the next few days, we should consider this punted. I have also just been informed that there is a licensing issue which I was unaware of

Twenty Fifteen

johnbillion
Twenty Fifteen is steaming ahead

johnbillion
@obenland @lancewillett @iamtakashi Anything of particular note you’d like to mention?

iandstewart
It’s looking good

iandstewart
@celloexpressions just did a great review

iandstewart
and doubled our ticketticket Created for both bug reports and feature development on the bug tracker. numbers :simple_smile:

celloexpressions
Well, that was just as much as I could do in an hour :simple_smile: but it’s pretty good overall, no huge issues. I’m still thinking about the color schemes implementation

iandstewart
Not much to report on beyond the update here https://make.wordpress.org/core/2014/10/28/twenty-fifteen-chat-summary-october-28/
Make WordPress Core
Twenty Fifteen Chat Summary October 28
Notes for our weekly chat about Twenty Fifteen: Twenty Fifteen continues to feel pretty robust — thanks to everyone who’s been testing the theme, reporting bugs, and contributing to patches with co…

obenland
We had some new template tags land yesterday, I started a ticket for the new `title-tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)` support and will publish a post on that later today

obenland
Also working on adding support for the navigational template tags

PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and Theme Install

johnbillion
Lastly from me, the proposed updates to the plugin and theme install and update process haven’t had much traction lately, as I’ve already noted, due to @nacin @melchoyce @pento @avryl being busy on other things, but we have mockups and that group are going to plow through it starting this afternoon

johnbillion
So that is still scheduled for 4.1

Feature Plugins

boren
Feature plugins need to be in the beta list. Only one of those discussed here is listed, Focus. /wp-adminadmin (and super admin)/plugin-install.php?tab=beta

nacin
@boren: Roger.

boren
Does that page have a .org analog?

nacin
Negative.

#dev-chat, #meeting-notes