Author Archives: Konstantin Obenland

Konstantin Obenland 3:45 am on February 27, 2018
Tags: ,   

X-post: Two Factor Authentication on WP.org

X-post from +make.wordpress.org/meta: Two Factor Authentication on WP.org

Konstantin Obenland 10:15 pm on June 12, 2016
Tags: ,   

Shiny Updates Update 6/12

Three more pull requests were opened, 1) to add basic validation of ajax requests, 2) to swap the term Core with WordPress in updates-coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and 3) to only show the compatibility note in upgrade-core if an update is not 100% compatible.
The PR to add the ability to activate a Theme after installation was merged and the feature added.

#4-6, #shiny-updates

Konstantin Obenland 4:34 am on June 12, 2016
Tags: ,   

Shiny Updates Update 6/11

Both were requested in the design review.

#4-6, #shiny-updates

Konstantin Obenland 2:03 am on June 11, 2016
Tags: ,   

Shiny Updates Update 6/10

  • There was more discussion on the design review post.
  • @mapk had a discussion with other designers to get a better grasp of the reasons behind the design meeting‘s outcome of recommending to not merge update-core.php changes.
  • @mapk created a survey to determine the severityseverity The seriousness of the ticket in the eyes of the reporter. Generally, severity is a judgment of how bad a bug is, while priority is its relationship to other bugs. of points mentioned in the design feedback.

#4-6, #shiny-updates

Konstantin Obenland 5:14 pm on June 9, 2016
Tags: ,   

Shiny Updates Update 6/9

We’ll be posting daily updates until the approval meeting on Monday.

#4-6, #shiny-updates

Konstantin Obenland 8:06 pm on June 1, 2016
Tags: , ,   

This is a summary of the shiny updates…

This is a summary of the shiny updates chat from May 31. (Slack log)

Attendees: @ocean90, @swissspidy, @mapk, @afragen, @screamingdev, @ipstenu, @obenland

Topics:

  • Merge plan
    @swissspidy will have a merge proposal ready for review and publish on 6/2. Friday, 6/3, was set as the deadline for code changes so that there will be enough time to prepare a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. prior to next weeks Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. meeting.
  • Overall status
    We discussed various options around how to display a notice on update-core.php when there are no updates pending. The issue of dismissible updates was brought up, and whether that could be deprecated. That should be brought before a bigger audience at the next dev chat. Allowing 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 installations from import.php came up as well; we need to find a solution there and make the experience better. We ended with discussing implementation details of various open tickets, that don’t have an effect on the bigger picture

Next meeting is on Tuesday June 7, 20:00 UTC.

#4-6, #shiny-updates, #upgrade-install

Konstantin Obenland 1:06 am on May 27, 2016
Tags: , , ,   

This is a summary of the shiny updates…

This is a summary of the shiny updates chat from May 24. (Slack log)

Attendees: @ocean90, @swissspidy, @mapk, @ryelle, @melchoyce, @adamsilverstein, @obenland

Topics:

  • Open Pull Requests
    • @swissspidy was waiting for feedback and a merge on PR120, which happened right after conclusion of the meeting.
    • @ryelle was waiting for clearance to re-globalize pagenow in order to make more parts of shiny updates testable.
  • Overall status
    We should be at a point where we can write the merge proposal and 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. in the coming week. We have one more week to fix more bugs and get some more user eyes on update-coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and themes. @ocean90 mentioned two core tickets that should be fixed before merge, #13071 and #36914 and asked for review and testing there.

Next meeting is therefore on Tuesday May 31, 20:00 UTC.

#4-6, #meeting, #shiny-updates, #upgrade-install

Konstantin Obenland 7:50 pm on May 17, 2016
Tags: , ,   

Shiny Updates Chat Summary 5/17/16

This is a summary of the shiny updates chat from May 17. (Slack log)

Attendees: @ocean90, @swissspidy, @j-falk, @mapk, @ethitter, @obenland

Topics:

  • Accomplished work since last week
    • Review requests were posted to the 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), Flow, Polyglots, and Design teams.
    • The feature project landing page was written and published.
    • @swissspidy merged update-core.php into master.
    • Lots of 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. fixes and smaller enhancements went in.
  • Activate after install
    We discussed what the best way would be to provide users with the ability to activate a 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 after it was installed. @swissspidy offered to work on a way that would switch the install button to an activation link after the install queue emptied, so it can be user tested for a more informed decision.
  • Update coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
    @swissspidy‘s update-core work was merged into master, where it will remain to receive a broader test coverage than it would in a branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".. All updates (except for ‘update all’ button) work via ajax.
  • Open floor
    We decided on a new meeting time, 20:00 UTC, that is one hour later than before.

Next meeting is therefore on Tuesday May 24, 20:00 UTC.

#4-6, #shiny-updates, #upgrade-install

Konstantin Obenland 8:16 pm on May 11, 2016
Tags: , ,   

Shiny Updates Chat Summary 5/10/16

This is a summary of the shiny updates chat from May 10. (Slack log)

Attendees: @ocean90, @swissspidy, @paaljoachim, @j-falk, @mapk, @obenland

Topics:

  • Accomplished work since last week
  • Remaining work
    The landing page for feature projects still needs to be written, as well as contributor groups asked to review Shiny Updates. @ocean90 opened a few issues that need addressing as well. These things should all be done by the time of the next meeting though.
  • Activate after install
    Shiny Updates introduced a disconnect between installing a 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 then activating it. @mapk offered to solicit more UXUX User experience feedback to address what happens when there are plugin install request in the queue while the user wants to activate a plugin, and how WP signals a successful installation while changing the button action to Activate.
  • Open floor
    …was mostly spent on discussing approaches to update-core.php and inconsistencies between the theme and plugin install UIUI User interface.

Next meeting is on Tuesday May 17, 19:00 UTC.

#4-6, #shiny-updates, #upgrade-install

Konstantin Obenland 7:43 pm on May 4, 2016
Tags: , ,   

Shiny Updates Chat Summary 5/3/16

This is a summary of the shiny updates chat from May 3. (Slack log)

Attendees: @ocean90, @swissspidy, @ethitter, @adamsilverstein, @mapk, @obenland

Topics:

  • Accomplished work since last week
  • Remaining work
    @obenland will work on the Shiny Updates landing page for feature projects and fix a 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. that were discovered during the most recent user test. @mapk offered to conduct another user test focused on the new interactions with some learnings from the previous one. Goal is to identify any hiccups or behaviors that are unexpected to users. @swissspidy wants to continue working on update-core.php and see if we can get it into shape for 4.6.
  • Most recent user tests
    We briefly talked about the most recent user test (linked above). It showed a variety of bugs that @obenland initially assumed were based on being in subviews of the 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 list. After the meeting it turned out that the test site ran an outdated version of WordPress that didn’t include some of the date that Shiny Update needs to work. It was a good demonstration of progressive enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. here though, as all actions still worked, they just weren’t shiny. More user tests to come, to make sure that users agree with the new interactions.
  • Schedule for 4.6 inclusion
    Next up is writing the merge proposal that was requested to be published around 6/1, definitely before 6/8.

Next meeting is on Tuesday May 10, 19:00 UTC.

#4-6, #shiny-updates, #upgrade-install